2016 OpenMesh connect to RoboRio issue

[5010Mentor]

Our students were having a connectivity issue between the 2016 Roborio and OpenMesh hardware.

While working on the issue, they decided to reconfigure the Roborio and OpenMesh using the 2017 configuration utilities. Now, they are having problems deploying to the Roborio through wireless access.

What I have been able to deduce is the following:
1) Deploying to the Roborio directly (bypassing the radio) is not a problem using 2017 utilities.
2) Deploying to the Roborio through the radio wireless fails when configured with 2017 configuration utility.
3) Deploying to the Roborio through the radio wireless when it is reconfigured with 2016 configuration utility is fine. But, the driver station has no control.

Any suggestions?

[Mark McLeod]

As a diagnostic would you ping each of these:

• roborio-6026-frc.local
• roborio-6026-frc.lan
• roborio-6026-frc.frc-robot.local
• The actual IP address assigned to the roboRIO

To get the roboRIO IP address, with the roboRIO connected to the radio , use a PC to connect directly to the roboRIO via a USB cable. Use a web browser (IE or Firefox) to go to 172.22.11.2 and see what Ethernet address was given to the roboRIO. It will be on the front page.

[5010Mentor]

Thanks. Will try some additional diagnostics tonight.

I did forget to include the following diagnostic statement....
1) The issue is related to the Ethernet access for this one specific OpenMesh radio. We moved the radio to another RoboRio along with swapping cabling and saw the same symptoms that existed with prior RoboRio.

[Mark McLeod]

There does appear to be an oddity in the construction of the roboRIO DNS name on some setups where the radio throws an extra frc-robot into the mix.

e.g., roborio-6026-frc.frc-robot.local

[5010Mentor]

Debugging detail tonight has narrowed the scope of the problem to the 2016 OpenMesh radio. The problem follows the radio no matter where we put it.

1) roboRio 172.xx.xx.xx address resolves thru USB.
2) roboRio gets a DHCP address assigned via the 2016 OpenMesh radio.
3) roboRio can get ping'd via IP address and roborio-xxxx-FRC.lan when connected through radio.
4) Laptops cannot find roboRio thru mDNS resolution. Switch out the OpenMesh radio to the one we received this year and configured....all is happy.

Thinking that there is a firmware update that needs to be applied to last year's radio, but we receive a timeout within the configuration utility.