During today's session the GPS was causing this reset. The following log happened:
2020-09-05T00:31:44 Telescope altitude is below minimum altitude limit of 0. Aborting motion...
2020-09-04T23:52:02 GPS driver detected. KStars and mount time and location settings are now synced to the GPS driver.
2020-09-04T23:51:54 Telescope info updated successfully.
Solution: Disable GPS if the signal is unreliable...
Disabling the gps or even remove it doesn’t solve solve the problem. The (-) alt keep popping up in the log...
I ordered one direct cable, but also I read that there are many of the has issues. Can someone recommend the cable that works fine with RPi4/indi/Ekos? My mount is EQ5
I assume you're talking about a cable that goes from your USB2 port to your mount.
I use the USB2EQ5 cable ordered from shoestring www.store.shoestringastronomy.com/products_eq.htm
Works fine with my Atlas Pro.
If you're good at such things, you can also build your own.
See eq-mod.sourceforge.net/eqdirect2.htm
I did that for a "proof-of-concept" backup cable, but have to admit it took me a while to get it working
and needed a good friend to coach me.
I just want I put an end to this thread. After running ekos debugger for 6 hours session, I lost tracking again. This time I had a full log to go through, and from the timestamp of the file (when the file was created and not the time stamp in the filename), I was able to know why I lost tracking. It was the maximum Alt I set as a limitation in Ekos.
I need to set up more realistic limitations and pickup suitable targets accordingly!!!
[2020-09-21T01:36:00.691 EDT INFO ][ org.kde.kstars.ekos.mount] - "Telescope altitude is above maximum altitude limit of 70. Aborting motion..."
[2020-09-21T01:36:00.693 EDT DEBG ][ org.kde.kstars.indi] - ISD:Telescope: Aborted.
The following user(s) said Thank You: Jasem Mutlaq