Hi Ken,
Here is what happened this morning. Clouds came in around 2am. I manually aborted and reset sequence (preserved progress).
Confirmed the run cal frames setting is checked in both the sequence settings and SGP options.
I set my first incomplete target to Start capture at 3:41 am and end capture at 6:15 am
Second incomplete target set to end capture at 6:15 am.
Dark targets are checked (no start or end capture time defined).
PHD was open and not looping. I cannot remember if I had the gear connected or disconnected with 100% certainty, but I think it may have been disconnected because I may have dismissed a end sequence notification without clearing the run end of sequence options check box.
- Side note: The gear connected state of PHD has not been a problem for the most part, but I've found recently that depending on if I aborted during the initial begin sequence routines (guesswork by the status displayed: PHD calibration, resume autoguider, etc.) that when resuming, SGP doesn't seem to know that PHD was aborted from SGP and sends a command to dither expecting the autoguider to be running. Which creates an error message.
I click run sequence and I see the waiting for capture time to start status. I go to bed.
This morning I woke up and SGP was displaying a modal message box saying: "Sequence was aborted because the auto guider is required, but not running."
I clicked ok. End Sequence notification message popped, sequence ended, dark frames did not start.
So, I'm not sure where the instruction to do the calibration frames is skipped, but it could be something to do with PHD communication, or SGP not understanding that the sequence has failed.
I've uploaded the nights user.config (I stripped the top 9 lines, thought there may be license info there), sgp logs, sg_ui_config, the .sgf file, and both the phd guide logs and debug logs here:
https://drive.google.com/open?id=0B6jfyDXDePmma3RSQ2tuTlR1ZGs
As always thanks for your hardwork and the awesome program that SGP is! 