05-15-2012 03:16 AM
Hi,
Before the read loop I send "initalize" to the display loop, and that initalizes the array. In the subvi I obtain the queue and send it the data and the "update display" state. The display loop is a queued state machine. Thanks for the suggestion, though!
My colleagues have also seen a problem with error probes in connection to hardware. In may cases the probes slow down the hardware. When I consulted by phone with our local NI support, they recommended not to use probes in data acquisition commands, rather to use indicators.
The original error was solved by increasing the hardware buffer size, even though according to the hardware support this should not be necessary. However, it seems that their guidelines are not reliable over long periods of time, or that LabView is slower than they thought.
If there is a method of prioritizing a labview thread over others, it would still help, but the problem seems to be solved.
Thanks for all your help!
Danielle
05-15-2012 04:52 PM
The only options you have for priotization in Windows are through the Task Manager, specifically the Processes tab. From there you can find LabVIEW.exe and right click >> set priority, to give LabVIEW higher priority over other processes. I do not know of a method for prioritizing individual components within your LabVIEW code, though.
Glad to hear things are functioning.
Regards,