-
Notifications
You must be signed in to change notification settings - Fork 1k
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
description: verify joint limits #510
Comments
@ipa-nhg @miguelprada @fmauch thoughts? |
I think, it does make sense to use those as the full torque limits. As I understand it, in most cases a total tcp (or elbow) force will be limiting those maximum torques depending on the robot's joint configuration. So, if we would want to stop users from driving the robot into safety limits by requesting high torques, we would also have to specify a force limit with a Cartesian reference and make sure this would be similar to the one configured on the robot. Additionally, in the real world they will probably be hard to violate in a non-contact situation, as commanded jerks will be smoothed by the underlying For in-contact situations, I think, it is not really unexpected that the robot goes into a protective stop, if the force limits are reached, although joint torque limits aren't met, yet. |
I've used the listed torque limits as the maximum limits in the configuration files in the end. Thanks for your comment @fmauch 👍 |
Closing as #513 was merged. |
Currently doing this for
melodic-devel-staging
and noticed that the joint limits for the UR5 fi are probably incorrect (at least the effort limits seem to be incorrect).I'm slightly unsure what to use as effort limits though: the docs state this:
So what should we configure as limits then?
The text was updated successfully, but these errors were encountered: