I just noticed a weird issue where my teams new RIO 2 is getting the wrong address. As opposed to getting 10.59.85.2 it was getting 10.59.85.34. This means that driverstation has issues finding it. Is this something I have done or is this another issue?
1 Like
You’re not supposed to need to do this, but we always set the roborio to a static ip through the web interface.
If mdns is working on your computer, then it doesn’t matter if the roboRIO is getting a different IP address on the same subnet.
1 Like
FWIW… setting a static IP address is just what we do every year. Sounds like the radio firmware should hand out a consistent one when it sees the RIO.
But… whenever the radio is involved, a belt-and-suspenders approach never seems to hurt.
Thanks for the replies, this appears to be an issue with the rio 2s as both teams I am on had the same issue. This just needs to be fixed in the web config. It also appears that the host name resets with the SD card. We were able to fix this and everything worked well.
If you are running DHCP which is standard. The radio assigns the first available IP from the DHCP pool. It does not have to be 10.xx.xx.2. If things are configured correctly, it does not matter.
A lot of teams run static address which is where .2 comes from.
All the configuration is on the SD card so that is where the IP settings comes from
After imaging the SD card, did you set the team number using the imaging tool per the instructions? roboRIO 2.0 microSD Card Imaging — FIRST Robotics Competition documentation This is what sets the host name.
Actually, the radio DHCP server special cases the Rio to put the Rio on .2.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.