Description of the task

Currently, when we send a kick command, we convert a kick speed (m/s) to a "kick_pulse_width".

When we send a chip command, we get a fixed "chip_pulse_width" from the Redis key/value store.

Elec/mech sometimes wants to control these pulse widths to test the kicker and chipper and they end up having to flash production code (Arduino). We should add the ability for pulse widths to be controlled via RobotDiagnostics so that they don't have to do this.

You can test the robot diagnostics locally by running:
./tbots.py run thunderscope_main --disable_communication --run_blue --run_diagnostics --interface=lo

Acceptance criteria

• Add the relevant new definitions in the protos
• Update the handling
• Add the ability to toggle to control the pulse widths directly in the PyQt ChickerWidget

Blocked By