So today I encountered an issue with INDI EQMod driver while using Ekos Align module. EQMod was set to "Nearest Point" Alignment Mode and Ekos Align module initially worked after a few iterations to go to my target (SH2 190). In about 2 hours, Ekos capture module initiated a commanded meridian flip, but once the flip was completed and the solver started again, it wasn't able to get the mount to move to to the target coordinates.
So the alignment stuff is over my head, and I don't know how they work exactly so I figured I'd share this here in case Jean-Luc or anyone else can share some insight. You have to read the attached files from bottom-up. The EQMod file contains time stamp in UTC while the Ekos Align module is in local time.
Now from what I could gather is that prior to meridian flip, it had the following coords:
So the "current" RA/DE is from encoders, while the Goto RA/DE is after the alignment math is applied to them and what gets reported to the client (I'm not sure if this assumption is correct). This is why Ekos in the meridian flip asked the mount to to RA=2.6043 DE=61.5481, because this is the current RA/DE of the mount as received by Ekos.
Now after the meridian flip was complete, Ekos took an image and found the solution:
And EQMod is getting synced to the solution coordinates, so back in EQMod driver:
However, again we see here telescope RA/DEC being different from what is reported by KStars/Ekos.. again I'm assuming those are the pure encoders coordinates without the alignment model transformation. So after commanding the sync, Ekos commands EQMod to go then to the target coordinates, and EQMod tries to go there:
However, back in Ekos, we wait until mount is finished slewing, then we solve again:
But it looks like the mount didn't move much! The solution coordinates are the same as before, and what is weird now is that the telescope coordinates were updated to values quite different from target coordinates, even though we asked the mount to go to target RA (02h 36m 17s) DEC ( 61° 32' 53"). Despite this sync then slew cycle, the mount is stuck at RA (02h 33m 46s) DEC ( 54° 54' 36") and the solver runs out of iteration before it bails.
Any idea what is going on?
So the alignment stuff is over my head, and I don't know how they work exactly so I figured I'd share this here in case Jean-Luc or anyone else can share some insight. You have to read the attached files from bottom-up. The EQMod file contains time stamp in UTC while the Ekos Align module is in local time.
Now from what I could gather is that prior to meridian flip, it had the following coords:
So the "current" RA/DE is from encoders, while the Goto RA/DE is after the alignment math is applied to them and what gets reported to the client (I'm not sure if this assumption is correct). This is why Ekos in the meridian flip asked the mount to to RA=2.6043 DE=61.5481, because this is the current RA/DE of the mount as received by Ekos.
Now after the meridian flip was complete, Ekos took an image and found the solution:
And EQMod is getting synced to the solution coordinates, so back in EQMod driver:
However, again we see here telescope RA/DEC being different from what is reported by KStars/Ekos.. again I'm assuming those are the pure encoders coordinates without the alignment model transformation. So after commanding the sync, Ekos commands EQMod to go then to the target coordinates, and EQMod tries to go there:
However, back in Ekos, we wait until mount is finished slewing, then we solve again:
But it looks like the mount didn't move much! The solution coordinates are the same as before, and what is weird now is that the telescope coordinates were updated to values quite different from target coordinates, even though we asked the mount to go to target RA (02h 36m 17s) DEC ( 61° 32' 53"). Despite this sync then slew cycle, the mount is stuck at RA (02h 33m 46s) DEC ( 54° 54' 36") and the solver runs out of iteration before it bails.
Any idea what is going on?