Why is my cRIO time one hour ahead?

[ChrisFarmerWIS]

Hi there,

I am running an application on a cRIO-9012, using LabVIEW 8.5.1, and the time on it seems to be one hour ahead.

Using NI-MAX 4.4.1f0, I have set the timezone to (GMT +10) Eastern Australia, Guam, Hobart. The "Automatically adjust target clock for daylight saving changes" button is greyed out and unselected. The Locale control is also greyed out.

FTPing onto the cRIO RT controller, I can look at my log files, and see that the files were created one hour ahead of time.  The timestamp inside the files also indicates time is one hour ahead.

I recall having many difficulties with the cRIO timebase when I last used it with LabVIEW 7.1 (in 2005/2006).  I eventually got around it by manually setting the data and time using the RT Set Date and Time.vi.  I'm writing to see if there is an easier way, as it makes sense that setting it up in NI-MAX should be sufficient!

Any help would be greatly appreciated!

[Aashish_M]

Hey Christopher,

I have faced the same problem as well and I use RT Set Date and Time.vi to work around it. For more details on this issue, please do refer to VxWorks Targets Do Not Honor New Daylight Savings Time Rules. This article mentions that VxWorks targets do not comply with the latest rules for Daylight Savings Time.

Hopefully this helps!!