Skip to content

Commit 8a30cb2

Browse files
authored
Fix several issues on Known Issues (#1715)
Correct formatting of 16448 code snipped Fix autorun issue since it affects LabVIEW not Game Tools. Add picture. Remove old java installation picture
1 parent 9fa1cd1 commit 8a30cb2

File tree

3 files changed

+12
-8
lines changed

3 files changed

+12
-8
lines changed
Binary file not shown.
85.5 KB
Loading

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

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -20,14 +20,7 @@ ADIS16448 not reading values in Java
2020

2121
**Issue:** In WPILib 2022.3.1, using the no-args constructor for the ADIS16448 IMU in Java results in an divide by zero exception in a separate thread and no IMU data updates.
2222

23-
**Workaround:** Instead of the no-args constructor, use `new ADIS16448_IMU(ADIS16448_IMU.IMUAxis.kZ, SPI.Port.kMXP, ADIS16448_IMU.CalibrationTime._1s);`.
24-
25-
Game Tools Autorun graphics say 2020
26-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
27-
28-
**Issue:** If you launch the Game Tools installer by using the Autorun file, the menu item correctly says 2022, but the graphic says 2020.
29-
30-
**Workaround:** This can be safely ignored, if the menu item says 2022, you are installing the correct software.
23+
**Workaround:** Instead of the no-args constructor, use ``new ADIS16448_IMU(ADIS16448_IMU.IMUAxis.kZ, SPI.Port.kMXP, ADIS16448_IMU.CalibrationTime._1s);``.
3124

3225
CAN bus utilization is noisy
3326
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -116,6 +109,17 @@ There is currently an issue with inter-operating C++/Java :term:`NetworkTables`
116109

117110
**Workaround**: Write code on the server to mirror any keys you wish to see on other clients (e.g. dashboards) to a separate key. For example, if you have a key named ``targetX`` being published by a co-processor that you want to show up on a dashboard, you could write code on the robot to read the key and re-write it to a key like ``targetXDash``.
118111

112+
LabVIEW Autorun graphics say 2020
113+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
114+
115+
.. image:: images/known-issues/labview-autorun.png
116+
:alt: LabVIEW autorun screen showing mismatched versions
117+
118+
**Issue:** If you launch the LabVIEW installer by using the Autorun file, the menu item correctly says 2022, but the graphic says 2020.
119+
120+
**Workaround:** This can be safely ignored, if the menu item says 2022, you are installing the correct software.
121+
122+
119123
Fixed in Image 2022_v4.0 (Game Tools 2022 f1 and WPILib 2022.3.1)
120124
-----------------------------------------------------------------
121125

0 commit comments

Comments
 (0)