LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

windows clock

Highlighted
I am experiencing a slowing down of the windows clock on two separate
LabVIEW vi's. The two vi's use different daq boards (PC TIO 10 and 4351).
I don't have any other software running. Has anyone encountered this?
Is there a fix?
0 Kudos
Message 1 of 3
(2,405 Views)
Highlighted
The windows clock is very unreliable for anything more accurate than a minute.
Things like mouse events, key press', screen savers, etc. can throw windows
timing way off. Also, optimizing your program could improve performance.
Things like declaring constants outside of loops rather than inside, limiting
the number of locals and globals, etc. On zone.ni.com there are some interesting
articles about writing more efficient LabVIEW code. For accurate timing it
is not wise to rely on windows, it would be better to use hardware timing
or look into LabVIEW RT (Real Time).

"monte sula" wrote:
>>I am experiencing a slowing down of the windows clock on two separate >LabVIEW
vi's. The two vi's use different daq boards (PC TIO 10 and 4351).>I don't
have any oth
er software running. Has anyone encountered this?>Is there a
fix?>
0 Kudos
Message 2 of 3
(2,405 Views)
Highlighted
Monte Sula didn't say what version of Windows he was using.

Win2000 is more accurate than a minute! I've found that several Dells running LV code or executables are stable to about 2 sec / day.

If your clock should be stabilized to within about 1 sec, consider Dimension 4 from www.thinkman.com ... let this run periodically to sync time to the Internet.

Mark
0 Kudos
Message 3 of 3
(2,405 Views)