You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
changed the title
Servo position, velocity, torque limits from robot model
Checking limits in servo commands
Nov 6, 2024
Position and velocity limits are already configured in the servos themselves, via servopos.position_max/min and servo.max_velocity. What would be the benefits of checking them before sending commands?
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:
The text was updated successfully, but these errors were encountered: