I was able to enable debug logging and locate the logs. A few things are still unclear, and looking at some errors in the log it appears like a BAD_PARAM condition is met during the run through the SBIG drivers. The code related to the error seemed to be issued in a call to SBIGUnivDrvCommand() either for CC_READ_SUBTRACT_LINE or CC_READOUT_LINE. Error message was ".. Timeout ..."
The strange part of looking at the logs showed a long time spent in reading the data, right after the polling which was pretty much what's expected given my settings for the test (1s and 1.5s exposure for darks) and 100ms for polling. Later on I changed the polling interval. The log info is a bit confusing, saying that exposure time was 100 and 150 respectively (as if the unit was ... 10ms ...)

I'll try to do a more thorough test and clean the logs to not mix up more events than I need.

Thank you. Please let me know if you find anything to help me decide where to go next with my setup.

Read More...