Why Does My Networked Device Not Show Up In Measurement & Automation Explorer (MAX)?
I have a CompactRIO controller or a Single-Board RIO that I am attempting to configure in Measurement & Automation Explorer (MAX), however it is not showing up under Remote Devices. What are the possible reasons for this?
There can be several reasons why a CompactRIO controller or Single-Board RIO does not show up under Remote Systems in MAX, and most of them are network-related. In addition to the list of most common issues detailed below, one of the best resources for setting up a CompacRIO or sbRIO and troubleshooting related issues is www.ni.com/gettingstarted
. Specifically, the Connect and Set Up Hardware
section has a comprehensive list of instructions and troubleshooting tips that will help you solve most issues related to setting up your CompactRIO or sbRIO system.
- Make sure that you have the correct version of NI-RIO installed on the host PC.
- Refer to related links section of this document for version compatibility information.
- If the software was recently upgraded, reinstall the NI-RIO driver.
- New controllers and backplanes require updated versions of NI-RIO. Always make sure you have the newest version installed.
- Check the status LED on the controller.
- If the light is not blinking, then your CompactRIO or sbRIO has an IP address set up already. You should reset the IP if you still do not see the target
- If the light is blinking once, it has an unconfigured IP address, and will be 0.0.0.0. If the status light is not blinking, it may have a link-local IP Address. Link-local addresses are network addresses which are intended only for communications within one segment of a local network. IPv4 addresses in the range 169.254.0.0/16 are assigned automatically by a host operating system when no other IP addressing assignment is available.
- Refer to your CompactRIO's operating instructions to determine what might be wrong with the system, or consult KnowlegeBase 3K5CTHQX: Why is the Status Light on a CompactRIO (cRIO) Controller Flashing Continuously? for a brief description of the blink codes. These blink codes also apply to the sbRIO.
- If the status light remains solid then the device isn't properly booting past the BIOS. This could be an indication that the device is not receiving adequate power. Check that the power supply meets the requirements listed in the Power Requirements section of the device's specifications.
- Read the Console Out of the controller.
- Allows you to discover the current firmware version and IP address of the controller.
- Useful for diagnosing unresponsive controllers or a controller with errors indicated by the LEDs.
- Switch the reset IP switch.
- This restores the controller to the default IP address (0.0.0.0) in earlier versions of RIO for LV RT 8.6.1 and later. In newer versions it will make the IP address link-local. This should allow the controller to be detected on the network.
Note: If your device does not have DIP switches such as the CompactRIO 9075/9076 hold the Reset button down for 5 s, then release it. The Status LED turns on, then starts blinking three times every few seconds. The chassis is now in safe mode with the Console Out enabled. Hold the Reset button down for another 5 s, then release it. The cRIO-9075/9076 attempts to establish a new DHCP connection. If it fails, it assigns itself a link-local IP address (169.254.x.x).
- Switch the No App switch.
- If the CompactRIO or sbRIO already has an application running, it may be using too much CPU time to allow any network communication. This can prevent the device from appearing in MAX, but you may still be able to ping the controller.
- After turning on the No App switch, press the reset button on the controller to reboot into an idle state with no user application running.
- Check that the network cable is secure on the target and host computer.
- If you are connecting directly from the host computer to the CompactRIO controller or sbRIO, make sure that you are using a crossover cable.
- If connecting through the local network, double check that you are using a standard network cable.
- You should see two lights on the network cable connection, one solid and one rapidly blinking. This indicates that there is communication. If you see no blinking lights on the cable connection, make sure you are properly connected with the correct cable.
- If you have network firewalls enabled, try temporarily turning them off.
- Security software such as BlackICE can possibly block network communication to and from your CompactRIO controller or sbRIO.
- On Windows computers, it is also possible that disabling the Windows firewall will not necessarily enable the blocked programs. In that case, you must explicitly enable MAX by doing the following:
- For Windows XP:
- Open Network Connections Control Panel, located in Start»Settings»Network Connections; this will result in listing the local networks.
- Right-click any connection and select Properties.
- Select the Advanced tab.
- Click Settings.
- Select the Exceptions tab.
- Click Add Program...
- Select Measurement & Automation in the list and click OK.
- Click OK on both remaining windows.
- Now MAX will be able to communicate with your real-time controller.
- For Windows 7:
- Open Allowed Programs Control Panel, located in Start»Control Panel»System and Security»Windows Firewall»Allow a program through Windows Firewall.
- Click Allow another program...
- Select Measurement & Automation in the list and click Add.
- Click OK to close the control panel.
- Now MAX will be able to communicate with your real-time controller.
- Port 44525 is used by National Instruments software for ethernet target discovery. Make sure that this port is open to discover your CompactRIO or sbRIO.
Related Links: Getting Started with NI ProductsKnowledgeBase 27K9UNKN: Connecting to a LabVIEW Real-Time (RT) Target with a Crossover CableKnowledgeBase 1XGF6R4U: I Cannot Connect to My PXI Real-Time Target on the NetworkSoftware Support: CompactRIO, CompactDAQ, and R Series DevicesKnowledgeBase 4E0DGASK: Configuring the Dual Ethernet Ports on Real-Time Controllers KnowledgeBase 3K5CTHQX: Why is the Status Light on a CompactRIO (cRIO) Controller Flashing Continuously? KnowlegeBase 42177BXJ: Connecting to Ethernet Targets with Multiple Network Cards in the HostNI LabVIEW for CompactRIO Developer's GuideKnowledge Base 3M87HMD7: Usage of Console Out Switch on CompactRIO, Single-Board RIO, cFP-21xx, and cFP-22xx ControllersKnowledgeBase 4ESLI3UI: NI-RIO and LabVIEW Version Compatibility
Attachments: Network Ports Used for Device Discovery.pdf
- Make sure that the host and target controller are on the same subnet.
- If the CompactRIO controller or sbRIO is on a different subnet to the host, you'll need to manually add the target in MAX by right-clicking the Remote Systems menu, and selecting Create New.
- If you are using an intelligent switch on the network, make sure that it is not disabling a port that is routed to the target.
- Some intelligent switches that are used on a network will automatically disable some ports that could be blocking communication to the target from the host.
- If you have multiple network adapters (i.e. wireless), be sure that all other network cards are disabled.
- When computers have multiple network cards, MAX may choose to look for remote devices through the card that your CompactRIO/sbRIO is not connected to. This is very common on laptops, as the wireless device is often the primary network card.
- If one card is wireless, be sure to disable it from the control panel, not just turn off the wireless antenna.
- In some situations, changing the network adapter used to communicate with your CompactRIO/sbRIO to the system default network card can cause MAX to correctly search for remote devices. Refer to KnowlegeBase 42177BXJ: Connecting to Ethernet Targets with Multiple Network Cards in the Host for more details on this procedure.
- If you are using a cRIO-9074 or cRIO-902x, make sure that you are connecting the CompactRIO to the computer using Port 1 and not Port 2. For a detailed explanation of when to use Port 2 and how to configure it please see the related links section below.
- If you have assigned a static IP address and moved the controller to another location, the subnet may have changed. You can grab the current computer's full IP and subnet address by entering ipconfig in the command prompt. To open the command prompt, go to Start»Run and type cmd. The ipconfig response should tell you the current setup of the computer. You can also attempt to ping the controller using the ping xx.xx.xx.xx command, where xx.xx.xx.xx is the static IP address set up on the controller. This will tell you if the computer can connect to the CompactRIO/sbRIO. If it can, it is possible your software install is incorrect. If you cannot, there is a network or firewall issue and you should contact your IT department. Keep in mind that controllers set to 0.0.0.0 are not pingable.
- Your NI-RIO server settings may be improperly configured. To ensure that your computer is allowed access to your RIO device, open NI-MAX and select Tools»NI-RIO Settings. Under Remote Device Access you should have a " * " listed, allowing all remote systems to access RIO devices on this system. If you do not want to allow all remote systems to access RIO devices on the system remove the " * " and add the IP address of the remote systems you wish to allow access.