Yes, I had a 2 second delay set for the run corresponding to the last log I posted.
Do you have a work around for recovery during dither?
Thanks again.
Hm, as a workaround you could set the delay to 0 and do not select the "Abort Autoguide on failure".
Alternatively, you could try to use my fix directly. If you know how to compile from sources, simply add my kstars fork as new remote and checkout the branch "scheduler_restart_guiding_dithering_errors". This works like this:
Ah, ok. Is there a new fix today?
It's clear here in Spain tonight so I'm out imaging (hoping we don't lose it on a dither!).
But of course, tomorrow, I'll work out the git stuff and build your branch.
Meanwhile, could you post if the fix (if there is a new one) makes it to master?
TIA,
Steve
Hi Wolfgang
Perfect; nothing I can do will now stop the sequence
This finally makes ekos' schedule-capture-guide bulletproof!
Thanks so much for your time.
Clear skies,
Steve
[2019-12-18T19:37:30.367 CET INFO ][ org.kde.kstars.ekos.guide] - "PHD2: There was a dithering error, but continue guiding."
That's because "Abort Autoguide on Failure" was not checked in Dither settings in guide options. Check that option and dither failures from PHD2 should result in autoguide abort and consequently, capture abort as expected.