Document Driver Station Timing Viewer (#2544)

Add known issues for DS print and error tags and DS disabling

source/docs/software/driverstation/driver-station-timing-viewer.rst

@@ -0,0 +1,25 @@
+Driver Station Timing Viewer
+============================
+
+The 2024 Driver Station has a a new window to help diagnose robot control issues.
+
+Opening the Timing Viewer
+-------------------------
+
+To start the Driver Station Timing Viewer, select the gear icon and then select :guilabel:`View Timing`.
+
+.. image:: images/view-timing/view-timing-menu.png
+   :alt: Driver Station gear menu with View Timing selected
+
+Viewing Timing
+--------------
+
+The Timing viewer shows the timing of the driver station loops measuring the joysick, keyboard, and control and status network packets. When timing is good, all values should be close to 0 ms. This can help diagnose what is causing robot control issues.
+
+.. image:: images/view-timing/normal-view-timing.png
+   :alt: Driver Station timing viewer with all timing measurements near 0 ms
+
+The next image shows what it looks like when network congestion causes network packets to be delayed and combined. In this example, the communication was so bad that the robot wouldn't stay enabled or connected for more then a second.
+
+.. image:: images/view-timing/bad-view-timing.png
+   :alt: Driver Station timing viewer with network congestion and many packets above 100 ms

source/docs/software/driverstation/index.rst

@@ -8,5 +8,7 @@ Driver Station
    driver-station-best-practices
    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
+

source/docs/yearly-overview/known-issues.rst

@@ -8,6 +8,35 @@ This article details known issues (and workarounds) for FRC\ |reg| Control Syste
 Open Issues
 -----------
 
+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.
+
+**Workaround:** There are multiple potential causes for tripping the safety mechanisms. 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 wifi 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. 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
+
+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:
+
+1. Reboot the driver station computer
+2. Close software that is running in the background
+3. Follow the :doc:`Driver Station Best Practices </docs/software/driverstation/driver-station-best-practices>`
+
+If you identify software that interferes with driver station, please post it to `<https://github.com/wpilibsuite/allwpilib/issues/6174>`__
+
+Driver Station internal issue with print error and tags
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Issue:** The Driver Station will occasionally print ``internal issue with print error and tags``. The message is caused when the DS reports a message on its side intermixed with messages from the robot; it is not caused by and does not affect robot code.
+
+**Workaround:** Thie will be fixed in the next Game Tools release. There is no known workaround.
+
 Visual Studio Code Reports Unresolved Dependency
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^