crio II imaging issue

[Greycrazygamer]

So i have been trying to format the crio II using the new 2013 image. however, when i try and image it i get an error saying the crio is running in safe mode and i have to fromat it first. but then it just gets stuck saying rebooting CompactRIO device! and on top of this, the Crio II doesnt have manual switches, so i have no idea how it is in safemode in the first place.

[joelg236]

On the CRIO Imaging tool, there is a little virtual switch that says "safe mode". If you click that it should turn off safe mode so you can image the CRIO.

[Alan Anderson]

The 4-slot cRIO will boot in safe mode if you hold down the reset button for 5 seconds, until the STATUS LED lights up solid yellow. If you ever get it confused enough that the imaging tool can't find it to flip the virtual switches, that's how you get it back to a more known state.

[Particle]

I'm having a similar issue. In my case the imaging tool didn't say that the device was in safe mode (it was showing up normally), but when I formatted the device with the 2013 image it sat at the "Rebooting CompactRIO device." stage indefinitely. After about 15 minutes of waiting at that point without progress, I rebooted the device in safe mode after finding this thread and tried to image it again with the same result.

The device never seems to finish rebooting. If I do a regular reset of the device now, the status light gives me double flashes. The 2012 configuration that was still working before the attempt at applying the 2013 image appears to be gone.

[turtleman]

Originally Posted by Particle

I'm having a similar issue. In my case the imaging tool didn't say that the device was in safe mode (it was showing up normally), but when I formatted the device with the 2013 image it sat at the "Rebooting CompactRIO device." stage indefinitely. After about 15 minutes of waiting at that point without progress, I rebooted the device in safe mode after finding this thread and tried to image it again with the same result.

The device never seems to finish rebooting. If I do a regular reset of the device now, the status light gives me double flashes. The 2012 configuration that was still working before the attempt at applying the 2013 image appears to be gone.

Bump for interest. We've been having this exact same problem and I can't for the life of me figure out how to fix this.

[Particle]

I've tried probably a dozen different permutations of the process today without any luck. I tried with the device networked to my LAN and direct cable both. I tried Windows 7 32-bit in case the Windows 8 64-bit machine was causing a problem. I tried imaging both in and out of safe mode. I tried setting the development environment to LabVIEW instead of Java. I also tried various combinations of those factors.

Still no luck. The process always hangs at the rebooting stage, even if I wait 45 minutes.

[Particle]

Good news: I've managed to successfully image our cRIO. I'm posting this in case others have the same issue in the future.

I installed Wireshark and started monitoring the traffic going between the two devices and noticed some odd behavior going on. There was lots and lots and lots of ARPing and browser election stuff going on when it normally wouldn't be. I then isolated the machine that was talking to the cRIO by connecting it directly to the cRIO instead of leaving it attached to the LAN. I wanted to make sure and isolate it from traffic on the domain. Once this was done, I saw FTP sessions that hadn't ever previously initiated and the process was rolling along.

Anyway, here is the bottom line of what worked. Other configurations might work too, but this is something you might try if you're having trouble:
- Use a physical machine. Using a VM is not sufficient.
- Leave your LAN. Connect the cRIO directly to the machine you're imaging from via a patch cable. Do not connect to a switched network with other devices.
- Do not use wireless.
- You do not necessarily need to leave your domain, but you do need to be isolated from it.
- Remove all other IP addresses from your computer's NIC except for the 10.x.x.5 address you plan to use. Do not just bind to this address in addition to your normal addresses.
- Remove all DNS, WINS, etc server references from your NIC.
- Power cycle the cRIO controller and wait about 30 seconds.
- Try imaging now.