Can connect to the roboRIO by IP but not by hostname

[Alan Anderson]

Originally Posted by tr6scott

Was told the IPv6 has something to do with the Driver Station idiot lights on the communications tab. Even when it was working the Driver Station never reported the "correct" lights.

Enet Link
DS Radio
Robot Radio
Robot
FMS

In pit only Robot and Robot Radio would turn green, yet we could enable the robot.

• Enet Link should light when there is a physical Ethernet connection active. It will be off in the pit when tethered with USB.
• DS Radio should light only when you're doing something fancy with a wireless access point connected to the Driver Station computer and with the Robot Radio configured as a bridge. It will be off in the pit when tethered with USB.
• Robot Radio should light when you're connected to the robot via wired or wireless Ethernet. It will be off in the pit when tethered with USB.
• Robot should light any time you have a network connection to a properly configured roboRIO.
• FMS should light only when you are plugged in on the competition field. It will be off in the pit when tethered with USB.

I'm surprised Robot Radio was lit. Are you not using the USB connection to tether to your robot in the pit?

[tr6scott]

Originally Posted by Alan Anderson

• Enet Link should light when there is a physical Ethernet connection active. It will be off in the pit when tethered with USB.
• DS Radio should light only when you're doing something fancy with a wireless access point connected to the Driver Station computer and with the Robot Radio configured as a bridge. It will be off in the pit when tethered with USB.
• Robot Radio should light when you're connected to the robot via wired or wireless Ethernet. It will be off in the pit when tethered with USB.
• Robot should light any time you have a network connection to a properly configured roboRIO.
• FMS should light only when you are plugged in on the competition field. It will be off in the pit when tethered with USB.

Our symptom is that the Enet Link is never lit, even when Ethernet tethered on practice field with the bot enabled.

Rest sound right.

I have never seen DS Radio lit either when tethered.

I did see FMS work on the field.

[josephno1]

I had the same issue.
Ended up just plugging in a USB printer cable and connecting to the roboRIO (The ip when connected via usb is always 172.22.11.2).
Then I changed it to a static ip and changed it to 10.36.47.2
To connect to the robot, change your IPV4 address to a static one. I used 10.36.47.5

[SuperBK]

Third Person: Tell Greg to have fun. I had a blast at the NC Guilford County district last weekend.

Hsifeulbhsifder: Sounds like there are some issues with mDNS and Windows 10. I would just switch to static and move on.

All: Here is an interesting article that mentions mDNS support in Windows 10. I know, the FRC software installs its own mNDS service, but maybe there is something build into Windows 10 that is conflicting with it.

Check out this line:

Windows will special‐case domains ending in the .local TLD...
and
The end result of this inconsistent support is that you may or may not be able to reach other machines from programs, games, and web browsers by typing in their mDNS address (for example MacBook.local).

https://www.slightfuture.com/technot...ows-mdns-dnssd

[Hsifeulbhsifder]

Originally Posted by SuperBK

Hsifeulbhsifder: Sounds like there are some issues with mDNS and Windows 10. I would just switch to static and move on.

We switched to static, but we ran into an issue at Greater Toronto East Regional where we were not able to connect to our rio after the configuring the radio. This involved switching from Static to DHCP, which made it so our rio did not have a valid IP at all, so to get an IP we would need to connect it to a DNS server, the only one being the field. Which asks another question: Do teams that are using co-processors connected to the radio, have to also undergo this process if they were static before?

Thank you.

[sanelss]

Originally Posted by Hsifeulbhsifder

We switched to static, but we ran into an issue at Greater Toronto East Regional where we were not able to connect to our rio after the configuring the radio. This involved switching from Static to DHCP, which made it so our rio did not have a valid IP at all, so to get an IP we would need to connect it to a DNS server, the only one being the field. Which asks another question: Do teams that are using co-processors connected to the radio, have to also undergo this process if they were static before?

Thank you.

Not sure if it's related but we're having major issues!!! spent ALL day today trying to fix it and we still don't have a solution.... we currently do not have working vision simply because our vision tablet can't communicate properly and it's all because of the real field setup.... works fine at home and prac field...this issue may very well cost us the one and only regional we do a year.... I really don't know what else can be done. here is the current post on it:

http://www.chiefdelphi.com/forums/sh...d.php?t=145546

[SuperBK]

Yes, read the document called "At the event" pointed out in this thread. https://wpilib.screenstepslive.com/s...g-at-the-event.

Once you switch the roboRIO to static, you have to set everything else to a static IP address as well: driver's station, camera, etc. For example, if you make your roboRio 10.54.28.2, then make the driver's station 10.54.28.5 with a mask of 255.0.0.0. It must have a mask of 255.0.0.0 to connect with the FMS.

You are correct that once you program your radio at the completion, it will no longer deliver any IP addresses. Tethering can work at a competitions if using dynamic IP's because each device will "fall back" to an auto configure address. (169.x.x.x). This didn't always work for us. For one thing, you have to remember to unplug the driver station to cycle the network interface.

For those at competitions with this issue, aren't there control system advisors present? I would think that would get it resolved faster than posting here.