Re-Imaging FAILURE...Losing sanity!

[manderson5192]

Hey guys,

I'm running a Dell XPS M1530 with Vista and I'm trying to reimage the cRIO. Unfortunately, all my attempts to do so have bet met with complete failure . I am connected to the cRIO port 1 via crossover cable and when I go to my LAN connection in the Network and Sharing center I can setup the IPv4 setting so that my ip address is 10.0.0.6 and the subnet mask is 255.0.0.0. The default gateway and preffered DNS server boxes are completely blank ( I assume that is right?).

I believe that Windows Firewall is shut off (at least in the GUI it says so read: how do I make sure it's absolutely dead?) and PcCillin is disabled. I am using the latest imaging tool/image. The tool is able to detect the cRIO but the update keeps FAILING!!!

I get a variety of errors: it will sometimes say that it cannot connect to the cRIO when I can fire up cmd and ping the **** thing. Other times it will connect and go on to the step after connecting and then output an error message that reads

"Unable to complete operation because of unexpected error 60: UDP Open in repFRC open connection.vi->SendRebootCmd.vi->RebootSystem.vi->SetTargetConfig.vi->Set IP Address.vi->ConfigUtility.lvlib:SetIPAddrAndGetInfo.vi->ConfigUtility.lvlib:ReImageTarget.vi->ConfigUtility.lvlibialog.vi"

One time it even went through all the re-imaging steps and indicated success but said the IP address was set to 10.0.0.2 instead of 10.9.48.2. (I'm on team 948).

For some more background, I am trying to set it up for WindRiver Workbench and the image is named FRC_2009_v7.zip. Every time the tool has been run the Device Name field has had "FRC-cRIO-948" and every time the Team ID field has read 948. The cRIO has always showed up with the Name "temp", if that bit of information is helpful.

I have also tried setting my laptop to 10.9.48.6, in case that was the problem. Yesterday, the problem I had was the same but every now and then the cRIO IP would randomly appear as 10.0.0.0, 10.0.0.2, or 10.9.48.2. This is soooooo infuriating. Could the problem be that I made the criminal mistake of installing Vista on my computer? Do I need to re-install labview?

I'm about at wit's end with this.

Thanks,
-Matt

[Jim E]

Hello,

I'm no expert, but I think for WindRiver there is a different image to load. The one you specified is for developing in labview. Please check to make sure you have the right image for Windriver.

I had issues with this image too. My issue was it wouldn't configure the secondary port properly. You can read about my successful solution here:

http://decibel.ni.com/content/message/3478#3478

Good Luck.

[manderson5192]

No, it is the same V7 image that is used for BOTH labview and WindRiver. The WPI site about programming w/ WindRiver SPECIFICALLY says that everyone needs to use that image.

Any other ideas?

-Matt

[Alan Anderson]

Unplug the cRIO and ping 10.9.48.2 to see if anything responds. Error 60 indicates the requested IP address is already in use on the network. Find the device that's hogging 10.9.48.2 and give it a slap upside the head...I mean, correct the problem.

[Joe Hershberger]

That is correct... you should be using the same image regardless of environment.

Is there more than one network interface on that computer? If there is, disable all but the one wired interface that you are using to connect to the controller.

Do you have a different computer you can try?

[Gopal]

Just a thought - use a straight thru Ethernet cable. The crossover is for the camera only. The ports on cRIO are not autosensing is what I read. Now this should not be a problem if the laptop's port is autosensing but why add another variable there?

While using the cRIO tool, make sure the right environment radio button is selected - it defaults to LabView.

A useful tool is the GeCo Pinger I saw either here or on CD - great tool to check that all connections are working correctly with the correct team number.

[manderson5192]

Problem solved, although I don't know what the reason for the failure was. I installed LabView on my 6-year-old laptop running good-old XP and it worked on the first shot (re-imaging).

I guess we chalk another one up for everyone's favorite operating system, Windows Vista .

-Matt

[TDohse]

We now understand why reimaging with Vista sometimes fails and we have a workaround. We're investigating if the imaging tool can be modified to not need the workaround. The workaround is to have a switch or router between the cRIO and Vista PC when running the imaging utility.

For inquiring minds who want to understand the issue: Vista resets the network card to 0.0.0.0 when the cable is unplugged or there is no connection, even when the NIC is set to use a static IP address. Because of this, when the cRIO reboots with IP 0.0.0.0 during the reimaging process, it may see its network address is already taken causing an error. There is a race condition between Vista recognizing the connection is back and changing to the correct IP and the cRIO erroring out due to IP conflict. The error 60 is actually coming from a conflict at 0.0.0.0, not 10.xx.yy.2 as one would otherwise suspect. XP does not have this network behavior.

[Stephanie Brierty]

You should call in to NI and talk to the engineers there. 1-866-511-6285 from 1-7pm Central.