×

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

Bi-monthly release with minor bug fixes and improvements

indi_celestron_gps - Failed to read RA/DEC values

  • Posts: 12
  • Thank you received: 2
I get this "Failed to read RA/DEC values" error when connecting using KStars to my Celestron AVX mount. I'm running Ubuntu (wily) on a RPi2. Has anyone else experienced this, and/or is this a know issue? Below is the debug log from the session, and software versions are at the end. Any help would be appreciated.

INFO 64.505017 sec : Session log file /tmp/indi_celestron_gps_2016-04-08T18:56:29.log
DEBUG 74.697636 sec : Toggle Debug Level -- Scope Verbose
DEBUG 75.502239 sec : Toggle Logging Level -- Scope Verbose
DEBUG 91.053220 sec : Initializing Celestron using Kx CMD...
DEBUG 91.336533 sec : RES (x#)
INFO 91.336769 sec : Telescope is online.
DEBUG 91.336949 sec : Getting controller version...
DEBUG 91.337010 sec : CMD (V)
DEBUG 91.341731 sec : RES (05 1C 23)
DEBUG 91.341976 sec : Getting controller model...
DEBUG 91.342043 sec : CMD (m)
DEBUG 91.364547 sec : RES (14 23)
WARNING 91.364775 sec : Unrecognized model (20).
DEBUG 91.364844 sec : Getting GPS firmware version...
DEBUG 91.364905 sec : CMD (50 01 10 FE 00 00 00 02)
DEBUG 91.397612 sec : RES (07 0B 23)
DEBUG 91.397896 sec : Getting RA firmware version...
DEBUG 91.397975 sec : CMD (50 01 10 FE 00 00 00 02)
DEBUG 91.430259 sec : RES (07 0B 23)
DEBUG 91.430497 sec : Getting DE firmware version...
DEBUG 91.430568 sec : CMD (50 01 11 FE 00 00 00 02)
DEBUG 91.463149 sec : RES (07 0B 23)
DEBUG 91.464666 sec : CMD (t)
DEBUG 91.469929 sec : RES (02 23)
INFO 91.473475 sec : Mount is unparked.
DEBUG 91.474998 sec : CMD (h)
ERROR 96.477992 sec : Timeout error
SCOPE 96.483676 sec : CMD (E)
ERROR 101.489036 sec : Timeout error
ERROR 101.494879 sec : Failed to read RA/DEC values.
DEBUG 101.497569 sec : CMD (48 0E 39 11 04 08 10 FC 00)
ERROR 106.503074 sec : Timeout error
DEBUG 106.506371 sec : CMD (57 2B 28 0C 00 4F 16 0C 01)
ERROR 111.511745 sec : Timeout error
SCOPE 111.516666 sec : CMD (E)
ERROR 116.522010 sec : Timeout error
ERROR 116.524757 sec : Failed to read RA/DEC values.
DEBUG 116.525114 sec : CMD (50 02 11 24 05 00 00 00)
ERROR 121.529589 sec : Timeout error
ERROR 121.532293 sec : Error setting N/S motion direction.
SCOPE 121.532526 sec : CMD (E)
ERROR 126.537806 sec : Timeout error
ERROR 126.540447 sec : Failed to read RA/DEC values.
DEBUG 126.540816 sec : CMD (50 02 11 24 00 00 00 00)
ERROR 131.546136 sec : Timeout error
ERROR 131.550306 sec : Error stopping N/S motion.
SCOPE 131.550621 sec : CMD (E)
ERROR 136.555965 sec : Timeout error
ERROR 136.561048 sec : Failed to read RA/DEC values.
DEBUG 136.561377 sec : CMD (50 02 10 24 05 00 00 00)
ERROR 141.562059 sec : Timeout error
ERROR 141.564623 sec : Error setting W/E motion direction.
SCOPE 141.564842 sec : CMD (E)
ERROR 146.567569 sec : Timeout error
ERROR 146.570015 sec : Failed to read RA/DEC values.
DEBUG 146.570336 sec : CMD (50 02 10 24 00 00 00 00)
ERROR 151.575576 sec : Timeout error
ERROR 151.580193 sec : Error stopping W/E motion.
SCOPE 151.580414 sec : CMD (E)
ERROR 156.585696 sec : Timeout error

I'm running:
INDI Library: 1.2.0
Code $Rev$. Protocol 1.7.

KStars Version 2.5.0
KDE Frameworks 5.15.0
Qt 5.4.2 (built against 5.4.2)
The xcb windowing system
7 years 11 months ago #7635

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

Hmmm it fails on querying date and time, and timeout error continues afterwards. Do you get this behavior every time you connect to your mount?
7 years 11 months ago #7640

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

  • Posts: 12
  • Thank you received: 2
Hi, yes I see the same error each time I connect. Do the errors refer to date/time, or RA/DEC? And once I get these errors, the mount hand control freezes and I have to power cycle the mount to connect again. I do set the date/time in the initialization process when the mount is powered on, then start the connection with KStars.
7 years 11 months ago #7642

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

It seems the timeout happens when querying for time, or just before it. If you have TeamViewer, send me the login detail via a private message and I'll see if I can check the issue.
7 years 11 months ago #7643

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

  • Posts: 12
  • Thank you received: 2
Hummm, I have not used TeamViewer before. Let me check it out and see if I can get it working on the RPi.
7 years 11 months ago #7646

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

  • Posts: 12
  • Thank you received: 2
I have VNC already running which I can set up to pass through my FW, is that good enough?
7 years 11 months ago #7647

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

  • Posts: 12
  • Thank you received: 2
I decided to download the INDI code in an attempt to debug what the underlying issue might be. celestrondriver.cpp appeared to be the code for gathering the mount info and, with the help from a NexStar Communication Protocol doc, I identified the driver commands.

For the first message:
DEBUG	91.342043 sec	: CMD (m)
DEBUG	91.364547 sec	: RES (14 23)
WARNING	91.364775 sec	: Unrecognized model (20).
I added a couple of lines so that my AVX mount (i.e. model 20) would be identified.

For the 2nd message:
DEBUG	91.474998 sec	: CMD (h)
ERROR	96.477992 sec	: Timeout error
the command "h" is to read the time/date from the mount. There didn't appear to be any issues with the code, so I used the UNIX "cu" command to connect to the hand controller's serial port and manually send the command and view the output. However, no matter what I did, the "h" command always timed out and left the hand controller unresponsive. My guess is "h" is no longer a valid command, at least with the version I have (5.28).

The only alternative I could think of was to remove the "h" command call from the code, and use the hard coded simulation values as the returned time/date. Doing this allowed the mount to be controlled, I was able to use the slew buttons to engage the mount motors, as well as choose objects in KStars and have the mount motors engaged to move to them. RA/Dec values were returned, though keep in mind this was only a test in my basement. I'm not sure what effect changing the code this way will have as far as the overall INDI code goes.
7 years 11 months ago #7747

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

Great progress!

I already added the AVX model to the code a few days ago. At any rate, I disabled the "h" command for AVX mounts for now. But I strongly urge you to report this bug to Celestron as well. You can discard your local changes to the code. Tomorrow's PPA should hopefully work on your mount without any modifications.
7 years 11 months ago #7748

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

  • Posts: 12
  • Thank you received: 2
I applied the latest updates from PPA and my mount is responding so looks good.
7 years 11 months ago #7761

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

  • Posts: 12
  • Thank you received: 2
FYI...I opened #PKB-613-80090 with Celestron on Apr 19 about the 'h' command not working. No feedback yet.
7 years 11 months ago #7974

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

Time to create page: 1.398 seconds