I should probably know what this is but I am a little out of it right now. Is there a thread with more details on the issue you describe here?
yep - here
thanks
rob
@pfile, thx. This is fixed. Legacy behavior has been removed, sequence will abort and safety options will run, BUT no recovery will be attempted at this spot (this is the pre-sequence guider initialization and is not subject to normal, in-sequence recovery). Might be a good place to beef up in the future for folks who want to have a delayed start.
thanks. strange though because this happened in the middle of the night twice, so it could not have been pre-sequence. meaning, i started the sequence at maybe 10PM, successfully acquired multiple images, and then this happened sometime in the early morning hours.
rob
Continued for 3.0.0.1 here: