I’m using 126.96.36.199 and I had an initial problem where it was averaging a bad temperature from the focuser, hence I was getting a lot of autofocus runs. A new driver for the focuser was released about a month ago (USBfocus) that actually addressed this issue and that seemed to fix the problem, but another cropped up…
On two nights, I had a problem where SGPro would “lockup” during an autofocus run. This was due to the focuser’s ASCOM driver throwing an exception when it was told to move. I’ve sent the relative part of the ASCOM log and the SGPro log bits from around the time of the fault to USB focus and they said, it is still a beta driver and there are still some problems with it, so I’ll fall back to the older one.
However, what concerns me is that SGPro kept in the autofocus loop for over three hours waiting for something and my scope was staring at my house at sunrise still trying to autofocus. Fortunately the lockup occurred after the meridian flip or it could have been interesting. I know that if the filter wheel does not change in a certain amount of time, SGPro will abort and run the end of sequence, parking the mount, etc, but does it have the same fallback for focuser problems? In the morning, I stopped the autofocus run and SGPro hung up and I had to use the task manager to kill it.
What this post is about is I know there is a problem with the ASCOM driver for the focuser which is not an SGPro issue, but if SGPro gracefully aborts the run if the focuser causes problems such as when there is problem with the filter wheel. In some cases, just a simple disconnect/reconnect clears it,but if I have to kill SGPro from the task manager or it hangs in the autofocus loop until I kill the system, then I’ll lose quite a bit of sleep.
Attached are the logs:
The problem occurred around 08:38