Table 3. Status LED Indications
Number of Flashes Indication
1 The chassis is unconfigured. Use MAX to configure the chassis. Refer
to the Measurement & Automation Explorer Help for information about
configuring the chassis.
2 The chassis has detected an error in its software. This usually occurs
when an attempt to upgrade the software is interrupted. Reinstall
software on the chassis. Refer to the Measurement & Automation
Explorer Help for information about installing software on the chassis.
3 The chassis is in safe mode because the SAFE MODE DIP switch is in
the ON position. Refer to the Configuring DIP Switches section for
information about the Safe Mode DIP switch.
4 The software has crashed twice without rebooting or cycling power
between crashes. This usually occurs when the chassis runs out of
memory. Review your RT VI and check the memory usage. Modify
the VI as necessary to solve the memory usage issue.
The device may be configured for DHCP but unable to get an IP address
because of a problem with the DHCP server. Check the network
connection and try again. If the problem persists, contact National
One thing you could try is to set the IP RESET dip switch to on, and powercycling the cRIO. It should now have the IP 0.0.0.0
Push the IP RESET switch to the ON position and reboot the chassis to
reset the IP address to 0.0.0.0. If the chassis is on your local subnet and
the IP RESET switch is in the ON position, the chassis appears in MAX
with IP address 0.0.0.0. You can configure a new IP address for the
chassis in MAX. Refer to the Resetting the Network Configuration of the
cRIO-FRC section for more information about resetting the IP address.
You also can push this switch to the ON position to unlock a chassis that
was previously locked in MAX.
After resetting the IP, try to ping the cRIO. If it responds, see if you can reimage it now.
Assuming you changed your team number while re-flashing, you should change your PC’s ip address to 10.24.93.6, and then try to ping 10.24.93.2. But that probably won’t matter now that you reset the IP address.
OK, powered down the cRIO, powered it back up and now the orange link light on the cRIO ethernet port is blinking, so I am assuming we have communication taking place. That is a step in the right direction.
The Status light on the cRIO is still doing a slow continous blink.
Still wired from the computer to the DS to the cRIO. We temporarily tried using the crossover cable which also shows blinking orange link led.
a ping of 10.0.0.2 and a ping of 10.24.93.2 (with the computer ip set appropriately) are now returning Destination Host Unreachable
Try connecting the cRio and your PC to a router with DHCP enabled. Then check the router DHCP table and see if it got an IP address from DHCP. Its possible when it was reset it changed to DHCP configuration.
I’ll have to go out and find a NULL Modem serial cable to try that, but in the mean time…
I did get MAX to talk to the cRIO and was able to reset the IP address from 0.0.0.0 to 10.0.0.2.
I then was able to reflash the cRIO to a point. It got to the point where it was formatting, and then I received a UDP Unexpected Error 60 (sorry for the paraphrase, I didn’t get to write the text of the message).
OK, so twice now we get this message during the Format phase of the reimage process:
Unable to complete operation because of unexpected error 60: UDP Open in repFPC open connection.vi->SendRebootCommand.vi->RebootSystem.vi->SetTargetConfig.vi->SetIPAddress.vi->ConfigureUtility.lvlib:SetIPAddrAndGetInfo.vi->ConfigUtility.lvlib:ReImageTarget.vi->ConfigUtilty.lvlib.Dialog.vi
The “Error 60” makes it sound like your computer was set to the IP address the cRIO wanted to use. It might be worth checking the network configuration on the first computer to see if that was your problem.
We did so many things to get this working including:
Loading the base NI-RIO software
Formatting the cRIO in Safe Mode (scary thing to do)
Running directly to the cRIO with the crossover cable
All kinds of address configurations (0.0.0.0, 10.0.0.2, 10.24.93.2)
The computer was always 10.0.0.6 or 10.0.0.10 (or subbing 24.93 for the zeros)
Using a different computer
Turning off the firewall
Disabling all other network connections on the computer
Clearing all COM channels (paraphrased I think) using MAX
Switching to another computer finally seemed to clear things up and make things work.
I think that was all the things we tried. It took us at least 5 hours today to finally get it figured out.
I did my best to document what I think were the relevant steps in an earlier post, hopefully to help other teams.
I sure wish I knew this morning what I know now about loading the cRIO image, things would have gone much easier
Although NI doesn’t offer phone support on the weekends (and not till Jan. 5 for FRC) we do have a large number of knowledge base articles including topics such as network communication issues with the cRIO. I recommend searching for the operating instructions for the cRIO-9074 for more information.
It also doesn’t hurt to ask questions like this on ni.com/FIRST so we can identify the gaps in our documentation (this being one of them).
One thing I would like to point out that Formatting the cRIO shouldn’t be a scary thing to do. Its more robust than you think.