FRC drive station connecting with USB but not wirelessly to RoboRio 2

Technical
1

newfrcdrive
newfrcdrive1028×231 17.4 KB

Recently after updating our software for this year(Flashing Rio SD, updating game tools) our drive station stopped being able to wirelessly connect to our robot via a robot radio.

Here are the notes we took while troubleshooting:

RoboRIO is not connecting to drive station(Communications isn’t green and “RoboRIO2” is red) (error 44002, 44004)

Could be a an issue with the hardware of the RoboRIO itself, we tried on 3 seperate computers.

The Drive Station IS connected to the Radio through wifi(As seen in the picture).

We tried several things:

  1. Connecting the RoboRIO to the computer manually works and allows for communication

  2. We initially pinged the roboRIO wirelessly from the computer and received 0 packets, we switched out the radio to the current one and now when pinging recieve 2-4 packets each time. This still did not fix the communications error however.

  3. We tried using different wires that connected the radio to the roboRIO(through ethernet) but it didn’t change anything.

  4. We tried using an old roboRIO 1 and it DID work and allowed for wireless communications making us think it was an issue with the roboRIO 2(Currently we have the latest RoboRIO 2.0 connected)

  5. After that we tried using an SD card with the 2022 flash connected to the roboRIO but it didn’t work.

  6. Tried reinstalling the game tools and reflashing the latest software to the SD using Balena Etcher.

Lights: (Status Light Quick Reference — FIRST Robotics Competition documentation)

Power working(Not a power issue for radio or roboRIO)

Status holds red for a bit when turned on then goes off

Comms stays red when it has a manual connection but not with wireless

Radio dosen’t light up

Ethernet from radio gives power to roboRIO(Lights up at port)

2

It could be possible that the RIO is actually running but it is not found at 10.TE.AM.2. Here are a couple of things to try:

Connect to the robot over ethernet or radio and open the roboRIO Team Number Setter tool included with WPILib. Check if the RIO shows up in this application, and make sure it is set to your team number if it shows up.

Download Angry IP Scanner here. Connect over Ethernet or radio and run Angry IP Scanner from 10.TE.AM.1 to 10.TE.AM.255. Check if there are any other open addresses other than 10.TE.AM.1 (the radio) or whatever IP your computer is on the robot network. If the RIO is running, you should be able to see the IP of it in Angry IP Scanner. Then, connect to the RIO IP in a browser, and manually change the IP of the RIO to be set at 10.TE.AM.2 (so that driver station will acknowledge that the RIO exists) in the network configuration tab.

3

We were able to use the Team Number Setter to reset the team number and it seemed to work, thanks for the help!

1 Like
4

Thank you for posting! we had the same problem with our Roborio 2. We couldn’t get the team number setter to work, but while on USB we opened 172.22.11.2 with a browser to get the NI dialog for making a static ip 10.TE.AM.2