Update DS Disable Known Issue (#2924)

* Update DS Disable Known Issue Remove some old history Update recommendations for new radio Add info about mounting access point radio high to radio programming * Apply suggestions from code review Co-authored-by: Jason Daming <jason.daming@intralox.com> --------- Co-authored-by: Jason Daming <jason.daming@intralox.com>
wpilibsuite · Jan 10, 2025 · 7cfaf42 · 7cfaf42
1 parent 8e7ac04
commit 7cfaf42
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 9 deletions.
diff --git a/source/docs/yearly-overview/known-issues.rst b/source/docs/yearly-overview/known-issues.rst
@@ -17,23 +17,24 @@ This article details known issues (and workarounds) for FRC\ |reg| Control Syste
 
 ### Driver Station randomly disabled
 
-**Issue:** The Driver Station contains tighter safety mechanisms in 2024 to protect against control issues. Some teams have seen this cause the robot to disable.
+**Issue:** The Driver Station contains tighter safety mechanisms introduced in 2024 to protect against control issues. Some teams have seen this cause the robot to disable.
 
 **Workaround:** There are multiple potential causes for tripping the safety mechanisms.
 
 .. note:: The new safety mechanisms will *not* disable the robot when connected to the :term:`FMS`.
 
-Driver Station 24.0.1 from Game Tools 2024 Patch 1 contains an update to the safety controls that may resolve the issue in certain circumstances. If the issue is still seen with this version installed, please continue with the troubleshooting steps below.
-
 The Driver Station software has new tools for control packet delays that could cause this. The control system team requests that teams that experience this issue post screenshots of the :doc:`Driver Station Timing window </docs/software/driverstation/driver-station-timing-viewer>` to https://github.com/wpilibsuite/allwpilib/issues/6174
 
 Some teams have seen this happen only when the robot is operated wirelessly, but not when operated via USB or ethernet tether. Some potential mitigations:
 
-1. Try relocating the robot radio to a better location (high in the robot and away from motors or large amounts of metal).
-2. :doc:`Measure your robot's bandwidth </docs/networking/networking-introduction/measuring-bandwidth-usage>` and ensure you have margin to the 4 Mbps bandwidth limit
-3. See if the Wi-Fi environment is congested using a tool like [WiFi Analyzer](https://apps.microsoft.com/detail/9NBLGGH33N0N?hl=en-US&gl=US). As the 5 ghz WiFi spectrum has more channels and is less crowded, switching the robot radio to operate at 5 ghz will likely improve WiFi communication.
-4. Update the Wi-Fi drivers for the computer.
-5. If you operate multiple robots in close proximity in access point mode, setting up a router and operating the radios in bridge mode will reduce the number of wireless access points and may improve communications
+1. Try relocating the robot radio to a better location (high in the robot and away from motors or large amounts of metal). Follow the `manufacturer's recommended mounting <https://frc-radio.vivid-hosting.net/getting-started/usage/mounting-your-radio>`__
+2. :doc:`Measure your robot's bandwidth </docs/networking/networking-introduction/measuring-bandwidth-usage>` and ensure you have margin under the 7 Mbps bandwidth limit
+3. See if the Wi-Fi environment is congested using a tool like [WiFi Analyzer](https://apps.microsoft.com/detail/9NBLGGH33N0N?hl=en-US&gl=US).
+4. Utilize the recommended :doc:`2 radio setup </docs/zero-to-robot/step-3/radio-programming>`.
+   1. Ensure the DS Radio is mounted high, away from interference and humans walking between the DS radio and the robot.
+   2. Use ethernet to connect the DS computer to the DS Radio
+5. Update the Wi-Fi drivers for the DS computer.
+
 
 Some teams have seen this happen due to software that is running on the driver station (such as Autodesk updater or Discord). Some potential mitigations:
 
@@ -43,7 +44,7 @@ Some teams have seen this happen due to software that is running on the driver s
 
 While rare, this can be caused by robot code that oversaturates the roboRIO processor or network connection. If all other troubleshooting steps fail, you can try running with one of the WPILib example programs to see if the problem still occurs.
 
-If you identify software that interferes with driver station, please post it to `<https://github.com/wpilibsuite/allwpilib/issues/6174>`__
+If you identify software that interferes with driver station, please post it to https://github.com/wpilibsuite/allwpilib/issues/6174
 
 ### Driver Station Reports Less Free RAM then is Available
 

diff --git a/source/docs/zero-to-robot/step-3/radio-programming.rst b/source/docs/zero-to-robot/step-3/radio-programming.rst
@@ -70,6 +70,8 @@ Follow all of the same steps as the robot radio configuration instead choosing :
 
 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.
 
+When mounting the access point radio, ensure it is mounted high where it has a clear line of sight to the robot.
+
 ### Only 1 VH-109 radio
 
 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: