No Communication with Robot

[2011FRC3740]

Re: No Communication with Robot

Check your IPRESET switch on the cRIO, if it is the wrong way it will reset the IP address of the cRIO and you wont target it. You may have to re-image it using the imaging software

[Gwai-lo_1345]

Re: No Communication with Robot

We tried to ping the cRio but it kept saying that the request timed out

[Gwai-lo_1345]

Re: No Communication with Robot

We know that the robot is connected because on another tab on the driver station there is a green light and next to it, it says "Robot"

[Greg McKaskle]

Re: No Communication with Robot

There was a boot timing issue where the wifi bridge would not pass traffic to the cRIO if it finished booting after the cRIO. The result was some of the lights on diagnostics tab would be on, but the robot and code lights would not be. This will resolve itself if you warm reboot the cRIO -- push the reset button.

If these symptoms fit, the latest DS, update 1.1 detects the router in this condition and forces it to rebuild its routing table. You will need this update for competition anyway, so perhaps it is good to install it even if the symptoms don't fit perfectly.

Greg McKaskle

[lhines]

Re: No Communication with Robot

How do you know that it is connected? Can you ping it from the Developer login? (Start>Run...>cmd>ping 10.xx.xx.2, where xx.xx is your team number.)

I have found that if I can ping the robot from the Developer login or access it from another computer plugged into the router, I can connect to the robot with the Driver Station. We have trouble when we forget to do things like power on the router or when we have changed the IP address to acquiring via DHCP or a different static address than 10.xx.xx.5. Maybe you can look to see if any of those issues exist?

[Gwai-lo_1345]

Re: No Communication with Robot

Already tried that, FRC laptop refuses to communicate with the robot

[Mr. Roboto Beefy Head]

Re: No Communication with Robot

try tethering it

[Gwai-lo_1345]

We are trying to program our robot using the FRC laptop and are having a problem.
When we open the driver station it states that there is no communications with the robot, but it also says that it is connected to the robot.
The werid part is that we can still imput the code.
We know its not a wiring problem because we can drive the robot from a desktop.
Any thoughts????????????????