Anybody know if NINA gracefully handles the time change during the middle of night? I'd hate to have my mount try to track an additional hour past the meridian.
Thanks,
Arnie
Posted 02 November 2024 - 06:25 PM
Anybody know if NINA gracefully handles the time change during the middle of night? I'd hate to have my mount try to track an additional hour past the meridian.
Thanks,
Arnie
Posted 02 November 2024 - 09:36 PM
I have no idea, but the proliferation of computer-controlled equipment is one more reason we need to get rid of these time changes.
It is technically easy for NINA to avoid the problem -- the computer can deliver the time in UTC, for example -- but I don't know what it does.
Posted 02 November 2024 - 10:35 PM
I have no idea, but the proliferation of computer-controlled equipment is one more reason we need to get rid of these time changes.
It is technically easy for NINA to avoid the problem -- the computer can deliver the time in UTC, for example -- but I don't know what it does.
Thanks for the suggestion. Unfortunately, the weather has tanked for tonight so it is now a moot point. I'll see what happens six months from now.
Arnie
Posted 03 November 2024 - 02:38 AM
So, "AF After Time" trigger did not operate a planned. I have it set to autofocus after 30 minutes and it skipped an hours worth. It must calculate the clock time of the next AF and not go off of actual duration.
"Loop for Time Span" was set for 7 hours. I started imaging at 19:43 Eastern Daylight Time, plus 7 hours should have tripped at 01:43 Eastern Standard Time. Loop condition was not met yet. Once again, it calculated a clock time and not actual duration.
Oh well, no harm done here, just an extra hour on M31.
Posted 03 November 2024 - 09:47 AM
So, "AF After Time" trigger did not operate a planned. I have it set to autofocus after 30 minutes and it skipped an hours worth. It must calculate the clock time of the next AF and not go off of actual duration.
"Loop for Time Span" was set for 7 hours. I started imaging at 19:43 Eastern Daylight Time, plus 7 hours should have tripped at 01:43 Eastern Standard Time. Loop condition was not met yet. Once again, it calculated a clock time and not actual duration.
Oh well, no harm done here, just an extra hour on M31.
Thanks for the bug report. We'll fix this.
![]() Cloudy Nights LLC Cloudy Nights Sponsor: Astronomics |