|
Re: 2016 OpenMesh connect to RoboRio issue
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.
|