Hi!
I’m currently following the instructions: https://frc-radio.vivid-hosting.net/getting-started/usage/wiring-your-radio. I’m not very familiar with such technologies, but from what I understand, one radio needs to be connected to your comp and one to the roborio to operate. However, I’m a bit confused how to connect to my computer, as the radio needs 12V power, and plugging an ethernet cable into the radio from my comp port doesn’t turn the radio on. Any help would be so so appreciated - I’m so lost, and nobody else on my team can help.
To run the bot wirelessly in your own shop with two of the VH radios: you are going to need supplemental power from the wall.
Lemme see if I can find some discussion on it.
Here ya go:
Great, it worked! We tried configuring both radios, one to Robot Radio Mode and the other to Access Point Mode. But upon opening up DriverStation, it still won’t connect.
The instructions don’t give any other info after configuring, so I’m a little lost as to what to do.
Drop some pictures of your setup and screenshots of both radios (the one in robot radio mode and the other in team access point mode)
This is what the driverstation says, not sure if it gives any useful info.
For the record, we didn’t know what the wifi channel meant, so we just randomly selected 5 (like in the example).
Have photos of your setup?
I’d update the firmware on both devices to 1.2.2, specifically the “radio variant” found on our website.
@kiettyyyy
Now we are struggling to reach the router address of the radio connected to the computer. We tried using the 10.xx.yy.1 (which worked previously), but now it is unsuccessful. We checked our IP address as well, and it still shows up as 10.43.38.xx. Also, the 192…(etc.) IP does not work either.
Context: We have already configured both, not updated though.
Any help would be greatly appreciated!
After we updated the firmware today we could only access at 10.0.1.1
VH-109’s programmed at the factory are configured to team #1 in Client/STA mode, setting the IP address to 10.0.1.1.
@kiettyyyy
@ArchdukeTim
Haven’t updated yet. And we tried, 10.0.1.1 - doesn’t work.
Alright, we were able to get them going via remote support.
Here’s what I discovered/did:
- Observed user did not statically assign 192.168.69.x/24 to an ethernet adapter
- Assigned 192.168.69.2/24 to an ethernet adapter
- Observed multiple attempted firmware updates, but, used the wrong image
- After clearing out the failed attempts (can be done via a restart), reattempted 1.2.2 FW upgrade on their “field side” radio
- Was successful, configured their “field side” radio as a “Team Access Point”
- Had the remote user move the ethernet cable to their robot
- Performed the 1.2.2 FW upgrade on the “robot” radio
- Was successful, configured their “robot” radio with the same team number and password configured on the “field side” radio
- Observed the radio link come up and was able to reach the “field side” wirelessly
- Had remote user power cycle robot
- Observed that we still didn’t have robot connectivity on the driver station
- Remote user began troubleshooting and discovered that the ethernet cable to the roboRIO was unplugged and reseated it
- Observed that we now had full connectivity on the driver station through the “field side” radio configured as a “Team Access Point” to the robot
11 Likes