TDMS data unreadable due to windows language settings??

[JeroenBK]

Hello Kevin,

I thought it would only be the display.

And yes the error is -20312 and I think is caused by a VI that expects a data array with content. At least that is what this page is telling me:

http://zone.ni.com/reference/en-XX/help/371361R-01/lverror/analysis_error_codes/

Opening the tdms file on my own pc gives no issues at all, everything works.

[Kevin_Price]

I'm afraid I have no other ideas.  Without code & data (or spare time to do anything with code & data), it's tough to guess.  I suppose I'd start by trying to figure out which function throws the error initially, then start tracing data from there, always thinking "how might 1 PC do something different here than 29 others?"

If you *can* post code & data, please do.  I won't have time to investigate, but someone else may...

-Kevin P

[JeroenBK]

Hello all,

I've been able to get my hands on the computer that is giving all the trouble and I found the origin of the error. It is something in the time stamp after all! I have an array with several start and end timestamps of tests that have been performed. If the test was not executed the stamps remain empty, so the timestamp should be 0 when converted to a double. However on that one laptop the double gives me -10800 as a value. Can anybody explain this? I've included the VI (that will not run on its own, sorry), the array is the "Initial test DataMarkers in".

Best regards,

Jeroen 

[JeroenBK]

---

@JeroenBK wrote:

Hello all,

I've been able to get my hands on the computer that is giving all the trouble and I found the origin of the error. It is something in the time stamp after all! I have an array with several start and end timestamps of tests that have been performed. If the test was not executed the stamps remain empty, so the timestamp should be 0 when converted to a double. However on that one laptop the double gives me -10800 as a value. Can anybody explain this? I've included the VI (that will not run on its own, sorry), the array is the "Initial test DataMarkers in".

Best regards,

Jeroen 

---

Update on the matter:

I think I found what is causing it, sort of. It seems to be an issue with the time zone, the laptop in question was running on Saudi Arabian local time (UTC+3), while we are running on Dutch time (UTC+1), so calculated: UTC+1 = 3600s UTC+3 = 10800s. However what is still strange is the fact that our Canadian colleagues don't seem to have any problems with this. In fact I can explain the difference but I don't understand why it is happening. You would expect that for the program the local time is the only time, why is one pc still using "our" local time?

And finally how can I solve this matter in a correct way?

Best regards,

Jeroen