ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to monitor PXI CPU utilization?

Solved!
Go to solution
Does anybody know of a way to programatically monitor CPU utlization on a PXI controller through LabVIEW? I know that NI had a proprietary VI to monitor memory usage called rtgetmemorysummary.vi to monitor memory usage, and I want to do the same for CPU usage.
0 Kudos
Message 1 of 14
(5,482 Views)
bump
0 Kudos
Message 2 of 14
(5,451 Views)

If memory serves me, I was only able to do that by connecting a display to the CPU.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 3 of 14
(5,437 Views)
Solution
Accepted by topic author sgregor249

If you are speaking of a RT targer, then you can use

RT get CPU loads.vi

See here

 

Marco

Message 4 of 14
(5,436 Views)
Thanks MarcoMauri thats exactly what I needed. I looked around NIs site and found out this this VI only appears on the palette if you are coding under an RT target.
0 Kudos
Message 5 of 14
(5,424 Views)

This seems to only be available in LV 8.6+. My immediate needs are for LV 8.5, but this might prove useful for code that I need to support in 8.2 as well. Is there any way an NI applications engineer can backsave this for me? I see that it requires  ni_emb.dll and NI_Real-Time Target Support.vi. Shoot, on second thought I have a Main VI that runs both on windows systems and RT systems and introducing this to the windows system would cause the code to break. Perhaps I could use a conditional disable with target type to avoid this.

0 Kudos
Message 6 of 14
(5,411 Views)
Unfortunately this function is not supported in LV 8.5 and to downgrade it to previous versions would, short story, break a lot of things.  Do you have a hardware limitation for being unable to have LVRT 8.6 on your target?
National Instruments
Applications Engineer
0 Kudos
Message 7 of 14
(5,389 Views)

No hardware reason to not upcovert. It's more of a risk thing, plus it's not my decision.

 

The reason I wanted to log PXI CPU utilization was beacuse one of the PXIs in a 5 PXI system seems to randomly reboot about once a week. We've been replacing pieces of the system part by part(chassis, controller, cards) and verifying the electrical system(the only thing left is the PXI Power cable). I don't think it's the software because the same code runs on all 5 PXIs. The CPU utilization might be useful in getting to the bottom of this, but I doubt its the culprit. I would only argue for upgrading to LV 8.6 if we've exhausted all other options first.

0 Kudos
Message 8 of 14
(5,379 Views)

sgregor249 wrote:

No hardware reason to not upcovert. It's more of a risk thing, plus it's not my decision.

 

The reason I wanted to log PXI CPU utilization was beacuse one of the PXIs in a 5 PXI system seems to randomly reboot about once a week. We've been replacing pieces of the system part by part(chassis, controller, cards) and verifying the electrical system(the only thing left is the PXI Power cable). I don't think it's the software because the same code runs on all 5 PXIs. The CPU utilization might be useful in getting to the bottom of this, but I doubt its the culprit. I would only argue for upgrading to LV 8.6 if we've exhausted all other options first.


If that chassis is a RT target then that is one of the signatures of a memory leak. When you run out of memory in a RT app it reboots.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 9 of 14
(5,372 Views)
The RT machine is running a build. We have code to log memory utilization and it doesn't increase prior to the restart.
0 Kudos
Message 10 of 14
(5,363 Views)