LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Timed-Loop Fininshes Late & Problem Getting Stated with RT Execution Trace Toolkit

Hello everyone,

 

I have a real-time application in which a 100Hz timed-loop is used for temperature data acquisition. The DAQ card is a PCIe6351 board and a desktop PC has been converted into a RT target.

 

Now I run into two problems. The first one is that; if every 500 values are to be sampled at the rate of 100Ks/s during each cycle, about 30% CPU is being used. However, when number of samples required during a loop is increased to above 550, the code begins to report finishing late, and CPU loading decreases!  (Theoretically data acquisition only takes 5.5ms).  In the 500 samples per loop case, the VI Profiler indicates, for example, for 268 runs (indicating 2680ms in total) the total execution time for the vi on the RT target is 1096.8ms, seemingly in agreement with the CPU loading approximately. So what is the problem? Do I make some mistakes?

 

The second one is, when I try to analyze the code with Real-Time Execution Trace Toolkit, the VIs demand specifying "the path to the trace session file on the RT target", but it seems that I fail to specify a path on the RT target. Maybe I have misunderstanding with the help document, but what is the correct way to do?

 

The files are attached. Thank you in advance if anyone can give your advice.

 

Su

Download All
0 Kudos
Message 1 of 2
(2,486 Views)

I am sorry some spelling mistakes happened in the title.

0 Kudos
Message 2 of 2
(2,466 Views)