Issue Details
The cRIO is connected to the network, but it cannot be detected in InsightCM.
Solution
Follow the steps below to diagnose and restore network connectivity between the cRIO and InsightCM.
1. Verify cRIO boot status using the Status LEDs
Before troubleshooting network settings, confirm that the cRIO is booting correctly.
- Observe the Status LED behavior on the controller.
- Compare the LED state with the official Status LED behavior table.
- If the LEDs indicate a boot or hardware issue, resolve that condition before continuing.
| LED Color/Pattern | Indication |
| Yellow, Blinks twice and pauses |
The cRIO is in safe mode. Software is not installed, which is the factory default state, or software has been improperly installed on the cRIO. An error can occur when an attempt to upgrade the software is interrupted. Reinstall software on the cRIO. Refer to Installing Software on the Controller for information about installing software on the cRIO. |
| Yellow, Blinks three times and pauses |
The cRIO is in user-directed safe mode, or the cRIO is in install mode to indicate that software is currently being installed. This pattern may also indicate that the user has forced the cRIO to boot into safe mode by pressing the reset button for longer than five seconds or by enabling safe mode in MAX. Refer to RESET Button for information about safe mode. |
| Yellow, Blinks four times and pauses | The cRIO is in safe mode. The software has crashed twice without rebooting or cycling power between crashes. |
| Yellow, Continuously blinks | The cRIO has not booted into NI Linux Real-Time. The cRIO either booted into an unsupported operating system, was interrupted during the boot process, or detected an unrecoverable software error. |
| Yellow, On momentarily | The cRIO is booting. No action required. |
| Red, Continuously blinks | Indicates a hardware error. An internal power supply has failed. Check front-panel I/O and C Series module connections for shorts. Remove any shorts and cycle power the cRIO. If the problem persists, contact NI. |
| Red, Solid | The cRIO internal temperature has exceeded a critical threshold. Ensure the ambient operating temperature does not exceed the specified operating temperature. If the problem persists, contact NI. |
| Off | The cRIO is in run mode. Software is installed and the operating system is running. |
2. USB connection method
-
Identify the IP address of the host computer using ipconfig (CMD) or Windows System Information.
-
Connect the cRIO using a USB Type‑C to USB Type‑A data cable on the “Device/Console Out” or “Dual Role” port.
- The USB driver assigns the cRIO an IP address in the 172.22.11.x range.
- Open NI MAX and expand Remote Systems.
- Select the cRIO and open the Network Settings tab.
- Configure IPv4 settings and reboot the controller if changes are made.
3. Ethernet connection method
- Connect an Ethernet cable from PORT0 on the cRIO to the host computer.
- Check for the device in NI MAX under Remote Systems.
- If not detected, reset the network settings.
4. Reset the cRIO network settings
- Hold the RESET button for 5 seconds and release.
-
Hold the RESET button again for 5 seconds to reset network adapters to DHCP.
5. Resolve “Connected – Inconsistent IP Settings” in NI MAX
NI MAX identifies a remote system as "Connected - Inconsistent IP Settings" when the RT target and the host PC are on different subnets. For example, the Ethernet adapter of the host PC is configured as Link-Local (169.254.x.x) while the RT Ethernet adapter is configured as static with the IP address 10.x.x.x.
To fix this problem follow the steps from the NI KB document.
Inconsistent IP Settings" When Using a Real-Time Target in NI MAX
Related Articles
- Controller Not Communicating Over Network
- Troubleshooting Network Connectivity
- cRIO Status LED Reference
- Inconsistent IP Settings When Using a Real‑Time Target in NI MAX
Do you need more help?
Submit your questions or requests using the Support Ticket Submission form.