Software
Software copied to clipboard
Fix RobotDiagnosticsCLI Chip & Kick
Description of the task
Chip and Kick commands do not work properly in the RobotDiagnosticsCLI. Autokick and autochip work however. I suspect this is due to either an improperly formed proto within the CLI or due a the stop command being issued too quickly after a chip or kick. The goal of this ticket is to fix this.
You could put:
LOG(INFO) << "PRIMITIVE INFO: " << input.DebugString();
in src/software/embedded/services/network/network.cpp to print your incoming protos being recieved in thunderloop
Acceptance criteria
- [ ] Chip works
- [ ] Kick works
Blocked By
#3379 Similar to #3330