If anyone still cares about this - I think I understand the problem of ASIAir/INDI not being able to do pulse guiding with the SS2K.
I have an SS2K with 2.10 EPROMS. Everything works perfectly using the most recent ASCOM driver for SS2K going through the ASCOM Device Hub to get around the 32 vs 64 bit issue. I'm running Windows 11 and NINA and everything works perfectly - Goto, plate solving, guide calibration and guiding (NOT using an ST4 cable).
However, my experience with the ASIAir Plus is the same as many others have documented: goto and plate solving work fine. Manual movements from the ASIAir work fine. But calibration and guiding to not move the scope at all.
I was also able to reproduce this problem using EKOS on my MacBook which uses the SS2K INDI driver (as the ASIAir apparently does also). So, I looked at the serial logs from both my Windows ASCOM setup that works, and my MacBook INDI setup that doesn't work.
The SS2K INDI driver uses the Meade pulse guide commands ":MGdnnnn" where d is the direction (n, s, e, w) and nnnn is the duration in ms. According to the documentation I've seen, the SS2K does NOT support this command.
The ASCOM driver, on the other hand, uses a series of commands to emulate pulse guiding:
:RG to set the movement rate to Guide
:Md where d is the direction (n, s, e, or w) to start the mount moving
then after a delay of however many ms it was supposed to do a pulse guide, it issues:
:Qd to stop movement in the d direction.
Of course the SS2K implements all of these commands.
If someone can modify the INDI SS2K driver to do this and IF ZWO will incorporate those changes, we can fully use ASIAir to control our SS2Ks. This assumes that the INDI framework has a mechanism like ASCOM to set a timer for nnnn ms so that the :Qd command will be issued at the correct time.
