This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

CPU and Memory Usage Not Visible in NI Distributed System Manager

Updated Mar 15, 2023

Reported In

Software

  • LabVIEW Real-Time Module

Driver

  • NI-RIO

Issue Details

I want to monitor the CPU and memory usage of a network-connected real-time controller using NI Distributed System Manager. I selected the real-time target of interest from the tree in the left-hand window and then made sure to enable Auto View by selecting View»Auto View. I expected to see the CPU/Memory tab, but it did not show up. How can I view the CPU and memory usage of my real-time controller?

Solution

You need to install System State Publisher in your controller, which publishes CPU and memory usage to NI Distributed System Manager:
1. Open Measurement & Automation Explorer. You can do this by selecting Start»Programs»National Instruments»Measurement & Automation.
2. Expand Remote Systems in the Configuration window.
3. Select your remote system from the configuration tree. Right-click Software and select Add/Remove Software.
4. Once the LabVIEW Real-Time Software Wizard panel is opened, click System State Publisher and select Install the Feature. Then, click Next as seen in the image below.
 
5. Once the controller reboots, access the NI Distributed System Manager by navigating to Start»Programs»National Instruments»NI Distributed System Manager. Add your controller by right-clicking the My Systems folder and selecting Add System. Type in your controller's IP address in the pop-up window. 
 
​​​​​​
 
 
6. Once your controller has been added, you will be able to see the CPU/Memory tab in Distributed System Manager.
 
 

Additional Information

This issue may also occur if the real-time target has inconsistent IP settings . Please check NI MAX to see if this issue is occurring and if so, use the linked article to ramify that error. 

This issue might also occur in some targets if the Embedded UI is enabled on it. This is a known issue 
and the current workaround is to disable the Embedded UI in the target and to read the CPI and Memory using one of the alternative options shown in this article:   Monitoring CPU and Memory Usage on Real-Time Embedded Targets