View Full Version : Problem Imaging cRIO to v52
domingocool
09-01-2014, 14:48
So we have been trying to image the cRIO with the 2014 imaging tool but it keeps giving the error shown:
http://gyazo.com/bab42c32429a79a6b4798b3da548e62f.png
http://gyazo.com/eb19a4858385303b0ff0e3394324b85e.png
We reset the cRIO and removed and re installed the software. I'm not sure what else there could be or what the error means.
Joe Ross
09-01-2014, 14:53
Have you tried the troubleshooting steps listed here: http://wpilib.screenstepslive.com/s/3120/m/8559/l/89727-imaging-your-crio
domingocool
09-01-2014, 15:13
Have you tried the troubleshooting steps listed here: http://wpilib.screenstepslive.com/s/3120/m/8559/l/89727-imaging-your-crio
I've tried the steps and it still throws the same error. The only thing that happens is that once in a while I see this happen:
http://gyazo.com/db2910c093459e8527e02f1b905224c3.png
The only thing is that the new image(v52) is not applied. If I give it another go after that, it shows the error message again.
Kevin Phan
09-01-2014, 16:39
Do you still have the console out soft-switch on when you tried to reformat the cRIO?
domingocool
09-01-2014, 16:42
Do you still have the console out soft-switch on when you tried to reformat the cRIO?
Yea the Console Out is on.
Kevin Phan
09-01-2014, 16:53
Can you try reformatting the cRIO with that switch off, when I was beta testing rebound rumble's LabVIEW version, it interfered with us reformatting the cRIO.
domingocool
09-01-2014, 17:15
Can you try reformatting the cRIO with that switch off, when I was beta testing rebound rumble's LabVIEW version, it interfered with us reformatting the cRIO.
Ok so now what it's doing is going through everything but gets stuck at Rebooting.
Kevin Phan
09-01-2014, 17:19
Can I see a screenshot of said rebooting. The rebooting takes a relatively small time, but it depends on what you are seeing.
Alan Anderson
09-01-2014, 20:31
You say you've done everything in the troubleshooting list, but let's focus on a couple of common problems directly.
Do you have your network adapter's IP address set properly? It should be 10.46.45.x, where x is either 5 (if you're using the Driver Station computer), 6 (the typical programming computer address), or something 10 or higher.
You should also make completely certain that no other network adapters are enabled on your computer. Don't just turn off the wireless network radio; actually go into the networking configuration and disable the adapter.
vBulletin® v3.6.4, Copyright ©2000-2017, Jelsoft Enterprises Ltd.