Can't connect to the robot

[OreNPluS]

Hello everyone !
my team got a new programming leptop for this year, we got labVIEW set-up and everything on the computer, but i can't get the communication light on the driver station to be green (only red...)(using Wi-Fi), the problem isn't the roboRIO itself because i can connect from every another computer i try...

when i try netstat command on the cmd, the computer did find the ip of the robot, 169.254.175.10, but i when i ping that ip or roboRIO-1577-FRC.local, i am getting:

when pinging 169.254.175.10:
Reply from 169.254.66.43: Destination host unreachable (x4 times)

when pinging roboRIO-1577-FRC.local, it just says it could not find the host...


another funny thing is, when trying to connect using ethernet cable diractly from the computer to the roboRIO, everything work just fine
(the usb port of the roboRIO is unreachable, don't ask.... but i guss it will also work just fine like the ethernet cable)

any ideas ?

[teletype-guy]

I am unsure about your ethernet issue, as I have not dug into the new radio setup (which uses 10.x.x.x, and I don't want to change my laptop from 192.x.x.x). I am testing with just an old router in place of the radio and it works fine.

However, USB should work -- connect a usb cable and disconnect the radio cable. In a browser (with SilverLight added) and go to 172.22.11.2 to get to roboRIO-(team-number)-FRC Sys Config page. Driverstation also works over usb, I believe, for tethered tests.

gil

[OreNPluS]

Originally Posted by teletype-guy

I am unsure about your ethernet issue, as I have not dug into the new radio setup (which uses 10.x.x.x, and I don't want to change my laptop from 192.x.x.x). I am testing with just an old router in place of the radio and it works fine.

However, USB should work -- connect a usb cable and disconnect the radio cable. In a browser (with SilverLight added) and go to 172.22.11.2 to get to roboRIO-(team-number)-FRC Sys Config page. Driverstation also works over usb, I believe, for tethered tests.

gil

that is the thing, using ethernet cable it works fine, usb should work also ...
my problem is, when connecting to the roboRIO using Wi-Fi, i cant get communication on the driverstation ....

[Mark McLeod]

I assume your PC wireless connects to the robot AP just fine.

Try disabling the Windows firewall and any anti-virus you may have running. Those can block the FRC handshake depending on how the connection is treated (Private, etc).

[rich2202]

First thing to check if the IP address of the Programming Laptop is: 169.254.175.xxx. If not, you will have trouble.

Is the IP Address of the Programming Laptop: 169.254.66.xxx? Why is Ping returning 169.254.66.43 if you asked for 169.254.175.10?

I am not a fan of mDNS. I prefer to give everything a valid IP address.

Use IPCONFIG from the CMD box to find out your IP Address.

[mdballard]

I have seen a possibly related problem where the radio sets a frc-robot.local domain on all DHCP clients. This causes pings to the roborio-xxxx-frc.local address to fail and the driver station will not connect. I flashed the ac radio with th 17.2 version of the radio configuration tool. There is no way to configure the domain on it.

I'm still tracking down the issue.

[nickmcski]

Originally Posted by rich2202

Is the IP Address of the Programming Laptop: 169.254.66.xxx? Why is Ping returning 169.254.66.43 if you asked for 169.254.175.10?

That second IP address would be the IP of his computer.

The problem I am seeing is you are getting and APIPA address. Do you have the Ethernet cable directly connected from your laptop to the roboRIO? You should make sure that your openmesh radio is imaged and configured for you team.

[rich2202]

Originally Posted by nickmcski

That second IP address would be the IP of his computer.

It would eventually be a problem if the first 3 numbers in the IP address did not match.

[pascal_bergeron]

Originally Posted by mdballard

I have seen a possibly related problem where the radio sets a frc-robot.local domain on all DHCP clients. This causes pings to the roborio-xxxx-frc.local address to fail and the driver station will not connect. I flashed the ac radio with th 17.2 version of the radio configuration tool. There is no way to configure the domain on it.

I'm still tracking down the issue.

Where you able to solve this?
We seem to be having the same problem with the wifi connection. We can connect through the radio by ethernet cable, but not by wifi.

When connected by wifi, we can ping the roborio by ip address (10.xx.xx.21) but not by name (roborio-xxxx-frc.local). The driver connection cannot connect however. It seems to be a problem with name resolution.