Hi Willem Jan,
could it be that you had non-guiding dithering on first, but turned it off at a later stage? I found in the log that you had a dithering error at 20:28:17, but after this no dithering happened until the meridian flip started at 23:27:48.

If this is the case, then we really have an edge case here, since after the dithering error at 20:28:17 the guiding state remains in state "Dithering error".

When a meridian flip is detected to be necessary EKOS evaluates whether guiding is on at this stage. And this is not that easy, since at this stage it could be that some guiding error stopped guiding. If the non-guiding dithering option is set at that point of time, guiding is considered to be off.

The mean thing in your case: the previous dithering created a guiding state that leads to the conclusion that guiding should run after the meridian flip. If you then turn the non-guiding dither option off, this last guiding state is taken as an indication that guiding should run after the meridian flip - leading to the problem that you observed.

But this explanation relies on the hypothesis that you changed the non-guiding dither option from ON to OFF during the session.

@Jasem: maybe we should consider clearing the guiding state when this option is turned off to avoid such a situation.

HTH
Wolfgang

Read More...