Major INDI Library release v1.9.0 bring significant internal changes championed by @pawel-soja to modernize core INDI Library drivers and clients. New drivers for DeepSkyDad Flat Panel & Pegasus devices plus further improvements to PCM8 drivers.
This is what I see from the HC towards the ALT/AZ on startup
0x3b 0x03 0x0d 0x11 0x05 0xda To ALT, CMD = 5 ???
0x3b 0x05 0x11 0x0d 0x05 0x0c 0x82 0x4a
0x3b 0x03 0x0d 0x10 0x05 0xdb To AZ, CMD = 5 ???
0x3b 0x05 0x10 0x0d 0x05 0x0c 0x82 0x4b
Just wondering about AUX command and not specifically about the indi aux driver
I have added some features to the indi_celestron_aux driver.
1. direct mount USB connection.
2. cordwrap position computed by alignment subsystem.
3. autoguide: the code is roughly copied from Rick's driver indi_celestron_cgx.
Unfortunately, I haven't any checking setup, so they compile and run without fatal errors but the functionality is completely untested.
If someone brave and patient wants to try them, the code is here github.com/fabriziop/indi-3rdparty/tree/celestronaux_eqtrack
Below is as far as I have gotten in scripting the startup for the Aux driver
The goal for this is I have added index sensors for the base whose status can be read via PI GPIO pins and are at a known location for my local sidereal time and scope altitude
Given the scope is at the ALT/AZ index sensors, the RA/DEC can be calculated close enough that a goto and plate solve will home it in.
So far the initial Connect must be done through the driver screen, I have not found a -t for the connect that does not error back
Two scripts are required, one sets the time and location and enables the math plugin and then need to drop over to the driver screen to enable the alignment subsystem, more on this below.
Script 1, set the parameters time, location
After going back to the driver screen and enabling alignment subsystem
Script 2, set an initial RA/DEC then do a small slew to enable tracking
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)
UpdateLocation(latitude, longitude, elevation);
Matching up with equmod driver handshake:
// Set this according to mount type
LOG_INFO("Successfully connected to EQMod Mount.");
And #ifdef WITH_ALIGN
INDI::AlignmentSubsystem::AlignmentSubsystemForDrivers::UpdateLocation(latitude, longitude, elevation);
// Set this according to mount type
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.