cRIO updating to v43 Image issue

[Paul Manns]

We wound up with an "unknown" image after trying to upgrade from the Beta image to v43. It kept claiming that the boot timed out.

We resolved the imaging problen by turning on the safe mode switch (8 slot version) and reimaging. The dialog box said in effect that the safe mode switch is on and to recover from a corrupted image, select the "FORMAT" button in the dialog box. After formatting, the dialog box said to turn off the safe mode switch and reformat. We reformatted to v43 and it unbricked!

[279 EMPIE]

My teams cRIO is now re imaged and it successfully worked the first time.

[AlDee]

We're having a similar problem only a slightly different error message. After formatting, neither tool can see the cRIO. We've tried safe mode, reformatting, etc. but nothing. We've duplicated the error on a second cRIO. I'm going to try some of the suggestions here, like switching laptops, going through the bridge, etc. Any other suggestions would be greatly appreciated.

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

Possible reason(s):

NI System Configuration: (Hex 0x80040491) System failed to reboot after hard drive format.


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

[Mark McLeod]

That message looks like a network switch intermediary is needed between your PC and the cRIO.

[billbo911]

We solved our issue with imaging the cRio II by simple installing the FRC "Tools" from the thumbdrive, something we had neglected to do because they were listed in the full install.

So, here is what we needed to get 'er done:

Fresh install of the 2012 FRC LabView from the thumb-drive,
FRC utilities from the NI website,
LabView update 4.00 from the NI website,
FRC tools from the thumb-drive.

After that, it was smooth as butta.

[JacobGH]

I'm getting the Error -2147220304 error too. Can someone explain how to flip the cRio into safe mode so I can try imaging it that way?

[PhilBot]

Hi

UPDATE....

This is the resolution to the problem I listed below.
It turns out that on my Win XP machine, there are two levels of Wireless Network Control.
I had been using the Intel Proset Wirless application that is connected to the Wireless status icon on the Status Bar.
This showed the Wireless as OFF, with an "Enable" button.

However, when I went to the Network Connections function of the control panel, the Wireless status showed up as "Enabled".. Hmm not nice.

So when I set the Wireless status to Disabled there, the problem was resolved.

So, the moral of the story is: Don't trust third part network tools to actually disable the Wireless interface. Make sure it's disabled at the Windows lowest level.

Hope this helps anyone using an older Win XP machine.

Phil.

----------------------


I'm having trouble formatting a brand new 4-slot CRIO.
I'm a seasoned beta tester so I expected this to go easier.
The error below shows what's happening.
The CRIO Has the correct IP, and so does my Laptop.
The wireless is turned off.
Firewall is off.
Router in between.
OS is Windows XP (oh oh!!)
The formatting process seems to be progressing but it does not complete.
I see the messages get all the way to "formatting....".
During the process I see the CRIO Network drop out twice. once at the beginning, and once a few seconds before the error occurs. It really does look like it's trying to reboot the crio.

Can I toggle the dip switches before it's formatted, to try a safe format?

The real question is how can it get so far along and then just tank... over and over again?

The MUST be a proven solution to this...
Many reboots later.

Phil.

-----------------------------------------------

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

[JacobGH]

I used the Fn-F2 on my laptop to physically cut power to the wireless card and I'm still getting the same error. Windows XP. No third party wireless software. Ideas, anyone?

[Mark McLeod]

Originally Posted by JacobGH

I used the Fn-F2 on my laptop to physically cut power to the wireless card and I'm still getting the same error. Windows XP. No third party wireless software. Ideas, anyone?

Do what Phil suggested in the post before yours.
Using Fn doesn't do what's necessary.

[AlDee]

UPDATE. We got ours working by trying a different laptop. As others have suggested here, it looks like the the first laptop we used was losing connectivity with the cRIO during the formating process. The cRIO was working fine, the laptop could just no longer see it.

If your still having issues, try the suggestions posted in this thread:
Make sure Firewalls are off.
Wireless is off.
Only one ethernet adapter is enabled.
Check IP settings.

--Al

[JacobGH]

Well that royally sucked, but I finally got it working. I used PhilBot's suggestion about disabling the network at the Control Panel Level, but even that wasn't enough. Here's what I did in Windows XP.

1. (PhilBot's instructions) Control Panel -> Network Connections. Right-click "Wireless Network Connection" and select disable. My machine also lists "1394 Connection" so I disabled that too (might be necessary, but don't know).
2. Physically disabled the wireless card. On my Dell Laptop that was accomplished with Fn-F2.
3. Run the cRio imaging tool.

Initially, I didn't do step 2 and it failed with the same error as before. I suspect that steps 1 & 2 must be done in order though I haven't tested it.

This whole setup process has been excruciatingly painful, even beyond the cRio imaging tasks, and as a professional software engineer FIRST will be hearing from me later about good software development and management practices.

[techdude]

Originally Posted by UriF

If this has any value, I solved my problem by installing FRC Tools from the NI USB..

Correct. Installing only the Updates without first installing the tools from the lab view flash drive does not install NI-RIO which is needed to flash the cRIO

[ebarker]

If you install this update from National Instruments it will fix the cRio imaging problem.

For download and details, please visit http://joule.ni.com/nidu/cds/view/p/id/2262

[ayeckley]

Originally Posted by JacobGH

This whole setup process has been excruciatingly painful, even beyond the cRio imaging tasks, and as a professional software engineer FIRST will be hearing from me later about good software development and management practices.

I remember lots of claims back in 2009 (when the new control system first came out) that we'd never have these sort of problems because [paraphrasing several folks at once] "everything is based on TCP/IP, which any child can use". Sigh.

[Capakowski]

I'm having the same problem as the original poster, however, we're using Java and the only image I found was the FRC_2011_v28.zip.

I'm not sure if the problem is with using the 2012 imaging tool, but any help would be much appreciated.