Hi Eric and Jasem,
I came across a new idiosyncracy in the scheduler: When I program a specific target and I set it to start ASAP it will work fine ONLY if I start the scheduler BEFORE astronomical twilight allows it to run (it goes to sleep until then). The same settings will no longer work once the earliest startup time defined by astronomical twilight has past. In that case the scheduler will tell me that the job is invalid, because startup time has passed (by anything between 0 and 3 seconds, depending on how fast the scheduler reacts to the push of the start button).
I would think that all that is required is to program a 10 second delay, i.e. add 10 s to the actual time at the moment the scheduler is started when set for ASAP. The only workaround I have found so far is to manually program a startup time with a delay added, but for that I need to sit at the computer and it is laborious to do if I need to restart the scheduler for any number of reasons, like the focuser failing or the guide module not finding a guide start right away.
Attached the log from 2 nights ago, not sure how informative they are. I had to add manual startup times between 2215h and ~2240h local time, because of the above described past startup time issue.
Please let me know your thoughts,
Jo
PS: Attachment was too large, here link for download: www.dropbox.com/sh/x6qa5fp1pv54i3x/AABWK...Zu-oxlNawATBt7a?dl=0
I came across a new idiosyncracy in the scheduler: When I program a specific target and I set it to start ASAP it will work fine ONLY if I start the scheduler BEFORE astronomical twilight allows it to run (it goes to sleep until then). The same settings will no longer work once the earliest startup time defined by astronomical twilight has past. In that case the scheduler will tell me that the job is invalid, because startup time has passed (by anything between 0 and 3 seconds, depending on how fast the scheduler reacts to the push of the start button).
I would think that all that is required is to program a 10 second delay, i.e. add 10 s to the actual time at the moment the scheduler is started when set for ASAP. The only workaround I have found so far is to manually program a startup time with a delay added, but for that I need to sit at the computer and it is laborious to do if I need to restart the scheduler for any number of reasons, like the focuser failing or the guide module not finding a guide start right away.
Attached the log from 2 nights ago, not sure how informative they are. I had to add manual startup times between 2215h and ~2240h local time, because of the above described past startup time issue.
Please let me know your thoughts,
Jo
PS: Attachment was too large, here link for download: www.dropbox.com/sh/x6qa5fp1pv54i3x/AABWK...Zu-oxlNawATBt7a?dl=0