View Single Post
  #3   Spotlight this post!  
Unread 01-02-2017, 00:42
BSV BSV is offline
FTC / FRC mentor
AKA: Travis
FRC #2723
 
Join Date: May 2013
Rookie Year: 2011
Location: Oklahoma City
Posts: 148
BSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud of
Re: Can't connect to the robot

Quote:
Originally Posted by Mark McLeod View Post
It'd be so much easier if you'd tell us what troubleshooting steps you have taken.
What other directions suggested in this thread and others have you followed?

- Does last year's radio still work as you said before?

- Turn off all firewalls, anti-virus, and third party network management software on your PC. Those all can block communications depending on how they were configured.

- Disable all other network connections (Disable not unplug)

- You can also try pinging roborio-6026-frc.local, roborio-6026-frc.lan, roborio-6026-frc.frc-robot.local
Sorry, I should have said that we looked at the WPI troubleshooting here: http://wpilib.screenstepslive.com/s/...anual-id=24193

as well as trying the other suggestions on this thread.

After your response, we tried a "ping roborio-2723-frc.lan" (did not work, couldn't find IP) "ping roborio-2723-frc.local" (also failed) and "ping roborio-2723-frc.frc-robot.local" (which got a response).

There is no firewall running. It seems that the DNS name is getting assigned incorrectly or not at all by the router, but I'm not a networking expert so I've no idea. Hopefully we can try again with the old radio in the next couple of days to compare results more closely.

Quote:
Originally Posted by Judge2005
Open a cmd window as admin.
Type: netsh int ip reset c:\resetlog.txt and press enter
Restart your computer
This worked... for about 5 seconds before the driver station lost connection again. "ping roborio-2723-frc.local" continued to work after this, though, at least until we restarted the RoboRio to try to get the connection back. When we reconnected after the reboot, that address failed again.

Entering the IP address in the driver station in place of the team number seems to work, but, like I said, it's kind of a guess. It usually comes up as 10.27.23.21 but not always.

Thanks for the suggestions.
Reply With Quote