Good to see, thanks for the update, I hope the weather improves for me, but I am working on a cooling solution at the moment so my rig is apart. I will get around to testing it later.
Contrary to my previous email, there is still a problem when running this with the simulators.
I set a scheduler job in the afternoon, to run from twilight, but it didn't start and I have just noticed that it seems to have scheduled it for the next day.
I am set to Melbourne, Australia which is currently in daylight savings time +11, AEDT.
I run a scheduled session starting after twilight to maintain the ASAP and the Twilight schedule. It was completed within the job constraint time minus 1 hour.
As it didn't complete the session it rescheduled it 2 days later. This confirms Pauls findings.
Most probably Australia only issue. Admittedly Daylight savings is not observed in every state. I know QLD and WA do not use Daylight saving. The rest I am not sure.
Malcolm
Last edit: 2 years 5 months ago by Malcolm Whinfield. Reason: Add little more information.
I reran this test yesterday, again using the simulators and I think it did actually wake up as instructed.
The problem, when I looked at the log displayed at the bottom was that it never completed a focus, it just kept trying, and so never captured any images, which I took to mean it did not wake up.
Of course, I was not actually watching what happened at the time.