We have a problem similar to this recent thread. Basically, our radio will turn on and flash the correct lights, and the computer will connect to the wifi, but the driver station will still show red for communications. In diagnostics, robot radio is green and we can ping the IP successfully. The web dashboard also does not show up. We tested all of the solutions mentioned in the previously linked thread. None had any effect, except for setting our team name to the radio IP. However, this only made the robot light turn green in diagnostics; we still couldn’t communicate;
But here’s where is gets interesting - the only times when we do connect successfully is the first time each day. If we ever turn the robot off again, the radio start getting weird again.
How is the *first time each day *defined?
Fresh boot of laptop + fresh boot of robot at the same time and it works again, or it works once every 24 hours?
So we figured out what it’s doing and we can get it to work, but we’re not exactly sure why. The radio assigns itself the IP of either 10.14.52.39 or 10.14.52.105, which we can find with ipconfig in Windows command prompt. The roboRIO is assigned the IP of either 10.14.52.40 or 10.14.52.106, which we think is because the radio gives it the next one up after its own address. Typing the roboRIO IP into driverstation or web dashboard allows us to connect to them, so we can use both perfectly well. Our only question now is what exactly determines whether the roboRIO is given the 40 or 106 IP, because so far as we can determine it’s completely random and unrelated to whether ipconfig gives 39 or 105 for the radio. It’s not a huge concern, as we can just try both very easily and it nearly always stays the same while the robot is on, but we did have one test where the IP actually switched from 106 to 40 about 3 seconds after we connected to 106, which would obviously be a problem if it occurred during competition. Any ideas on what could be causing this? Thanks!
It’s called DHCP (Dynamic Host Configuration Protocol).
It’s the dynamic part of it that’s moving the IP assignments around.
It means IPs are assigned and they can be different all the time, but devices like PCs and roboRIOs can add-in or drop out at any time.
Instead of using IP addresses, you should be using DNS names, but you probably have a DNS suffix problem.
As a test try typing this name into the Driver Station in place of the IP address you have been using:
roboRIO-1452-FRC.frc-robot.local
If that works, then I have something else for you to experiment with to fix your issue.
Sometimes, but if it is then the Driver Station shouldn’t have problems finding it.
There is sometimes a spurious “.frc-robot.” thrown into the middle.
There is an easy solution if this is the case here, but I’d like to confirm the issue, before going through that.
You could try updating. The 2016 Version will configure the OM5P-AN, The 2017 version will configure the OM5P-AN and OM5P-AC. BUT, YOU MUST UPDATE THE FIRMWARE FOR THE OM5P-AN OR THE FIRST RADIO CONFIGURATION UTILITY VERSION 17 WILL NOT COMMUNICATE WITH THE OM5P-AN. The OM5P-AN in its current firmware can be configured to communicate on an unauthorized frequency. The OM5P-AC is setup to not allow ANY SSH Communications OR Manual Configuration.