Forward enabled_motors
set from motor.cpp to thunderscope
#3424
Labels
Difficulty - 7
Well-defined tasks that requires some understanding about the relevant system and tools
Elaborated Starters
Robot Software
Thunderscope
Triage
When it's unclear if it's worth doing or how to start
Assuming #3425 is merged, motor.cpp will have a field called
enabled_motors
that represents the motors that are currently usable (out of the 4 drive motors and the dribbler).The motor driver code is organized to disable any motors that experience multiple critical faults in a short amount of time.
We should find a way to communicate to thunderscope (and the AI) that a motor has been disabled, so that we can see in real time which motor on which robot has failed.
From what I know, there are a couple of ways to achieve this.
enabled_motors
through to the thunderscope level code.Acceptance criteria
Blocked By
The text was updated successfully, but these errors were encountered: