7 hours missing between DIAdem and LabVIEW time??

[Andreas]

Hi all,

I read in the context help of "DIAdem Write Header file.vi" (All Channel info Arry-> type):

""Bear in mind that LabVIEW timestamps (the number of seconds since 1904) are different than DIAdem timestamps (the number of seconds since 0000). To convert a LabVIEW timestamp into a DIAdem timestamp, just add 60084266400 to the LabVIEW timestamp.""

But if I do this (add the mentioned value to a LabVIEW timestamp converted into double) the imported data in DIAdem shows 7 hours less.
Where do these seven hours come from? I'm in Germany, we currently don't have summer-time which could cause a 1 hour delay. And world-time, afaik, is Greenwich time and could cause a 1 hour delay to our local time, too.
Still 6 ho
urs missing...
Am I doing anything wrong or what's the explanation?

Andreas

P.S.: If you know what happens in regard to summer-time change (can I forget about it?), please tell me..

[Otmar]

Hi Andreas,

Austin, TX has a seven hour time difference to Germany (Central US time vs. Central European Time). I guess the help system is is referring to Austin time.

To get the correct time for Central Europe, please add 25200 to the timestamp in addition to what was described in the help system (total number should be 60084291600).

If your system updates to summer time automatically (most Windows version do that for you), you should not have to change this number ever).

Please let me know if this is working for you.

Otmar

[Andreas]

Thanks, Otmar, herzlichen Dank,

it works fine, but help system should be corrected in coming versions...

Andreas

[Brad_Turpin]

Hi Andreas,

What time zone was the data taken in (using LabVIEW), and what time zone are you in when you look at it? The issue here is that LabVIEW by default stores absolute time and DIAdem stores relative time, geographically speaking. If you use the "DIAdem File Write.VI" to record the data, look at the "Time Parameters" INPUT at the top RIGHT of the VI. You have 2 parameters to choose from: "store absolute time" and "correct for time zone". Do let us know if those don't take care of the conversion for you the way you want it.

Cheers,
Brad

[Andreas]

Hi Brad,

I didn't notice any effect of these two parameters.

Please have a look at the attached file...

Regards,

Andreas

[Andreas]

... and I suppose this is correct, because I'm only sending "normal" data to DIAdem (seconds). In DIAdem I change the channel attribute to "time channel".
I think these two parameters do only effect the optional time channel which I'm not using.

Andreas

[Brad_Turpin]

Hi Andreas,

You're right that parameter only affects the implicit time channel, and I should have asked if that was what you were talking about. Dig down into the "DIAdem File Write.vi" and you will find "TimeZoneCorrection.vi", which is the vi these parameters use. You can use that vi yourself to manipulate your time values in LabVIEW prior to sending them to the "DIAdem File Write.vi".

Let me know if that doesn't do it for you,
Brad

[Andreas]

Yes, thanks, that's it!
I use the "Convert LV Time to DDTime.vi", and it does all I want it to do...


Best regards,
Andreas