Losing robot communication a few seconds after enabling

My team is currently having problems communicating with the robot. We successfully connect to the radio but are unable to communicate with the robot. It was originally only happening once in a while, but now we’re totally unable to actually run the robot before it loses communication. We tried connecting the radio directly to the roborio instead of through our switch, but to no avail. What could be wrong?

1 Like

Do you see “No Robot Code” or “No Robot Communication”? If the former, there is a runtime error in your code that’s causing it to crash, and the log should have good info about where the crash is occurring in your code.
If the latter, there are a number of things to check. Is the radio (or roboRio) not getting sufficient power? Is there something (like a piece of metal) shorting one of the PWM or I/O pins? Do you lose communication repeatedly after enabling, or does it happen other times? Try connecting to the robot through ethernet rather than wirelessly to take more components out of the loop and see where the problem is

1 Like

The piece of metal shorting out the Roborio can be very tricky to solve. We had that in a competition. The robot would drive and then stop with a similar issue. Really hard to diagnose.

1 Like