Maybe you could try to connect using the USB port for testing as long as we develop the driver. I've looked at the AltAzSimple driver source, it does not have the Alignment stuff, just normal syncs. So it should work as well.
did another run now with the geehalel indi branch:
prior to the compilation I could connect to my mount via direct USB @115k. After the compilation I could not connect with either skywatcher_altaz, Altaz_simple or EQmod.
For the EQmod I received the following log message:
[2020-09-11T13:45:25.870 CEST INFO ][ org.kde.kstars.indi] - EQMod Mount : "[ERROR] Error: Communication failed -> tty write failed, check connection: Write Error: Bad file descriptor "
[2020-09-11T13:45:25.872 CEST DEBG ][ org.kde.kstars.ekos] - "EQMod Mount" is disconnected.
[2020-09-11T13:45:25.873 CEST INFO ][ org.kde.kstars.ekos] - "EQMod Mount is disconnected."
For the other two, I attach the log file. It occurs to me, that for the skywatcher_altaz the config.xml in the .indi directory is missing. I could set the connection parameters in the indi control panel, but I am unsure whether they have any effect:
At least one of the driver has succeded in opening and writing to the mount:
[2020-09-11T13:18:05.060 CEST DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az Wedge : "[DEBUG] Connecting to /dev/ttyUSB0 @ 115200 "
[2020-09-11T13:18:05.061 CEST DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az Wedge : "[DEBUG] Port FD 3 "
[2020-09-11T13:18:05.061 CEST DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az Wedge : "[DEBUG] Connection successful, attempting handshake... "
[2020-09-11T13:18:05.061 CEST DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az Wedge : "[SCOPE] SkywatcherAltAzSimple::Handshake "
[2020-09-11T13:18:05.061 CEST DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az Wedge : "[SCOPE] InitMount "
[2020-09-11T13:18:05.062 CEST DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az Wedge : "[SCOPE] CheckIfDCMotor "
[2020-09-11T13:18:06.415 CEST DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az Wedge : "[DEBUG] Handshake failed. "
[2020-09-11T13:18:06.532 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-09-11T11:18:06: Driver indi_skywatcherAltAzSimple: SkywatcherAltAzSimple::ISGetProperties"
`CheckifDCMotor` sends a ':' which is not a valid command for AZEQ5/6 mounts, and they return '!1'. This is what I test, exactly '!1' as this is what my AZEQ5 replies. Maybe the AZEQ6 returns another error code and the function returns false. You may test that using picocom if you have it installed: `picocom -b 115200 /dev/ttyUSB0`, hit ':' followed with ctrl-M (there is no echo), and look at the reply. You may close picocom with ctrl-A then ctrl-X. Don't send other commands if you are not sure of what you do (<strong>never</strong> send ':Q'....).
Concerning EQMod, as we change the indi core library without recompiling it, it may explain the connection issue. But usually this implies a crash when the API has changed and the dynamic loader fails and aborts. Otherwise EQMod should be able to work as usual. I wonder if you actually run the hand compiled binaries. May you try to check if they have been installed in `/usr`:
ls -l `which indiserver indi_eqmod_telescope indi_skywatcherAltAzMount`
If their date are correct, you may try to launch them by hand and connect kstars directly to that indiserver (on localhost port 7624):
Actually I don't exactly know your setup.
Edit: the EQMod error (bad file descriptor) suggests as disconnection/reconnection of the USB serial dongle, changing its device file (USB1 for instance).
did the update. AltAzSimple still handshake failing; skywatcherAltAz does not connect due to other reasons. Log attached. First attempt is with AltAzSimple (because there the connection at least was initiated), second with skywatcher_AltAZ
Dear Jasem, sorry to be communicating about the same subject on many fronts (Stellarmate support ticket HAYB-000932, Github enhancement demand
, and now here).
As I mentioned in both other places, the version of the indi_skywatcherAltAzMount driver you are using with the alias AZ-GTI AltAz is the one that still contains the bug that doesn't allow UDP connection with Az-GTI, as explained -and then solved- in this GitHub bug
So that's the first problem. The second problem for is that when using AZ-GTI in AltAz with indi_skywatcherAltAzMount driver (not your version), it does not track. The driver connects through WiFi (UDP), and then it is parked. If I unpark, it goes somewhere, but when it gets there it doesn't track. I can slew somewhere else (sometimes, sometimes it stops) but again when it gets to destination it does not track.
As the original post demanded, I also think the best would be to have an AltAz "translation layer" between Ekos and AZ-GTI eqmod-based driver, translating from AltAz to EQ and back in every interaction with said driver, would that be possible? Since that driver works seamlessly with AZ-GTI whereas the indi_skywatcherAltAzMount driver does not.
It's alright! Ok, let's move all the discussions here
I am using this driver with my AZ-GTi Alt-Az driver over UDP.
I just tested this and issued GOTO to Phecda. It slewed there and it was tracking. RA/DE are constant while AZ/AL change to keep the object centered.
I'm not sure I follow the last point though.. you want to help explicit Az/Alt input in the driver? This can be added, but it's not strictly necessary. If this is required for a very good reason, then I'll add it. Otherwise usually clients simply send the RA/DE and the driver internally converts that to Al/Az and command the mount.
Ok, I see that you are making it work.
In my case, after switching to the beta channel, only one driver works (AZ-GTI AltAz), all other drivers (including Nikon, etc) give me the "driver xxxx was not found on the system" error (and then Kstars closes). So that's bad, I think I'll have to download the image and start all over again. It's frustrating because I had downloaded the 4+ gb plate solving data files and my connection is slow.
In any case, the AZ-GTI AltAz driver (which does work) does not connect via UDP. I don't know why. The indi-SkyWatcher-AltAzMount driver did connect fine via UDP, but did not track correctly.
My last point was about what I mentioned in
enhancement: the point is that AZ-GTI driver is a superior driver compared to indi_Skywatcher_AltAzMount in many ways, it has more features and is more stable I think. If I am correct, then my point is that it would be better to make an AltAz version of that driver, an altAz version of the Eqmod driver beneath it. I know that sounds difficult, but that way altaz users would inherit all the advantages of the AZ-GTI driver and you would have a unified driver for altaz/EQ use, I think.
No need to reflash again. Make sure to update_indi_core and update_indi_drivers then remove the Ekos profile and recreate it again. Hopefully that should help you run all the devices. If not, we can try Teamviewer method again.