Nothing Special   »   [go: up one dir, main page]

Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Checking limits in servo commands #387

Open
stephane-caron opened this issue Apr 3, 2023 · 2 comments
Open

Checking limits in servo commands #387

stephane-caron opened this issue Apr 3, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@stephane-caron
Copy link
Member
stephane-caron commented Apr 3, 2023

Position commands are currently forwarded unchecked to the actuators, but we can forward their limits e.g. at spine configuration time. A safer behavior would be to:

  • Store and enforce position (if applicable), velocity and torque limits
  • Warn when they are not provided at spine configuration time
@stephane-caron stephane-caron self-assigned this Apr 3, 2023
@stephane-caron stephane-caron added the enhancement New feature or request label May 5, 2023
@stephane-caron stephane-caron removed their assignment May 23, 2023
@stephane-caron stephane-caron transferred this issue from stephane-caron/vulp Aug 7, 2024
@stephane-caron
Copy link
Member Author

Following up on this: we now pass joint limits (parsed from the URDF description) in Gymnasium environments. On the spine side, the proposal in #454 is to duplicate joint limits from upkie_description in a static C++ model, and use them for the last checks before sending position commands to the actuators.

@stephane-caron stephane-caron changed the title Servo position, velocity, torque limits from robot model Checking limits in servo commands Nov 6, 2024
@stephane-caron
Copy link
Member Author

After some more examination:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant