Incorrect/different sensor size on QHY-600M

[archer1960]

BTW, I'll be glad to beta test it for you if needed.

[archer1960]

I just noticed that you now have a option in the camera setup tab of Settings to attempt to disable the overscan area on QHY cameras. I am testing that out, but turning it off doesn't seem to do anything; I still get the smaller images whether that option is checked or not. Is there something special I need to do to activate it beyond disconnecting and reconnecting the camera? My camera is a QHY-600M, and the overscan enable/disable works when I use the QHY native setup dialog, so I know the camera has that ability.

[admin]

Hi,

if it was going to work then re-opening the camera should be sufficient - the old code would always request that the overscan be ignored if the camera claimed to support that functionality, while the new code will only request it to be ignored if the camera supports it *and* that option has been set.

The trouble is that I don't have any cameras that support this functionality to test with, so all I can do is write the code and hope... I wonder if I should change things so that the code explicitly sets 'ignore overscan' to off if the camera claims to support the overscan disable and the option is unticked?

cheers,

Robin

[archer1960]

Maybe something in the chain from SharpCap to the camera is remembering previous settings and applying them, so an explicit command to change the setting in either direction might make sense.

[admin]

Hi,

I think most likely there is a default value in the SDK that is perhaps 'ignore', so when SharpCap sends the 'please ignore' request it stays on ignore, and when it sends no request it is also on ignore. I'm going to add code to explicitly set 'do not ignore' to the next update - that should be a safe change as it will only come into effect for users who have changed the default value of that setting.

When you do get the next update, it will be worth seeing if it helps (and also check the log to see if there are messages about overscan when opening the camera - they will confirm that the right code path is running).

cheers,

Robin

[archer1960]

Thanks; I'll let you know what I find.

[archer1960]

BTW, do you handle the case where one of the QHY cameras supports the overscan area and the other does not? I have a QHY-168C and a -600M, and they might be different...

[admin]

Hi,

yes, it should handle that - when the camera is opened it will ask the camera if it supports overscan, and only send any config related to it if it does support it. Of course, that relies on the SDK giving the correct status for the overscan support when asked - we will see from what is in the log if that is correct or not

cheers,

Robin

[archer1960]

Here is the log from a test run with my QHY-600M this morning; I had the Ignore Overscan checkbox UNchecked.

[admin]

Hi,

this is interesting, locating the bits relevant to overscan in the log, we have...

Code: Select all

Info   	09:24:43.421745	#1 	CAM_IGNOREOVERSCAN_INTERFACE implemented : False	
...
Info   	09:24:45.060183	#1 	QHY camera does not support overscan ignore functionality	
Info   	09:24:45.062472	#1 	Overscan area is {Width=0, Height=0}
...
Info   	09:25:00.177216	#26	Opening QHY Camera QHY600M-676faa4d854c4a683, result was 2303522425520													in void SharpCap.Cameras.QHY.QHYSDK+Camera.Open()
Info   	09:25:02.250504	#26	Set read mode, now setting stream mode to False																			in void SharpCap.Cameras.QHY.QHYCameraProxy.SetupGrabThread()
Info   	09:25:04.324339	#26	Asking QHY camera to ignore overscan area																				in void SharpCap.Cameras.QHY.ResolutionPropertyControl.SetEffectiveSize()
Info   	09:25:04.324519	#26	Effective area is {X=24,Y=34,Width=9576,Height=6388}

So, initially the camera reports that it doesn't support overscan, and SharpCap doesn't try to set anything related to overscan because of that, but then later it looks like you change mode from video mode to still mode (setting 'stream mode to false' in QHY terms), and then the camera must report that it does support overscan, since we see the message about asking the camera to ignore overscan, so there is something interesting to think about.

I can also see from the log that you are still using an older version (4.1.14120) which doesn't try to turn the overscan ignore off - please give this a try with the very latest 4.1.14155 and see if anything changes.

cheers,

Robin