In the current implementation it could happen, that guiding problems bring the Scheduler and the Capture module out of sync. If capturing is suspended, a subsequent guiding error remains undetected. As a consequence, capturing remains suspended and guiding will not be restarted.
This situation is not untypical during a night with high cirrus that occasionally disturb guiding. First they lead to guiding deviations and from time to time to lost guiding stars. In such nights it could happen, that a single cirrus cloud interrupts the entire capturing.
In order to cover this, the behaviour of Capture and Scheduler is changed:
- Aborted guiding leads to aborted capturing even when capturing is already suspended.
- Repeated guiding problems lead to jobs being aborted, not to be marked with errors.
- In order to avoid aborted jobs to be immediately restarted, the scheduler considers aborted jobs for restart, if all potentially executable jobs have been aborted.
Additionally, two other weaknesses have been resolved:
- Removed restarting aborted capture when guiding resumes, since it conflicts with the Scheduler.
- In the PHD2 adapter, connectEquipment() may be called arbirtrarily often when equipment is connected.