-
Notifications
You must be signed in to change notification settings - Fork 132
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
Actuator inertia #78
Comments
Correct, neither the transmission element nor the actuator element have inertia in URDF. If we were to introduce actuator inertia, it would probably be as a sub-element of the actuator element, which is a sub-element of transmission. I'm not a mechanical engineer, so can you provide a specific example, perhaps a formula for a motor model, where actuator inertia is needed and cannot be faked by some combinator of the joint dynamics and limit sub-elements? |
This is excellent documentation! Thanks for this example. Here's my comments:
|
In response to the comments by @scpeters:
|
Any update on this? I am surprised that motor inertia is not included in URDF. It is not something one can ignore when dealing with dynamics. Just to give you an example, the motor inertias (considering the gear ratio) of the first 2 joints of a 5kg payload robot can contribute 30-40% to the diagonals of the mass matrix. |
Is there any update? I tried to use the |
Actuators used in industrial robotic arms typically have a reasonably low inertia, which can be included in the link inertia. However, the actuator inertia has another important effect on the rigid body dynamics; namely, due to the gear ratio between the motor and the joint, the actuator inertia significantly contributes to the required torque to achieve a certain requested motion.
At the moment it seems that the URDF specification does not support the specification of such contribution of motor inertia. I think it could be well-placed in the transmission tag.
Some relevant questions for the discussion:
Thanks in advance for your input.
The text was updated successfully, but these errors were encountered: