Closed ammaraljodah closed 7 months ago
Allow collisions, not disallow them:
-disable_collision->allowCollisions( "tool1", all_links, false);
+disable_collision->allowCollisions( "tool1", all_links, true);
I want the gripper to grasp the tool, thus I need to disable collision, is that the right logic?
void moveit::task_constructor::stages::ModifyPlanningScene::allowCollisions (const std::string & first,
const T & second,
bool enable_collision )
Cross-posted to RSE it seems: Persistent "Goal State is in Collision" Error Despite Disabling Collisions
Can you guys check the posted answer
Allow collisions, not disallow them:
-disable_collision->allowCollisions( "tool1", all_links, false); +disable_collision->allowCollisions( "tool1", all_links, true);
you are not disabling collisions, you set allow_collision
to false
-disable_collision->allowCollisions( "tool1", all_links, false);
+disable_collision->allowCollisions( "tool1", all_links, true);
Yes that fixed the issue, many thanks @rhaschke
I am working with the MoveIt Task Constructor to set up a robotic task sequence and am encountering a persistent collision detection issue despite explicitly disabling collisions for certain links. I have tried disabling global collisions for a specific object called ("tool1") against all links in the planning scene, but the task still fails with a "Goal state is in collision" error. I've confirmed that the collision disabling stage is executed before any planning or motion execution stages. Below is the relevant part of my code where I set up the collision disabling:
my task setup:
This is how I add the collision object:
This is how I disable the collision
Then closing the fingers on the object:
Despite this configuration, the stage named "close fingers" reports a collision. I have checked the execution order and used RViz to visually inspect the scene. All links are included, and debugging outputs confirm that the stage is processed.
Here is what I have already checked:
• Execution order of stages.
• Correctness of all_links vector (contains all relevant link names).
• RViz visual inspection shows no unexpected overlaps.
• Increased debugging verbosity around collision settings application.
• Tested with different motion planners.
I am using ROS2 humble, and MoveIt 2.
Could there be a misunderstanding on my part regarding how collision settings are supposed to be applied, or might there be a bug or limitation in the software versions I am using?
Thank you!