cRIO-II not connecting

[JonathonSchad]

Hi. My name is Jonathon Schad, a programmer for FRC team 3418. Last night we successfully connected, imaged v43, and deployed code to the cRIO and were able to connect the Driver Station and run the robot. Somewhere inbetween now and then I think the reset button on the cRIO may have been pressed. Now we can't see the cRIO using the FRC Imaging Tool or Measurement and Automation and can't deploy code through Wind River (it just times out, no error), but the Driver Station can still successfully connect and is able to run the previously deployed code. I still have access to ftp the cRIO. I have checked the IP and subnet settings and they are as they should be. Our laptop is connected directly to the cRIO with a crossover cable.

Any ideas...

[Kevin_F]

Hey Jonathon,

Is the status light blinking on your cRIO? I would try putting the cRIO into safe mode (holding the reset button for ~5 seconds) and then seeing if you can connect to it in MAX.  Are you able to ping the cRIO from the command prompt?

[JonathonSchad]

Kevin,

I put it into safe mode and could see it on MAX. I tried to do an IP Reset to see if it reestablished the connection with the imaging tool and now nothing recognizes it.

[Kevin_F]

Hey Jonathon,

When you hit the IP Reset on the cRIO when it is directly connected to the computer it is goign to assign a local IP address to the cRIO. Your computer is probably set up to have a static IP right now. I think the steps you will need to fix this are:

-Set your PC network adapter back to DHCP/Automatically obtain ip address

-Restart your controller and locate it in MAX

-Set the IP address of your controller in MAX (Network Settings Tab) to what you need for FRC (The 10.xx.yy.6)

-Set your computer back to its original static IP

-See if it shows up in MAX again.

-If it does you should be able to image it again

Did you make any modifications to the original robot code when you ran into this issue originally? It sounds like what maybe happened is that the code running on the cRIO was doing something super processor intensive that was starving the TCP communication loop to be able to access the cRIO from LabVIEW.

[JonathonSchad]

Kevin,

This seemed to fix the issues. Whatever was causing it not to fully connect must have been fixed by the IP reset and then it was just a matter of going through the process you described above to get it back connected. Everything works now. Thanks for the support.