You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
violent oscillations when guiding is on and sending pulses to the mount that start immediately after guiding starts.
no oscillations are seen in the logs when guiding corrections are turned off.
I've done quite a bit of research and noticed in the logs that the pulse commands are sent as "CMD <:Ms2500#>" (moving south) and likewise for the other directions. But iOptron's protocol (https://www.ioptron.us/ASCOM/RS-232_Command_language2013.pdf) states the commands as ":MsXXXXX#", and the document also states that the length of each number must be exact.
The driver in function LX200ZEQ25::SendPulseCmd formats the command using 4 digits only. This is what is causing the issue, I'm guessing the mount interprets ":Ms2500" as 25k ms instead of 2.5k ms.
I also use Indigo with my gear, the indigo driver formats the command using 5 digits and guiding works like a charm.
The text was updated successfully, but these errors were encountered:
Mount: iOptron iEQ45 (HC 8407)
Driver: lx200zeq25
Observed behaviour:
I've done quite a bit of research and noticed in the logs that the pulse commands are sent as "CMD <:Ms2500#>" (moving south) and likewise for the other directions. But iOptron's protocol (https://www.ioptron.us/ASCOM/RS-232_Command_language2013.pdf) states the commands as ":MsXXXXX#", and the document also states that the length of each number must be exact.
The driver in function LX200ZEQ25::SendPulseCmd formats the command using 4 digits only. This is what is causing the issue, I'm guessing the mount interprets ":Ms2500" as 25k ms instead of 2.5k ms.
I also use Indigo with my gear, the indigo driver formats the command using 5 digits and guiding works like a charm.
The text was updated successfully, but these errors were encountered: