10-24-2008 12:35 AM
10-24-2008 01:58 AM
This usually happens when you have a loop with no wait, because then it tries to run as fast as possible. Usually, TCP reads and event structures have some delay built in, so if I had to guess, I would guess it was the TCP writing loop. The easiest solution is to add a simple wait command to each loop, even of 0 or 1 ms.
As for a more general answer, if you have the professional version of LabVIEW, you should have some profiling tools in the Tools menu. You can also do debugging by placing case structures around pieces of your code and disabling and enabling them while monitoring your CPU usage. When it drops, you can usually assume you've disabled the culprit and investigate further.
10-24-2008 03:54 AM
Hi 5thGen,
You can get a snap shot of the VI's memory and performance usage by using the Performance and Memory window. You can find this window in Tools->Profile->Performance and Memory. There are also two other tools there which may be useful to you when evaluating your VIs performance.
Hope this helps,
10-24-2008 10:56 AM