LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Time stamp constant changes

Solved!
Go to solution

Yep.  I forgot to mention that as well.  You have to close LabVIEW and restart for the time zone change to take effect.

 

Fortunately that won't be a problem for me since the time zone with the system we're delivering will always be UTC.

 

Thanks again,

Mark

0 Kudos
Message 11 of 15
(586 Views)

I figured that's why you said the original program worked since the time zone change never took effect.  I stumbled across that issue in doing my debugging making it take longer than I had anticipated.  Oh well.

0 Kudos
Message 12 of 15
(585 Views)

No, it was because I was looking at the end of the DBL values instead of the middle.  I saw the end was correct and missing the 3600 second offset ( or more depending on the time zone).

0 Kudos
Message 13 of 15
(583 Views)

Bad guess on my part. 

Anyway,  all issues are resolved.

 

Thanks again,

Mark

0 Kudos
Message 14 of 15
(581 Views)

The most common problem is in storing and retrieving timestamp data. If you work with databases or XML, the most universal format is ISO-8601. 

 

You can create and read this format using the "Format into String" and "Scan from String" functions using the following format string:

 

%^<%Y-%m-%dT%H:%M:%S%3uZ>T

 

 

 

 

 

 

 

 


Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.

"You are what you don't automate"
Inplaceness is synonymous with insidiousness

0 Kudos
Message 15 of 15
(575 Views)