×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Meade LX200 Classic Connects But Doesn't Slew

  • Posts: 6
  • Thank you received: 0
=16.6pxi had the same Problem with a LX200 compatible mount. it did not move.

the driver sends the command ":SdsDD:MM#"
according to the meade original lx200 docs it should be :SdsDD*MM#

see www.meade.com/support/LX200CommandSet.pdf

problem is in
lx200driver.cpp
int setObjectDEC(int fd, double dec)

regards

 
2 years 2 months ago #79906

Please Log in or Create an account to join the conversation.

This could be a regression, please open a bug report here: github.com/indilib/indi/issues
2 years 2 months ago #79907

Please Log in or Create an account to join the conversation.

  • Posts: 6
  • Thank you received: 0
i've opened a bug report.
i am new to indi, great work !
Joerg
2 years 2 months ago #79909

Please Log in or Create an account to join the conversation.

  • Posts: 276
  • Thank you received: 52
There are three :Sds command formats specified in the lx200driver.cpp
case LX200_EQ_LONG_FORMAT:
case LX200_EQ_LONGER_FORMAT:
and
case LX200_EQ_SHORT_FORMAT

The first two use the ":", the SHORT uses the "*"

The driver attempts to determine the format by parsing the response to the :GR# command

The response to thr :GR# is
  :GR# Get Telescope RA
   Returns: HH:MM.T# or HH:MM:SS#
   Depending which precision is set for the telescope

If it gets back a "." in byte 5 it attempts to switch to

U - Precision Toggle
  :U# Toggle between low/hi precision positions
  Low - RA displays and messages HH:MM.T sDD*MM
  High - Dec/Az/El displays and messages HH:MM:SS sDD*MM:SS
  Returns Nothing


It will then re-issue the :GR#
If "." found in byte 5 then sets SHORT
Else sets  LX200_EQ_LONG_FORMAT

If you enable logging with telescope driver debug you should see what the response to the :GR# command is, or execute the commands above manually

Gene
 
2 years 2 months ago #79911

Please Log in or Create an account to join the conversation.

  • Posts: 276
  • Thank you received: 52
Sorry, one question please, what firmware version does you scope have?
The latest was 3.34L I believe.

I had owned a circa 2002 classic , and made changes to the lx200 driver a few years ago and had no issues with scope movement, and the given section has not changed in the driver.

Gene
2 years 2 months ago #79912

Please Log in or Create an account to join the conversation.

  • Posts: 6
  • Thank you received: 0
it is a LX200 10" from the mid 90's, firmware is 3.20 or 3.21 (not sure, had to take a look, next time i use it)
maybe newer firmware is more tolerant.

on the other hand i have never seen an original Meade document where ":" is used as a seperator for this command.
where does this ":" come from?

regards
2 years 2 months ago #79913

Please Log in or Create an account to join the conversation.

  • Posts: 6
  • Thank you received: 0
it is a LX200 10" from the mid 90's, firmware is 3.20 or 3.21 (not sure, had to take a look, next time i use it)
maybe newer firmware is more tolerant.

on the other hand i have never seen an original Meade document where ":" is used as a seperator for this command.
where does this ":" come from?

regards
2 years 2 months ago #79914

Please Log in or Create an account to join the conversation.

  • Posts: 6
  • Thank you received: 0
2 years 2 months ago #79918

Please Log in or Create an account to join the conversation.

  • Posts: 268
  • Thank you received: 72
More than two years ago I reported some defective implementations in the lx200 core driver here . I stumbled upon it writing the driver for the AOK Skywalker mount which is hundred percent lx200-compatible. Nobody seemed to be interested then!

I still think the driver needs an overhaul, as there are other commands with the same flaw. May I have hope to reactivate the discussion with this thread ?
Last edit: 2 years 2 months ago by Toni Schriber.
2 years 2 months ago #79929

Please Log in or Create an account to join the conversation.

  • Posts: 85
  • Thank you received: 40
Yup, ping received :-) See brief followup in that other thread
-- Hans
2 years 2 months ago #79963

Please Log in or Create an account to join the conversation.

  • Posts: 268
  • Thank you received: 72
Thanks for your efforts, Hans!

It's good to realise that INDILib improves more and more!
Two years ago i implemented the correct lx200 command strings inside the 3rdparty driver of Sykwalker. It's very pleasing to see their correct implementation in the lx200 core driver now.

By the way: I'm excited that meanwhile KStars 3.5.7 together with INDIlib 1.9.3  is working rock steady at our observatory.
Last edit: 2 years 2 months ago by Toni Schriber.
2 years 2 months ago #79967

Please Log in or Create an account to join the conversation.

  • Posts: 276
  • Thank you received: 52
For Meade at least, what is documented may not be what is fully supported, there may be other formats..
When made a few changes to the lx200 driver I also captured the communications

INDIlx200->TCP->Linux(SOCAT tcp to serial lx200)
For Autostar and lx200 classic with 3.34L roms
Unfortunately I could not find the pcap with the Sr/Sd to the lx200
Attached are snippets from  Autostar and the lx200 in wireshark pcap.
 

File Attachment:

File Name: Autostar_a...grgd.zip
File Size:1 KB

Autostar
:Sr 01:54:10# - Response "1"
:Sd +29:40:06# - Response "1"
:GR#
06:00:31
:GD#
+44ß55:5 where 'ß' = hex 0xdf

lx200 classic firmware 3.34L
GR#
+18:22:31#
:GD#
-18*50:53#
2 years 2 months ago #79977
Attachments:

Please Log in or Create an account to join the conversation.

Time to create page: 1.098 seconds