×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

indi_lx200_OnStep driver or OnStep firmware ACK problem

  • Posts: 294
  • Thank you received: 54
It seems there is a ACK handshake problem between the indi_lx200_OnStep driver version 1.3 and the OnStep firmware 1.8s under Ubuntu 18.04 LTS. Things work OK under Ubuntu 16.04 LTS.

My configuration: ODROID XU4Q, Ubuntu Mate 18.04 LTS, MiniPCB OnStep with 1.8s firmware.

OnStep won't ACK (special command 0x06) with indi unless I send a command to the controller (e.g. ":GVN#") from a serial communications app such as 'cutecom'. Once I do that, the ACK between OnStep and indi will happen and things will work. I looked at the code from both lx200_driver.cpp (indi) and command.ino (OnStep) but could not see anything obvious.

I am attaching the indi log file below for info. I will also submit to the indilib group.

Any help will be appreciated. Thanks.

Log file:

INFO 24.572425 sec : Session log file /home/gilles/.indi/logs/2018-11-10/indi_lx200_OnStep/indi_lx200_OnStep_17:29:03.log

DEBUG 30.811541 sec : Connecting to /dev/OnStep

DEBUG 30.812563 sec : Port FD 8

DEBUG 30.812632 sec : Connection successful, attempting handshake...

DEBUG 30.812684 sec : Testing telescope connection using ACK...

DEBUG 40.917488 sec : Failure. Telescope is not responding to ACK!

DEBUG 40.917599 sec : Handshake failed.


********* This is when I sent a command to the OnStep controller with 'cutecom'


DEBUG 130.431524 sec : Connecting to /dev/OnStep

DEBUG 130.431833 sec : Port FD 9

DEBUG 130.431900 sec : Connection successful, attempting handshake...

DEBUG 130.431964 sec : Testing telescope connection using ACK...

DEBUG 130.436976 sec : Testing successful!

INFO 130.437053 sec : LX200 OnStep is online.

DEBUG 130.439580 sec : Configuration successfully saved for DEVICE_PORT.

DEBUG 130.442179 sec : Configuration successfully saved for DEVICE_BAUD_RATE.

DEBUG 130.445073 sec : Configuration successfully saved for CONNECTION_MODE.

DEBUG 130.467094 sec : Site Name <Test>

DEBUG 130.482126 sec : Mount Controller Latitude: 0 Longitude: -0

DEBUG 130.497170 sec : Mount controller UTC Time: 2018-11-09T22:15:29

DEBUG 130.497281 sec : Mount controller UTC Offset: -5.00

INFO 130.517644 sec : Mount is unparked.

DEBUG 130.518061 sec : InitPark Axis1 0 Axis2 0

INFO 130.518150 sec : =============== Parkdata loaded

INFO 130.528279 sec : Mount is unparked.

DEBUG 130.528585 sec : InitPark Axis1 0 Axis2 0

INFO 130.540937 sec : Site location updated to Lat 0:00:00 - Long 0:00:00

INFO 130.541724 sec : Debug is disabled.

DEBUG 130.545900 sec : Active Snoop, driver: Dome Simulator, property: DOME_PARK

INFO 130.556936 sec : Site location updated to Lat 0:00:00 - Long 0:00:00

DEBUG 130.558274 sec : Configuration successfully saved for GEOGRAPHIC_COORD.

INFO 130.559079 sec : Pulse guiding is enabled.

DEBUG 130.559420 sec : Configuration successfully loaded.

DEBUG 130.805379 sec : Configuration successfully saved.

INFO 131.461171 sec : Mount is unparked.

INFO 134.147493 sec : LX200 OnStep is offline.
5 years 5 months ago #31498

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

  • Posts: 294
  • Thank you received: 54
As a followup, I was told that this is a Teensy issue that can be circumvented by running a Python script prior to connecting the OnStep controller to indi. So, case closed but I can provide those interested with the information.
5 years 5 months ago #31518

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

Time to create page: 0.184 seconds