Can't communicate with cRIO

[duffany1]

So I just installed all the necessary updates (finally...) and we re-imaged the cRIO with the proper 2011 image.

Now we are having difficulty connecting our driver station to the cRIO. Here's the error: when we choose the option "Reboot Robot...," we get "cRIO isn't responding, physical reboot required." In diagnostics, the 'Enet link' circle is green, but the 'Robot' circle is red.

Overall we just can't establish communication. Any ideas?

Thanks in advance.

[kinganu123]

we had a similar problem as well, but couldn't upload files into the cRIO. Did you change your classmate's ip to 10.0.0.5 or 10.0.0.6?

[Alan Anderson]

Originally Posted by duffany1

So I just installed all the necessary updates (finally...) and we re-imaged the cRIO with the proper 2011 image.

Now we are having difficulty connecting our driver station to the cRIO.

Is it just the Driver Station having problems communicating with the cRIO? What computer did you use to load the cRIO image? What program have you loaded into the cRIO?

[Greg McKaskle]

What lights are lit on the Diagnostics tab? The first indicates that a valid cable connects the DS to something. I believe the second is for the .4 router if in use, the third is for the bridge on the robot, fourth is for cRIO.

These are the result of pings to the devices.

If the first light is on and no others, it typically means an IP address issue. When you formatted the cRIO, you should have entered your team#. Enter the same into the Setup tab of the DS laptop and the DS will set the NICs IPs appropriately. If that doesn't work, please try to determine the IP addresses of the laptop NIC you are using, the cRIO, the dlink and all other devices between the DS and cRIO. If the issue isn't apparent, post that list here for more assistance.

Greg McKaskle

[Pat_Cunningham]

Hello,
I am from FRC Team 178 and I am having the same issue. I've checked my IP Address's and they all check out ok. The robot doesn't communicate properly after an OTA Server Update has been put on by NetBeans (6.7.1 with 2011 FRC plugins). Any help with this issue would be appreciated.

Thanks,
Pat Cunningham

[tutkows1]

In netbeans you have to go to options and set your select your team number for the FRC plug in. Otherwise netbeans will try to contact 10.00.00.2 not your proper IP address no matter what your computer is set at.

[Pat_Cunningham]

Hello,
I have that all setup and the only thing it does it connect to the robot, 'load the image', and says 'waiting for robot to reboot' and never comes back. When I manually reboot the robot, it says that no code got loaded.

Thanks,
Pat Cunningham

[duffany1]

Well the thing is, I am in WindRiver and I go to FIRST > Deploy and I am able to deploy the proper code to the robot (I was using a simple program I had written to flip a switch and enable the compressor).

I am not using the classmate but I have tried the classmate and our team laptop; I have tried 10.1.95.6 and 10.1.95.5. Neither worked.

EDIT:

I solved the problem! Thanks for all the suggestions you guys offered.

[bodoggy]

How do you load an image to the cRios if you cannot establish communictaion with your driver station? I missed that part.

[donny2011]

Hello, I am from team 3373 and my issue is that I can connect to the cRIO, but the connection keeps flickering on and off consistently. Is there anything that could be interfering with the communication between the cRIO and the router?

[bodoggy]

how did you setup the ip on the crio?

[plnyyanks]

Originally Posted by bodoggy

how did you setup the ip on the crio?

you set your team number when you image the cRIO. it will then set the IP to 10.xx.yy.02 (for example, for team 1124: 10.11.24.02)

[wazcodez]

Did you follow the instruction ?

make sure cirio is not in safe mode !!!!

and ur ip configuration regarding classmate or laptop is correct !

[bodoggy]

I had done all that but the D-Link bridge/hub was not assigning the cRio 10.16.35.2 (1635 is our team). So I was able to use the Linksys we had to manually reserve that address for it. Now I see green for robot in the Driver station and am able to ping it successfully but cannot reboot it from the software button and the FRC imaging tool keeps wanting to rescan because it cannot find it, either. Now what? This is real frustrating-working on it for two whole days!

[bodoggy]

Update: Now I rebooted the cRio by powering down and back up and I cannot ping it again. Robot is red in DS. All this on the D-Link!