I do not have anything turned on except Axis1, 2 and 4 as foxuser (3 is rotator)


So it seems it is something with my Standard Operating Procedure. When I restart everything, focuser works but in my process, update datetime update location, goto plate solve, sync with mount(probable culprit) and then focus. I need to do. action per action and focus i between each action to find where exactly issue occurs.

Hi, I can't read the properties of the LX200_OnStep driver outputs. I run the indi_getprop command, but I don't see any properties related to the outputs. I would like to use it to write simple scripts to be started at the beginning of the sessions to switch relays on or off and control part of the instrumentation which I now manage manually with the outputs. For example the switching on or off of the TDM (Telescope Drive Master) every time a fast movement of the mantle is performed or when a meridian flip is performed. Basically the question is: is it possible to control the outputs listed in the last tab of the LX200_OnStep driver with a script? If yes, can you show me some examples?

Hello, why in wifi have this error:

2023-01-29T19:44:55: [WARNING] Communication error on Barometer (:GX9B#), this update aborted, will try again...
2023-01-29T19:42:55: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-01-29T19:35:21: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-01-29T19:31:21: [INFO] Setting Max Slew Rate to 6 (24x)
2023-01-29T19:31:16: [WARNING] Communication error on Humidity (:GX9C#), this update aborted, will try again...
2023-01-29T19:30:29: [INFO] Slewing to RA: 11:33:40 - DEC: 79:44:43
2023-01-29T19:29:57: [INFO] Setting Max Slew Rate to 7 (48x)

Regards.
Ettore.

Nothing response.

Hello, why in wifi have this error:

2023-01-29T19:44:55: [WARNING] Communication error on Barometer (:GX9B#), this update aborted, will try again...
2023-01-29T19:42:55: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-01-29T19:35:21: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-01-29T19:31:21: [INFO] Setting Max Slew Rate to 6 (24x)
2023-01-29T19:31:16: [WARNING] Communication error on Humidity (:GX9C#), this update aborted, will try again...
2023-01-29T19:30:29: [INFO] Slewing to RA: 11:33:40 - DEC: 79:44:43
2023-01-29T19:29:57: [INFO] Setting Max Slew Rate to 7 (48x)

Regards.
Ettore.

Any Tips for station mode wifi connect crash？

On my computer，onstep INDI wifi connection is 100% got crash.

WiFi concerns:

I cannot reproduce loss of connection nor crash.
my configuration is:
may be you could use Khalid's wonderfull Python tool to test communication github.com/kbahey/onstep-python

Also could you please define which versions you useit would help

another option would be to test is with indi_lx200_TeenAstro driver the problem is the same

It's generally lost connection or a communication error. So it skips the rest of the update on error. You'd need to have verbose logs on and find where that is to see what's going on. Could be parsing a reply (maybe a change in OnStep) or something else.

Repete may last message. in WIF onstep have may error:
2023-02-11T20:08:31: [WARNING] Communication error on Align Status Update, this update aborted, will try again...
2023-02-11T20:08:31: [WARNING] Fail Align Command
2023-02-11T20:08:31: [INFO] Getting Alignment Status: response Error, response = >
2023-02-11T20:08:22: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-02-11T20:05:07: [INFO] Polar Align Error Status response Error, response = >
2023-02-11T20:03:37: [WARNING] Communication error on Dewpoint (:GX9E#), this update aborted, will try again...
2023-02-11T19:55:54: [WARNING] Communication error on Preferred Pier Side (:GX96#), this update aborted, will try again...
2023-02-11T19:53:30: [WARNING] Communication error on Degrees past Meridian West (:GXEA#), this update aborted, will try again...
2023-02-11T19:53:21: [WARNING] This update aborted, will try again...
2023-02-11T19:53:21: [INFO] RA/DEC could not be read, possible solution if using (wireless) ethernet: Use port 9998
2023-02-11T19:53:15: [WARNING] Communication error on Humidity (:GX9C#), this update aborted, will try again...
2023-02-11T19:51:50: [WARNING] Communication error on Degrees past Meridian East (:GXE9#), this update aborted, will try again...
2023-02-11T19:50:55: [WARNING] Communication error on Preferred Pier Side (:GX96#), this update aborted, will try again...
2023-02-11T19:49:15: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-02-11T19:47:32: [WARNING] Communication error on Degrees past Meridian West (:GXEA#), this update aborted, will try again...
2023-02-11T19:46:06: [INFO] Polar Align Error Status response Error, response = >
2023-02-11T19:25:42: [WARNING] Communication error on Humidity (:GX9C#), this update aborted, will try again...
2023-02-11T19:23:12: [WARNING] This update aborted, will try again...
2023-02-11T19:23:12: [INFO] RA/DEC could not be read, possible solution if using (wireless) ethernet: Use port 9998
2023-02-11T19:23:01: [WARNING] This update aborted, will try again...
2023-02-11T19:23:01: [INFO] RA/DEC could not be read, possible solution if using (wireless) ethernet: Use port 9998
2023-02-11T19:11:21: [INFO] OnStep: Synchronization successful.
2023-02-11T19:06:02: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-02-11T19:02:28: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-02-11T18:58:55: [ERROR] Check system & Align if doing align to see if it went through!
2023-02-11T18:58:55: [ERROR] Unexpected return on sync call!
2023-02-11T18:58:54: [WARNING] Communication error on Preferred Pier Side (:GX96#), this update aborted, will try again...
2023-02-11T18:58:26: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:58:26: [INFO] OnStep: Synchronization successful.
2023-02-11T18:58:00: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:57:59: [INFO] OnStep: Synchronization successful.
2023-02-11T18:57:33: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:57:33: [INFO] OnStep: Synchronization successful.
2023-02-11T18:57:11: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:57:10: [INFO] OnStep: Synchronization successful.
2023-02-11T18:56:44: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:56:44: [INFO] OnStep: Synchronization successful.
2023-02-11T18:56:18: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:56:18: [INFO] OnStep: Synchronization successful.
2023-02-11T18:55:48: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:55:47: [INFO] OnStep: Synchronization successful.
2023-02-11T18:55:11: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:55:11: [INFO] OnStep: Synchronization successful.
2023-02-11T18:53:40: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:52:56: [INFO] Observer location updated: Latitude 46:10:58.0 (46.18) Longitude 13:32:59.0 (13.55)
2023-02-11T18:52:56: [INFO] Site location updated to Lat 46:10:58.00 - Long 13:32:59.00
2023-02-11T18:52:56: [INFO] Time updated, updating planetary data...
2023-02-11T18:52:56: [INFO] Device configuration applied.
2023-02-11T18:52:56: [INFO] Pulse guiding is enabled.
2023-02-11T18:52:56: [INFO] Custom tracking rates set. Tracking mode must be set to Custom for these rates to take effect.
2023-02-11T18:52:56: [INFO] Setting Max Slew Rate to 5 (8x)
2023-02-11T18:52:56: [INFO] Observer location updated: Latitude 46:10:58.0 (46.18) Longitude 13:32:59.0 (13.55)
2023-02-11T18:52:56: [INFO] Site location updated to Lat 46:10:58.00 - Long 13:32:59.00
2023-02-11T18:52:56: [INFO] Dome Policy set to: Dome ignored. Mount can park or unpark regardless of dome parking state.
2023-02-11T18:52:56: [INFO] Loading device configuration...
2023-02-11T18:52:51: [INFO] Initialization Complete
2023-02-11T18:52:51: [INFO] Mount is unparked.
2023-02-11T18:52:51: [INFO] No Rotator found.
2023-02-11T18:52:51: [INFO] No Focusers found
2023-02-11T18:52:51: [INFO] Focuser 2 NOT found
2023-02-11T18:52:51: [INFO] Focuser 1 NOT found
2023-02-11T18:52:51: [INFO] Network based connection, detection timeouts set to 2 seconds
2023-02-11T18:52:51: [INFO] =============== Parkdata loaded
2023-02-11T18:52:51: [INFO] Mount is unparked.
2023-02-11T18:52:51: [INFO] V4 OnStep detected, setting some defaults
2023-02-11T18:52:50: [INFO] Mount has Latitude 46:10:58.0 (46.1828) Longitude 13:32:59.0 (13.5497) (Longitude sign in carthography format)
2023-02-11T18:52:50: [INFO] Telescope detected having Pier Side, adding that capability (many messages duplicated)
2023-02-11T18:52:50: [INFO] Initialization Complete
2023-02-11T18:52:50: [INFO] Mount is unparked.
2023-02-11T18:52:50: [INFO] No Rotator found.
2023-02-11T18:52:50: [INFO] No Focusers found
2023-02-11T18:52:50: [INFO] Focuser 2 NOT found
2023-02-11T18:52:50: [INFO] Focuser 1 NOT found
2023-02-11T18:52:50: [INFO] Network based connection, detection timeouts set to 2 seconds
2023-02-11T18:52:50: [INFO] =============== Parkdata loaded
2023-02-11T18:52:50: [INFO] Mount is unparked.
2023-02-11T18:52:50: [INFO] V4 OnStep detected, setting some defaults
2023-02-11T18:52:48: [INFO] Mount has Latitude 46:10:58.0 (46.1828) Longitude 13:32:59.0 (13.5497) (Longitude sign in carthography format)
2023-02-11T18:52:48: [INFO] Telescope detected having PEC, setting that capability
2023-02-11T18:52:48: [INFO] Initialization Complete
2023-02-11T18:52:48: [INFO] Mount is unparked.
2023-02-11T18:52:48: [INFO] Outputs not detected, disabling further checks
2023-02-11T18:52:46: [INFO] No Rotator found.
2023-02-11T18:52:46: [INFO] No Focusers found
2023-02-11T18:52:46: [INFO] Focuser 2 NOT found
2023-02-11T18:52:46: [INFO] Focuser 1 NOT found
2023-02-11T18:52:45: [INFO] Network based connection, detection timeouts set to 2 seconds
2023-02-11T18:52:45: [INFO] =============== Parkdata loaded
2023-02-11T18:52:45: [INFO] Mount is unparked.
2023-02-11T18:52:45: [INFO] V4 OnStep detected, setting some defaults
2023-02-11T18:52:45: [INFO] Mount has Latitude 46:10:0.0 (46.1667) Longitude 13:32:0.0 (13.5333) (Longitude sign in carthography format)
2023-02-11T18:52:45: [INFO] LX200 OnStep is online.
2023-02-11T18:52:44: [INFO] Connecting to 192.168.1.110@9998 ...

What version of OnStep do you use?
OnStepX ( Version 10.) and OnStep (Version 4.24.s ) do not behave exactly the same.

Strange you have a good communication all along initailisation and then loose apparently communication.
What has changed between last working set-up?
OnStep Update?
Raspbian Update?
Indi Update (seems not since it shows upo version 1.17)

Again doing some tests with Khalid's Python secript would help a lot to exclude WiFi as a source of problem since I canno reproduce the error here with eitehr OnStep and OnStep X with all other beeing nightly builds.

Thank for response.
I use onstep version 4.24 s.
I've always had this problem and I've opened 3 requests with no response.
I use latest indi and raspbian 64bit bullseye.
If use usb nothing problems.
Regards.
Ettore

Ettore,

here my logs with OnStep 4.2.m and WiFi

As you can see I have no timeouts and so.
I definitively woul go for testing with github.com/kbahey/onstep-python