Skip to content
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

Collision meshes of LR 200id too restrictive. #34

Closed
jettan opened this issue Jul 26, 2017 · 4 comments · Fixed by #36
Closed

Collision meshes of LR 200id too restrictive. #34

jettan opened this issue Jul 26, 2017 · 4 comments · Fixed by #36

Comments

@jettan
Copy link
Contributor

jettan commented Jul 26, 2017

The current collision meshes of the LR mate 200id are too restrictive.
In particular, I'm talking about the mesh for link2.
Link 2 is supposed to have a bigger opening such that link 4 is partly inside of the current link 2 collision mesh (example of such a joint configuration in radians: [0, 0.3, -1, 0, 1.3, 0]).

@gavanderhoorn
Copy link
Member

Take a look at ros-industrial/kuka_experimental#59, which is basically the same problem, but for KUKA Agilus KR6 and KR10.

See ros-industrial/kuka_experimental#76 for a PR that addressed that issue.

You could probably improve the collision mesh for link_2 using the bounding_mesh tool mentioned in the PR.

@jettan
Copy link
Contributor Author

jettan commented Jul 26, 2017

Thanks, I managed to get the bounding_mesh tool to work. Will make a PR after I tested tomorrow whether the bounded mesh of link2 works and/or whether I need to also change link3/4.

@gavanderhoorn
Copy link
Member

@jettan: did your collision meshes work better?

@jettan
Copy link
Contributor Author

jettan commented Aug 8, 2017

Yes it did, but I am hesitant to make a PR because it might be too lax (or the robot I am working with isn't mastered very accurate). The only replacement I needed in collision mesh was as you suggested link_2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants