I tried to test upcoming C2-46000 camera, which I have in prototype for testing, but when I replaced cxUsb.dll by new one (not officially out in public SDK yet), the SharpCap stopped showing the camera in direct (not ASCOM) list. With the previous cxUsb.dll the camera is in the list, but does not work (that is OK, because is not supported).
Did not you know, what may cause this ? I will also ask camera manufacturer. But nothing changed in the interface of the library.
Moravian Instruments C2-46000
-
admin
- Site Admin
- Posts: 17344
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Moravian Instruments C2-46000
Hi,
there are two possible reasons that could cause it not to show up in the list
1) The 'Enumerate' call on the SDK is not reporting the camera
2) Enumerate is reporting it, but the camera is not opening properly (SharpCap calls Initialize on the camera as part of the detection and sees if that succeeds or not).
If you turn on logging of 'Camera Hardware Communication' in the logging settings, you won't see the Enumerate call, but if that returns the camera then the Initialize call and its parameters/result show show in the log. If there is no Initialize call in the log then Enumerate didn't report the camera.
I suppose one other cause would be if the attempt to list the available cameras causes an error/exception - that would show in the log too.
cheers,
Robin
there are two possible reasons that could cause it not to show up in the list
1) The 'Enumerate' call on the SDK is not reporting the camera
2) Enumerate is reporting it, but the camera is not opening properly (SharpCap calls Initialize on the camera as part of the detection and sees if that succeeds or not).
If you turn on logging of 'Camera Hardware Communication' in the logging settings, you won't see the Enumerate call, but if that returns the camera then the Initialize call and its parameters/result show show in the log. If there is no Initialize call in the log then Enumerate didn't report the camera.
I suppose one other cause would be if the attempt to list the available cameras causes an error/exception - that would show in the log too.
cheers,
Robin
Re: Moravian Instruments C2-46000
Hi,
problem solved, there was an bug in the camera driver. Yesterday the new camera drivers was officially released, and all works properly in SharpCap. So no action needed.
You can put new cxUsb.dll into next release of SharpCap.
https://www.gxccd.com/cat?id=164&lang=409
The camera name si C2-46000 equipped with 4/3" Sony IMX492, 8336 × 5648px. rolling shutter sensor.
Here is the Moon image, captured at prime focus of my 400/1600 newtonian, with ES-HR coma corrector, using SharpCap (over the slower ASCOM, due to error in native support). Stacked with AutoStakkert, 50 best images of 500.
This is NOT MOSAIC
http://hvbo.cz/data/uploads/galerie/sl_ ... -46000.jpg
Martin
problem solved, there was an bug in the camera driver. Yesterday the new camera drivers was officially released, and all works properly in SharpCap. So no action needed.
You can put new cxUsb.dll into next release of SharpCap.
https://www.gxccd.com/cat?id=164&lang=409
The camera name si C2-46000 equipped with 4/3" Sony IMX492, 8336 × 5648px. rolling shutter sensor.
Here is the Moon image, captured at prime focus of my 400/1600 newtonian, with ES-HR coma corrector, using SharpCap (over the slower ASCOM, due to error in native support). Stacked with AutoStakkert, 50 best images of 500.
This is NOT MOSAIC
http://hvbo.cz/data/uploads/galerie/sl_ ... -46000.jpg
Martin
-
admin
- Site Admin
- Posts: 17344
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Moravian Instruments C2-46000
Hi Martin,
thanks for letting me know that this was a driver related fix and for pointing out the latest SDK - I will get that into the next SharpCap update no problem
A very nice moon image there - well done!
Do watch out with the new camera if you have manual control over the conversion gain (LCG/HCG) setting of the camera - the IMX294 and 492 sensors can misbehave if set into HCG mode with the conventional gain set to less than 2.0x - when configured this way, the sensor may not fully saturate, even when over exposed, which is particularly bad if you are trying to capture flats as you can think they are well exposed (the histogram looks fine) when they are not. If the manufacturers are auto-setting the LCG/HCG switch over point based on gain then it should really happen at about a total gain of 9.0x minimum to avoid this problem.
cheers,
Robin
thanks for letting me know that this was a driver related fix and for pointing out the latest SDK - I will get that into the next SharpCap update no problem
A very nice moon image there - well done!
Do watch out with the new camera if you have manual control over the conversion gain (LCG/HCG) setting of the camera - the IMX294 and 492 sensors can misbehave if set into HCG mode with the conventional gain set to less than 2.0x - when configured this way, the sensor may not fully saturate, even when over exposed, which is particularly bad if you are trying to capture flats as you can think they are well exposed (the histogram looks fine) when they are not. If the manufacturers are auto-setting the LCG/HCG switch over point based on gain then it should really happen at about a total gain of 9.0x minimum to avoid this problem.
cheers,
Robin