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?

That looks like a power issue. Are you sure there are no disruptions to the power to the mount? If it is battery power, that's where I'd look first.

It's plugged into the mains supply via a 12V 3A power adapter www.amazon.co.uk/gp/product/B07383SK35/r...06_s01?ie=UTF8&psc=1
Is this theoretically sufficient to power the HEQ5? 36w sounds like plenty but I don't know.

The power connector of HEQ5 is a bit flimsy, had all sorts of weird serial issues especially when it was cold until I replaced the stock connector with a screwed one.

12 @ 3A should be fine. There is an issue somewhere else, but not in the driver as it has been used flawlessly for many years.

I believe in the end it may have been something to do with the mount model. When I clicked "clear model" and "clear parking" in the mount tab in ekos, the issue did not present itself that night. I had never considered what a mount model is or how Ekos/Kstars uses them until now, are they maybe useful for people who have permanently setup systems, like garden observatories?

I heard that sometimes Skywatcher can start acting like this. What should help is start mount and slew to some part of sky. Then run align while selected "do nothing". Then correct any error in align manualy by releasing clutches wittout moving by motors.