-
Notifications
You must be signed in to change notification settings - Fork 31
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
Acceleration limit constraint #27
Comments
Just to be clear, you do mean a joint acceleration constraint? If so, there is nothing implemented for now. Indeed, we usually prefer to set a torque limit. But yes, a joint acceleration constraint would be easy to implement. |
Small thing to add: the joint limits (torque, position, velocity) also correspond nicely to the URDF limit tag so these values are somewhat standard/easy to get. |
Yes sorry I meant a constraint. Right now we are controlling our robot via position only but the system has built in acceleration limits so we want to keep the rate of motion to within those limits. |
I'm looking into implementing this, would it be best to extend BoundedSpeedConstr with acceleration and name it BoundedCartesianMotionConstr, or should I create a separate BoundedAccelConstr? |
I went with just one object, seemed simpler and like it will make for less duplicate code in #28. I'd appreciate a review, still need to make the unit test. It is on top of the alignment changes to avoid those crashes. |
In addition to the position/velocity constraints, is there an acceleration constraint available? Presumably it should be fairly trivial to implement if not since everything is done in acceleration space.
The text was updated successfully, but these errors were encountered: