|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
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. Last edited by BadonskyJ56 : 13-02-2016 at 12:27. Reason: Forgot to add in additional information. |
|
#2
|
|||
|
|||
|
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.
|
|
#3
|
|||
|
|||
|
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: ![]() |
|
#4
|
|||||
|
|||||
|
Re: Connected to Radio, Not Roborio
Make sure the Windows firewall is turned off.
|
|
#5
|
|||||
|
|||||
|
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). |
|
#6
|
|||
|
|||
|
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 |
|
#7
|
|||
|
|||
|
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. |
|
#8
|
||||
|
||||
|
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
|
|
#9
|
|||
|
|||
|
Re: Connected to Radio, Not Roborio
Quote:
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... Last edited by nighterfighter : 14-02-2016 at 00:58. |
|
#10
|
|||
|
|||
|
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. Last edited by MooseGoose : 14-02-2016 at 02:38. |
|
#11
|
|||
|
|||
|
Re: Connected to Radio, Not Roborio
Did you try hitting the Reset button on the RoboRio after the Radio has booted up?
|
|
#12
|
|||
|
|||
|
Re: Connected to Radio, Not Roborio
Can I see your Driver Station settings panel?
|
|
#13
|
||||
|
||||
|
Re: Connected to Radio, Not Roborio
Quote:
|
|
#14
|
||||
|
||||
|
Re: Connected to Radio, Not Roborio
Quote:
|
|
#15
|
||||
|
||||
|
Re: Connected to Radio, Not Roborio
We are also having this issue. +1
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|