cRIO updating to v43 Image issue

[Zuelu562]

Originally Posted by compwiztobe

Any ideas?

Read Mark McLeod's post #19. Some things to try. Post what happens if you try them.

[Mark McLeod]

Originally Posted by KenBudnik

Not sure what to try next. Frustrating.

That sounds like when comm gets dropped at the point of the changing of the cRIO IP address.

• Disable ALL unused PC network connections, leaving only the Ethernet port active.
• Set the Ethernet port to your 10.xx.yy.5
• Connect the PC Ethernet port to the robot bridge (or any network switch really)
• Connect the cRIO to the network switch as well
• Attempt to Image the cRIO

P.S. If you have network connection issues, some general recommendations:

• Turn off PC firewall
• Turn off anti-virus
• Turn off all network ports, except for the one you're using for the cRIO
• Check IP addresses all along the line
• Look to see what all the cRIO status lights are doing, particularly Status, Power, & FPGA
• Look at the Ethernet connection status lights all along the line: PC port, switch ports, cRIO port

[279 EMPIE]

Where is the imaging tool located?

Was it supposed to download with the USB or is it on wind river?

[Aren Siekmeier]

Originally Posted by Zuelu562

Read Mark McLeod's post #19. Some things to try. Post what happens if you try them.

Yeah sorry, forgot to mention that we tried exactly that. No changes. We are suspecting (based on some tips from a friend) perhaps a Windows firewall issue, and will check that out tomorrow.

[mgurgol]

Booting in Safe Mode solved the issue, thank you!

[Mark McLeod]

Originally Posted by 279 EMPIE

Where is the imaging tool located?

Was it supposed to download with the USB or is it on wind river?

In the Utilities Update: http://joule.ni.com/nidu/cds/view/p/id/2262

Check the bottom of the KOP Website to see if you missed other necessary Updates.

[jwakeman]

Originally Posted by KenBudnik

Has anyone seen this re-imaging error message?
---------------------------------

Unable to complete operation because of unexpected error:
Error -2147220304 occurred at nisyscfg.lvlib:Restart.vi:1

Possible reason(s):

NI System Configuration: (Hex 0x800404B0) Timeout while waiting for reboot. System is offline.


Complete call chain:
nisyscfg.lvlib:Restart.vi:1
ConfigUtility.lvlib:2012_FormatSystem.vi
ConfigUtility.lvlib:ReImageTarget.vi
ConfigUtility.lvlibialog.vi

---------------------
The imaging tool version is 2011.11.18
The image is FRC_2012_v43.zip

When opening the re-imaging tool for the first time, it correctly identified the cRIO and its' current configuration... so appears to work somewhat and there doesn't seem to be an IP communication issue.

When attempting to re-image normally, the progress box indicates it has made connection, checked the dip switch settings, and was reformating. Then the error.

Tried to reformat in safe mode. Correctly indicated that a reformat was necessary. Ended up waiting 15-20 minutes because the display wasn't giving any progress information. Then went back and tried in normal mode and the same error message just keeps coming up no matter what I try.

Not sure what to try next. Frustrating.

I want to second this post. This is EXACTLY what I saw today when trying to update 8 slot cRIO from 2011 with the v43 image. The only difference being I also got this error when trying the safemode imaging. I did try disabling the wireless radio on my laptop as some have suggested. I was able to recover the cRIO by using the 2011 imaging tool and v28 of the firmware. A couple of times I bricked it with the 2012 imaging tool and v43 and recovered with 2011 tool and v28. One other possible clue is that when the 2012 image fails I get the following sequence on cRIO status light. amber blink blink, 1 second pause, amber blink blink, etc. I am confident I installed all the labview software on my laptop correctly. USB stick, the three updates (lv, then utilities, then ds), then windriver. I tried many many times, safemode, rebooting everything...at this point i am pretty sure its not going to work.

[Mark McLeod]

Have you tried imaging from a different PC?

[jwakeman]

That's where i left off today, installing all the labview stuff on another pc. I will try it tomorrow night.

[Alan Anderson]

Originally Posted by compwiztobe

We can ping the cRIO, but the "Communications" light on the Driver Station is not lit. We can also deploy code from LabVIEW, but we still can not enable because the Driver Station will not recognize the cRIO... Any ideas?

What computer are you using as the Driver Station? If it's the Classmate, have you reimaged it from the 2012 USB flash drive?

There was an issue a year ago with network settings sometimes getting duplicated by the Driver Station software and causing communication to get confused. If you're using a computer that still has its files from back then, it might be worth checking deeply into the "Advanced" network settings of the interfaces and making sure there aren't any extraneous IP addresses defined.

[Alan Anderson]

Originally Posted by jwakeman

I did try disabling the wireless radio on my laptop as some have suggested.

When you say "disabling the wireless radio", what did you actually do? Just turning off the WiFi doesn't help. The way I suggest is to right-click on the relevant icon on the Network Connection control panel and select Disable from the popup menu.

[Aren Siekmeier]

Originally Posted by Alan Anderson

What computer are you using as the Driver Station? If it's the Classmate, have you reimaged it from the 2012 USB flash drive?

There was an issue a year ago with network settings sometimes getting duplicated by the Driver Station software and causing communication to get confused. If you're using a computer that still has its files from back then, it might be worth checking deeply into the "Advanced" network settings of the interfaces and making sure there aren't any extraneous IP addresses defined.

This issue was fixed by using a different laptop today, so it seems apparent that it was a firewall issue (even though we had checked some of the telltale signs of such a problem). The first computer was not the classmate, it was a computer with a 3 or 4 day old windows install (probably why the firewall hadn't already been configured appropriately for the driver station).

We later were trying to reimage our second cRio and got exactly the error in post 29, but after an hour so of monkeying with things (through switch, not through switch, safe mode imaging, disabled nics, etc.) it finally worked, so we're not sure what happened there. Sounds like NI is working on this one (see also http://forums.usfirst.org/showthread.php?t=18509).

[279 EMPIE]

We have the image tool now but we do not have the right image.

Where do i get the right image from?

[Mark McLeod]

The image comes when you install the language specific Update from the bottom of this page:
http://www.usfirst.org/roboticsprogr...control-system

[jwakeman]

Originally Posted by jwakeman

That's where i left off today, installing all the labview stuff on another pc. I will try it tomorrow night.

I used another PC and everything went through fine. It probably was firewall settings on the first PC.