Real-Time Measurement and Control

cancel
Showing results for 
Search instead for 
Did you mean: 

RT Sys Manager shows 100% CPU always

When using the RT System Manager, I have found that the CPU usage is always 100% - even when all loaded VIs are idle. The chart is segmented with yellow (normal priority) tasks and white (low priority tasks) - yellow on top.
0 Kudos
Message 1 of 3
(3,647 Views)
Tommy,

What sort of target are you using?

If it is a FieldPoint or Compact FieldPoint RT Controller, this is the normal operation of the module. With FieldPoint RT controllers, there are two programs running simultaneously; the LabVIEW Run-Time Engine and the IA Control Environment. The LabVIEW Run-Time engine is the portion that runs any LabVIEW code that you develop and download. The IA Control Environment is the program that reads/writes to the IO and publishes the data over ethernet (providing all NI Logos protocol based communication). The IA Control Environment is set to run at normal or low priority so that it shares time with your application (running in the LabVIEW Run-Time Engine).

You can reduce the time being used by the IA Control Environment by setting the Pause parameter to a value other than 0 ms (valid values are 0 - 1000 ms). By setting the Pause parameter to a non-zero value, you place the control environment to sleep. This will slow down the rate at which new values are published and updates are applied. For example, setting the Pause parameter to 1000 ms means that the channels will be read and published over the network at 1000 ms intervals, potentially causing a delay in the notification of value changes, or the application of new values from write commands that were sent to the module. Note that FieldPoint Reads/Writes performed using the FieldPoint VIs running on code that was downloaded into the module is not effected by the Pause parameter. Alternatively, you can increase the thread priority of your downloaded VIs if you need the processor to spend more time on the LabVIEW code and less on the IA Control Environment.

Regards,
Aaron
LabVIEW Champion, CLA, CPI
Message 2 of 3
(3,643 Views)
This was extremely helpful. I had already found the priority change on my own and that produced significant results. The information on changes to the IA pause parameter will prove just as paramount. I am certain.

Again, thanks. I am finding these forums very reassuring in terms of our company's commitment to the NI product and LabView.

TommyH
0 Kudos
Message 3 of 3
(3,641 Views)