LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Timestamp is not accurate

Hi,
 
im my program i want to put a timestamp on every measured value, so I log after every acquisition the time with the "Get Date" function. The result was the timestamp has only a accuracy about 16ms, witch ist not admissible for my application. (see the picture of a simplified program).
 
My question is now:
 
Why has the timestamp / "getDate" such a miserable accuracy ?
How can work around this problem? I think there must be a way, because the "Tick Count" works quite well!
 
Thank you
 
M.Tiedje
0 Kudos
Message 1 of 2
(2,669 Views)

hi there

your systems has two clocks:

system clock: large range (years), but poor resolution
processor ticks: rather small range (2^32 ms ~ 50 days), but good resolution

you can mix both clocks: get the start of your measurement with "Get Date/Time in Seconds" and add the number of milliseconds since start of measurement (subtract "Tick Count (ms)" values).

 

 

Best regards
chris

CL(A)Dly bending G-Force with LabVIEW

famous last words: "oh my god, it is full of stars!"
0 Kudos
Message 2 of 2
(2,665 Views)