[/quote]
The re-calibration is always guaranteed to recalculate these variables correctly, albeit at the expense of time. Maybe someone can try to go the math route? If it is working in PHD2, there is no reason why it shouldn't work in Ekos.[/quote]
I think I may just have found an exception to that rule - or at least a bug that negates the effects of the recalibration.
I implemented Wolfgang's fix and recompiled Kstars from the latest git.
The fix does what it is supposed to do: Everytime the mount slewed and the guiding module was active, it recalibrated.
So far so good.
However, when I ran my schedule for 1. sequence IC1848, after completion 2. sequence NGC2023 again, which had produced star trails the last time, I ended up with star trails again!
From the logs it looks to me that Declination Swap was first enabled at 2019-11-23T23:25:15.407 CST when IC1848 had passed the meridian and the mount had flipped, then that sequence ended at 2019-11-24T00:05:17.304 CST and NGC2023 was started as planned, mount slewed back across the meridian and guiding was recalibrated, but at 2019-11-24T00:07:47.402 CST Declination swap was enabled again resulting in star trails for the consecutive images until around 1.23 AM I manually stopped the scheduler and restarted it. Only that led to the Swap being disabled again, until 2019-11-24T02:09:41.406 CST at which point it was reenabled after NGC2023 had crossed the meridian and the flip had occurred.
So it looks to me the problem lies in the scheduler, where Declination Swap is not reset between targets. Is there a command that can just reset the Declination Swap once one sequence is finished and before the next one is started?
Complete log is here:
www.dropbox.com/s/bgvi2dmb5vg9ry4/log_19-43-09.txt?dl=0
I hope this helps with fixing the problem.
Jo
PS: Perhaps the simplest way to fix this is to instruct the scheduler to just recalibrate after a Declination swap has occurred? Of course, only when "Always recalibrate" has been selected.