-
Notifications
You must be signed in to change notification settings - Fork 91
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
Using Descartes with attached collision objects #244
Comments
I think I managed to use an attached collision object (as a tool) by further modifying Descartes. The planning now fails if the tool touches the environment and doesn't if the path is valid. Although, it is at least 10x slower than before to plan a path. I haven't tested it that much though. Here's what I did :
Where planning_scene_ is updated at the end of MoveitStateAdapter::initialize() :
Do you guys have any idea how to speed it up? |
I used a similar approach to collision check with attached collision objects. I modified the code further and used |
Hey all,
I've been using Descartes with collision objects without problem, but I didn't manage to use it with attached collision objects (collision is ignored between the attached collision object and the robot + environment). In my case, I want to use an attached collision object as a tool to facilitate tool changing, but the tool currently ignores collision with the robot/environment.
It is possible to use Descartes with attached collision objects?
I'm using the kinetic version of Descartes and I modified Descartes according to this tutorial for enabling collision since moveit planning scene was not being updated correctly:
http://wiki.ros.org/descartes/Tutorials/Robot%20Welding%20With%20Descartes
If this is not an issue since Descartes is not supposed to work with attached collision objects, I'll close this issue right away.
The text was updated successfully, but these errors were encountered: