-
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
Fix joint limits for all supported variants #513
Fix joint limits for all supported variants #513
Conversation
Based on values from the User Manuals.
Because of this I'll look at the history of the various |
For the UR10 specifically, the incorrect joint limits (mostly velocity) were introduced in 78b2702. Then changed again (to correct ones I believe) in 953d046. And then changed a few times more. At least for the UR10, it's a bit unclear where Edit: ah. [Joint]
min_limit = -6.2831853071795862
max_limit = 6.2831853071795862
v_max = 2.16 # 2.16 = 2/3 * 3.2
a_max = 60.0 # Guess
torque_max = 330 So Note also the
[Joint]
min_limit = -6.2831853071795862
max_limit = 6.2831853071795862
v_max = 2.16 # 2.16 = 2/3 * 3.2
a_max = 60.0
torque_max = 330 Current manuals and datasheets spec this limit as 120 degree/sec though, which is In the worst case, the maximum joint velocity planned with for a UR10 would be approx 3% slower than what the robot is capable of (although the |
I'm in doubt whether or not to keep 56fab86: while it's convenient to be able to directly compare the limits, it's also using non-standard units which goes against REP-103. I'd like some additional input from others: @miguelprada @ipa-nhg @fmauch: thoughts? |
I think, going with radians (and maybe as a comment the according deg values) might be a good choice. As most of them are |
True, but limiting them (artificially) is easier when it's in degrees and degrees/sec. Using degrees will make re-using the limits files for MoveIt and |
I'm going to remove 56fab86. Radians is what it should be, and it allows reuse of the joint limits file for other packages/nodes. If only |
56fab86
to
8f7c90d
Compare
I've checked and double-checked the limits for all variants and joints. I believe they are now correct. If it turns out something is still not right, we'll fix that in a follow-up PR. |
I'm somewhat confused as to where the previous values for the limits came from, as there seemed to be quite some deviations from the specs (except for the UR16e, but that was only added very recently).
First commit fixes the limits (position, velocity and effort) based on the specs in the linked documents (user manuals and the support site article).
Second commit changes the
_macro.xacro
to accept joint limit data in degrees and degrees/sec (instead of radians). This makes it much easier to compare the limits in the files with the ones on the datasheets and the manuals.Table used for joint torque limits (from here, but with torques instead of motor sizes):