Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Programming (http://www.chiefdelphi.com/forums/forumdisplay.php?f=51)
-   -   Connected to Radio, Not Roborio (http://www.chiefdelphi.com/forums/showthread.php?t=143762)

BadonskyJ56 13-02-2016 12:20

Connected to Radio, Not Roborio
 
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 13-02-2016 12:44

Re: Connected to Radio, Not Roborio
 
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 13-02-2016 13:01

Re: Connected to Radio, Not Roborio
 
I tried that, but I encountered the same issue as before.

Also, here is a screenshot of the drive station:


Alan Anderson 13-02-2016 13:24

Re: Connected to Radio, Not Roborio
 
Make sure the Windows firewall is turned off.

Mark McLeod 13-02-2016 13:32

Re: Connected to Radio, Not Roborio
 
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 13-02-2016 17:02

Re: Connected to Radio, Not Roborio
 
Try giving the roborio a fixed IP address of 10.TE.AM.2

In your case, that would be 10.47.16.2

nighterfighter 13-02-2016 22:11

Re: Connected to Radio, Not Roborio
 
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 14-02-2016 00:52

Re: Connected to Radio, Not Roborio
 
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 14-02-2016 00:56

Re: Connected to Radio, Not Roborio
 
Quote:

Originally Posted by Thad House (Post 1539983)
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 14-02-2016 02:35

Re: Connected to Radio, Not Roborio
 
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 14-02-2016 07:51

Re: Connected to Radio, Not Roborio
 
Did you try hitting the Reset button on the RoboRio after the Radio has booted up?

aaronjeline 14-02-2016 14:47

Re: Connected to Radio, Not Roborio
 
Can I see your Driver Station settings panel?

Thad House 14-02-2016 15:01

Re: Connected to Radio, Not Roborio
 
Quote:

Originally Posted by nighterfighter (Post 1539986)
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 14-02-2016 16:02

Re: Connected to Radio, Not Roborio
 
Quote:

Originally Posted by nighterfighter (Post 1539986)
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 14-02-2016 19:55

Re: Connected to Radio, Not Roborio
 
We are also having this issue. +1


All times are GMT -5. The time now is 16:46.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi