So back to this, with particular questions about PHD2.
Since starting to use the scheduler with repeated ~1-hour jobs set to re-try on failure, I have had a few partly cloudy nights but never yet had PHD2 act in a way that triggered the sequence job to abort/restart. Instead, capture aborts (because guiding is out of limits), PHD2 continues to "guide" even though it can see only a few, if any, stars. When the cloud passes by and guiding gets back within limits, capture restarts. That is fine, except I think the point of abort/restart is to allow a re-alignment to deal with the mount drifting off target during the cloudy break.
Is there a PHD2 setting I should be looking for to help trigger the scheduler to abort the job?
Last night I had a particularly vexing PHD2 behavior with clouds. The early part of the night had several episodes of cloudy crummy guiding, but I was getting enough successful 4-minute exposures to keep going. Tried to get some sleep. Woke up to discover this:
The guide camera view showed that there were not currently clouds, but the guide star had a huge HFR. I guess it latched onto a really bright star when that was what was visible, and never let go. I stopped and restarted guiding, and it turned into this:
If I had not woken up and checked, I assume it would have continued trying to guide on that same bright star.
Read More...