Stellarium

LX200 sync command (CM) - undocumented expected answer?

Asked by Stefan Jahn

Dear Stellarium team,

I found in the source code of the LX200 telescope drivers, that Stellarium is expecting a 0/1/2 answer from the telescope
after the :CM# command. I am wondering if this actually works in a real LX200 scope? I am about to emulate such an interface
using a selfmade goto-mount. And I am looking into documentation like:
1) http://www.company7.com/library/meade/LX200CommandSet.pdf OR
2) https://www.ap-i.net/mantis/file_download.php?file_id=1224&type=bug
In both documents it is written that after a :CM# command a quasi-random <string># answer would be allowed/expected.
Is there a specific reason why you expect the 0/1/2 answers similar to the :MS# command?
Which other document describes it otherwise correctly?

Thank you in advance
Stefan.

Question information

Language:
English Edit question
Status:
Answered
For:
Stellarium Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
gzotti (georg-zotti) said : 		#1

The commit message from 2019 says "attempt to add support of SYNC command..." but it seems to be code adapted from 2010.
If our solution does not work and you can fix it to make it work, please send a "pull request". Note that Stellarium development has moved to github in 2017.

If you have a physical LX200: we need somebody to fix current issues with the Qt6 update in the TelescopeControl plugin. Also ASCOM support seems problematic. We just don't have the hardware (and also time) to test anything. Stellarium stays alive with fixes from its users!

Can you help with this problem?

Provide an answer of your own, or ask Stefan Jahn for more information if necessary.

To post a message you must log in.