Connected to Radio, Not Roborio

[BadonskyJ56]

Hey CD,

I am able to deploy my code to the robot, but can only connect to the robot radio, and not the roborio. On my drive station, communications and robot code is red, however I can ping it through cmd. Other programmers' computers are able to connect to the driver station. What can I do to fix this?

Thanks.

[rich2202]

On the radio, is the Ethernet cord for the roborio plugged into the port closest to the power plug? If not, try it there.

[BadonskyJ56]

I tried that, but I encountered the same issue as before.

Also, here is a screenshot of the drive station:

[Alan Anderson]

Make sure the Windows firewall is turned off.

[Mark McLeod]

Turn off all firewalls and anti-virus.
Disable all NICs except for the one you are using for the robot (you can add them back in after you get it running).

[rich2202]

Try giving the roborio a fixed IP address of 10.TE.AM.2

In your case, that would be 10.47.16.2

[nighterfighter]

I was experiencing the same problem today.

We could deploy code, ping the RIO, go to the roboRIO web interface, and view the Axis camera connected to the 2nd ethernet port.

But the driver station would not connect.

Firewall was disabled, all other networks except for the Wireless were disabled.

The fix we found was to reset the roboRIO itself, and then the driver station would connect. Not the best solution, but it worked.

[Thad House]

We actually just ended up switching back to the old radios for practice. The new ones are just too unstable for use, especially when you need consistent connections. Hopefully FIRST gets this worked out by competition, otherwise there are going to be major issues with field connectivity the first few weeks

[nighterfighter]

Originally Posted by Thad House

We actually just ended up switching back to the old radios for practice. The new ones are just too unstable for use, especially when you need consistent connections. Hopefully FIRST gets this worked out by competition, otherwise there are going to be major issues with field connectivity the first few weeks

Can you elaborate on that?

Other than the long boot times (~1 minute) for the new radio, after it gets configured we haven't noticed any trouble connecting to the radio. The problem I've been noticing has been between the radio and the roboRIO. (But really it's just the driver station, because we can always ping things).

That's just my experience with it so far; would like to hear other's experiences with the radio.

Edit: That said, I'm sure the long boot times will make turnaround time between matches fun...

[MooseGoose]

We were having the same problem even after we disabled our firewall. We ended setting an exception for driverstation.exe in our firewall and it worked perfectly.

Also, try disabling all of your network adapters except for the wireless adapter to make sure the Driver Station is using the wireless network adapter.

[rich2202]

Did you try hitting the Reset button on the RoboRio after the Radio has booted up?

[aaronjeline]

Can I see your Driver Station settings panel?

[Thad House]

Originally Posted by nighterfighter

Can you elaborate on that?

Other than the long boot times (~1 minute) for the new radio, after it gets configured we haven't noticed any trouble connecting to the radio. The problem I've been noticing has been between the radio and the roboRIO. (But really it's just the driver station, because we can always ping things).

That's just my experience with it so far; would like to hear other's experiences with the radio.

Edit: That said, I'm sure the long boot times will make turnaround time between matches fun...

The actual root cause of the DS not connecting to the roboRIO is the mDNS resolution on the new radio not working right. It's still possible to ping, but the mDNS address won't resolve, which causes the DS to not connect. Switching to the old radio makes all those problems go away, and DS to RoboRIO connections become much more reliable. For practice, its just not worth dealing with the issues with the new radio. Hopefully competition doesn't have those issues.

[edong4273]

Originally Posted by nighterfighter

Can you elaborate on that?

Other than the long boot times (~1 minute) for the new radio, after it gets configured we haven't noticed any trouble connecting to the radio. The problem I've been noticing has been between the radio and the roboRIO. (But really it's just the driver station, because we can always ping things).

That's just my experience with it so far; would like to hear other's experiences with the radio.

Edit: That said, I'm sure the long boot times will make turnaround time between matches fun...

Besides the long boot time, our team has had no issues with the new radio.

[tr6scott]

We are also having this issue. +1