Hi. I've been using astroberry on a PI 4 2GB with Kstars-Ekos. This has worked well until relatively recently when i have noticed odd behaviour with regards to my mount.
I love the auto meridian flip and auto park at [time] feature, but a few times now I have lost considerable imaging time due to my HEQ5 either just turning tracking off with no input, whether the scheduler is running or not. And while I wasn't able to look at any logs the first time because my dad unplugged the raspberry pi in the morning before I could check anything, I did see in the data that after a certain frame I got star trails and my target flew out of view.
Most recently, I was barely getting a few minutes in before I'd get a message in the mount tab of Ekos mentioning a meridian flip, however I was imaging Sadr in Cygnus, which is closer to the horizon than the meridian at present!
Someone on SGL mentioned that if I have never created a mount model in the alignment tab, it could explain some errors, but it seems fishy to me as it has worked well in the past. Can the HEQ5 even remember anything without the handset plugged in, or is it just a dumb micro controller for stepper motors electronically?

I'm using EQmod drivers, asi ccd, asi efw, toupcam. The first sign that something was wrong on my last session was that PHD claimed it "was no longer sufficient to maintain guiding" or words to that effect. However this error shut off the refreshing camera so I couldn't see the true effect.

Does this issue sound familiar to any common pitfalls?

Read More...