VH-109 Radio doesn't work very well

We are trying to get this radio configured like the old OpenMesh OM5P-AN radios. We would put a OpenMesh OM5P-AN radio on the robot and it would act as an AP.

Reading through this:
https://frc-radio.vivid-hosting.net/getting-started/usage/practicing-at-home#id-2.4ghz-access-point

It seems like I should be able to configure to AP mode. I was able to connect to it, it gave me an IP address. I was able to get to the config page. But after setting a team number, it is dead. I can’t connect to it, I can ping it. I’ve tried numerous static IP address:
10.12.34.100
10.0.1.100
10.70.48.100 (our team number, which is what address seemed to be assigned to my computer after setting the team number).
192.168.69.100

I don’t see any AP. Is this radio bricked? We only used it at worlds.

I also read through this one, but nothing in there works for me.

Do I need newer firmware? On the management interface it doesn’t show the firmware version. So I have no idea what version I’m running or if I need to update.

It should be 10.70.48.1 as far as I’m aware. Check the second blue box at the top of the page here:

I’m not sure what you mean by the second blue box. I can’t get to the management interface anymore nor can I ping the device.

On the page I linked to, there are two info boxes near the top with blue backgrounds.

That said, I stand corrected. AP mode should have a .4 address

3 Likes

Is your radio configured to the “Robot Radio Mode” or the “Access point mode”?
Are you trying to connect wirelessly or through ethernet?
Where did you find that made you try the 10.yy.zz.100 IP’s?

So this radio seems really slow to boot. I walked away from my computer for about an hour. Now I have an IP address of 10.70.48.100. I did set it to AP mode. I can ping 10.70.48.4, but I can’t access a management interface at that location, nor do I see a WiFi AP.

OK, I was able to connect to the management interface on 10.70.48.4, I reconfigured the radio to a “Robot Radio Mode”, put in a WPA key for the 2.4 GHz AP mode. Then it showed up as an AP. Thanks for the help folks!!!

2 Likes

Glad you got it working!

Circling back to a different question you had on firmware - there is a critical firmware update you should apply ASAP. Get beyond V1.2.5 (as of tonight it looks like 1.2.6 is the latest).

Also note: as documented here on CD and having seen some teams experience it this last weekend at an offseason demo - the 2.4GHz radio is not the “priority” radio. When running robots for a lengthy period of time and the radio becomes hot it will throttle 2.4GHz performance and you may experience comms drops. Separately you are also competing with numerous other devices on 2.4GHz and may experience comms drops or degrading performance with distance dependign on your wireless environment.

So far all teams to use a 2ed radio connected to their laptop and utilize the 6GHz radio have seen superb performance - I have yet to see anyone complain about the connection after the upgrade.

2 Likes

Definitely sounds like you’re on a much older software release. Please update :slight_smile:

1 Like

I will try and update. I tried last night and it just did nothing. No LEDs flashed. The management interface showed the firmware uploading but then nothing. I have no idea what version of software is currently in there.

It looks like, per the docs, that I need a second radio if I want to use the 6 GHz channels or I need to buy a WiFi 6 router to place next to the laptop. Is that correct?

Is there a way to reset the radio to factory defaults. It will NOT assign an IP address now… This thing is a bit fragile it appears.

You likely uploaded the wrong version. On the downloads page there’s firmware for devices currently on releases older than 1.2.0 and another that’s for devices at 1.2.0 or newer.

We had the same issue. Newer releases clearly declare what version they are running, while older releases do not. So if you do not see a footer with the version clearly declared, it’s probably old enough that you should use the older method. The good news is if you supply the wrong firmware (i.e., signed with the incorrect key), nothing “bad” seems to happy; it just somewhat silently does nothing, until you realize you should probably use the other version. :slight_smile:

Sorry about that… it was clearly an oversight on our part.

3 Likes