I have tried formatting a new CRIO-FRC II from NI, when I connect the crio to the FRC CRIO imaging tool from 2013 and apply the applicable settings, I get this error “Unable to assign an IP address for the CompactRIO device. Ensure the IP Reset switch on the CompactRIO device is turned off.” When I got this error I went into NI MAX where I ensured that the IP Reset switch was disabled on the CRIO. I still get this error, what should I perform to fix this error?
That could also be caused by confusing network setup.
- Disable all NIC’s on your laptop, except for the Ethernet port
- Configure the port with your standard IP of 10.16.1.5
- Hardwire via Ethernet between the laptop and the DLink, then the cRIO. (the DLink helps preserve the connection while the cRIO is changing IP addresses)
- Turn off all firewalls on the laptop
- Run as administrator
*]
For the FRC cRIO’s the measurement and automation explorer tools don’t really work. The only way to change the switches on the new cRIO II is by using the imaging tool, but that only works if the imaging tool recognizes an FRC image on the device. We’ve had the same problem and we solved it by pushing and holding the reset button on the cRIO for about 10 seconds to make it start in safe mode. Then, when you go to the imaging tool, it lets you reformat the cRIO and erase everything and reset everything. After you cycle the power it should let you image the cRIO as normal.
EDIT- also try a different computer if another is available. If the imaging tool doesn’t reconnect to the cRIO quick enough, you get weird errors. For whatever reason the classmate laptop works the best for us.
Thanks Mark,
It turns out that the crio had add ons which were preventing me from using the CRIO Imaging tool. I had to reinstall the base image in NI MAX which then allowed me to proceed into formatting the CRIO with the FRC v43 image in the imaging tool.
Thanks for the help!!
If you’re connecting your computer directly to the cRIO, you must use a crossover LAN cable, per the instructions in the “Getting started with the <year> control system.” What’s confusing is that connectivity can be established using a “regular” (not crossover) cable, but the imaging won’t complete. I saw this about a week ago (Dec. 2013) preparing for the 2014 season, with 668’s 8-slot cRIO.
We saw the same thing last year, but only on one computer. After imaging, both the crossover and the “regular” cables both work well. From my experience, the reimaging issues come up when the cRIO doesn’t reconnect with the imaging tool fast enough. Any modern computer will have an autodetect feature (auto MDIX) that detects if it needs to switch the tx/rx pins, so you only really need a crossover cable to connect the camera and cRIO, which both don’t have the auto MDIX.
My thought is that it takes a few seconds for the ethernet controller to decide that it needs to do the switch, so the imaging tool times out before the cRIO can be imaged, but I’m not really sure. We had some pretty extreme imaging issues in 2012, and solved them by using a random desktop computer we had laying around, so it seems like the computer being used might have an effect on the imaging process.
If the computer has an IP of 10.16.1.5, what does the IP address of the D-Link have to be?
10.16.1.1, however just about anything in the form of 10.16.1.X will technically work where X = 0-254 excluding 2, 5, and 6.
It doesn’t need to be anything special if you’re just using it to connect your computer to the cRIO.
Its address does have to be compatible with the computer’s network settings if you intend to log on to it for administration tasks. The 2013 FRC Bridge Configuration Utility will take care of setting it correctly according to your team number.