Date
1 - 7 of 7
Daylight saving time glitch in goto positions
|
Joshua Hufford
Dave, I was responding to Dan, my idea was just for testing purposes. Josh On Mon, Nov 7, 2022 at 12:53 PM Dave Lane <dave@...> wrote: Thanks Dan - not easy to test for sure and it's not always clear on one of the two nights each year! In the spring I will try to remember to turn on all the logging! |
|
|
|
Thanks Dan - not easy to test for sure and it's not always clear on one of the two nights each year! In the spring I will try to remember to turn on all the logging!
Dave |
|
|
|
Hi Josh - that would be a workaround and does not work for automated telescopes where the operator is asleep :-)
--- Dave |
|
|
|
Joshua Hufford
Maybe I'm missing something but could you disconnect a PC from the internet and then just change the date/time to right before when DST starts and stops? Josh On Mon, Nov 7, 2022 at 9:51 AM Dan Gray <grayarea@...> wrote:
|
|
|
|
Dan Gray
Hi Dave, I looked at my code this morning, it looks like I use DateTime.Now, but there is a place I see it could be wrong by 60 minutes for one loop time. It could also be something in pointxp. This is something I can only test 2 x per year! Might be hard. When I get to working on SiTEchExe again, I'll see if I can figure out a way to test my part of the code (not PointXP). Dan
|
|
|
|
SIMON
I've been using goto systems for over 23 years, and in all that time I've kept them on UT/GMT. Local time is so fickle it is best avoided, so my advice is ditch the local time for UT.
(Not saying the problem shouldn't be fixed)
|
|
|
|
Hi Dan,
I am finally reporting this Daylight saving time change glitch which I have noticed for the past few years. I have noticed this with 2 different mounts and different versions of sitechexe (currently 0.92g). What happens is during the night of the daylight saving change (spring or fall), approximately when the time zone (UT-Local) changes subsequent goto positions are one hour in RA off. In the case of last night, they are one hour less. This was verified by reviewing my logs of where the telescope was sent and then blind solving three separate sync images for the telescope's position. Unfortunately, sitechexe logs were not enabled last night. What is interesting is that this problem happened last night not after 2am local time when the computer time switched from 2am to 1am, but an hour or so earlier. The fact that this happens before the computer time switches make me think sitechexe is doing its own UT-Local conversions rather than asking the O/S. Needless to say, it blows-away the rest of the night. Has anyone else noticed this? --- Dave |
|
|