cRIO imaging tool hangs on "Rebooting cRIO"

Technical Control System
1

Hi,

I’ve been trying to image our cRIO II with the imaging tool, but evertime I do it, It always gets stuck on “Rebooting cRIO.”

I have the latest imaging tool (2013.1.10) and I have tried EVERYTHING. Safe-mode, direct Ethernet connect, direct crossover connection, connecting through the d-link, changing my ip between 10.27.61.5 and 10.27.61.6, and changing the subnet masks between 255.255.255.0 and 255.0.0.0. But each time I get the same result:

It gets stuck on “Rebooting cRIO” and all I get see is the little User1 light blinking rapidly.

Any help?

Edit: I opened up wireshark to see if it was accually doing something, since nothing seemed to be happing. Then, I found out that this happens everytime I open up the imaging tool or press “Apply”:

https://lh4.googleusercontent.com/-abU3kXrO1t0/UPG3Ychpx4I/AAAAAAAAAL4/8OXZvnIbi7Y/s800/Screenshot_3.png

So, it doesn’t login with the right password?

2

I spent two days of beating my head against the wall doing this with the original cRio-FRC. It would hang at the “Rebooting cRio…” prompt.

We had a number of errors about the Set IP dip switch, which is virtual in your cRio II, but no flipping of it or any other switches helped.

It finally worked, and I’m not 100% sure why (but we’ll take it) when I pressed the reset button on the cRio and/or cycled power to it before running the Imaging Tool.

I haven’t tried to image the cRio II yet this year and don’t recall if it has a reset button, but try that and see if it helps.

3

We’ve been having the same problem. We set our IP address to 10.31.75.5, our gateway to 255.255.255.0, connect the cRIO, open the Imaging Tool, and see this:


(The Current Image is unknown because we’ve failed formatting several times now. I assume we can’t see the Modules Installed for the same reason.)

And when we click Apply:

And it never stops. We’ve waited at Rebooting Compact RIO device… for at least 20 minutes at a time, and nothing.

At least you’re not alone with this problem.

As for rebooting the cRIO, we’ve tried this several times after several power switches and reboots, and we’re stuck.

The interesting thing is that the Imaging Tool seems to stop completely at Rebooting: if we power off the cRIO or disconnect the Ethernet cable, the tool doesn’t respond. I wonder whether this is helpful information for anyone.

4

Okay, so I did some poking around and found out that you can connect to the cRIO using FTP, and you can modify settings on the cRIO, if you have the admin password, using MAX.

The default username is “admin” and the default password is either “admin” or just blank.

So when I try and get onto the cRIO manually, I found out that those passwords have been changed, as it won’t take them, and that the FTP’s anonymous mode was disabled. That’s probably the source of the problem.

Now how do I fix it is the question. Is there some way reset the cRIO to factory state or something?

5

If you hold the reset button for about 5 seconds (until the status light turns on) then the cRIO will reboot in safe-mode and the imaging tool will allow you to format it (returning it to a factory state).

6

According to this:
http://digital.ni.com/public.nsf/allkb/FFE0CF7C2D1D13918625747300812E8C

You’re partially right. I’ll try this later and see how it goes.

7

We imaged a fresh cRIO this evening. It stuck at the “Rebooting cRIO” step. It took us a while, but we finally tracked down something that was misconfigured on our computer. Somehow the wired network interface had gotten two IP addresses set, and removing the extra one let everything work properly.

(I’m guessing the extra address ended up there when we selected the wrong interface in the D-Link configuration tool a half hour earlier, but I’m not about to go through that mess again to verify the cause of the problem.)

So I suggest that you double-check the “Advanced” IPV4 properties of your network connection and delete any superfluous entries.

8

Okay I got it all figured out now.
The process is a long one, so I might miss a few steps:

  1. The first thing I did was use the above link to reboot the cRIO into safe mode and unlock and reset the ip config
  2. Reset your computer’s ip configuration to “automatic”
  3. Go to MAX, and check to see if the safe mode switch is enabled, if it isn’t enable it. DO NOT USE THE IMAGING TOOL!
  4. Reboot the cRIO
  5. Open your favorite ftp client (I use filezilla) and upload the cRIO image manually (located in the same directory as the cRIO imaging tool)
  6. Go to the cRIO imaging tool, set your options, but make sure that the safe-mode switch is still on!
  7. Check “apply”
  8. Now, the cRIO’s ip has been set back to 10.xx.yy.2, change the computer’s IP setting back to normal
  9. Use FTP again to upload the latest firmware manually
  10. Now, you can use the Imaging tool to format the cRIO regularly

Hope it helps!

9

We were having the same problem with Crio and we managed to fix the problem.

http://digital.ni.com/public.nsf/allkb/FFE0CF7C2D1D13918625747300812E8C

We used the link above and followed the three steps( after the third step we set the RESET IP switch back to on).

We checked that our IP settings were correct on our laptop. We ran the FRC 2013 Crio imaging tool, and we successfully imaged the Crio.

10

Thanks Alan, this cleared it up for us. I had imaged an 8 slot cRIO with no trouble. After using the Bridge Configuration Utility nothing seemed to work when trying to reimage it, or another 8 slot we had. When I reset the IPv4 settings everything worked fine.

11

Is there a fix of some sort for the imaging program yet? Were having this issue now.

12

There doesn’t seem to be anything “wrong” with the Imaging Tool. It just can’t deal with the changing IP addresses of the cRIO if the Windows network settings aren’t trivially simple.

So make sure you’re connected using a physical Ethernet cable, disable the wireless interface (and any other interfaces other than the one with the wire) on your computer, and make absolutely sure that the wired interface has only the single 10.te.am.6* IP address associated with it.

  • 10.te.am.5, if you’re using the Driver Station computer
13

The second IP address that will cause the failure was due to an issue with the radio programming tool, and that has been corrected. But while it prevents the IP from accumulating again, I believe you have to remove it by hand.

Greg McKaskle

14

First of all, we have no idea what we are doing! Our programmer who handled everything to do with the sorts has left without teaching anyone how to connect. The first year our mentor said even our last programmer had no idea until someone came and “fixed it.”
When we try to connect to the CRio, it gets stuck on rebooting and eventually ends with a Re-scan.
As far as we can see we do initially connect to the CRio, but as we continue to the rebooting part, it waits a while, then tells us to re-scan.
Over and over and over and over and over.
Our screen looks identical to the original posters screen and we have the same error.

15

Here’s what I was able to figure out after a few hours of hitting my head against a wall:

  1. Set cRio into safe mode, reboot.
  2. Format the cRio, when the tool warns about safe mode choose “Format in Safe Mode” or whatever it says.
  3. When finished, turn safe mode off and reboot.
  4. Image it normally. It should work this time.

This worked perfectly for me. Good luck.