Get Time Date String is one hour off from Get Time/Date in Seconds

[viScience]

Upon upgrading to LV2010 I noticed that my cRIO time (which I can set remotely) is always one hour ahead of the time that I programmatically set.

Some previous discussions mentioned that the Get Time Date in Seconds function will display with DST sensitivity, so I also placed a Get Time Date string vi which does return the correct time.

In both cases I am just probing wires on the RT code (no UI indicators involved).  I should mention that I also have NI timesync installed but am not currently connected to my IEEE1588 PTP master so no background clock sync is occuring.  Also noticed that MAX is able to get the correct time from the cRIO.  Is this a bug in LV2010 or is this the way it always worked but perhaps I never noticed it since most of the time I am sync'd to GPS time.

I also noticed that my NSV timestamps are also 1 hour off and are showing up in my citadel DB with this incorrect timestamp.

BTW, both my cRIO and Windows PC are set to Central Time with the PC set to adjust for daylight savings time.

[viScience]

Ok, I think I have an answer to my own question.  After turning off DST and restarting LV I now am getting the correct time.  I still do not really understand why turning off DST on my PC

affects a vi being run on my cRIO.  When I set the cRIO time I am using the RT Set Time and Date vi which takes a simple numeric cluster as an input.  In both cases (DST on and off) I

observed the same cluster data being send into the RT Set Time and Date vi but yet reading out the time using the Get Time and Date in seconds changes depending on the setting of my PC???

[Cyrille_D.]

It seems there are some "hidden technical features" built in the time/date indicators.

http://forums.ni.com/t5/Real-Time-Measurement-and/Confused-about-setting-time-on-cRIO/td-p/891907

I also get this 1-hour off (PST8PDT), but it returns the right time when set on UTC.