I finally got around to building your latest code and have just spent a couple of hours testing, so far all is good. The cord-wrap works a treat.
I can only test in Alt/Az.
What would be the sequence of operations using Kstars/Ekos to use the aux driver in Equatorial North mode please?
I keep seeing this with AltRate never 0
How far apart should the first, second and third etc sync's be in RA/DEC ?
And in bool CelestronAUX::updateLocation(double latitude, double longitude, double elevation)
{
//ESN
UpdateLocation(latitude, longitude, elevation);
SetApproximateMountAlignmentFromMountType(EQUATORIAL);
Matching up with equmod driver handshake:
#ifdef WITH_ALIGN
// Set this according to mount type
SetApproximateMountAlignmentFromMountType(EQUATORIAL);
#endif
LOG_INFO("Successfully connected to EQMod Mount.");
return true;
And #ifdef WITH_ALIGN
INDI::AlignmentSubsystem::AlignmentSubsystemForDrivers::UpdateLocation(latitude, longitude, elevation);
// Set this according to mount type
SetApproximateMountAlignmentFromMountType(EQUATORIAL);
#endif
I am the first author of the driver.
First: Thanks all of you, brave souls, for testing the driver!
Just a reminder, since I have noticed some of this mentioned in few posts:
<strong>Never</strong> use the driver with HC active (moving, alignment etc.). It is fine to use it as a serial interface. If you do, both HC and the driver will probably get confused and the movement will be unpredictable.
We got a <strong>nasty</strong> bug in recent release (1.8.9) - the type for the position got changed to unsigned during refactoring. The effect is fast movement below encoder position 0 on Alt axis (If you have tracking on). It is already fixed in master. <strong>Please</strong> update your testing build with this fix.
Remember that this is a <strong>beta</strong> level driver during development. <strong>Never</strong> operate it unattended without ability to stop the erratic motion. I do not want to have your damaged hardware on my conscience. If you test with OTA on the mount have your clutches not tighten - so if the tube bumps on something it will not get damaged.
The initial code was intended to AltAz mount, so the EQ case is newer and less tested. Be extra careful. E.g. this recent bug is probably worse for EQ - since negative Alt is rare in operation. Negative Dec - not so much.
I have been testing with NextStar 6SE Alt/Az and everything works BUT after slewing to a target the scope hunts up and down sometimes 10 to 15 times before it settles. This is a problem when plate solving is taking multiple exposures to refine the solve.
This is strange. It is supposed to be:
1. Fast GoTo to the position the object *was* at one minute ago
2. Slow GoTo to the final position
This is intended to cancel out any backlash by not changing direction on approach
It should never "hunt around". Are you sure you are not running alignment tool from EKOS in the "slew to target" mode?