Communication issues with the mount occasionally cause these spurious out-of-limits issues too if the step count from mount gets corrupted. With this particular mount the power connector is unfortunately flimsy and causes voltage drops and communication issues. I replaced the connector with a screw secured one and didn't have these issues after that.

How do I get the settings to stick? Last night I unchecked the "Abort Tracking" box and disabled "Limit Goto", however this morning when I re-started everything it was again selected. I assumed that if I clicked on the "Save" button on the Options tabs then it would automatically restore my setting the next time I started up?



Jim

The save button should do its job, except if it can't write to the configuration file. Try to save and load, and watch the console log.

-Eric

I've got the same thing on my NEQ6R. I just uncheck the disable tracking on the Horizon tab. That particular setting has never saved for me, its one I change each time I connect to the devices.

That's unexpectedly entirely true. Let me take care of this.

-Eric

Eric,

It would be much appreciated if you could have a look at this and possibly fix it

Jim

I pushed PR #64 at github.com/indilib/indi-3rdparty/pull/64 for the only case of saving that configuration.

As often, do save your configuration when the device is connected, else you will revert the properties that are undefined at the time you press "save" to defaults.

Eric,

Thank you. If I am running Astroberry, do I update by just running "sudo apt update & upgrade"?

Jim

Thank you! It was a minor item, I just worked it into my workflow. But it will be nice to have it addressed for scheduler purposes.

This is exactly what happened to me because of a noisy power supply (and it was a 12V 5A one, so no low current issues, just noise). Looking at the logs it was clear that DEC and RA counts were off-limits (meaning off the expected number range) because of spurious bytes being received.

I would be very wary of just disabling the "abort tracking" option as a permanent fix. Communication problems also affect slews and you might end up with your scope trying to become one with the tripod.

Ricardo.

Depending on which package you are pulling from, you may need to wait until the patch is integrated into a new version. Given that the PR was merged yesterday, the next new version you see when running your apt upgrade should have the change.

EDIT: I'm also in the process of fixing the indi-eqmod horizon management. Stay tuned.

-Eric

I also pushed PR#65 at github.com/indilib/indi-3rdparty/pull/65 that should fix the horizon management, at least in the eqmod driver.

You should be able to enter your horizon sets and have them properly asserted by the mount driver, promptly aborting tracking/slewing/goto-ing. That might help people with cramped observatory spaces

Note that the interpolation of altitude between horizon points is still linear, not spherical.

-Eric