Skip to content

Commit

Permalink
Update to using the VH-109 Radio (#2885)
Browse files Browse the repository at this point in the history
  • Loading branch information
jasondaming authored Jan 1, 2025
1 parent 6ae1c5b commit a6ad120
Show file tree
Hide file tree
Showing 50 changed files with 169 additions and 446 deletions.
22 changes: 6 additions & 16 deletions source/docs/controls-overviews/control-system-hardware.rst
Original file line number Diff line number Diff line change
Expand Up @@ -66,25 +66,15 @@ The [REV Power Distribution Hub](https://docs.revrobotics.com/rev-11-1850/) (PDH
:alt: CTRE Voltage Regulator Module
:width: 500

The CTRE Voltage Regulator Module (VRM) is an independent module that is powered by 12 volts. The device is wired to a dedicated connector on the PDP. The module has multiple regulated 12V and 5V outputs. The purpose of the VRM is to provide regulated power for the robot radio, custom circuits, and IP vision cameras. For more information, see the [VRM User Manual](https://ctre.download/files/user-manual/VRM%20User's%20Guide.pdf).
The CTRE Voltage Regulator Module (VRM) is an independent module that is powered by 12 volts. The device is wired to a dedicated connector on the PDP. The module has multiple regulated 12V and 5V outputs. The purpose of the VRM is to provide regulated power for the custom circuits, and IP vision cameras. For more information, see the [VRM User Manual](https://ctre.download/files/user-manual/VRM%20User's%20Guide.pdf).

## REV Radio Power Module
## Vivid-Hosting VH-109 Radio

.. image:: images/control-system-hardware/radio-power-module.png
:alt: REV Radio Power Module
.. image:: images/control-system-hardware/radio.png
:alt: VH-109 Radio on a white background with nothing plugged in.
:width: 500

The [REV Radio Power Module](https://docs.revrobotics.com/rev-11-1856/) is designed to keep one of the most critical system components, the OpenMesh WiFi radio, powered in the toughest moments of the competition. The Radio Power Module eliminates the need for powering the radio through a traditional barrel power jack. Utilizing 18V Passive POE with two socketed RJ45 connectors, the Radio Power Module passes signal between the radio and roboRIO while providing power directly to the radio. After connecting the radio and roboRIO, easily add power to the Radio Power Module by wiring it to the low-current channels on the Power Distribution Hub utilizing the color coded push button WAGO terminals.

## OpenMesh OM5P-AN or OM5P-AC Radio

.. image:: images/control-system-hardware/openmesh-radio.png
:alt: OpenMesh OM5P-AN or OM5P-AC Radio
:width: 500

Either the OpenMesh OM5P-AN or [OpenMesh OM5P-AC](https://www.andymark.com/products/open-mesh-om5p-ac-dual-band-1-17-gbps-access-point-radio) wireless radio is used as the robot radio to provide wireless communication functionality to the robot. The device can be configured as an Access Point for direct connection of a laptop for use at home. It can also be configured as a bridge for use on the field. The robot radio should be powered by one of the 12V/2A outputs on the VRM and connected to the roboRIO controller over Ethernet. For more information, see :ref:`Programming your Radio <docs/zero-to-robot/step-3/radio-programming:Programming your Radio>`.

The OM5P-AN [is no longer available for purchase](https://www.firstinspires.org/robotics/frc/blog/radio-silence). The OM5P-AC is slightly heavier, has more cooling grates, and has a rough surface texture compared to the OM5P-AN.
The [Vivid-Hosting VH-109 radio](https://frc-radio.vivid-hosting.net/) is designed specifically for FRC. It uses Wi-Fi 6E to avoid the common congestion problems that plague 2.4 GHz Wi-Fi networks. The ruggedized design allows for unfiltered power input coming directly from a power distribution device. It also has 4 Ethernet ports reducing the need for an additional network switch.

## 120A Circuit Breaker

Expand Down Expand Up @@ -303,4 +293,4 @@ The Microsoft Lifecam HD3000 is a USB webcam that can be plugged directly into t

## Image Credits

Image of roboRIO courtesy of National Instruments. Image of DMC-60 courtesy of Digilent. Image of SD540 courtesy of Mindsensors. Images of Jaguar Motor Controller, Talon SRX, Talon FX, Victor 888, Victor SP, Victor SPX, and Spike H-Bridge Relay courtesy of VEX Robotics, Inc. Image of SPARK MAX, Power Distribution Hub, Radio Power Module, and Pneumatic Hub courtesy of REV Robotics. Lifecam, PDP, PCM, SPARK, and VRM photos courtesy of *FIRST*\ |reg|. All other photos courtesy of AndyMark Inc.
Image of roboRIO courtesy of National Instruments. Image of DMC-60 courtesy of Digilent. Image of SD540 courtesy of Mindsensors. Images of Jaguar Motor Controller, Talon SRX, Talon FX, Victor 888, Victor SP, Victor SPX, and Spike H-Bridge Relay courtesy of VEX Robotics, Inc. Image of SPARK MAX, Power Distribution Hub, and Pneumatic Hub courtesy of REV Robotics. Lifecam, PDP, PCM, SPARK, and VRM photos courtesy of *FIRST*\ |reg|. Image of the VH-109 radio courtesy of Vivid-Hosting. All other photos courtesy of AndyMark Inc.
9 changes: 1 addition & 8 deletions source/docs/controls-overviews/control-system-software.rst
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ The FRC\ |reg| software consists of a wide variety of mandatory and optional com

The primary supported OS for FRC components is Windows. All required FRC software components have been tested on Windows 10 & 11.

Many of the tools for C++/Java/Python programming are also supported and tested on macOS and Linux. Teams programming in C++/Java/Python should be able to develop using these systems, using a Windows system for the Windows-only operations such as the Driver Station, Radio Configuration Utility, and roboRIO Imaging Tool.
Many of the tools for C++/Java/Python programming are also supported and tested on macOS and Linux. Teams programming in C++/Java/Python should be able to develop using these systems, using a Windows system for the Windows-only operations such as the Driver Station and roboRIO Imaging Tool.

## LabVIEW FRC (Windows Only)

Expand Down Expand Up @@ -89,13 +89,6 @@ LiveWindow is a feature of SmartDashboard and Shuffleboard, designed for use wit

This tool is used to format and setup a roboRIO for use in FRC. Installation instructions can be found :ref:`here <docs/zero-to-robot/step-2/frc-game-tools:Installing the FRC Game Tools>`. Additional instructions on imaging your roboRIO using this tool can be found :doc:`here </docs/zero-to-robot/step-3/imaging-your-roborio>`.

## FRC Radio Configuration Utility (Windows Only)

.. image:: images/control-system-software/frc-radio-configuration-utility.png
:alt: Initial screen of the FRC Radio Configuration Utility.

The FRC Radio Configuration Utility is a tool used to configure the standard radio for practice use at home. This tool sets the appropriate network settings to mimic the experience of the FRC playing field. The FRC Radio Configuration Utility is installed by a standalone installer that can be found :ref:`here <docs/zero-to-robot/step-3/radio-programming:Programming your Radio>`.

## FRC Driver Station Log Viewer (Windows Only)

.. image:: images/control-system-software/frc-log-viewer.png
Expand Down
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -97,17 +97,13 @@ If you can remove the blade fuses by hand then they are not in completely. Make

Swarf is fine chips or filings of stone, metal, or other material produced by a machining operation. Often modifications must be made to a robot while the control system parts are in place. The circuit board for the roboRIO is conformally coated, but that doesn't absolutely guarantee that metal chips won't short out traces or components inside the case. In this case, you must exercise care in making sure that none of the chips end up in the roboRIO or any of the other components. In particular, the exposed 3 pin headers are a place where chips can enter the case. A quick sweep through each of the four sides with a flashlight is usually sufficient to find the really bad areas of infiltration.

## Radio Barrel Jack

Make sure the correct barrel jack is used, not one that is too small and falls out for no reason. This isn’t common, but ask an :term:`FTA` and every once in awhile a team will use some random barrel jack that is not sized correctly, and it falls out in a match on first contact.

## Ethernet Cable

If the RIO to radio ethernet cable is missing the clip that locks the connector in, get another cable. This is a common problem that will happen several times in every competition. Make sure that your cables are secure. The clip often breaks off, especially when pulling it through a tight path, it snags on something then breaks.

## Loose Cables

Cables must be tightened down, particularly the radio power and ethernet cable. The radio power cables don’t have a lot of friction force and will fall out (even if it is the correct barrel) if the weight of the cable-slack is allowed to swing freely.
Cables must be tightened down, particularly the radio power and ethernet cable.

Ethernet cable is also pretty heavy, if it’s allowed to swing freely, the plastic clip may not be enough to hold the ethernet pin connectors in circuit.

Expand Down
55 changes: 32 additions & 23 deletions source/docs/hardware/hardware-basics/status-lights-ref.rst
Original file line number Diff line number Diff line change
Expand Up @@ -64,30 +64,39 @@ A compact and printable `Status Light Quick Reference <https://wpilib.org/s/Stat
| **RSL** | `See above <#robot-signal-light-rsl>`_ |
+------------+----------------------------------------------------------------------------------------------------+

## OpenMesh Radio
## Vivid-Hosting VH-109 Radio

.. image:: images/status-lights/openmesh-radio-status-lights.png
:alt: Radio with the Wifi, Eth Link (2), and Power ports labeled.
.. image:: images/status-lights/radio-lights.png
:alt: The 5 lights positioned on the top side of the radio.
:width: 600

+----------+---------------+------------------------------+
| Power | Blue | On or Powering up |
| +---------------+------------------------------+
| | Blue Blinking | Powering Up |
+----------+---------------+------------------------------+
| Eth Link | Blue | Link up |
| +---------------+------------------------------+
| | Blue Blinking | Traffic Present |
+----------+---------------+------------------------------+
| WiFi | Off | Bridge mode, |
| | | Unlinked or non-FRC firmware |
| +---------------+------------------------------+
| | Red | AP, Unlinked |
| +---------------+------------------------------+
| | Yellow/Orange | AP, Linked |
| +---------------+------------------------------+
| | Green | Bridge mode, Linked |
+----------+---------------+------------------------------+
[VH-109 Status Lights](https://frc-radio.vivid-hosting.net/overview/led-status-indications)

+----------+----------------+------------------------------+
| Power | Green | On or Powering up |
| +----------------+------------------------------+
| | Off | No Power |
+----------+----------------+------------------------------+
| System | Solid Green | Able to ping the field |
| Status +----------------+------------------------------+
| | Blinking (1Hz) | Unable to ping the field |
| +----------------+------------------------------+
| | Blinking (20Hz)| Firmware being flashed |
| +----------------+------------------------------+
| | Blinking (50Hz)| Performing "first boot" |
| +----------------+------------------------------+
| | Off | Booting Up |
+----------+----------------+------------------------------+
| 2.4 GHz | Solid Green | Wifi available |
| +----------------+------------------------------+
| | Blinking (20Hz)| Battery detected, |
| | Sys Blinking | Wireless is disabled |
+----------+----------------+------------------------------+
| 6 GHz | Solid Blue | 6 GHz connection made |
| +----------------+------------------------------+
| | Blinking (20Hz)| Battery detected, |
| | Sys Blinking | Wireless is disabled |
+----------+----------------+------------------------------+

## Power Distribution Panel

Expand Down Expand Up @@ -135,7 +144,7 @@ A compact and printable `Status Light Quick Reference <https://wpilib.org/s/Stat

+-------------------------+--------------------------------------------------------+
| LED Color | Status |
+-------------------------+--------------------------------------------------------+
+=========================+========================================================+
| Blue Solid | Device on but no communication established |
+-------------------------+--------------------------------------------------------+
| Green Solid | Main Communication with roboRIO established |
Expand All @@ -159,7 +168,7 @@ A compact and printable `Status Light Quick Reference <https://wpilib.org/s/Stat

+--------------+----------------------------------------------------------------------------------------------------------+
| LED Color | Status |
+--------------+----------------------------------------------------------------------------------------------------------+
+==============+==========================================================================================================+
| Off | Channel has voltage and is operating as expected |
+--------------+----------------------------------------------------------------------------------------------------------+
| Red Solid | Channel has NO voltage and there is an active fault. Check for tripped or missing circuit breaker / fuse |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ An FRC\ |reg| Robot is an incredibly rough environment when it comes to vibratio

## Redundancy

Unfortunately there are few places in the FRC Control System where redundancy is feasible. Taking advantage of opportunities for redundancy can increase reliability. The primary example of this is wiring the barrel connector to the radio in addition to the provided PoE connection. This ensures that if one of the cables becomes damaged or dislodged, the other will maintain power to the radio. Keep an eye out for other potential areas to provide redundancy when wiring and programming your robot.
Unfortunately there are few places in the FRC Control System where redundancy is feasible. Taking advantage of opportunities for redundancy can increase reliability. The primary example of this is wiring the VH-109 radio with a :term:`PoE` connection in addition to the direct Weidmuller radio power. This ensures that if one of the cables becomes damaged or dislodged, the other will maintain power to the radio. Keep an eye out for other potential areas to provide redundancy when wiring and programming your robot.

## Port Savers

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 0 additions & 1 deletion source/docs/networking/networking-introduction/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -10,4 +10,3 @@ This section outlines basic robot configuration and usage relating to communicat
roborio-network-troubleshooting
windows-firewall-configuration
measuring-bandwidth-usage
om5p-ac-radio-modification
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ This section describes networking when connected to the Field Network for match
The Field Network runs a :term:`DHCP` server with pools for each team that will hand out addresses in the range of ``10.TE.AM.20`` to ``10.TE.AM.199`` with a subnet mask of ``255.255.255.0``, and a default gateway of ``10.TE.AM.4``.
When configured for an event, the Team Radio runs a DHCP server with a pool for devices onboard the robot that will hand out addresses in the range of 10.TE.AM.200 to 10.TE.AM.219 with a subnet mask of 255.255.255.0, and a gateway of 10.TE.AM.1.

- OpenMesh OM5P-AN or OM5P-AC radio - Static ``10.TE.AM.1`` programmed by
- Vivid-Hosting VH-109 Robot Radio - Static ``10.TE.AM.1`` programmed by
Kiosk
- roboRIO - DHCP ``10.TE.AM.2`` assigned by the Robot Radio
- Driver Station - DHCP ("Obtain an IP address automatically")
Expand All @@ -47,9 +47,9 @@ When configured for an event, the Team Radio runs a DHCP server with a pool for

### On the Field Static Configuration

It is also possible to configure static IPs on your devices to accommodate devices or software which do not support mDNS. When doing so you want to make sure to avoid addresses that will be in use when the robot is on the field network. These addresses are ``10.TE.AM.1`` for the OpenMesh radio, ``10.TE.AM.4`` for the field router, and anything ``10.TE.AM.20`` or greater which may be assigned to a device configured for DHCP or else reserved. The roboRIO network configuration can be set from the webdashboard.
It is also possible to configure static IPs on your devices to accommodate devices or software which do not support mDNS. When doing so you want to make sure to avoid addresses that will be in use when the robot is on the field network. These addresses are ``10.TE.AM.1`` for the VH-109 radio, ``10.TE.AM.4`` for the field router, and anything ``10.TE.AM.20`` or greater which may be assigned to a device configured for DHCP or else reserved. The roboRIO network configuration can be set from the webdashboard.

- OpenMesh radio - Static ``10.TE.AM.1`` programmed by Kiosk
- VH-109 radio - Static ``10.TE.AM.1`` programmed by Kiosk
- roboRIO - Static ``10.TE.AM.2`` would be a reasonable choice, subnet mask
of ``255.255.255.0`` (default)
- Driver Station - Static ``10.TE.AM.5`` would be a reasonable choice,
Expand All @@ -62,11 +62,11 @@ It is also possible to configure static IPs on your devices to accommodate devic

## In the Pits

.. note:: **New for 2018:** There is now a DHCP server running on the wired side of the Robot Radio in the event configuration.
.. note:: There is a DHCP server running on the wired side of the Robot Radio in the event configuration.

### In the Pits DHCP Configuration

- OpenMesh radio - Static ``10.TE.AM.1`` programmed by Kiosk.
- VH-109 radio - Static ``10.TE.AM.1`` programmed by Kiosk.
- roboRIO - ``10.TE.AM.2``, assigned by Robot Radio
- Driver Station - DHCP ("Obtain an IP address automatically"),
``10.TE.AM.X``, assigned by Robot Radio
Expand All @@ -75,4 +75,4 @@ It is also possible to configure static IPs on your devices to accommodate devic

### In the Pits Static Configuration

It is also possible to configure static IPs on your devices to accommodate devices or software which do not support mDNS. When doing so you want to make sure to avoid addresses that will be in use when the robot is on the field network. These addresses are ``10.TE.AM.1`` for the OpenMesh radio and ``10.TE.AM.4`` for the field router.
It is also possible to configure static IPs on your devices to accommodate devices or software which do not support mDNS. When doing so you want to make sure to avoid addresses that will be in use when the robot is on the field network. These addresses are ``10.TE.AM.1`` for the VH-109 radio and ``10.TE.AM.4`` for the field router.
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,6 @@

On the FRC\ |reg| Field each team is allocated limited network bandwidth (see R704 in the 2024 manual). Some teams may wish to measure their overall bandwidth consumption. This document details how to make that measurement.

.. note:: Teams can simulate the bandwidth throttling at home using the FRC Bridge Configuration Utility with the bandwidth checkbox checked.

## Measuring Bandwidth Using the Performance Monitor (Win 7/10)

Windows contains a built-in tool called the Performance Monitor that can be used to monitor the bandwidth usage over a network interface.
Expand Down
Loading

0 comments on commit a6ad120

Please sign in to comment.