cRIO getting wrong IP after reimaging

So we are reusing last years cRIO and I am trying to teach the new members how to reimage the cRIO. The imaging tool works perfectly fine except that it sets the cRIO’s IP to 10.0.0.1. I entered our team number into the correct box but it isn’t setting it. I searched the forums but found nothing. Anyone else have this problem?

Is the IP RESET switch on the cRIO flipped?

It’s off when I try to reimage it, I’ve gone through ip reset procedures a couple times and it resets it. Still doesn’t receive the right ip from reimaging ):

I’m not sure exactly how the IPs work in port 2, but is there any chance you’ve accidentally connected into ethernet port 2?

Port IP is set via MAX, the Measurement and Automation eXplorer. You shouldn’t really need to change it from what the image sets it to.

Greg McKaskle

Grasping at straws here – what computer are you using to do the imaging? Do you have it connected to the cRIO directly, or through a router? The Classmate has trouble when directly-connected, when the cRIO’s ethernet port gets reconfigured during the format and re-image process, and re-establishing the physical network link on the Classmate side of the wire takes longer than the software is prepared to wait. Other computers might have the same problem. If you aren’t using a router, try adding one.

Yep, port1

Using a dell laptop (we’ve used it before to do this)
Tried the following:

  • straight
  • crossover
  • through router

same thing every time D:

The existing imaging process moves the cRIO from IP to IP as part of the process. If the networking isn’t simplified, it is pretty for the laptop to be unable to locate it at one of the intermediate IPs.

Make sure that any secondary NICs are turned off, including wifi.

Greg McKaskle

Yep, wifi is disabled and the laptop only has one ethernet port. Trying it again to see If I have better luck this time, if not I will record a video of what I am doing and upload it to youtube.

It works now… just kept going through the reflashing process over and over and eventually It came back with the correct IP.

EDIT: NVM, it wont give it the custom name, if I try to use a custom name, it gives me an error after it tries. Oh well, I guess it is okay that it is named temp -_-