Recently encountered a new issue w/ SGP 184.108.40.206 and my AP Mach1-GTO w/ CP4.
After a session completes, and SGP parks the mount, the mount goes to its park position, reports parked, but then suddenly reports “unparked” but not tracking.
Saw a post in the AP GTO group about an identical issue, and the explanation given there was that this was due to this change in SGP 220.127.116.11 :
Any park command issued through SGPro will now be followed by a stop tracking command.
The issue appears to be, according to Ray Gralak
Immediately after the park had completed, it looks like SGPro (or some other ASCOM application) read that the park completed but then sent an ASCOM command to disable tracking. Part of disabling tracking is to stop any slews in progress, which requires sending a “Q” command. Unfortunately the “Q” command does double duty in that it will unpark the mount.
From Howard in the AP-GTO group :
Quit does NOT mean “quit tracking.” It stops slews and directional moves (button moves). It also terminates a parked state or a stall condition.
While I understand the “safety/sanity check” nature of forcing tracking to stop after parking, it seems that for any well-behaved mount a parked state is by definition not tracking.
Could we, then, perhaps have this feature/sanity check implemented as an option when this version gets released?