It’s hard to tell, but my initial guess is a possible incompatibility with the ASCOM driver and USB 3.0. We might be able to provide more details if you are able to also provide the Altair ASCOM logs.
Do any of Altair Capture, Firecapture or Sharpcap use ASCOM or do they use native drivers?
Here are the related Altair log files. I can see from the failed sequence what appears to be the relevant issue. I suspect that the developer of the Altair ASCOM driver needs to amend the driver however could you confirm this is the case and what the main issue seems to be?
Neither log fragment seems to indicate a driver problem. Optional properties are generating errors. The FAIL log shows an error with GetLastExposureStartTime because no exposure has been done, nothing wrong with that.
However log fragments can be very misleading it’s always worth providing full log files.
Thanks for the logs. According to SGPro your image should have completed integration on the camera at:
[03/11/17 19:11:27.164]
At this point SGPro started polling the camera to ask if the image was ready for download. This continues for 480 seconds and the camera never reports that it has made the image data ready for download. Looking at the camera logs, this is returned throughout the polling period:
Bottom line is that we cannot speak to any reason why the camera was in this state.
BTW, not super important, but the fact that Altair logs the name of the SGPro threads from which calls were invoked makes troubleshooting WAY easier. I wish all logs posted thread names.