Radio Configuration Utility 17.3 vs. 2016 Radio

Technical Programming
1

Radio Configuration Utility 17.3, released last week, is giving us grief when used on last year’s Open Mesh OM5P-AM radio. I’m curious if anyone else is seeing the same results.

The firmware update/config process goes fine, but after applying that update the connected roboRIO will no longer respond to ping or SSH login requests, either by hostname or static IP address. This prevents code from deploying. Oddly, it still connects to the driver station application, and the roboRIO webpage configuration can still be brought up.

If we re-configure the older radios using the 17.0 utility, they work fine. The newer Open Mesh OM5P-AC models work fine with either configuration utility/firmware. We’re reproduced this on two radios of each model and two roboRIOs.

Is anyone else seeing this? Is there a detail we’re maybe missing somewhere?

2

We were having the same issue last night. Reverting to the 17.2 release of the radio configuration utility and flashing/configuring the radio fixed it for us. This issue was observed on both the new radio, and radio from last year.

The only difference we were having compared to you was that we were also unable to access the configuration page via the hostname of the roboRio.

3

The way we were able to fix was to uncheck the bandwidth limit box. After that we could access the RIO again and deploy code.

4

What mode did you set it in? We had issues with 5ghz, but not 2.4ghz.

5

We’re using the defaults (except for team number). 2.4 GHz, BW limit on, Firewall off, etc.

Tonight I’ll try with the BW limit off, see if that changes the behavior.

6

Experiencing the same issues with AC and AN radios. Requires multiple reboots of DS and RIO to reconnect.