ASI1600MM-Cool, Lightd look like bias frames

stevenwissler

I have a new 1600MM-Cool, controlled through Nebulosity 4 on a Windows 10 laptop. I'm getting a large percentage (47%) of my light frames coming through looking like bias frames. The dn of the pixels is around 200. These are 60-120 second exposures at Gain-76, Offset=13 and temp=-18C

It looks like the sensor is getting flushed prior to the readout? Any ideas what might cause this? Has anyone else seen this behavior?

Steve

Sam@ZWO

please use our latest ASCOM driver instead of native support

Nebulosity didnot update to our latest SDK

stevenwissler

I'll double check which driver I was using, my recollection is that only one of them worked at all. Does the driver control the timing of the radout and flush? Not sure how the driver would cause this problem...

Sam@ZWO

StevenWissler wrote:
I'll double check which driver I was using, my recollection is that only one of them worked at all. Does the driver control the timing of the radout and flush? Not sure how the driver would cause this problem...

the ASCOM driver or native support control everything

you can use the ASCOM driver or push Craig for a new version of Nebulosity

stevenwissler

I updated to the latest drivers and ran some more tests. The issue with having ~45% of the light frames having no signal seems to be gone ( one test run ). I have been using the native driver, as I'm having issues controlling the TEC with the ASCOM driver. I turn the TEC power on through Nebulosity with the ASCOM driver and it immediately turns off. This works fine with the native driver. With the native driver, Nebulosity 4 hangs when exiting frame and focus mode. I've posted this to the Nebulsoity Users group...

Sam@ZWO

StevenWissler wrote:
I updated to the latest drivers and ran some more tests. The issue with having ~45% of the light frames having no signal seems to be gone ( one test run ). I have been using the native driver, as I'm having issues controlling the TEC with the ASCOM driver. I turn the TEC power on through Nebulosity with the ASCOM driver and it immediately turns off. This works fine with the native driver. With the native driver, Nebulosity 4 hangs when exiting frame and focus mode. I've posted this to the Nebulsoity Users group...

that's good news!

stevenwissler

Problem solved. There is an "Advanced Camera Control" dialog in Nebulosity when using the ASCOMM drive. If you don't check the Enable TEC Control button, then the TEC control in the main Nebulosity control panel doesn't work, it just appears to turn the TEC off right away, no warning message that says" Hey dummy, enable TEC control..." ;)