Can connect to the roboRIO by IP but not by hostname

[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.