Hi ZWO team,
I am validating an AM5N on firmware 1.8.8 and seeing that PulseGuide appears nonfunctional via the documented serial protocol. I would like confirmation on intended behavior and any missing prerequisites.
Environment
Mount: AM5N
Firmware:1.8.8
Driver: Shows 6.5.24.0 even though I downloaded the v6.5.35
Connection: direct serial over USB (device tty.usbmodem1234561)
Protocol docs referenced: ZWO AM mount serial protocol (v2.1/final)
Conformance tool: ASCOM ConformU 4.2.1 (Windows)
Observed behavior
:Mgdnnnn# returns 1 (OK) but no RA/Dec movement is observed.
:GU# never reports T/t guiding flags during :Mgd.
Manual move commands do move the mount (e.g., :RC# then :Me#/:Mw#/:Mn#/:Ms#).
Guide rate commands :Rg0.nn# and :Ggr# respond, but do not change :Mgd effectiveness.
Questions
Is :Mgdnnnn# supported on AM5N firmware 1.8.8? If not, what firmware version added support?
Are there prerequisites for :Mgd to work (tracking on, unparked, specific mode, “guide mode”, or alignment state)?
What is the expected behavior of :GU# during pulse guiding? Should it show T/t? Is there a different status command?
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.)
Does AM5N require an alternate command for pulse guide (non-:Mgd), or a different command set for LX200 compatibility?
Can you provide a minimal command sequence for a successful RA/Dec pulse guide on AM5N?
References
Protocol docs I am using (from Indigo/ZWO):
https://github.com/indigo-astronomy/indigo/tree/master/indigo_drivers/mount_asi/docs
ConformU:
https://github.com/ASCOMInitiative/ConformU/releases/tag/v4.2.1
I have attached the ConformU report which has 52 Issues and 27 timing problems.