Problemas Conocidos

Este artículo detalla problemas conocidos (y soluciones) para el Software de Control de Sistema de FRC®

Problemas Abiertos

roboRIO 2.0 Ethernet Settings

Issue: On the roboRIO 2.0, the Ethernet port is configured to DHCP only. This will work in normal networking setups where the radio acts as a DHCP server, but will not communicate when tethered directly to the Driver Station via Ethernet.

Workaround: Use the RoboRIO Web DashBoard to change the Ethernet Adapter eth0 Configure IPv4 Address to DHCP or Link Local.

Driver Station Reporting No Code

Issue: There is a rare occurrence in the roboRIO 2.0 that causes the roboRIO to not properly start the robot program. This causes the Driver Station to report a successful connection but no code, even though code is deployed on the roboRIO.

Workaround: We are currently investigating the root cause, but FIRST volunteers have been made aware and the recommendation is to reboot the roboRIO when this occurs.

Nota

Pressing the physical User button on the roboRIO for 5 seconds can also cause the robot code to not start, but a reboot will not start the robot code. If the robot code does not start after rebooting, press the User button. Ensure that nothing on the robot is in contact with the User button.

Radio Second Port Sometimes Fails to Communicate

Issue: There is a rare occurrence in the OM5P Radios that causes the second Ethernet port (the one farthest from the power plug) to not communicate.

Workaround: Generally, power cycling the radio will restablish communication with the second port. Alternately, utilize a network switch such as the tp-link switch available from FIRST Choice or the brainboxes SW-005 and plug all ethernet devices into the network switch and then plug the switch into the radio’s first Ethernet port. This also allows easier tethering while at competition.

Onboard I2C Causing System Lockups

Issue: Use of the onboard I2C port on the roboRIO 1 or 2, in any language, can result in system lockups. The frequency of these lockups appears to be dependent on the specific hardware (i.e. different roboRIOs will behave differently) as well as how the bus is being used.

Workaround: The only surefire mitigation is to use the MXP I2C port or another device to read the I2C data. Accessing the device less frequently and/or using a different roboRIO may significantly reduce the likelihood/frequency of lockups, it will be up to each team to assess their tolerance of the risk of lockup. This lockup can not be definitively identified on the field and a field fault will not be called for a match where this behavior is believed to occur. This lockup is a CPU/kernel hang, the roboRIO will completely stop responding and will not be accessible via the DS, webpage or SSH. If you can access your roboRIO via any of these methods, you are experiencing a different issue.

Several alternatives exist for accessing the REV color sensor without using the roboRIO I2C port. A similar approach could be used for other I2C sensors.

• Use a Raspberry Pi Pico. Supports up to 2 REV color sensors, sends data to the roboRIO via serial. The Pi Pico is low cost (less than $10) and readily available.

• Use a Raspberry Pi. Supports 1-4 color sensors, sends data to the roboRIO via NetworkTables. Primarily useful for teams already using a Raspberry Pi as a coprocessor.

Updating Properties on roboRIO 2.0 may be slow or hang

Issue: Updating the properties on a roboRIO 2.0 without reformatting using the Imaging Tool (such as setting the team number) may be slow or hang.

Workaround: After a few minutes of the tool waiting the roboRIO should be able to be rebooted and the new properties should be set.

Simulation crashes on Mac after updating WPILib

Issue: On macOS, after updating the project to use a newer version of WPILib, running simulation immediately crashes without the GUI appearing.

Workaround: In VS Code, run WPILib | Run a command in Gradle, clean. Alternatively, run ./gradlew clean in the terminal or delete the build directory.

Construcción inválida debido a la falta de GradleRIO

Problema: En raras ocasiones, el caché de Gradle de un usuario se rompe y se muestran errores similares a los siguientes:

Could not apply requested plugin [id: ‘edu.wpi.first.GradleRIO’, version: ‘2020.3.2’] as it does not provide a plugin with id ‘edu.wpi.first.GradleRIO’

Solución Alternativa:

Elimina tu caché de Gradle ubicado en ~$USER_HOME/.gradle. Las máquinas Windows pueden necesitar habilitar la capacidad de ver archivos ocultos. Este problema sólo ha aparecido en Windows hasta ahora. Por favor, informe este problema si lo tiene en un sistema operativo alternativo.

Caracteres Chinos al iniciar la Driver Station

Problema: Rara vez, al iniciar la driver station se mostrarán caracteres Chinos en vez de texto en Inglés. Esto aparece solo cuando Windows esta configurado en otro idioma que no es Inglés.

Solución alternativa: Hay dos soluciones alternativas conocidas:

1. Copie y pegue los caracteres Chinos en un bloc de notas, y el texto en Inglés se mostrará.

2. Cambie temporalmente el lenguaje de Windows a Inglés.

C++ Intellisense - Los Archivos Abiertos al Iniciarse No Funcionan Correctamente

Problema: En C++, los archivos que se abren cuando se inicia VS Code tendrán problemas con Intellisense mostrando sugerencias de todas las opciones desde una unidad de compilación y no solo las apropiadas o no encontrando archivos de encabezado. Este es un error en VS Code.

Solución Alternativa:

1. Cierre todos los archivos en VS Code, pero deje VS Code abierto

2. Elimine el archivo c_cpp_properties.json en la carpeta .vscode, si existe

3. Run the «Refresh C++ Intellisense» command in VS Code.

4. En la esquina inferior derecha debe ver algo que se vea como una plataforma (linuxathena o windowsx86-64 etc). Si no es linuxathena de click y configure a linuxathena (lanzamiento)

5. Espere ~1 min

6. Abra el archivo main cpp (no el archivo de título). Intellisense debe de funcionar ahora

Issues with WPILib Dashboards and Simulation on Windows N Editions

Issue: WPILib code using CSCore (dashboards and simulated robot code) will have issues on Education N editions of Windows.

• Shuffleboard will run, but not load cameras

• Smartdashbard will crash on start-up

• Robot Simulation will crash on start-up

Solución: Intalar el Media Feature Pack

Fixed in Game Tools 2023.1.0

Driver Station does not detect joysticks at startup

Issue: The Driver Station application does not detect already connected joysticks when it starts up. Connecting joysticks after it is already running works.

Workaround: Connect joysticks after starting the DS, or use the joystick rescan button or the F1 shortcut to rescan for joysticks.

Fixed in WPILib 2023.2.1

SysId - Robot program crash on startup when using CAN Spark Maxes

Issue: SysId 2023.1.1’s deployed robot program crashes on startup if it was configured to use CAN Spark Maxes.

Solution: Install WPILib 2023.2.1 or newer.

Manually flushing a client NetworkTableInstance does not work

Issue: Calling flush() on a NetworkTableInstance does not cause the data to be flushed to remote subscribers immediately. This issue will be fixed in an upcoming WPILib release.

Workaround: Set the periodic option on the NetworkTable publishers that need a faster update rate:

JavaC++

// Get a DoubleEntry for myTopic and update it with a 10ms period.
DoubleEntry myEntry = table.getDoubleTopic("myTopic").getEntry(0, PubSubOption.periodic(0.01));