I was having a play with the new .335 build trying this & trying that. I then came across a problem which appeared to freeze SGP completely requiring Windows task manager to shut down the App.
Before going any further I am fully aware it was my fault and not SGP’s but as a result of my own error SGP seemed to freeze solid with no way to escape the situation.
I connected the equipment ‘simulator’ from the Focuser drop down box, set the bits and pieces and connected (also had the Camera simulator V2 connected also). Cutting a longer story short, ensure the focus position is at Zero (this was my accidental mistake) and hit ‘Run’ on the ‘Focus Control’ module.
Initially the focus display box does not appear which was not normal to start with, after a delay it eventually did and it looked like this and stayed like this:
This image with ‘Wait…’ in the middle button was after attempting to cancel the operation and it stayed like this forever until a forced stop of the application was executed.
In the Log it showed the following as a quick snippet:
[11/02/19 09:49:36.543][DEBUG] [Camera Thread] Auto focus: setting filter None
[11/02/19 09:49:36.547][DEBUG] [Camera Thread] Auto focus running…
[11/02/19 09:49:36.550][DEBUG] [Camera Thread] Turning temp comp off…
[11/02/19 09:49:36.556][DEBUG] [Camera Thread] Performing Sequence Generator auto focus using Half Flux Radius. AFID: 0
[11/02/19 09:49:36.561][DEBUG] [AfChartThread] Showing AF chart dialog…
[11/02/19 09:49:36.561][DEBUG] [Camera Thread] Error in auto focus! Current focuser position does not support required range (currently at 0 and needs to move inward by 120).
[11/02/19 09:49:36.581][DEBUG] [Camera Thread] Set temp comp baseline marker -> Temp: 18.825 …
[11/02/19 09:49:36.581][DEBUG] [Camera Thread] Auto focus complete…
[11/02/19 09:49:36.586][DEBUG] [Camera Thread] SGM_FOCUSER_AUTO_FOCUS complete…
No point in attaching the whole log as the cause is obvious (this is where I realized I had the focuser still at zero and SGP was trying to move it ‘IN’ by 120 steps)
The main issue here is that this accidental situation left SGP in an unresponsive state with no way to regain control except for a forced stop…Not Good !
I also reloaded .330 in case it was an issue introduced in build .335 and it does the same there so this is a common situation/exception which could catch anyone out.
Maybe when the Auto Focus procedure starts SGP could check the position of the focuser and if it’s ‘initial move’ can not be done (like in this situation) it can stop the whole process and put up a general message box telling the user what the problem is ? ? ?