cRIO Cannot Be Found in NI-MAX After Real-Time Executable Crashed

Updated Feb 26, 2019

Reported In

Hardware

  • CompactRIO Controller

Software

  • Measurement & Automation Explorer (MAX)

Issue Details

I have a real-time system with a startup executable (.rtexe) embedded on the controller. The real-time executable appears to have crashed. Now my cRIO controller is no longer detected by NI-MAX. Restarting the device does not solve the problem.

Solution

  1.  If you have not already done so, try restarting your device
  2. Check the Status LED of your cRIO device according to this article or the manual of the device. If the Status LED indicates that the device has not booted into NI Linux Real-Time, force the cRIO to boot into the safe mode. Refer to the device manual on how to boot into the safe mode.
  3.  Refresh your device list in NI-MAX by pressing F5.
  4. Reformat your RT controller or try to manually uninstall/install the Software on your RT-System
  5. Try the troubleshooting guide to get the device to show up in NI-MAX.


 

Additional Information

If the cRIO cannot boot into the NI Linux Real-Time it cannot be detected by NI-MAX. By forcing the device into the safe-mode only the most essential components for the NI Linux Real-Time are loaded. This allows the detection of the cRIO by NI-MAX.

WAS THIS ARTICLE HELPFUL?

Not Helpful