-
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
Add support for UR16e #460
Comments
I started working on that on a train trip during the Christmas holidays. For the sake of simplicity I decided to start working on top of #371. The current status is on https://github.com/fmauch/universal_robot/tree/ur16e (easier diff: here). Things still to be done:
I hope, this covers everything otherwise please add more points, I'll add them to the list. |
I have urdfs + unstyled meshes for the UR16e if you'd like me to send them to you. Have not broken the model up into separate visual and collision meshes yet, but it's a start. |
We could certainly take a look at them @arthurpetron. Would you have them somewhere available in a repository? That would be most convenient. |
Sure, try here: https://github.com/arthurpetron/ur16e-dev . The inertial values are a rough estimate, but the masses should be correct. |
@arthurpetron Some parameters (such as mass and DH-converted kinematics) from eSeries_UR16e_15012020_URDF_ONLY.csv differ from https://www.universal-robots.com/how-tos-and-faqs/faq/ur-faq/parameters-for-calculations-of-kinematics-and-dynamics-45257/. Are they extracted based on the solidworks model? Apart from that I took all of my rudimentary blender skills and chopped out a piece from the ur10e upperarm and forearm models to get the correct meshes. |
The mass values are all correct (entered by hand) the intertial values are not. They are extracted from the solidworks URDF creation. UR does provide the full, 3x3 intertial matrices. I've copied them here: It's important that the arm is in the position that I've specified in the URDF so that the zero positions line up. |
Initial support for UR16e was merged into We'd still need to check the inertias and other dynamic parameters though, just to make sure they are correct. @fmauch: which values did you end up adding to your PR? |
I modeled them similar to the other models already inside the description packages. |
And the changes in dhled/universal_robot@ur_description_args...fmauch:inertia_from_ur? Especially the later commits seem relevant perhaps? |
I'll try to come back on that during the weekend |
I rebased my work and further elaborated it inside #504, as this doesn't only affect the ur16e. |
Hello guys, what is the current status of this topic? We would need a MoveIt support for the UR16e. Is there a chance to implement this in the near future? BR |
Creating a MoveIt configuration package is just a matter of completing the wizard. For any use other than a quick test you need to do this in any case, so I don't believe you're held back by a MoveIt configuration not being available yet. |
MoveIt config has been added in #538, updating my summary comment above. |
kinematics has been added, so everything is done. Closing this issue. |
Recently released.
ur_support
should be extended to include meshes, config, launch files and xacro macro.The text was updated successfully, but these errors were encountered: