Re: Can't connect to the robot
 

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

Re: Can't connect to the robot
 

We were having very similar problems as described in the first post in this thread. This fixed it:

1. Open a cmd window as admin.
2. Type: netsh int ip reset c:\resetlog.txt and press enter
3. Restart your computer

Hope this works for anyone looking for a solution to this.

Re: Can't connect to the robot
 

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.

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.

Re: Can't connect to the robot
 

Since it works, you can type roborio-2723-frc.frc-robot.local into the Driver Station in place of the team number. That should keep you connected.

There does appear to be an oddity in the construction of the roboRIO DNS name on some setups where it throws that extra frc-robot into the mix.

It really disrupts Java/C++ downloads which check a variety of addresses to connect, but not that extra frc-robot address.
Then you have to add that extra address to the list it checks.

Re: Can't connect to the robot
 

Thanks Mark! This is the condition we've been struggling with.It's great to know someone understands the problem; a solution is sure to follow. No pressure. :)

The "what do we do meanwhile" bottom line appears to be:
1) The DS won't connect. The workaround you gave handles this.
2) Cannot deploy from Eclipse. Direct connection via USB works around this. Back to the old IFI days.

Re: Can't connect to the robot
 

Can you clarify what the web page says that the device name is? Is it roboRIO-####-frc or does the name shown in the web page end in .frc-robot?

If so, can you remove .frc-robot to get it to work?

Greg McKaskle

Re: Can't connect to the robot
 

In the cases I've seen the roboRIO has the expected

• Hostname: roboRIO-team#-FRC

But with

• DNS Name: roboRIO-team#-FRC.frc-robot.local

I can't edit the DNS name through the web browser and I haven't tried other methods.

On the PC connected to run the Driver Station it might or might not include a DNS Suffix Search List: frc-robot.local (from an ipconfig /all).
It appears to be somewhat random on any particular PC, i.e., I can have two side-by-side PC's attempting to connect and one will work, but the other fail. After disconnecting/restarting the radio both PCs may work.
Depending on if the PC has the search suffix then the Driver Station will connect, but code download still might fail probably from not including the unexpected DNS suffix.

I made Kevin aware of the issue.

Re: Can't connect to the robot
 

The unexpected ".frc-robot" is apparently confusing both the DS and Eclipse deployment.

What I have seen on my system (Windows 10):

1) Somebody, somewhere, is setting the "Connection-specific DNS Suffix" for the wireless adapter to "frc-robot.local" (see "ipconfig /all"). I don't know how this is happening but it looks broken to me. Radio firmware?

2) If you go to Control Panel->Network and Internet->Network and Sharing Center->Change Adapter Settings->(select) Wi-Fi->(tab)Change settings of this connection->(in dialog, select)Internet Protocol Version 4->Properties->Advanced->(tab)DNS, you'll see what appear to be a couple of ways to override the above setting:

a) Change "Append primary..." to "Append these..." and put "local" in the list.
-or-
b) Put "local" into the "DNS suffix for this connection" box.

In very limited testing either seems to work for me.

I am NOT a Windows expert (and wouldn't admit it if I were). If those who are disagree, trust them not me.

Re: Can't connect to the robot
 

I've had success with this as well, but I haven't been able to vet it in all cases yet. I have to make my team rounds.
I had one case where it didn't help, because the PC suffix was wrong, but I didn't try adding frc-robot.local as an ending on that one.

Re: Can't connect to the robot
 

One more observation to throw into the mix: everything works for over Ethernet. Interestingly, if I ping the roboRIO over Ethernet, it uses an IPv6 address.

Also, further to my post about netsh: for us it works until we switch the wifi to the Internet. Then when we switch back it is all broken again.

The only solution we have which seems to work for eclipse and the drive station (and hopefully GRIP) is to set a static IP address on the roboRIO, then add all host name variants to the Windows host file.

This makes me very nervous though: What is going to happen when we get to competition? We really need a permanent solution to this soon.

Re: Can't connect to the robot
 

One more observation to throw into the mix: everything works for over Ethernet. Interestingly, if I ping the roboRIO over Ethernet, it uses an IPv6 address.

Also, further to my post about netsh: for us it works until we switch the wifi to the Internet. Then when we switch back it is all broken again.

The only solution we have which seems to work for eclipse and the drive station (and hopefully GRIP) is to set a static IP address on the roboRIO, then add all host name variants to the Windows host file.

This makes me very nervous though: What is going to happen when we get to competition? We really need a permanent solution to this soon.

Re: Can't connect to the robot
 

We're expecting the Sam problem and easy fixes yet?

Re: Can't connect to the robot
 

Unable to ping the Wifi but able to ping with USB cable to RoboRio.

Re: Can't connect to the robot
 

Don't know how to edit previous post sorry. We solved our problem by simply disabling all wifi connections on the PC except the robot and it connected perfectly. It appears the wifi connection to the internet on the PC was the problem.