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.
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?