Hi,
This weekend, when we switched back to standard time, SGPro misbehaved: the frame being integrated when the time change occurred started reporting a long time to completion. I suspect my 5 minute sub became a 65 minute sub. I had to abort the sequence and restart it.
A friend also running SGPro at the same time had similar problems.
Anyone else see weird behavior at 2am Sunday morning?
Richard
This was using the latest release.
Yes, I had the same thing with alpha release 4.5.1445.
This has been an on-going problem. Search for daylight savings in the posts and you see ones from several years ago. The image being integrated when the time changes has an hour added to its time, and ones being downloaded (I assume in the spring) when the time changes give an error about “too long to download”.
I experienced the same thing. A session was running and when I checked it this morning it was aborted. In the SGP console window the end entries showed an autofocus completed successfully then quite a few minutes afterwards a red window error indicated the autofocus timed out and the session aborted and ran the end of sequence shutdown. Checking the SGP raw log file, it happened at the same time the PC clocks automatically change at 2AM.
Mike
Hi folks,
I am the friend who ‘rsewards/Richard’ referenced in his post about unexpected time-change misbehaviour.
While imaging/collecting data I witnessed the SGP interface tell me that several thousand seconds had just been added to my sub.
In addition, my auto-focus, on next use, would not work. After multiple tries at getting autofocus to work again, I ended up exiting SGP – in mid data acquisition in my observatory – and remounted SGP. All was good then.
Thanks
Jeff Booth