This will probably remind the older amongst us of the Y2K bug :-)
Last night, I had set NINA to switch to a different target at exactly midnight. I put this in NINA as 00;00:00.
In the morning, I saw the sequence had failed at the switchover with the message
"2024-01-23T00:00:00.7835|ERROR|AscomDevice.cs|GetProperty|341|An unexpected exception occurred during GET of Telescope.UTCDate:
ASCOM.DriverException: Hour, Minute, and Second parameters describe an un-representable DateTime.
---> System.ArgumentOutOfRangeException: Hour, Minute, and Second parameters describe an un-representable DateTime."
On going to the AM5 logs, it says
"00:00:00.757 UTCDate Get Local time: 24:00:00"
So looks like NINA takes midnight as 00:00:00, while AM5 driver reports it as 24:00:00. NINA has no provision for 24:00:00. Hence the "unrepresentable" DateTime.
Request to ZWO team: Can you make midnight as 00:00:00 instead of 24:00:00. I think that would be more in line with general conventions.
00:00:01.051 --> :GG#
