Get Trace List - Last Timestamp returns a time that is one hour behind

[Mattjk]

Hello,

I am using the DSC module for creating traces.  I need the last timestamp of a trace.  When I view the trace via MAX (export to text file) I can see all timestamps in that trace.  When I use the "Get Trace List.vi" it returns time that is one hour behind.  I would just compensate an hour but I thought I seen that it compensates back after writing again.  I have some complex code and after thinking about it, I think that the "Get Trace List.vi" should work.  I tried fooling with the timezone but this makes no difference.  A solution I just thought of now is to use the read trace but use a most recent time interval.  In my case I don't know the most recent time but if I got data from the last month and used the array max/min on the incomming timestamp array; this would work.  OK, so I figured out a work around but maybe someone knows something about why this Last timestamp is an hour off?

Thanks

Matt

[altenbach · Accepted solution]

You did not include any essential subVIs, but I suspect an issue with the "Daylight Saving Time" setting.

[Mattjk]

Yes it was daylight savings time.  I guess when you write a timestamp to citadel it adjusts one hour when extracting to text file as well as when you read it back.  So, you write a timestamp and then when you read it back it is one hour behind.  It really screws things up when you use the read in timestamp to generate the next timestamp.

Solution:

Uncheck "Automatically adjust clock for daylight savings time" in the windows date and time properties.