New cRIO Imaging Tool Not Showing Modules

[random.hero]

We ordered a new cRIO this year so we could keep our old one as a test bed. When I installed it on our 2014 robot and connected all of the modules and went to image it using the Imaging Tool none of the modules show up, although it does recognize the cRIO and I can image it.

We swapped it out for our old cRIO, which is noticeably different, having 2 ethernet ports and physical switches as well as several more VGA slots. I put our modules in there in the same order as I had them in our new one, 9201>9403>9472, and it worked perfectly. Everything showed up in the Imaging Tool software.

When using our new cRIO, the lights come on on the modules, they are in the same order, but the Imaging Tool doesn't notice them.

What are we doing wrong? Any direction would be appreciated.

Thanks in advance!

[Joe Ross]

I've noticed that the modules only come up if the netmask of the computer is 255.255.255.0

[Mr. Lim]

I've had a few instances where the imaging took reported a successful image, but actually failed.

Check to see if the installed image version correctly shows up beside the cRIO in the imaging tool.

If not, keep reimaging until it dies.

[zeldathegood]

We are having the same issue as stated in the original post.

We got a new CRIO and the 3 modules this year on the FIRST choice. We have been trying to image the CRIO but when we bring up the imaging tool or rescan it is not showing the modules in the picture on the right. That means that the toggle switches on the bottom are disabled so when we try to image we get an error regarding IP Address.

We have tried all the trouble shooting ideas I have found in numerous spots on chief delphi and this forum but nothing seems to work.
1. We tried with and without the router between the computer and the CRIO
2. We set our mask to 255.255.255.0
3. We tried multiple different IP addresses on the computer. 10.XX.YY.5 where xxyy is our team number. We also matched the ip address of the crio with the last number different.
4. We are able to ping the CRIO using it's IP address
5. We also turned off the firewall

Does anyone have any ideas? Could we have gotten a bad CRIO?

We have our old CRIO and we were able to bring up the imaging tool fine using the same computer. We can see the all the modules on that device. We did try the old modules one by one in the new CRIO and they are still not recognized so we don't feel it is the modules.

Please help.

Thanks in advance. We are going crazy.

[Alan Anderson]

The imaging tool can't read the modules directly. The cRIO has to tell it which module is in which slot. It can only do that if it has been loaded with a version of the image that supports it.

So when you connect a new cRIO without an FRC image already loaded into it, you won't see the modules listed. You have to put a "modern" image in place (v47 or later will do) before the modules will show up.

If you put this year's image on the cRIO and you still don't see the modules on the picture in the imaging tool, it's possible that the image didn't "take". The "Current Image" column in the tool should tell you what is loaded.


What is the exact IP address error you are seeing?

[Storcky]

I'm guessing it's the same issue as this: http://www.chiefdelphi.com/forums/sh...hreadid=124873 Looks like everyone decided to reimage their cRIO today. We had the same issue but couldn't find anything on CD this afternoon. Solved it by pushing the reset button then power cycling the cRIO.

[zeldathegood]

The above steps worked for us to get the CRIO to take the image. After we finally got it imaged we still could not detect the middle module 9403. We swapped in a good module for our old machine and we can see the module in the spot. We called NI FIRST support line. We have been told that our great donation from FIRST Choice has a defective module. NI says that module is out of warranty and will cost $750 to get it fixed! I'm trying back with the FIRST FRC support guys. Has anyone had any issues with trying to get replacements for FIRST Choice defective stuff. Should I be using a different process?

I sent an email to the wonderful folks at FIRSTChoice and they are sending us a new one today. Thank you to AndyMark!