Hello everybody!
I think I have a quite odd behaviour on Ekos and I'll try my best to explain what happens. My setup is a EQ5 with EQMod and guided with a QHY5L-II-C before and a ASI 120MM Mini now, controlled by an Astroberry on RPi 4 with 4gb. Everything works normally fine, except for the two strange behaviours, but I'll ask for the second after this one is, hopefully, solved.
First one: sometime, often, I'd say once per minute, on KStars the mount makes a "sudden movement" that seems to "jump" the telescope pointer to a random direction very far away from the actual position, and by far I mean far, 90 or more degrees too. It looks like the program is detecting a sudden movement of the mount, but of course no movement is done and the mount is tracking nicely. In the mount log on Indi control panel this is an example of what is recorded for such "jumps":
2021-12-19T22:46:02: [WARNING] Horizon Limits: Scope at AZ=167.096 ALT=-23.796 is outside limits. Nothing to abort.
2021-12-19T22:45:11: [WARNING] Horizon Limits: Scope at AZ=163.885 ALT=-16.541 is outside limits. Nothing to abort.
2021-12-19T22:44:49: [WARNING] Horizon Limits: Scope at AZ=166.885 ALT=-23.676 is outside limits. Nothing to abort.
2021-12-19T22:44:21: [WARNING] Horizon Limits: Scope at AZ=295.669 ALT=-43.693 is outside limits. Nothing to abort.
2021-12-19T22:41:50: [WARNING] Horizon Limits: Scope at AZ=166.671 ALT=-23.981 is outside limits. Nothing to abort.
Another trail of what happens can be seen if I pulse guide, because it becomes absolutely impossible: Ekos reads a false movement so sends a correction based on that that totally spoils the guide. You can see this in this PHD2 sample graph:
As said, if I guide via ST4 I still see the "jumps" on the KStars starmap but no strange PHD2 graph.
Does anyone have an idea of why this happens?
Thanks!