LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Timestamp and Daqmx Read is reading "0" every 10 seconds?

This is my first LabVIEW project. I need to read 9 different sensors simultaneously and log to a .csv on command. Can anyone help me limit the timestamps on the .csv? And does anyone know why my data is reading "0" every 10 seconds in my datasheet? Any help would be greatly appreciated

0 Kudos
Message 1 of 3
(1,700 Views)

Hi mjm,

 


@mjm937 wrote:

And does anyone know why my data is reading "0" every 10 seconds in my datasheet?


While I don't have LabVIEW NXG installed I still can examine your CSV file.

Your error description is wrong: those dropout don't occur "every 10 seconds", they occur at irregular intervals:

 

2.001,387.219,2.001,93.562,2.001,95.869,2.001,96.421,2.001,NaN,2.001,-0.120,2.001,-0.101,2.001,0.122,2.001,200.321
2.002,0.000,2.002,0.000,2.002,0.000,2.002,0.000,2.002,0.000,2.002,0.000,2.002,0.000,2.002,0.000,2.002,202.124
2.002,389.516,2.002,94.578,2.002,96.661,2.002,95.662,2.002,NaN,2.002,-0.010,2.002,-0.082,2.002,NaN,2.003,204.665

11.000,386.399,11.000,366.445,11.000,94.068,11.000,125.515,11.000,0.112,11.000,1.869,11.000,3.388,11.000,1.689,10.999,180.976
11.001,0.000,11.001,0.000,11.001,0.000,11.001,0.000,11.001,0.000,11.001,0.000,11.001,0.000,11.001,0.000,11.000,183.302
11.001,383.507,11.001,367.819,11.001,93.813,11.001,125.470,11.001,0.075,11.001,2.671,11.001,1.303,11.001,1.823,11.001,184.500

14.000,381.712,14.000,378.075,14.000,94.359,14.000,130.218,14.000,0.064,14.000,3.023,14.000,2.519,14.000,1.696,13.999,172.594
14.001,0.000,14.001,0.000,14.001,0.000,14.001,0.000,14.001,0.000,14.001,0.000,14.001,0.000,14.001,0.000,14.000,174.141
14.001,383.825,14.001,378.064,14.001,95.110,14.001,129.172,14.001,0.071,14.001,3.299,14.001,4.163,14.001,1.762,14.001,177.082

 

The first occurances are at 2s, 11s, 14s. The last columns still shows non-zero data…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 3
(1,651 Views)

Thanks GerdW. When I plotted the data on excel those times didn't show, thanks for pointing them out. 

 

Also, this issue isn't due to DAQ or sensors. This behavior was happening yesterday in my test vi as well? If that helps clear anything up.

0 Kudos
Message 3 of 3
(1,623 Views)