Focuser sometimes fails to respond to commands or runs the focuser continuously without stopping

[illigtr]

I use my OAT with the MKS L 2.1 board, running firmware version 1.13.15. When using KStars and the INDI Control Panel for the LX200 OpenAstroTech mount, if I adjust the focuser in or out the actual stepper will not respond all the time. Sometimes it responds and move the necessary steps, other times it does nothing. In addition, in some cases the stepper begins to turn and then never stops. This is a serious issue as there are no end limit sensors on the focuser.

It would appear that the communication handshake when using focuser is having problems, or something else is blocking the comm, or may be overloaded (PHD2 is running) How can I resolve this issue?

What logging could I do to help diagnose the problem?

[ClutchplateDude]

The only way to diagnose this would be for you to add a second serial port for debugging , configure the firmware to support that and try to reproduce the issue. Then we could look at the logs and see what the problem is.

…

---- On Tue, 24 Jun 2025 16:04:17 +0200 ***@***.***> wrote ---- illigtr created an issue #267 I use my OAT with the MKS L 2.1 board, running firmware version 1.13.15. When using KStars and the INDI Control Panel for the LX200 OpenAstroTech mount, if I adjust the focuser in or out the actual stepper will not respond all the time. Sometimes it responds and move the necessary steps, other times it does nothing. In addition, in some cases the stepper begins to turn and then never stops. This is a serious issue as there are no end limit sensors on the focuser. It would appear that the communication handshake when using focuser is having problems, or something else is blocking the comm, or may be overloaded (PHD2 is running) How can I resolve this issue? What logging could I do to help diagnose the problem? — Reply to this email directly, #267 , or https://github.com/notifications/unsubscribe-auth/ADD3KS2RS42XFIGBV43LX6T3FFLGDAVCNFSM6AAAAACAANN5FOVHI2DSMVQWIX3LMV43ASLTON2WKOZTGE3TEMJUGYZDMNA . You are receiving this because you are subscribed to this thread.

[illigtr]

I can do that, I already have a second serial port for debugging. What entries do I need to add to ensure debug logs for the above problem.

In other words, what parameters do you want me to add to this line?
This is what I will go wtih by default:

#define DEBUG_LEVEL (DEBUG_SERIAL|DEBUG_STEPPERS|DEBUG_FOCUS|DEBUG_MEADE)

[illigtr]

I did a test and reproduced the stepper running continuously after I used the INDI Control Panel to "Focus In" 80 steps a few times. The stepper then started turning continuously until is used the ABORT command in the Focuser tab.

Log file attached:

COM5LOG.TXT

[illigtr]

This is the log from INDI Control Panel

2025-06-24T16:12:09: [INFO] getCommandChar 3: :FB# -> '0' 
2025-06-24T16:12:09: [INFO] Current focuser: 46612.000000 
2025-06-24T16:12:08: [INFO] Executed Meade Command Immediate: :FQ# 
2025-06-24T16:12:08: [INFO] getCommandChar 3: :FB# -> '1' 
2025-06-24T16:12:08: [INFO] Current focuser: 46647.000000 
2025-06-24T16:12:06: [INFO] getCommandChar 3: :FB# -> '1' 
2025-06-24T16:12:06: [INFO] Current focuser: 46984.000000 
2025-06-24T16:12:05: [INFO] getCommandChar 3: :FB# -> '1' 
2025-06-24T16:12:05: [INFO] Current focuser: 47320.000000 
2025-06-24T16:12:04: [INFO] getCommandChar 3: :FB# -> '1' 
2025-06-24T16:12:04: [INFO] Current focuser: 47655.000000 
2025-06-24T16:12:03: [INFO] getCommandChar 3: :FB# -> '1' 
2025-06-24T16:12:03: [INFO] Current focuser: 47992.000000 
2025-06-24T16:12:02: [INFO] getCommandChar 3: :FB# -> '1' 
2025-06-24T16:12:02: [INFO] Current focuser: 48328.000000 
2025-06-24T16:12:00: [INFO] getCommandChar 3: :FB# -> '1' 
2025-06-24T16:12:00: [INFO] Current focuser: 48665.000000 
2025-06-24T16:11:59: [INFO] getCommandChar 3: :FB# -> '1' 
2025-06-24T16:11:59: [INFO] Current focuser: 49002.000000 
2025-06-24T16:11:58: [INFO] getCommandChar 3: :FB# -> '1' 
2025-06-24T16:11:58: [INFO] Current focuser: 49338.000000 
2025-06-24T16:11:57: [INFO] getCommandChar 3: :FB# -> '1' 
2025-06-24T16:11:57: [INFO] Current focuser: 49676.000000 
2025-06-24T16:11:56: [INFO] Executed Meade Command Immediate: :FM-80# 
2025-06-24T16:11:56: [INFO] Executed Meade Command Immediate: :FM-80# 
2025-06-24T16:11:56: [INFO] Executed Meade Command Immediate: :FM-80# 
2025-06-24T16:11:56: [INFO] getCommandChar 3: :FB# -> '0' 
2025-06-24T16:11:56: [INFO] Current focuser: 49840.000000 
2025-06-24T16:11:55: [INFO] Executed Meade Command Immediate: :FM-80# 
2025-06-24T16:11:55: [INFO] getCommandChar 3: :FB# -> '0' 
2025-06-24T16:11:55: [INFO] Current focuser: 49920.000000 
2025-06-24T16:11:54: [INFO] Executed Meade Command Immediate: :FM-80# 
2025-06-24T16:11:15: [INFO] Observer location updated: Latitude 45:30:00.0 (45.50) Longitude -73:34:47.0 (-73.58) 
2025-06-24T16:11:15: [INFO] Site location in the mount updated to Latitude 45:30:00.0 (45.5) Longitude -73:34:47.0 (-73.5797) (Longitude sign in carthography format) 
2025-06-24T16:11:15: [INFO] Time updated, updating planetary data... 
2025-06-24T16:11:14: [INFO] Device configuration applied. 
2025-06-24T16:11:14: [INFO] Set backlash 0 
2025-06-24T16:11:14: [INFO] Pulse guiding is enabled. 
2025-06-24T16:11:14: [INFO] Observer location updated: Latitude 45:30:00.0 (45.50) Longitude 106:25:00.0 (106.42) 
2025-06-24T16:11:14: [INFO] Site location in the mount updated to Latitude 45:30:00.0 (45.5) Longitude 106:25:00.0 (106.417) (Longitude sign in carthography format) 
2025-06-24T16:11:14: [INFO] Dome Policy set to: Dome ignored. Mount can park or unpark regardless of dome parking state. 
2025-06-24T16:11:14: [INFO] Loading device configuration... 
2025-06-24T16:11:14: [INFO] getCommandChar 3: :FB# -> '0' 
2025-06-24T16:11:14: [INFO] Current focuser: 50000.000000 
2025-06-24T16:10:59: [INFO] Mount has Latitude 45:30:0.0 (45.5) Longitude (0 to +360 Eastwards) 106:25:00.0 (106.417) 
2025-06-24T16:10:59: [INFO] LX200 OpenAstroTech is online. 

[illigtr]

Has anyone had a look at this issue? What else can I provide?

[illigtr]

Has anyone looked into this issue?

[illigtr]

Has this version of firmware been completely abandoned due to the new firmware 2.x development?

[ClutchplateDude]

No, it has not. There might be limited dev availability in general, but we do try to update this version when we find issues.