Second instance of NINA doesn't realise auto-focus is occurring on another instance and continues to image unguided

[Kevin Jackson]

[ Y ] Is the issue reproducible?
[ Y ] Are you running the latest version? (Latest Beta, not Development)
[ Y ] Are all prerequisites that are mentioned inside the manual met?

Description

When running 2 instance of NINA with Synchronised PHD2, when a dithering event occurs, both sequencers wait until PHD2 is guiding again. I’d expect the same kind of behaviour when an autofocus routine occurs in one instance.
Currently when an autofocus routing occurs, PHD2 stops guiding, the autofocus routine occurs, and once done, the sequence of image capture resumes.
When running 2 instances of NINA, it doesn’t realise that an autofocus is occurring in the other instance - but PHD2 guiding stops [an option of course, in NINA]. It would be preferable for an instance to recognise that guiding has stopped, and therefore pause the sequence until guiding has resumed again.

Steps to Reproduce

• Set up 2 NINAs (Synchronised PHD2) and 2 sequences
• In one of the sequences, set up an autofocus
• Watch one instance continue to take images whilst an autofocus has stopped PHD2
• (Worse is a situation where the unaware instance of NINA starts PHD2 again, perhaps as part of the sequence it is obeying - thus causing autofocus problems)

Expected behaviour

When Guiding is stopped (or dithering) neither instance of NINA, whilst Synchronised PHD2 is used, should be performing any type of image capture routine/image capture should be paused until guiding starts again.

Actual behaviour

A second instance of NINA will continue imaging whilst autofocus (PHD2 stopped) is occurring, causing waste captures.

[Stefan B]

This is not a bug, but a gap of the implementation. The Synchronized Dithering is only happening for Dithering.