Jordi Sesé
Jordi Sesé replied to the topic 'Robofocus - 'Busy' state produces tty timeout / bogus' in the forum. 2 years ago

Hi all,

New test tonight, and same results in the log. After every "Linear: un-doing extension. Moving back in by XX", there is a tty error.
I post here the lines, no need to attach all the log file, it's the very same. 

[2022-10-01T23:40:04.814 CEST INFO ][           org.kde.kstars.indi] - RoboFocus :  "[INFO] Moving outward... "
[2022-10-01T23:40:04.841 CEST INFO ][           org.kde.kstars.indi] - RoboFocus :  "[INFO] Stopped. "
[2022-10-01T23:40:04.841 CEST DEBG ][     org.kde.kstars.ekos.focus] - Abs Focuser position changed to  10301 State: Ok
[2022-10-01T23:40:04.841 CEST DEBG ][     org.kde.kstars.ekos.focus] - "Linear: un-doing extension. Moving back in by 15"
[2022-10-01T23:40:04.841 CEST INFO ][     org.kde.kstars.ekos.focus] - "Focusing inward by 15 steps..."
[2022-10-01T23:40:04.847 CEST INFO ][           org.kde.kstars.indi] - RoboFocus :  "[INFO] Focuser is moving to position 10286 "
[2022-10-01T23:40:08.102 CEST INFO ][           org.kde.kstars.indi] - RoboFocus :  "[ERROR] TTY error detected: Timeout error "
[2022-10-01T23:40:08.107 CEST INFO ][           org.kde.kstars.indi] - RoboFocus :  "[WARNING] Bogus position: (00 00 00 00 00 00 00 00 00) - Bytes read: -1 "

And I did use another power source this time to feed the Robofocus: a reliable 12V 4A, to discard that also.

I guess next test will be to change the autofocus algorithm...

Any other idea?

Thanks for you help, and regards.

Jordi.

Read More...