-
Notifications
You must be signed in to change notification settings - Fork 122
Open
Labels
BugIssues that describe a bug and possibly a suggested solutionIssues that describe a bug and possibly a suggested solutionDifficulty - 7Well-defined tasks that require some understanding about the relevant system and toolsWell-defined tasks that require some understanding about the relevant system and toolsNeeds HardwareThis ticket needs extra hardware, like a robot or development board to work onThis ticket needs extra hardware, like a robot or development board to work onRobot Software
Description
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
Metadata
Metadata
Assignees
Labels
BugIssues that describe a bug and possibly a suggested solutionIssues that describe a bug and possibly a suggested solutionDifficulty - 7Well-defined tasks that require some understanding about the relevant system and toolsWell-defined tasks that require some understanding about the relevant system and toolsNeeds HardwareThis ticket needs extra hardware, like a robot or development board to work onThis ticket needs extra hardware, like a robot or development board to work onRobot Software