Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Forward enabled_motors set from motor.cpp to thunderscope #3424

Open
1 task
GrayHoang opened this issue Feb 8, 2025 · 0 comments
Open
1 task

Forward enabled_motors set from motor.cpp to thunderscope #3424

GrayHoang opened this issue Feb 8, 2025 · 0 comments
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

Comments

@GrayHoang
Copy link
Contributor

GrayHoang commented Feb 8, 2025

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.

  1. We could protobuffer enabled_motors through to the thunderscope level code.
  2. @wmostrenko mentioned something about passing motor fault information through to robot diagnostics. I believe it's a flag in sensor_fusion.cpp? Depending on the information sent, this might be enough to help the AI determine which motor has been disabled and plan accordingly.

Acceptance criteria

  • Thunderscope logs which motor has faulted (and the fault) on a robot, and when that fault occured.

Blocked By

@GrayHoang GrayHoang added Difficulty - 13 Require a good understanding of relevant systems and tools, and may require some pathfinding Motion Planning Robot Software Testing Field testing, test infrastructure, robot tuning Triage When it's unclear if it's worth doing or how to start labels Feb 8, 2025
@GrayHoang GrayHoang changed the title Add dribbler-free/three wheel/two wheel drive capability to motor.cpp [ON HOLD] Forward enabled_motors set from motor.cpp to thunderscope Mar 2, 2025
@GrayHoang GrayHoang added Difficulty - 7 Well-defined tasks that requires some understanding about the relevant system and tools Thunderscope Elaborated Starters and removed Difficulty - 13 Require a good understanding of relevant systems and tools, and may require some pathfinding Triage When it's unclear if it's worth doing or how to start Motion Planning Testing Field testing, test infrastructure, robot tuning labels Mar 2, 2025
@GrayHoang GrayHoang changed the title Forward enabled_motors set from motor.cpp to thunderscope Forward enabled_motors set from motor.cpp to thunderscope Mar 2, 2025
@GrayHoang GrayHoang changed the title Forward enabled_motors set from motor.cpp to thunderscope Forward enabled_motors set from motor.cpp to thunderscope Mar 2, 2025
@GrayHoang GrayHoang added the Triage When it's unclear if it's worth doing or how to start label Mar 2, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant