first draft, need more work on radio programming

Author: jasondaming

source/docs/controls-overviews/control-system-hardware.rst

@@ -74,17 +74,15 @@ The CTRE Voltage Regulator Module (VRM) is an independent module that is powered
   :alt: REV Radio Power Module
   :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.
+The [REV Radio Power Module](https://docs.revrobotics.com/rev-11-1856/) was designed to keep one of the old 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
+## Vivid-Hosting VH-109 Radio
 
-.. image:: images/control-system-hardware/openmesh-radio.png
-  :alt: OpenMesh OM5P-AN or OM5P-AC Radio
+.. image:: images/control-system-hardware/radio.png
+  :alt: VH-109 Radio on a white background with nothing plugged in.
   :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 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 you power distribution.  It also has 4 Ethernet ports reducing the need for an additional network switch.
 
 ## 120A Circuit Breaker
 

source/docs/controls-overviews/images/control-system-hardware/radio.png

@@ -64,30 +64,34 @@ 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.4G     | Blinking (20Hz)| Battery detected,            |
+|          | Sys Blinking   | Wireless is disabled         |
+|----------+----------------+------------------------------+
+| 6G       | Blinking (20Hz)| Battery detected,            |
+|          | Sys Blinking   | Wireless is disabled         |
++----------+----------------+------------------------------+
 
 ## Power Distribution Panel
 

source/docs/hardware/hardware-basics/images/status-lights/openmesh-radio-status-lights.png

@@ -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

source/docs/hardware/hardware-basics/images/status-lights/radio-lights.png

@@ -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")
@@ -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,
@@ -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
@@ -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.

source/docs/hardware/hardware-basics/status-lights-ref.rst

@@ -78,7 +78,7 @@ In the pits, a team may encounter issues with mixing Static and DHCP devices for
 .. image:: diagrams/mixing-static-dynamic.drawio.svg
    :alt: How you can't mix link-local and static IP configurations.
 
-.. warning:: When connected via USB to the roboRIO, a :ref:`docs/networking/networking-utilities/portforwarding:Port Forwarding` configuration is required to access devices connected to the OpenMesh radio (on the green network shown above).
+.. warning:: When connected via USB to the roboRIO, a :ref:`docs/networking/networking-utilities/portforwarding:Port Forwarding` configuration is required to access devices connected to the VH-109 radio (on the green network shown above).
 
 ### Available Network Ports
 
@@ -155,7 +155,7 @@ If using the USB interface, no network setup is required, but you do need the :d
 
 ## Ethernet/Wireless
 
-The :ref:`docs/zero-to-robot/step-3/radio-programming:Programming your Radio` will enable the DHCP server on the OpenMesh radio in the home use case (AP mode), if you are putting the OpenMesh in bridge mode and using a router, you can enable DHCP addressing on the router. The bridge is set to the same team-based IP address as before (``10.TE.AM.1``) and will hand out DHCP address from ``10.TE.AM.20`` to ``10.TE.AM.199``. When connected to the field, :term:`FMS` will also hand out addresses in the same IP range.
+The :ref:`docs/zero-to-robot/step-3/radio-programming:Programming your Radio` will enable the DHCP server on the VH-109 radios. Both Robot Radio (``10.TE.AM.1``) and AP Radio (``10.TE.AM.4``) will have the team-based IP address and will hand out DHCP address from ``10.TE.AM.20`` to ``10.TE.AM.199``. When connected to the field, :term:`FMS` will also hand out addresses in the same IP range.
 
 ## Summary