Alfred,
this indeed matches my experience: There is a continuous stream of exposures from guiding at the requested exposure time exactly up to the point when, after dither, guiding is resumed. This resume triggers a new exposure, which aborts the currently ongoing one:

and the guide module gets that aborted frame, which has only been exposed for a second or so, instead of the requested 4.5s. The time between readouts is basically given by readout time ad processing time. You can see that, e.g., the flux of the brightest star went down from 27902 before the dither to 9532 after dither.

As I mentioned in post #72049, that abort also happened in the 'old' version, but there only once, and after that only one stream of exposure/readouts continues with proper exposure times, whereas now both seem to continue.

Thinking about it, my guess is that the main error is that when an exposure is already going on at the time when a frame capture is requested, the ongoing exposure is aborted, but read out, and then returned as the requested frame, instead of completely dumping it and waiting until the newly triggered frame exposure ends.

Read More...