Add selective motor control API#625
Open
mvrius wants to merge 1 commit into
Open
Conversation
Allow enabling/disabling specific motors by name via REST API.
Adds optional 'motors' parameter to /api/motors/set_mode/{mode} endpoint.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add selective motor control API
Motivation
When running Reachy Mini in "always-on" mode (e.g., as an ambient assistant), I want to keep all motors disabled to save power and reduce wear. However, when detecting certain keyword sounds (like a wake word), I want to activate only the antennas to provide visual feedback without moving the head or body.
Changes
motorsparameter toPOST /api/motors/set_mode/{mode}endpointmotorslist is provided, only those specific motors are affectedmotorsis omitted or empty, all motors are affected (existing behavior preserved)Usage
Testing
Tested on Reachy Mini Wireless running version 1.2.4 patched with this PR. Verified that: