jtadmin
The :Mgdnnnn# guide command can only be set or executed when the mount is in tracking mode. Guide commands are ignored in any other state.
From the log, we can see that ASCOM first set Tracking to False, which means the mount was no longer in tracking mode:
08:05:03.235 Tracking Write OK False
08:07:45.169 PulseGuide -9.0 North ISSUE
Is :Mgdnnnn# supported on AM5N firmware 1.8.8? If not, what firmware version added support?
Yes, it is supported on AM5N firmware 1.8.8.
Are there prerequisites for :Mgd to work (tracking on, unparked, specific mode, “guide mode”, or alignment state)?
Yes, only in the tracking on state.
What is the expected behavior of :GU# during pulse guiding? Should it show T/t? Is there a different status command?
:GU# has no status for pulse guiding. T/t are for RA/DEC ST4 guiding. Right now no other status command show the pulse guiding.
What is the exact expected unit for :Rg0.nn# and :Ggr# on AM5N? (Docs show 0.10–0.90, older docs mention multiplying by 15.)
:Rg0.nn# accepts a value in the range 0.10–0.90.
This value represents a multiplier of the sidereal tracking speed (15.0 arcseconds per second).
In other words:
Guide Speed = Sidereal Tracking Speed (15.0″/s) × Custom Guide Rate (0.10–0.90)
- :Ggr# simply returns the currently configured guide rate value (0.10–0.90) that was previously set using :Rg0.nn#.
