Hi
New build. Now, on guiding failure, guiding restarts but capture doesn't.
Log attached.
Thanks

Hm, another case where it slips. Do you have "Abort Autoguide on failure" set in the guiding options?

Yes. I have abort autoguide on failure checked.
Is that correct?
Cheers

Depends, I'm not so familiar with this option. I tested both variants with this option checked and unchecked. In both cases guiding and capturing is restarted. But obviously in your case it doesn't.

Could you give it a try with the option unchecked? In my setup, capturing resumes and in parallel guiding restarts. The difference in my setup is, that with the option checked, KStars waits with restarting the capturing until guiding is running while without the option set, it does both in parallel.

Option checked: guiding restarts, capture does not
Option unchecked: capture continues, guiding does not.
Log attached.
Thanks

That's really strange! I think I have the same setup as yours, but mine behaves as expected, yours definitely not...

I have (very ordinary) Ubuntu 18.04 with all the updates. Would that make a difference perhaps?
Is there any difference between your and my logs when guiding or capture fails?
TIA

OK. A bit more testing.
'abort autoguide on failure' unchecked

Now, both guiding and capture are resumed BUT not if the guiding fails during a dither.
Is there any chance of getting both guiding and capture restarted if guiding fails during the dither and during the exposure?
TIA,
Steve
Log attached.

Good news, I could reproduce it.

In the capture sequence, do you have set a delay? If I set a delay and have the "Abort Autoguide on failure" option set, then guiding starts, but capturing not. Instead, it shows "Waiting..." on the Capture tab.

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:After this, compile kstars as usual.

- Wolfgang

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