diff --git a/source/docs/controls-overviews/control-system-hardware.rst b/source/docs/controls-overviews/control-system-hardware.rst index aa5750cb08..655abb1620 100644 --- a/source/docs/controls-overviews/control-system-hardware.rst +++ b/source/docs/controls-overviews/control-system-hardware.rst @@ -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 `. - -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 @@ -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. diff --git a/source/docs/controls-overviews/control-system-software.rst b/source/docs/controls-overviews/control-system-software.rst index ac68163cb7..7eca79b983 100644 --- a/source/docs/controls-overviews/control-system-software.rst +++ b/source/docs/controls-overviews/control-system-software.rst @@ -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) @@ -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 `. Additional instructions on imaging your roboRIO using this tool can be found :doc:`here `. -## 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 `. - ## FRC Driver Station Log Viewer (Windows Only) .. image:: images/control-system-software/frc-log-viewer.png diff --git a/source/docs/controls-overviews/images/control-system-hardware/radio-power-module.png b/source/docs/controls-overviews/images/control-system-hardware/radio-power-module.png deleted file mode 100644 index 87087f84a1..0000000000 Binary files a/source/docs/controls-overviews/images/control-system-hardware/radio-power-module.png and /dev/null differ diff --git a/source/docs/controls-overviews/images/control-system-hardware/radio.png b/source/docs/controls-overviews/images/control-system-hardware/radio.png new file mode 100644 index 0000000000..cd67fbba2c Binary files /dev/null and b/source/docs/controls-overviews/images/control-system-hardware/radio.png differ diff --git a/source/docs/controls-overviews/images/control-system-software/frc-radio-configuration-utility.png b/source/docs/controls-overviews/images/control-system-software/frc-radio-configuration-utility.png deleted file mode 100644 index 9ff7a203db..0000000000 Binary files a/source/docs/controls-overviews/images/control-system-software/frc-radio-configuration-utility.png and /dev/null differ diff --git a/source/docs/hardware/hardware-basics/images/status-lights/openmesh-radio-status-lights.png b/source/docs/hardware/hardware-basics/images/status-lights/openmesh-radio-status-lights.png deleted file mode 100644 index 3bc3de76cb..0000000000 Binary files a/source/docs/hardware/hardware-basics/images/status-lights/openmesh-radio-status-lights.png and /dev/null differ diff --git a/source/docs/hardware/hardware-basics/images/status-lights/radio-lights.png b/source/docs/hardware/hardware-basics/images/status-lights/radio-lights.png new file mode 100644 index 0000000000..d9814ede5d Binary files /dev/null and b/source/docs/hardware/hardware-basics/images/status-lights/radio-lights.png differ diff --git a/source/docs/hardware/hardware-basics/preemptive-troubleshooting.rst b/source/docs/hardware/hardware-basics/preemptive-troubleshooting.rst index d096bd1918..5d8cdac51d 100644 --- a/source/docs/hardware/hardware-basics/preemptive-troubleshooting.rst +++ b/source/docs/hardware/hardware-basics/preemptive-troubleshooting.rst @@ -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. diff --git a/source/docs/hardware/hardware-basics/status-lights-ref.rst b/source/docs/hardware/hardware-basics/status-lights-ref.rst index 6a886d08d5..2fc21b1dc9 100644 --- a/source/docs/hardware/hardware-basics/status-lights-ref.rst +++ b/source/docs/hardware/hardware-basics/status-lights-ref.rst @@ -64,30 +64,39 @@ A compact and printable `Status Light Quick Reference `_ | +------------+----------------------------------------------------------------------------------------------------+ -## 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 @@ -135,7 +144,7 @@ A compact and printable `Status Light Quick Reference + -
On the Field
(Connected to FMS)
On the Field...
via FMS
via FMSroboRIODHCP10.TE.AM.2OpenMesh RadioStatic10.TE.AM.1
In the Pits
(Connected via Radio)
In the Pits...
via Ethernet
via EthernetroboRIODHCP10.TE.AM.2OpenMesh RadioStatic10.TE.AM.1
In the Pits
(Connected via roboRIO USB)
In the Pits...roboRIOOpenMesh RadioStatic10.TE.AM.1
via USB
via USB
10.TE.AM.2 via Ethernet
10.TE.AM.2 via Ethernet
172.22.11.2 via USB
172.22.11.2 via USB
Additional Devices
DHCP
10.TE.AM.Y
Additional Devices...
Additional Devices
DHCP
10.TE.AM.Y
Additional Devices...
Additional Devices
DHCP
10.TE.AM.Y
Additional Devices...Driver StationDHCP10.TE.AM.XDriver StationDHCP10.TE.AM.XDriver StationStatic172.22.11.1Viewer does not support full SVG 1.1 \ No newline at end of file +
On the Field
(Connected to FMS)
On the Field...
via FMS
via FMSroboRIODHCP10.TE.AM.2VH-109 RadioStatic10.TE.AM.1
In the Pits
(Connected via Radio)
In the Pits...
via Ethernet
via EthernetroboRIODHCP10.TE.AM.2VH-109 RadioStatic10.TE.AM.1
In the Pits
(Connected via roboRIO USB)
In the Pits...roboRIOVH-109 RadioStatic10.TE.AM.1
via USB
via USB
10.TE.AM.2 via Ethernet
10.TE.AM.2 via Ethernet
172.22.11.2 via USB
172.22.11.2 via USB
Additional Devices
DHCP
10.TE.AM.Y
Additional Devices...
Additional Devices
DHCP
10.TE.AM.Y
Additional Devices...
Additional Devices
DHCP
10.TE.AM.Y
Additional Devices...Driver StationDHCP10.TE.AM.XDriver StationDHCP10.TE.AM.XDriver StationStatic172.22.11.1Text is not SVG - cannot display \ No newline at end of file diff --git a/source/docs/networking/networking-introduction/index.rst b/source/docs/networking/networking-introduction/index.rst index b077752309..dccbcf3eeb 100644 --- a/source/docs/networking/networking-introduction/index.rst +++ b/source/docs/networking/networking-introduction/index.rst @@ -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 diff --git a/source/docs/networking/networking-introduction/ip-configurations.rst b/source/docs/networking/networking-introduction/ip-configurations.rst index fab6676dd6..211cd3111f 100644 --- a/source/docs/networking/networking-introduction/ip-configurations.rst +++ b/source/docs/networking/networking-introduction/ip-configurations.rst @@ -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. diff --git a/source/docs/networking/networking-introduction/measuring-bandwidth-usage.rst b/source/docs/networking/networking-introduction/measuring-bandwidth-usage.rst index 1c9f9cb82e..13903c2824 100644 --- a/source/docs/networking/networking-introduction/measuring-bandwidth-usage.rst +++ b/source/docs/networking/networking-introduction/measuring-bandwidth-usage.rst @@ -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. diff --git a/source/docs/networking/networking-introduction/networking-basics.rst b/source/docs/networking/networking-introduction/networking-basics.rst index d652ead20b..941c276b1f 100644 --- a/source/docs/networking/networking-introduction/networking-basics.rst +++ b/source/docs/networking/networking-introduction/networking-basics.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 diff --git a/source/docs/networking/networking-introduction/om5p-ac-radio-modification.rst b/source/docs/networking/networking-introduction/om5p-ac-radio-modification.rst deleted file mode 100644 index 31b5d90181..0000000000 --- a/source/docs/networking/networking-introduction/om5p-ac-radio-modification.rst +++ /dev/null @@ -1,85 +0,0 @@ -.. include:: - -# OM5P-AC Radio Modification - -The intended use case for the OM5P-AC radio does not subject it to the same shocks and forces as it sees in the FRC\ |reg| environment. If the radio is subjected to significant pressure on the bottom of the case, it is possible to cause a radio reboot by shorting a metal shield at the bottom of the radio to some exposed metal leads on the bottom of the board. This article details a modification to the radio to prevent this scenario. - -.. warning:: It takes significant pressure applied to the bottom of the case to cause a reboot in this manner. Most FRC radio reboot issues can be traced to the power path in some form. We recommend mitigating this risk via strategic mounting of the radio rather than opening and modifying the radio (and risk damaging delicate internal components): - -- Avoid using the "mounting tab" features on the bottom of the radio. -- You may wish to mount the radio to allow for some shock absorption. A little can go a long way, mounting the radio using hook and loop fastener or to a robot surface with a small amount of flex (plastic or sheet metal sheet, etc.) can significantly reduce the forces experienced by the radio. - -## Opening the Radio - -.. note:: The OpenMesh OM5P-AC is not designed to be a user serviceable device. Users perform this modification at their own risk. Make sure to work slowly and carefully to avoid damaging internal components such as radio antenna cables. - -### Case Screws - -.. image:: images/om5p-ac-radio-modification/rubber-feet.png - :alt: Location of the two front rubber feet. - -.. image:: images/om5p-ac-radio-modification/case-screws.png - :alt: Location of the screws beneath the rubber feet. - -Locate the two rubber feet on the front side of the radio then pry them off the radio using fingernails, small flat screwdriver, etc. Using a small Phillips screwdriver, remove the two screws under the feet. - -### Side Latches - -.. image:: images/om5p-ac-radio-modification/lift-cover.png - :alt: Slightly lifting the top cover of the radio. - -There is a small latch on the lid of the radio near the middle of each long edge (you can see these latches more clearly in the next picture). Using a fingernail or very thin tool, slide along the gap between the lid and case from front to back towards the middle of the radio, you should hear a small pop as you near the middle of radio. Repeat on the other side (note: it's not hard to accidentally re-latch the first side while doing this, make sure both sides are unlatched before proceeding). The radio lid should now be slightly open on the front side as shown in the image above. - -### Remove Lid - -.. warning:: The board may stick to the lid as you remove it due to the heatsink pads. Look through the vents of the radio as you remove the lid to see if the board is coming with it, if it is you may need to insert a small tool to hold the board down to separate it from the lid. We recommend a small screwdriver or similar tool that fits through the vents, applied through the front corner on the barrel jack side, right above the screw hole. You can scroll down to the picture with the lid removed to see what the board looks like in this area. - -.. image:: images/om5p-ac-radio-modification/side-latch.png - :alt: Side latches of the top cover shown and how to slide the cover off pushing it forwards. - -To begin removing the lid, slide it forward (lifting slightly) until the screw holders hit the case front (you may need to apply pressure on the latch areas while doing this. - -.. image:: images/om5p-ac-radio-modification/barrel-jack.png - :alt: The barrel jack corner that needs to be rotated away from. - -Next, begin rotating the lid slightly away from the barrel jack side, as shown while continuing to lift. This will unhook the lid from the small triangle visible in the top right corner. Continue to rotate slightly in this direction while pushing the top left corner towards the barrel jack (don't try to lift further in this step) to unhook a similar feature in the top left corner. Then lift the lid completely away from the body. - -### Remove Board - -.. image:: images/om5p-ac-radio-modification/antenna.png - :alt: Note the three fragile antenna wires on the board. - -.. warning:: Note the antenna wires shown in the image above. These wires, and their connectors, are fragile, take care not to damage them while performing the next steps. - -.. image:: images/om5p-ac-radio-modification/grab-ethernet.png - :alt: Grab the Ethernet port to help lift the board. - -.. image:: images/om5p-ac-radio-modification/board.png - :alt: The board lifted slightly out of the case. - -To remove the board, we recommend grasping one or both network ports with your fingers (as shown) and pushing inward (toward the front of the radio) and upward until the network ports and barrel jack are free from the case. - -.. image:: images/om5p-ac-radio-modification/shield.png - :alt: The board angled vertically and the flat metal shield underneath where it was. - -Tilt the board up (towards the short grey antenna cable) to expose the metal shield underneath. - -.. note:: When you perform this step, you may notice that there is a small reset button on the underside of the board that is larger than the hole in the case. Note that pressing the reset button with the FRC firmware installed has no effect and that drilling the case of the radio is not a permitted modification. - -## Apply Tape - -.. image:: images/om5p-ac-radio-modification/electrical-tape.png - :alt: Applying electrical tape at the front of the shield near the Ethernet ports. - -Apply a piece of electrical tape to the metal shield in the area just inside of the network port/barrel jack openings. This will prevent the exposed leads on the underside of the board from short circuiting on this plate. - -## Re-assemble Radio - -Re-assemble the radio by reversing the instructions to open it: - -- Lay the board back down, making sure it aligns with the screw holes near the front and seats securely -- Slide the lid onto the back left retaining feature by moving it in from right to left. Take care of the capacitor in this area -- Rotate the lid, press downwards and slide the back right retaining feature in -- Press down firmly on the front/middle of the lid to seat the latches -- Replace 2 screws in front feet -- Replace front feet diff --git a/source/docs/networking/networking-introduction/roborio-network-troubleshooting.rst b/source/docs/networking/networking-introduction/roborio-network-troubleshooting.rst index e006d08813..0368bbd6d9 100644 --- a/source/docs/networking/networking-introduction/roborio-network-troubleshooting.rst +++ b/source/docs/networking/networking-introduction/roborio-network-troubleshooting.rst @@ -13,7 +13,7 @@ The first step to identifying roboRIO networking issues is to isolate if it is a If there is no response, try pinging ``10.TE.AM.2`` (:ref:`TE.AM IP Notation `) using the command prompt as described above. If this works, you have an issue resolving the mDNS address on your PC. The two most common causes are not having an mDNS resolver installed on the system and a DNS server on the network that is trying to resolve the .local address using regular DNS. - Verify that you have an mDNS resolver installed on your system. On Windows, this is typically fulfilled by the NI FRC Game Tools. For more information on mDNS resolvers, see the :ref:`Network Basics article `. -- Disconnect your computer from any other networks and make sure you have the OM5P-AN configured as an access point, using the :ref:`FRC Radio Configuration Utility `. Removing any other routers from the system will help verify that there is not a DNS server causing the issue. +- Disconnect your computer from any other networks. Removing any other routers from the system will help verify that there is not a DNS server causing the issue. ## Ping Fails @@ -36,7 +36,7 @@ If this ping succeeds, but the .local ping fails, it is likely that either the r .. image:: images/roborio-troubleshooting/roborio-ip-address.png :alt: The IP address from the roboRIO webdashboard. -If you are troubleshooting an Ethernet connection, it may be helpful to first make sure that you can connect to the roboRIO using the USB connection. Using the USB connection, open the :ref:`roboRIO webdashboard ` and verify that the roboRIO has an IP address on the ethernet interface. If you are tethering to the roboRIO directly this should be a self-assigned ``169.*.*.*`` address, if you are connected to the OM5P-AN radio, it should be an address of the form ``10.TE.AM.XX`` where TEAM is your five digit FRC team number(:ref:`TE.AM IP Notation `). If the only IP address here is the USB address, verify the physical roboRIO ethernet connection. +If you are troubleshooting an Ethernet connection, it may be helpful to first make sure that you can connect to the roboRIO using the USB connection. Using the USB connection, open the :ref:`roboRIO webdashboard ` and verify that the roboRIO has an IP address on the ethernet interface. If you are tethering to the roboRIO directly this should be a self-assigned ``169.*.*.*`` address, if you are connected to the VH-109 radio, it should be an address of the form ``10.TE.AM.XX`` where TEAM is your five digit FRC team number(:ref:`TE.AM IP Notation `). If the only IP address here is the USB address, verify the physical roboRIO ethernet connection. ## Disabling Network Adapters diff --git a/source/docs/software/driverstation/driver-station-best-practices.rst b/source/docs/software/driverstation/driver-station-best-practices.rst index e52321e8b9..ad811bc599 100644 --- a/source/docs/software/driverstation/driver-station-best-practices.rst +++ b/source/docs/software/driverstation/driver-station-best-practices.rst @@ -28,7 +28,7 @@ Want to ensure the driver station isn't a stopper for your team at the FIRST Rob d. A keyboard. It’s hard to quickly do troubleshooting on touch-only computers at the field. e. A solid-state disk (SSD), 256 GB or larger. If the laptop has a rotating disk, spend $50 and replace it with a SSD. f. Updated to the current release of Windows 10 or 11. - g. A laptop that supports Wi-Fi 6E (6 GHz) is recommended for use with the [Wi-Fi 6E radio](https://www.firstinspires.org/robotics/frc/blog/2023-technology-updates-past-present-future-and-beyond) for 2025 and later. + g. A laptop that supports Wi-Fi 6E (6 GHz) is recommended for use with the [Wi-Fi 6E radio](https://frc-radio.vivid-hosting.net/). 5. Install all Windows updates a week before the competition. This allows you time to ensure the updates will not interfere with driver station functions. To do so, open the Windows Update settings page and see that you're up-to-date. Install pending updates if not. Reboot and check again to make sure you’re up to date. 6. Change "Active Hours" for Windows Updates to prevent updates from installing during competition hours. Navigate to Start -> Settings -> Update & Security -> Windows Update, then select Change active hours. If you’re traveling to a competition, take time zone differences into account. This will help ensure your driver station does not reboot or fail due to update installing on the field. diff --git a/source/docs/software/driverstation/driver-station-log-viewer.rst b/source/docs/software/driverstation/driver-station-log-viewer.rst index ffa7af3a3c..a332f4fb6f 100644 --- a/source/docs/software/driverstation/driver-station-log-viewer.rst +++ b/source/docs/software/driverstation/driver-station-log-viewer.rst @@ -116,4 +116,4 @@ An issue with the ethernet cable on the robot is primarily indicated by the ping .. image:: images/driver-station-log-viewer/radioreboot.png :alt: The ping here shows the roboRIO and the radio as BAD. -A reboot of the robot radio is typically characterized by a loss of connection to the radio for ~40-45 seconds. In this example, the radio briefly lost power at 3:22:44, causing it to start rebooting. The event at 3:22:45 indicates that the ping to the radio failed. At 3:23:11, the DS regains communication with the roboRIO and the roboRIO indicates it has been up for 1272.775 seconds, ruling out a roboRIO reboot. Note that the network switch on the radio comes back up very quickly so a momentary power loss may not result in a "radio lost"/"radio seen" event pair. A longer disturbance may result in radio events being logged by the DS. In that case, the distinguishing factor which points towards a radio reboot is the ping status of the radio from the DS. If the radio resets, the radio will be unreachable. If the issue is a cabling or connection issue on the robot, the radio ping should remain "GOOD". +A reboot of the robot radio is typically characterized by a loss of connection to the radio for ~40-50 seconds. In this example, the radio briefly lost power at 3:22:44, causing it to start rebooting. The event at 3:22:45 indicates that the ping to the radio failed. At 3:23:11, the DS regains communication with the roboRIO and the roboRIO indicates it has been up for 1272.775 seconds, ruling out a roboRIO reboot. Note that the network switch on the radio comes back up very quickly so a momentary power loss may not result in a "radio lost"/"radio seen" event pair. A longer disturbance may result in radio events being logged by the DS. In that case, the distinguishing factor which points towards a radio reboot is the ping status of the radio from the DS. If the radio resets, the radio will be unreachable. If the issue is a cabling or connection issue on the robot, the radio ping should remain "GOOD". diff --git a/source/docs/software/driverstation/index.rst b/source/docs/software/driverstation/index.rst index b0a8a41c69..b847f2125d 100644 --- a/source/docs/software/driverstation/index.rst +++ b/source/docs/software/driverstation/index.rst @@ -8,6 +8,4 @@ driver-station-log-viewer driver-station-errors-warnings driver-station-timing-viewer - programming-radios-for-fms-offseason manually-setting-the-driver-station-to-start-custom-dashboard - diff --git a/source/docs/software/driverstation/programming-radios-for-fms-offseason.rst b/source/docs/software/driverstation/programming-radios-for-fms-offseason.rst deleted file mode 100644 index 9eaaadd151..0000000000 --- a/source/docs/software/driverstation/programming-radios-for-fms-offseason.rst +++ /dev/null @@ -1,103 +0,0 @@ -.. include:: - -# Programming Radios for FMS Offseason - -When using the :term:`FMS` Offseason software, the typical networking setup is to use a single access point with a single SSID and WPA key. This means that the radios should all be programmed to connect to this network, but with different IPs for each team. The Team version of the FRC\ |reg| Bridge Configuration Utility has an FMS Offseason mode that can be used to do this configuration. - -## Pre-Requisites - -Install the FRC\ |reg| Radio Configuration Utility software per the instructions in :ref:`Programming your radio ` - -Before you begin using the software: - -#. Disable WiFi connections on your computer, as it may prevent the configuration utility from properly communicating with the bridge -#. Plug directly from your computer into the wireless bridge ethernet port closest to the power jack. Make sure no other devices are connected to your computer via ethernet. If powering the radio via PoE, plug an Ethernet cable from the PC into the socket side of the PoE adapter (where the roboRIO would plug in). If you experience issues configuring through the PoE adapter, you may try connecting the PC to the alternate port on the radio. - -### Programmed Configuration - -The Radio Configuration Utility programs a number of configuration settings into the radio when run. These settings apply to the radio in all modes (including at events). These include: - -- Set a static IP of ``10.TE.AM.1`` (:ref:`TE.AM IP Notation `) -- Set an alternate IP on the wired side of ``192.168.1.1`` for future programming -- Bridge the wired ports so they may be used interchangeably -- The LED configuration noted in the status light referenced below. -- 4Mb/s bandwidth limit on the outbound side of the wireless interface (may be disabled for home use) -- QoS rules for internal packet prioritization (affects internal buffer and which packets to discard if bandwidth limit is reached). These rules are: - - - Robot Control and Status (UDP ``1110``, ``1115``, ``1150``) - - Robot TCP & :term:`NetworkTables` (TCP ``1735``, ``1740``) - - Bulk (All other traffic). (disabled if BW limit is disabled) - -- :term:`DHCP` server enabled. Serves out: - - - ``10.TE.AM.11`` - ``10.TE.AM.111`` on the wired side - - ``10.TE.AM.138`` - ``10.TE.AM.237`` on the wireless side - - Subnet mask of ``255.255.255.0`` - - Broadcast address ``10.TE.AM.255`` - -- DNS server enabled. DNS server IP and domain suffix (``.lan``) are served as part of the DHCP. - -.. tip:: See the :ref:`Status Light Reference ` for details on the behavior of the radio status lights when configured. - -When programmed with the team version of the Radio Configuration - Utility, the user accounts will be left at (or set to) the firmware - defaults **for the DAPs only**: - -- Username: root -- Password: root - -.. note:: It is not recommended to modify the configuration manually - -## Launch the software - -.. image:: /docs/zero-to-robot/step-3/images/radio-programming/radio-launch.png - :alt: The FRC Radio Configuration Utility in the start menu. - -Use the Start menu or desktop shortcut to launch the program. - -.. note:: If you need to locate the program, it is installed to ``C:\Program Files (x86)\FRC Radio Configuration Utility``. For 32-bit machines the path is ``C:\Program Files\FRC Radio Configuration Utility`` - -## Allow the program to make changes, if prompted - -.. image:: /docs/zero-to-robot/step-3/images/radio-programming/allow-changes.png - :alt: User Account Control dialog that pops up when running the config utility. - -A prompt may appear about allowing the configuration utility to make changes to the computer. Click :guilabel:`Yes` if the prompt appears. - -## Enter FMS Offseason Mode - -.. image:: images/programming-radios-for-fms-offseason/tools-fmsoffseason.png - :alt: Click on "Tools" then "FMS-Lite Mode". - -Click ``Tools`` -> ``FMS-Lite Mode`` to enter FMS-Lite Mode. - -## Enter SSID - -.. image:: images/programming-radios-for-fms-offseason/ssid.png - :alt: Enter the network SSID in the dialog box. - -Enter the SSID (name) of your wireless network in the box and click OK. - -## Enter WPA Key - -.. image:: images/programming-radios-for-fms-offseason/wpa.png - :alt: Enter the WPA Key (password) for this SSID. - -Enter the WPA key for your network in the box and click OK. Leave the box blank if you are using an unsecured network. - -## Program Radios - -.. image:: images/programming-radios-for-fms-offseason/program-radio.png - :alt: Program the radio through the utility like normal for all of the radios at your event. - -The Kiosk is now ready to program any number of radios to connect to the network entered. To program each radio, connect the radio to the Kiosk, set the Team Number in the box, and click Configure. - -The kiosk will program OpenMesh, D-Link Rev A or D-Link Rev B radios to work on an offseason FMS network by selecting the appropriate option from the "Radio" dropdown. - -.. note:: Bandwidth limitations and QoS will not be configured on the D-Link radios in this mode. - -## Changing SSID or Key - -If you enter something incorrectly or need to change the SSID or WPA Key, go to the Tools menu and click FMS-Lite Mode to take the kiosk out of FMS-Lite Mode. When you click again to put the Kiosk back in FMS-Lite Mode, you will be re-prompted for the SSID and Key. - -## Troubleshooting - -See the troubleshooting steps in :ref:`Programming your radio ` diff --git a/source/docs/software/frc-glossary.rst b/source/docs/software/frc-glossary.rst index 068532b8ab..40fe58fb92 100644 --- a/source/docs/software/frc-glossary.rst +++ b/source/docs/software/frc-glossary.rst @@ -202,6 +202,9 @@ PH Pneumatic Hub - is a standalone module that is capable of switching both 12V and 24V pneumatic solenoid valves. The Pneumatic Hub features 16 solenoid channels which allow for up to 16 single-acting solenoids, 8 double-acting solenoids, or a combination of the two types. + PoE + Power Over Ethernet - method of powering a device by an Ethernet cord that also carries power. FRC uses passive PoE usually 12-24V that is always being supplied, this can damage a device not expecting the provided voltage. The most common industry standard is active PoE which uses 48V but first verifies that the device is expecting the power. + property In :term:`NetworkTables`, named information (metadata) about a :term:`topic` stored and updated separately from the topic's data. A topic may have any number of properties. A property's value can be any data type that can be represented in JSON. diff --git a/source/docs/software/support/support-resources.rst b/source/docs/software/support/support-resources.rst index 2ac2f70c2a..2e0e8f8225 100644 --- a/source/docs/software/support/support-resources.rst +++ b/source/docs/software/support/support-resources.rst @@ -12,6 +12,7 @@ In addition to this site there are a few other places teams may check for docume - [FIRST Inspires Technical Resources Page](https://www.firstinspires.org/resource-library/frc/technical-resources) - [CTRE Software & Resources Page](https://store.ctr-electronics.com/software/) - [REV Robotics Documentation](https://docs.revrobotics.com/docs/) +- [Vivid Hosting](https://frc-radio.vivid-hosting.net/) ## Forums @@ -29,6 +30,10 @@ Support for Cross The Road Electronics components (Pneumatics Control Module, Po Support for REV Robotics components (SPARK MAX, Sensors, Pneumatic Hub, Power Distribution Hub, Radio Power Module) is provided via phone at [844-255-2267](tel:844-255-2267) or via the email address [support@revrobotics.com](mailto:support@revrobotics.com). +## WCP Support + +Support for WestCoast Products components (VH-109 radio) is provided via phone at [559-206-2920](tel:559-206-2920) or via the email address [support@wcproducts.com](mailto:support@wcproducts.com). + ## Other Vendors Support for vendors outside of the KOP can be found below. @@ -40,7 +45,6 @@ Support for vendors outside of the KOP can be found below. - [Playing with Fusion](https://www.playingwithfusion.com/contactus.php) - [Redux Robotics](https://shop.reduxrobotics.com/) - [The Thrifty Bot](https://www.thethriftybot.com/) -- [Vivid Hosting](https://frc-radio.vivid-hosting.net/) ## Unofficial Support diff --git a/source/docs/yearly-overview/returning-quickstart.rst b/source/docs/yearly-overview/returning-quickstart.rst index 4c67f0f504..f435c32211 100644 --- a/source/docs/yearly-overview/returning-quickstart.rst +++ b/source/docs/yearly-overview/returning-quickstart.rst @@ -9,5 +9,6 @@ It is advised that **all** teams read through the :doc:`changelog ` (Java / C++ teams only) 4. :doc:`Update third party libraries ` 5. Reimage :doc:`roboRIO 1 ` or :doc:`roboRIO 2 ` -6. :doc:`Import robot project ` (Java / C++ teams only) -7. Update software based on the changes described in the :doc:`changelog ` +6. Update firmware on and :doc:`program VH-109 radios ` +7. :doc:`Import robot project ` (Java / C++ teams only) +8. Update software based on the changes described in the :doc:`changelog ` diff --git a/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/rpm-pdh-power.jpg b/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/pdh-power.jpg similarity index 100% rename from source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/rpm-pdh-power.jpg rename to source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/pdh-power.jpg diff --git a/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/pdp-radio-power.jpg b/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/pdp-radio-power.jpg new file mode 100644 index 0000000000..771efed5b1 Binary files /dev/null and b/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/pdp-radio-power.jpg differ diff --git a/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/radio-power.jpg b/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/radio-power.jpg deleted file mode 100644 index 52daadf8e2..0000000000 Binary files a/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/radio-power.jpg and /dev/null differ diff --git a/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/radio-power.png b/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/radio-power.png new file mode 100644 index 0000000000..91a7bf7104 Binary files /dev/null and b/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/radio-power.png differ diff --git a/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/radio.jpg b/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/radio.jpg deleted file mode 100644 index ea1e94ac36..0000000000 Binary files a/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/radio.jpg and /dev/null differ diff --git a/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/rio-port.png b/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/rio-port.png new file mode 100644 index 0000000000..7463094a19 Binary files /dev/null and b/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/rio-port.png differ diff --git a/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/rpm.jpg b/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/rpm.jpg deleted file mode 100644 index 832834b471..0000000000 Binary files a/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/rpm.jpg and /dev/null differ diff --git a/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/vrm-power.jpg b/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/vrm-power.jpg deleted file mode 100644 index 1f973c0b08..0000000000 Binary files a/source/docs/zero-to-robot/step-1/images/how-to-wire-a-simple-robot/vrm-power.jpg and /dev/null differ diff --git a/source/docs/zero-to-robot/step-1/intro-to-frc-robot-wiring.rst b/source/docs/zero-to-robot/step-1/intro-to-frc-robot-wiring.rst index 64021613c9..0c153cd802 100644 --- a/source/docs/zero-to-robot/step-1/intro-to-frc-robot-wiring.rst +++ b/source/docs/zero-to-robot/step-1/intro-to-frc-robot-wiring.rst @@ -56,8 +56,7 @@ Locate the following control system components and tools - Power Distribution Hub (:term:`PDH`) / Power Distribution Panel (:term:`PDP`) - roboRIO - Pneumatics Hub (:term:`PH`) / Pneumatics Control Module (:term:`PCM`) - - Radio Power Module (:term:`RPM`) / Voltage Regulator Module (:term:`VRM`) - - OpenMesh radio (with power cable and Ethernet cable) + - VH-109 radio - Robot Signal Light (:term:`RSL`) - 4x SPARK MAX or other motor controllers - 2x :term:`PWM` y-cables @@ -107,6 +106,8 @@ For a test board, cut piece of 1/4" or 1/2" (6-12 mm) material (wood or plastic) Lay out the components on the board. An example layout is shown in the image above. +.. note:: A Vivid-Hosting has a [guide](https://frc-radio.vivid-hosting.net/getting-started/usage/mounting-your-radio) for mounting the VH-109 radio. + ## Fasten Components .. image:: images/how-to-wire-a-simple-robot/ziptie.png @@ -338,49 +339,41 @@ After making the connection check to be sure that it is clean and secure: ## Radio Power + +[Vivid-Hosting Wiring Guide](https://frc-radio.vivid-hosting.net/getting-started/usage/wiring-your-radio) + .. tab-set:: .. tab-item:: REV :sync: REV - .. image:: images/how-to-wire-a-simple-robot/rpm-pdh-power.jpg - :alt: Power going from the PDH to the RPM. + .. image:: images/how-to-wire-a-simple-robot/pdh-power.jpg + :alt: Power coming from a PDH non-switchable fused channel. - .. image:: images/how-to-wire-a-simple-robot/rpm.jpg - :alt: Power going into the RPM. - - Requires: Wire stripper, small flat screwdriver (optional), 18 AWG (1 :math:`mm^2`) red and black wire: + Requires: Wire stripper, small flat screwdriver (optional), 18 AWG (1 :math:`mm^2`) red and black wire: - 1. Insert the 10A fuse into the PDH in one of the non-switchable fused channels (20-22). - 2. Strip ~5/16" (~8 mm) on the end of the red and black 18 AWG (1 :math:`mm^2`) wire and connect the wire to the corresponding terminals on the PDH. - 3. Measure the length required to reach the "12V Input" terminals on the Radio Power Module. Take care to leave enough length to route the wires around any other components such as the battery and to allow for any strain relief or cable management. - 4. Cut and strip ~5/16" (~8 mm) from the end of the wire. - 5. Connect the wire to the RPM 12V Input terminals. + 1. Insert the 10A fuse into the PDH in one of the non-switchable fused channels (20-22). + 2. Strip ~5/16" (~8 mm) on the end of the red and black 18 AWG (1 :math:`mm^2`) wire and connect the wire to the corresponding terminals on the PDH. .. tab-item:: CTR :sync: CTR - .. image:: images/how-to-wire-a-simple-robot/vrm-power.jpg - :alt: Power going from the PDP to the VRM. + .. image:: images/how-to-wire-a-simple-robot/pdp-radio-power.jpg + :alt: Power going from the PDP "Vbat VRM PCM PWR" terminals. Requires: Wire stripper, small flat screwdriver (optional), 18 AWG (1 :math:`mm^2`) red and black wire: 1. Strip ~5/16" (~8 mm) on the end of the red and black 18 AWG (1 :math:`mm^2`) wire. 2. Connect the wire to one of the two terminal pairs labeled "Vbat VRM PCM PWR" on the PDP. - 3. Measure the length required to reach the "12Vin" terminals on the VRM. Take care to leave enough length to route the wires around any other components such as the battery and to allow for any strain relief or cable management. - 4. Cut and strip ~5/16" (~8 mm) from the end of the wire. - 5. Connect the wire to the VRM 12Vin terminals. - - .. warning:: DO NOT connect the Rev passive POE injector cable directly to the roboRIO. The roboRIO MUST connect to the socket end of the cable using an additional Ethernet cable as shown in the next step. - .. image:: images/how-to-wire-a-simple-robot/radio-power.jpg - :alt: Connection power to the robot radio via a PoE cable. +.. image:: images/how-to-wire-a-simple-robot/radio-power.png + :alt: Power connections to the VH-109 robot radio. - Requires: Small flat screwdriver (optional), Rev radio PoE cable - - 1. Insert the ferrules of the passive PoE injector cable into the corresponding colored terminals on the 12V/2A section of the VRM. - 2. Connect the RJ45 (Ethernet) plug end of the cable into the Ethernet port on the radio closest to the barrel connector (labeled 18-24v POE) +3. Measure the length required to reach the "12V" Weidmuller terminals on the VH-109 Radio. Take care to leave enough length to route the wires around any other components such as the battery and to allow for any strain relief or cable management. +4. Cut and strip ~5/16" (~8 mm) from the end of the wire. +5. Connect the wire to the VH-109 "12V" Weidmuller terminals. +.. note:: The radio can additionally be powered by :term:`PoE` to create a more redundant connection. ## Pneumatics Power (Optional) @@ -425,31 +418,16 @@ After making the connection check to be sure that it is clean and secure: ## Ethernet Cables -.. tab-set:: +.. image:: images/how-to-wire-a-simple-robot/rio-port.png + :alt: Power going from the PDP to the PCM. - .. tab-item:: REV - :sync: REV - - .. image:: images/how-to-wire-a-simple-robot/rpm.jpg - :alt: Picture of the RPM. - - .. image:: images/how-to-wire-a-simple-robot/radio.jpg - :alt: Picture of the radio. - - Requires: 2x Ethernet cables - - 1. Connect an Ethernet cable from the RJ45 (Ethernet) socket of the roboRIO to the port on the Radio Power Module labeled roboRIO. - 2. Connect an Ethernet cable from the RJ45 socket of the radio closest to the barrel connector socket (labeled 18-24v POE) to the socket labeled WiFi Radio on the RPM - - .. tab-item:: CTR - :sync: CTR +Requires: an Ethernet cable - .. image:: images/how-to-wire-a-simple-robot/radio-ethernet.jpg - :alt: Connecting Ethernet from the roboRIO to the PoE cable. +1. Connect an Ethernet cable from the RJ45 (Ethernet) socket of the roboRIO to the `RIO` port on the VH-109 Radio. - Requires: Ethernet cable +.. note:: If using :term:`PoE` you may need a second Ethernet cable or longer power wires. - Connect an Ethernet cable from the RJ45 (Ethernet) socket of the Rev Passive POE cable to the RJ45 (Ethernet) port on the roboRIO. +.. warning:: DO NOT connect the Rev passive :term:`PoE` injector cable directly to the roboRIO. The roboRIO MUST connect to the socket end of the cable using an additional Ethernet cable as shown in the next step. ## CAN Devices @@ -644,7 +622,6 @@ For the SPARK or other non-integrated-wire controllers (bottom image): - Check that the red wire passes through the main breaker and to the + terminal of the PDP and that the black wire travels directly to the - terminal. - For each motor controller, verify that the red wire goes from the red PDP terminal to the V+ terminal on the motor controller (not M+!!!!) - For each non-motor controller device, verify that the red wire runs from a red terminal on the PD connects to a red terminal on the component. -- Make sure that the PoE cable is plugged directly into the radio NOT THE roboRIO! .. tip:: It is also recommended to put the robot on blocks so the wheels are off the ground before proceeding. This will prevent any unexpected movement from becoming dangerous. diff --git a/source/docs/zero-to-robot/step-2/offline-installation-preparations.rst b/source/docs/zero-to-robot/step-2/offline-installation-preparations.rst index 86a346e17d..35c841dbcf 100644 --- a/source/docs/zero-to-robot/step-2/offline-installation-preparations.rst +++ b/source/docs/zero-to-robot/step-2/offline-installation-preparations.rst @@ -18,8 +18,6 @@ This documentation can be downloaded for offline viewing. The link to download t - [2024 FRC Game Tools](https://www.ni.com/en/support/downloads/drivers/download.frc-game-tools.html#500107) (Note: Click on link for "Individual Offline Installers") -- [2024 FRC Radio Configuration Utility](https://firstfrc.blob.core.windows.net/frc2024/Radio/FRC_Radio_Configuration_24_0_1.zip) or [2024 FRC Radio Configuration Utility Israel Version](https://firstfrc.blob.core.windows.net/frc2024/Radio/FRC_Radio_Configuration_24_0_1_IL.zip) - ### LabVIEW Teams - [LabVIEW Base Installer](https://www.ni.com/en-us/support/downloads/drivers/download.labview-software-for-frc.html) (Note: Click on link for "Individual Offline Installers") diff --git a/source/docs/zero-to-robot/step-3/images/radio-programming/allow-changes.png b/source/docs/zero-to-robot/step-3/images/radio-programming/allow-changes.png deleted file mode 100644 index 0bb0c0dc32..0000000000 Binary files a/source/docs/zero-to-robot/step-3/images/radio-programming/allow-changes.png and /dev/null differ diff --git a/source/docs/zero-to-robot/step-3/images/radio-programming/config-completed.png b/source/docs/zero-to-robot/step-3/images/radio-programming/config-completed.png deleted file mode 100644 index c4746a9d65..0000000000 Binary files a/source/docs/zero-to-robot/step-3/images/radio-programming/config-completed.png and /dev/null differ diff --git a/source/docs/zero-to-robot/step-3/images/radio-programming/config-errors.png b/source/docs/zero-to-robot/step-3/images/radio-programming/config-errors.png deleted file mode 100644 index d847bd762f..0000000000 Binary files a/source/docs/zero-to-robot/step-3/images/radio-programming/config-errors.png and /dev/null differ diff --git a/source/docs/zero-to-robot/step-3/images/radio-programming/config-in-progress.png b/source/docs/zero-to-robot/step-3/images/radio-programming/config-in-progress.png deleted file mode 100644 index 0e959495a8..0000000000 Binary files a/source/docs/zero-to-robot/step-3/images/radio-programming/config-in-progress.png and /dev/null differ diff --git a/source/docs/zero-to-robot/step-3/images/radio-programming/configuration-page.png b/source/docs/zero-to-robot/step-3/images/radio-programming/configuration-page.png new file mode 100644 index 0000000000..5aad690e05 Binary files /dev/null and b/source/docs/zero-to-robot/step-3/images/radio-programming/configuration-page.png differ diff --git a/source/docs/zero-to-robot/step-3/images/radio-programming/openmesh-firmware.png b/source/docs/zero-to-robot/step-3/images/radio-programming/openmesh-firmware.png deleted file mode 100644 index 94ef10a227..0000000000 Binary files a/source/docs/zero-to-robot/step-3/images/radio-programming/openmesh-firmware.png and /dev/null differ diff --git a/source/docs/zero-to-robot/step-3/images/radio-programming/radio-firmware.png b/source/docs/zero-to-robot/step-3/images/radio-programming/radio-firmware.png new file mode 100644 index 0000000000..715b472a06 Binary files /dev/null and b/source/docs/zero-to-robot/step-3/images/radio-programming/radio-firmware.png differ diff --git a/source/docs/zero-to-robot/step-3/images/radio-programming/radio-installer.png b/source/docs/zero-to-robot/step-3/images/radio-programming/radio-installer.png deleted file mode 100644 index 4cda4dc0d5..0000000000 Binary files a/source/docs/zero-to-robot/step-3/images/radio-programming/radio-installer.png and /dev/null differ diff --git a/source/docs/zero-to-robot/step-3/images/radio-programming/radio-launch.png b/source/docs/zero-to-robot/step-3/images/radio-programming/radio-launch.png deleted file mode 100644 index 4f8679e938..0000000000 Binary files a/source/docs/zero-to-robot/step-3/images/radio-programming/radio-launch.png and /dev/null differ diff --git a/source/docs/zero-to-robot/step-3/images/radio-programming/select-bridge-model-mode.png b/source/docs/zero-to-robot/step-3/images/radio-programming/select-bridge-model-mode.png deleted file mode 100644 index 413410a920..0000000000 Binary files a/source/docs/zero-to-robot/step-3/images/radio-programming/select-bridge-model-mode.png and /dev/null differ diff --git a/source/docs/zero-to-robot/step-3/images/radio-programming/select-network-connection.png b/source/docs/zero-to-robot/step-3/images/radio-programming/select-network-connection.png deleted file mode 100644 index a619d23bec..0000000000 Binary files a/source/docs/zero-to-robot/step-3/images/radio-programming/select-network-connection.png and /dev/null differ diff --git a/source/docs/zero-to-robot/step-3/images/radio-programming/select-options.png b/source/docs/zero-to-robot/step-3/images/radio-programming/select-options.png deleted file mode 100644 index f3e49a2e03..0000000000 Binary files a/source/docs/zero-to-robot/step-3/images/radio-programming/select-options.png and /dev/null differ diff --git a/source/docs/zero-to-robot/step-3/images/radio-programming/start-config.png b/source/docs/zero-to-robot/step-3/images/radio-programming/start-config.png deleted file mode 100644 index 089a7d0bc2..0000000000 Binary files a/source/docs/zero-to-robot/step-3/images/radio-programming/start-config.png and /dev/null differ diff --git a/source/docs/zero-to-robot/step-3/radio-programming.rst b/source/docs/zero-to-robot/step-3/radio-programming.rst index 404f9bbb6e..e1a90aeafb 100644 --- a/source/docs/zero-to-robot/step-3/radio-programming.rst +++ b/source/docs/zero-to-robot/step-3/radio-programming.rst @@ -2,198 +2,140 @@ # Programming your Radio -This guide will show you how to use the FRC\ |reg| Radio Configuration Utility software to configure your robot's wireless bridge for use outside of FRC events. +This guide will show you how to do a basic setup for controlling your robot "at home" using the VH-109 FRC\ |reg| Radio. For complete documentation and information please see the [Vivid-Hosting radio site](https://frc-radio.vivid-hosting.net/). ## Prerequisites -The FRC Radio Configuration Utility requires administrator privileges to configure the network settings on your machine. The program should request the necessary privileges automatically (may require a password if run from a non-administrator account), but if you are having trouble, try running it from an administrator account. +The recommended setup requires: 2 VH-109 radios, 1 VH-117 :term:`PoE` Wall Adapter, and 1 Radio Heatsink. Available [here](https://wcproducts.com/products/frc-radio). -Download the latest FRC Radio Configuration Utility Installer from the following links: +Please see the :ref:`docs/zero-to-robot/step-3/radio-programming:Alternative Setup Discussion` if you do not currently have this hardware. -[FRC Radio Configuration 24.0.1](https://firstfrc.blob.core.windows.net/frc2024/Radio/FRC_Radio_Configuration_24_0_1.zip) +## Getting to the Web Configuration Page -[FRC Radio Configuration 24.0.1 Israel Version](https://firstfrc.blob.core.windows.net/frc2024/Radio/FRC_Radio_Configuration_24_0_1_IL.zip) +1. Connect the radio directly to your computer using an Ethernet cable in the :guilabel:`DS` port. -.. note:: The _IL version is for Israel teams and contains a version of the OM5PAC firmware with restricted channels for use in Israel. +2. Ensure the radio has power either through the Weidmuller connectors or :term:`PoE`. -.. note::. Teams planning on using the radio tool on a machine without the WPILib suite installed, will need a copy of Java installed. This can be downloaded [here](https://adoptium.net/temurin/releases/?version=17). +3. Open a web browser and navigate to :guilabel:`http://radio.local/`. See :ref:`docs/zero-to-robot/step-3/radio-programming:Troubleshooting` if the connection doesn't work. -Before you begin using the software: +## Radio Firmware Update -1. :ref:`Disable all other network adapters ` -2. Plug directly from your computer into the wireless bridge ethernet port closest to the power jack. Make sure no other devices are connected to your computer via ethernet. If powering the radio via PoE, plug an Ethernet cable from the PC into the socket side of the PoE adapter (where the roboRIO would plug in). If you experience issues configuring through the PoE adapter, you may try connecting the PC to the alternate port on the radio. +.. image:: images/radio-programming/radio-firmware.png + :alt: The Firmware Upload section of the radio configuration page -.. warning:: The OM5P-AN and AC use the same power plug as the D-Link DAP1522, however they are 12V radios. Wire the radio to the 12V 2A terminals on the VRM (center-pin positive). +.. note:: Newer versions of the radio firmware will have the version listed at the bottom. If you do not see the version listed you have firmware prior to 1.2.0. -## Application Notes +You can skip this section if already at version 1.2.6. -By default, the Radio Configuration Utility will program the radio to enforce the 4Mbps bandwidth limit on traffic exiting the radio over the wireless interface. In the home configuration (AP mode) this is a total, not a per client limit. This means that streaming video to multiple clients is not recommended. +1. On the Vivid-Hosting [firmware releases](https://frc-radio.vivid-hosting.net/miscellaneous/firmware-releases) page download the proper firmware for the current firmware version you have. Always choose the `Radio Variant`. -The Utility has been tested on Windows 7, 8 and 10. It may work on other operating systems, but has not been tested. +2. Copy the SHA-256 key below the firmware you downloaded. -### Programmed Configuration +3. Paste that key into the :guilabel:`Checksum` box of the :guilabel:`Firmware Upload` section at the bottom of the configuration page we navigated to above. -.. image:: /docs/hardware/hardware-basics/images/status-lights/openmesh-radio-status-lights.png - :alt: Lists the names of each of the status lights on the two legal radios. +4. Click :guilabel:`Browse...` and select the firmware file you downloaded. -The Radio Configuration Utility programs a number of configuration settings into the radio when run. These settings apply to the radio in all modes (including at events). These include: +5. Click the :guilabel:`Upload` button. -- Set a static IP of ``10.TE.AM.1`` -- Set an alternate IP on the wired side of ``192.168.1.1`` for future programming -- Bridge the wired ports so they may be used interchangeably -- The LED configuration noted in the graphic above. -- 4Mb/s bandwidth limit on the outbound side of the wireless interface (may be disabled for home use) -- QoS rules for internal packet prioritization (affects internal buffer and which packets to discard if bandwidth limit is reached). These rules are: +.. warning:: The radio will take approximately 2-3 minutes to complete firmware updates. Do not remove power during this process. Damage to the radio can occur. When the PWR light is solid and the SYS light is slowly blinking at 1 Hz, the firmware upgrade process is complete. - - Robot Control and Status (UDP ``1110``, ``1115``, ``1150``) - - Robot TCP & :term:`NetworkTables` (TCP ``1735``, ``1740``) - - Bulk (All other traffic). (disabled if BW limit is disabled) +## Robot Radio Configuration (All Teams) -- :term:`DHCP` server enabled. Serves out: +.. image:: images/radio-programming/configuration-page.png + :alt: The top section of the radio configuration page - - ``10.TE.AM.11`` - ``10.TE.AM.111`` on the wired side - - ``10.TE.AM.138`` - ``10.TE.AM.237`` on the wireless side - - Subnet mask of ``255.255.255.0`` - - Broadcast address ``10.TE.AM.255`` +This section is used for configuring the VH-109 radio outside of competition. At competition, configuration will be done by a provided computer and manual configuration using this page **should not be used**. -- DNS server enabled. DNS server IP and domain suffix (``.lan``) are served as part of the DHCP. +1. Select :guilabel:`Robot Radio Mode` -At home only: +2. Enter the team number -- SSID may have a "Robot Name" appended to the team number to distinguish multiple networks. -- Firewall option may be enabled to mimic the field firewall rules (open ports may be found in the Game Manual) +3. Enter the suffix, if desired. This will help identify your robot and distinguish it from other networks. -.. warning:: It is not possible to modify the configuration manually. +4. Enter the 6 GHz WPA/SAE key. This key will need to match the key on the Access Point you configure. -## Install the Software +5. Enter the 2.4 GHz WPA/SAE key. This is the password team members will type in when connecting to the 2.4 GHz network, if available. -.. image:: images/radio-programming/radio-installer.png - :alt: The radio configuration installer .exe file in windows explorer. +## Access Point Radio Configuration -Double click on ``FRC_Radio_Configuration_VERSION.exe`` to launch the installer. Follow the prompts to complete the installation. +Follow all of the same steps as the robot radio configuration instead choosing :guilabel:`Access Point Mode` at the top of the configuration page. -Part of the installation prompts will include installing Npcap if it is not already present. The Npcap installer contains a number of checkboxes to configure the install. You should leave the options as the defaults. +## Alternative Setup Discussion -## Launch the software +### Optimal Setup: Two VH-109 Radios -.. image:: images/radio-programming/radio-launch.png - :alt: The FRC Radio Configuration Utility in the start menu. +For the best experience and to closely simulate field conditions, it is strongly recommended that your team uses two VH-109 radios during testing and preparation. This dual-radio setup mirrors the competition environment, ensuring your robot operates under realistic network conditions. Additionally, having two radios allows you to fully leverage the high-speed, low-latency communication provided by the 6GHz band, which is crucial for optimal robot performance in high-stakes scenarios. -Use the Start menu or desktop shortcut to launch the program. +### Only 1 VH-109 radio -.. note:: If you need to locate the program, it is installed to ``C:\Program Files (x86)\FRC Radio Configuration Utility``. For 32-bit machines the path is ``C:\Program Files\FRC Radio Configuration Utility`` +If your team has access to only one VH-109 radio, there are still viable options to continue testing and preparing for competition. However, these setups require additional considerations: -## Allow the program to make changes, if prompted +#### Use an Old Radio for Testing -.. image:: images/radio-programming/allow-changes.png - :alt: User Account Control dialog that pops up when running the config utility. +If your team still has an older radio from a previous season, it can serve as a temporary substitute for the VH-109 on your robot. In this case, you should: -A prompt may appear about allowing the configuration utility to make changes to the computer. Click :guilabel:`Yes` if the prompt appears. +- Reserve a spot on your robot specifically for the VH-109 radio to ensure seamless integration during competition. +- Provide the older radio regulated power with a REV Radio Power Module or a CTRE Voltage Regulator Module. +- Be prepared to connect devices via a network switch if the older radio does not provide enough Ethernet ports. This may add complexity but ensures all devices are networked properly during testing. -## Select the network interface +Advantages: -.. image:: images/radio-programming/select-network-connection.png - :alt: Each of the Parts of the Network Interfaces selection pop up. +- Connection strength similar to previous years. -Use the pop-up window to select the which ethernet interface the configuration utility will use to communicate with the wireless bridge. On Windows machines, ethernet interfaces are typically named "Local Area Connection". The configuration utility can not program a bridge over a wireless connection. +Disadvantages: -1. If no ethernet interfaces are listed, click :guilabel:`Refresh` to re-scan for available interfaces. -2. Select the interface you want to use from the drop-down list. -3. Click :guilabel:`OK`. +- Requires additional hardware (e.g., the old radio and maybe a network switch). +- The older radio may not offer the same performance as the VH-109, potentially affecting test results. -## Open Mesh Firmware Note +#### Enable 2.4GHz Wifi on the VH-109 -For the FRC Radio Configuration Utility to program the OM5P-AN and OM5P-AC radio, the radio must be running an FRC specific build of the OpenWRT firmware. +The VH-109 radio includes a standalone mode that can be activated using DIP switch 3. In this configuration, the radio hosts its own 2.4GHz network, enabling direct connections without additional hardware. -If you do not need to update or re-load the firmware, skip the next step. +To enable standalone mode: -.. warning:: Radios used in 2019-2023 **do not** need to be updated before configuring, the 2024 tool uses the same 2019 firmware. +1. Locate the DIP switches on the VH-109 radio, removing the sticker if required. +2. Flip DIP switch 3 to the "ON" position. +3. Connect devices directly to the 2.4GHz network hosted by the radio, using the 2.4 GHz WPA/SAE key from configuration. -## Loading FRC Firmware to Open Mesh Radio +Advantages: -.. image:: images/radio-programming/openmesh-firmware.png - :alt: Highlighting the radio dropdown and the Load Firmware button on the main configuration utility screen. +- Simple setup with no need for additional hardware. +- Allows immediate use of the VH-109 without extra configuration. -If you need to load the FRC firmware (or reset the radio), you can do so using the FRC Radio Configuration Utility. +Disadvantages: -1. Follow the instructions above to install the software, launch the program and select the Ethernet interface. -2. Make sure the Open Mesh radio is selected in the Radio dropdown. -3. Make sure the radio is connected to the PC via Ethernet. -4. Unplug the power from the radio. (If using a PoE cable, this will also be unplugging the Ethernet to the PC, this is fine) -5. Press the Load Firmware button -6. When prompted, plug in the radio power. The software should detect the radio, load the firmware and prompt you when complete. +- The 2.4GHz band is more prone to congestion and interference, especially in crowded environments. +- Range and accessibility may be limited compared to the 6GHz band. -.. warning:: If you see an error about NPF name, try disabling all adapters other than the one being used to program the radio. If only one adapter is found, the tool should attempt to use that one. See the steps in :ref:`Disabling Network Adapters ` for more info. +### No VH-117 :term:`PoE` Wall Adapter - Teams may also see this error with Operating Systems configured for languages other than US English. If you experience issues loading firmware or programming on a foreign language OS, try using an English OS, such as on the KOP provided PC or setting the Locale setting to "en_us" as described on [this page](https://www.java.com/en/download/help/locale.html). +You can power the access point radio with a 12V wall plug connecting wires to the Weidmuller ports. We recommend trying to find one with a [switch](https://a.co/d/cUsD25n) to simplify turning on and off the radio. The primary concern will be cord length which will likely not be long enough to run from your wall outlet so you will need to bring the power closer with an extension cord. -## Select Radio and Operating Mode +### No Radio Heatsink -.. image:: images/radio-programming/select-bridge-model-mode.png - :alt: Highlights the Radio and Mode dropdown boxes. +The access point radio will get hot after being on for a longer than a full match. This will cause latency to increase. -1. Select which radio you are configuring using the drop-down list. -2. Select which operating mode you want to configure. For most cases, the default selection of 2.4GHz Access Point will be sufficient. If your computers support it, the 5GHz AP mode is recommended, as 5GHz is less congested in many environments. - -## Select Options - -.. image:: images/radio-programming/select-options.png - :alt: Setting the robot name will change the SSID. The checkboxes make the radio more similar to competition operation. - -The default values of the options have been selected to match the use case of most teams, however, you may wish to customize these options to your specific scenario: - -1. **Robot Name:** This is a string that gets appended to the SSID used by the radio. This allows you to have multiple networks with the same team number and still be able to distinguish them. -2. **Firewall:** If this box is checked, the radio firewall will be configured to attempt to mimic the port blocking behavior of the firewall present on the FRC field. For a list of open ports, please see the FRC Game Manual. -3. **BW Limit:** If this box is checked, the radio enforces a 4 Mbps bandwidth limit like it does when programmed at events. Note that this is a total limit, not per client, so streaming video to multiple clients simultaneously may cause undesired behavior. - -.. note:: Firewall and BW Limit only apply to the Open Mesh radios. These options have no effect on D-Link radios. - -.. warning:: The "Firewall" option configures the radio to emulate the field firewall. This means that you will not be able to deploy code wirelessly with this option enabled. This is useful for simulating blocked ports that may exist at competitions. - -## Starting the Configuration Process - -.. image:: images/radio-programming/start-config.png - :alt: At the bottom of the screen is instructions for completing the configuration process. - -Follow the on-screen instructions for preparing your wireless bridge, entering the settings the bridge will be configured with, and starting the configuration process. These on-screen instructions update to match the bridge model and operating mode chosen. - -## Configuration Progress - -.. image:: images/radio-programming/config-in-progress.png - :alt: The progress bar dialog while the configuration is working. - -Throughout the configuration process, the window will indicate: +## Troubleshooting -1. The step currently being executed. -2. The overall progress of the configuration process. -3. All steps executed so far. +### Cannot Reach the Configuration Page at radio.local -## Configuration Completed +Set a [static ip address](https://www.trendnet.com/press/resource-library/how-to-set-static-ip-address) with these parameters: -.. image:: images/radio-programming/config-completed.png - :alt: A pop up dialog indicating the programming was successful. +- IP Address: 192.168.69.2 +- Subnet Mask: 255.255.255.0 +- Gateway: Leave Blank +- DNS: 192.168.69.1 or Leave Blank -Once the configuration is complete: +Navigate to :guilabel:`http://192.168.69.1/` -1. Press :guilabel:`OK` on the dialog window. -2. Press :guilabel:`OK` on the main window to return to the settings screen. +### Setting Up an Entire Field -## Configuration Errors +See the documentation on using the [VH-113 Access Point](https://frc-radio.vivid-hosting.net/getting-started/usage/practicing-at-home#vh-113-access-point). -.. image:: images/radio-programming/config-errors.png - :alt: A error dialog pop up. +### How do I run an Offseason Event? -If an error occurs during the configuration process, follow the instructions in the error message to correct the problem. +Use the [Vivid-Hosting radio kiosk](https://frc-radio.vivid-hosting.net/miscellaneous/offseason-kiosk-programmer). -## Troubleshooting +### Additional Radio Problems -- :ref:`Disable all other network adapters `. -- Make sure you wait long enough that the power light has stayed solid for 10 seconds. -- Make sure you have the correct network interface, and only one interface is listed in the drop-down. -- Make sure your firewall is turned off. -- Plug directly from your computer into the wireless bridge and make sure no other devices are connected to your computer via ethernet. -- Ensure the ethernet is plugged into the port closest to the power jack on the wireless bridge. -- If using an Operating System configured for languages other than US English, try using an English OS, such as on the KOP provided PC or setting the Locale setting to "en_us" as described on [this page](https://www.java.com/en/download/help/locale.html). -- Due to Unicode incompatibilities, non-US Teams may face a configuration failure because of incorrect network interface reading. In that case, change the network adapter name to another name in English and retry. -- Some users have reported success after installing [npcap 1.60](https://npcap.com/). If this doesn't resolve the issue, it's recommended to uninstall npcap and the radio tool and then reinstall the radio tool in order to get back to a known configuration. -- If all else fails, try a different computer. +Contact WCP support at: [support@westcoastproducts.com](mailto:support@westcoastproducts.com) diff --git a/source/docs/zero-to-robot/step-4/running-test-program.rst b/source/docs/zero-to-robot/step-4/running-test-program.rst index 40ad35caa1..877f6f0458 100644 --- a/source/docs/zero-to-robot/step-4/running-test-program.rst +++ b/source/docs/zero-to-robot/step-4/running-test-program.rst @@ -64,8 +64,8 @@ Before attempting wireless operation, tethered operation should have been confir ### Configuring the Access Point -See the article :ref:`Programming your radio ` for details on configuring the robot radio for use as an access point. +See the article :ref:`Programming your radio ` for details on configuring the second VH-109 for use as an access point. -After configuring the access point, connect the driver station wirelessly to the robot. The SSID will be your team number (as entered in the Bridge Configuration Utility). If you set a key when using the Bridge Configuration Utility you will need to enter it to connect to the network. Make sure the computer network adapter is set to DHCP ("Obtain an IP address automatically"). +After configuring the access point, connect the driver station via Ethernet to the VH-109 AP radio. You can now confirm wireless operation using the same steps in **Confirm Connectivity** and **Operate the Robot** above. diff --git a/source/redirects.txt b/source/redirects.txt index de74203708..ef98272f7d 100644 --- a/source/redirects.txt +++ b/source/redirects.txt @@ -307,3 +307,5 @@ "docs/software/wpilib-tools/axon/using-on-a-robot.rst" "docs/software/vision-processing/index.rst" "docs/software/wpilib-tools/axon/viewing-datasets.rst" "docs/software/vision-processing/index.rst" "docs/software/wpilib-tools/choreo/index.rst" "docs/software/pathplanning/choreo/index.rst" +"docs/networking/networking-introduction/om5p-ac-radio-modification.rst" "docs/zero-to-robot/step-3/radio-programming.rst" +"docs/software/driverstation/programming-radios-for-fms-offseason.rst" "docs/zero-to-robot/step-3/radio-programming.rst"