When I run Frame and Focus in continuous mode fo ra ZWO ASI 1600MM pro camera with 2x2 binning running exposures 3 seconds or less, SGP will unexpectedly crash with no errors or warnings (it vanishes). I notice that the CPU usage is about 38% when in this mode. Simultaneously, I have PD2 running (2 sec exposure time), Celestron’s CPWI ASCOM driver and application, StellariumScope and Stellarium. Total CPU time is < 80% (Stellarium uses about 15% CPU).
The other thing that happens is that when I have SGP F&F exposures at 1 or 2 seconds, CPWI will occasionally time out and disconnect from the mount (connected through hand controller via a USB hub port) All cameras, focuser, etc. also connect via the USB 2/3 hub.
If I connect the ASI 1600 camera to SharpCap Pro 3.2 instead of SGP, everything runs without any problems. SharpCap with exposure times of 1/2 or 1 second only take about 8 to 8.5% CPU time, and CPWI never times out.
So, Frame and Focus with short exposures is eating a significant amount of CPU resources and the busy traffic is causing some kind of fatal error. Note that I am not running a sequence or doing anything in SGP other than F&F. I am not saving images or doing an HFR. I have a locked stretch in the image. All gear is connected and the only things active are the mount/CPWI, the ASI1600 and ASI174 guide cam (in PHD2 - not guiding).
Lenovo Thinkpad 11e with latest Windows 10
Celestron CPWI V2.2.3 (latest production)
Latest ZWO ASCOM and direct drivers
Pegasus Astro FocusCube2 with latest ASCOM driver