Unable to re-image cRIO

[slavik262]

My team tried re-imaging the cRIO first using the update that was installed with LabVIEW and the other NI equipment. An error occurred in the middle of imaging. I then realized we had misread the documentation and downloaded the newest update FRCLabVIEWUpdate1.0, as per the instructions on the WPI C++ page (we are coding in C++). I then tried to re-image the cRIO with the image installed with the update (version 2). This however continuously failed and generated an error saying that the IP of the cRIO could not be found.

(For reference in the next paragraph, we are team 537.)

Every time we loaded the NI cRIO Imaging tool, the tool would indicate that our cRIO was located at either 10.5.37.2 or 10.0.0.2. The IP seemed to switch every time I launched the Imaging tool (from 10.0.0.2 to 10.5.37.2 or from 10.5.37.2 to 10.0.0.2) on an apparently random basis. I'm wondering if this could have been caused by the abortion of the imaging process the first time we tried to image the cRIO (see the above paragraph). To test connectivity, command prompt was used to ping the cRIO. It always responded at 10.0.0.2, but never from 10.5.37.2.

The entire process was done following Chapter 5 Configuration of the documentation located at http://usfirst.org/community/frc/content.aspx?id=10934 yesterday (Dec. 2).

The laptop was plugged into the driver station (which was powered on) and the driver station was connected to port 1 of the cRIO. The laptop's IP was set to both 10.5.37.6 and 10.0.0.6. Both did not generate any new success. A subnet mask of 255.0.0.0 was used at all times.

We are using a laptop with one ethernet port, built-in wireless (which was on at the time), and running Windows Vista. Other than disabling the wireless card next time I try this, do you have any suggestions?

[TDohse]

I've never seen behavior like you describe, but the IP address changing could be caused by running the tool and forgetting to enter your team number, it would then use the default team 0 and set the IP to 10.0.0.2.

As to the unreachable IP error, this would suggest that maybe the wireless card is interfering, or maybe your network setup has some additional piece of hardware in it (router) which is not forwarding packets. During the re-imaging process, the cRIO is temporarily in a state where its IP is 0.0.0.0.

[slavik262]

I've never seen behavior like you describe, but the IP address changing could be caused by running the tool and forgetting to enter your team number, it would then use the default team 0 and set the IP to 10.0.0.2.

I am positive that this mistake was never made. For one instance the team number was intentionally set to 0 once we couldn't get it to work using team number 537. This still produced no results.

As to your other comments, I'll double check to make sure that nothing else is interfering or I'll use another laptop.

[kbaker159]

You might try only connecting the cRIO and the laptop and eliminating the DS and router entirely. That seemed to get me a reliable connection with ours. Use the orange crossover cable between the laptop and cRIO. Also, Not sure if this is an issue, but I have the IPv6 disabled on my vista computer because it doesn't seem to do anything. It might cause an issue, but I'm not sure. You can change that in the connection properties.

Hope you get it working soon

[slavik262]

You might try only connecting the cRIO and the laptop and eliminating the DS and router entirely. That seemed to get me a reliable connection with ours. Use the orange crossover cable between the laptop and cRIO. Also, Not sure if this is an issue, but I have the IPv6 disabled on my vista computer because it doesn't seem to do anything. It might cause an issue, but I'm not sure. You can change that in the connection properties.

Hope you get it working soon

We tried a direct connection with the crossover cable without success. From what I've gathered here and on Chief Delphi, we're going to experiment with some network options on the computer and see how things go from there. Thanks for the help.

[kbaker159]

Might I also recommend that you try another computer. It might be configured correctly. It would be good to know the source of this problem though.

[slavik262]

The problem was caused by the firewall. Disabling it solved all everything. Thanks for the help.

[jboette]

Thank you for the tip about disabling the Firewall. I was having the same problem as you described and was scratching and getting nothing but splinters. You saved the day with the disable firewall tip. TNX agn. They should include the firewall disable comment in the next revision of the how to doc. Everybody usually has their firewall on. This forum earned its pay today!

[jross]

What firewall(s) are giving people trouble? It seems that most people don't have trouble, so it's probably limited to a specific firewall or two. It works just fine on my computer with McAfee Internet Security Suite.

[slavik262]

The default Windows Vista firewall was causing the problem.