The topic I added earlier “Target Settings List/Editor” lists all the targets I imaged last night.
A sequence problem occurred after #1 and #2 finished running and #3 should have started.
#1 and #2 ran perfectly within the allowed Start/End times.
However, after #2 finished, instead of running #3 which was next in line, it reverted back to #1, which it ran for the next 1.7 hours (from 10:24pm to 12:13am) which allowed it to finish the total of 3 hours of frames that were set in the events. After finishing the remaining frames in #1, it then ran Target #3 from 12:19am to 12:36am.
The rest of the targets ran perfectly, until the last target which quit with a bogus Unsafe condition at 5:07:05am. Or so my graph of clouds and weather using the AAG_CloudWatcher tells me. Perfectly clear all night long. I can post the weather log if you would like.
Target #1: IC1396 Elephant,…Start: 7:30pm, End: 9:00pm (a total of 1.5 hours) Frame/Event counts add up to total time of 3 hrs, if there were no time limits.
Target #2: LBN529 Cave,…Start: 9:00pm, End: 10:10pm (a total of 1.2 hours) Frame/Event counts add up to total time of 3 hrs, if there were no time limits.
Target #3: NGC7000 North A…Start: 10:10pm, End: 12:40am (a total of 2.5 hours) Frame/Event counts add up to total time of 3 hrs, if there were no time limits.
Running 220.127.116.11. No target swapping was done after Target #2 started running.
A closely related problem which has happened many times with previous 2.4.3.x releases is that the sequencing rules do not honor the Start/End times if you run the sequence later in the night and 1 or more of the initial targets are already past their End time. They get run even though the time is past the set End time. If you need a log for this issue, I will do a new run to confirm this is still an issue.