Added most of the backend code required to make the application functional. The most substantial missing features of this PR compared to a theoretically completed DS are joystick support and ROS topic pub/sub.
Summary of changes:
Add data containers for all UI elements to interact with. ROS sub/pubs will also interact with this data.
This includes stuff like enabled/disabled/estop, teleop/autonomous/test, event name, match number, alliance, etc
Add logic for the connection indicators (ie. connected to radio, to robot, etc)
Add logic for the PC battery & CPU usage indicators
Add logic and timing for practice mode
Set timing based on user input
Cycle through the modes with the desired sequence
Optionally enable sound effects
Add logic for the Reboot roboRIO and Restart Robot Code buttons
Add logic for the main status string (No Robot Communications, Teleop Disabled, etc)
What's not included:
Joystick support
ROS topic subscribers and publishers
Persistent data (Saving team number, practice timing, etc between instances)
Full firewall detection support
USB connection detection (Currently, plugging in directly to the RIO over USB shows up as ethernet)
Missing a few sound effects (Countdown blip and disable robot effect)
Pull Request
Added most of the backend code required to make the application functional. The most substantial missing features of this PR compared to a theoretically completed DS are joystick support and ROS topic pub/sub.
Summary of changes:
Reboot roboRIO
andRestart Robot Code
buttonsNo Robot Communications
,Teleop Disabled
, etc)What's not included:
Contribution Checklist
Change Checklist