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

Removed collision objects linger on somewhere colliding with the robot #1775

Closed
skaeringur97 opened this issue Dec 2, 2022 · 2 comments
Closed
Labels
bug Something isn't working E-medium Medium Effort stale Inactive issues and PRs are marked as stale and may be closed automatically.

Comments

@skaeringur97
Copy link

Description

When running a pick and place demo for a while, objects that I have placed and removed from the planning scene somehow linger on and collide with the robot even though they are not visible in Rviz or from psi.getKnownObjectNames(). This only happens if I publish the objects in one node, and remove them in another. I have tried removing them with PSI, PSM and publishing to the planning scene with synchronous and asynchronous updates. This is the same problem as explained in #924 .

I made a minimal example where you can see the error [servo_node-2] [WARN] [1669973859.126323207] [moveit_collision_detection.collision_common]: Objects in collision (printing 1st of 1 pairs): applex, panda_hand after applex has been removed. I made it so that you can easily modify it to publish the apples locally and then you won't see this error.

Your environment

  • ROS2: [Humble]
  • OS Version: e.g. Ubuntu 22.04
  • Binary build

Steps to reproduce

minimal example node.
Apple spawner node.
Panda driver launch file,
Panda moveit launch file,
Main launch file.

How to run showing the error:
Run the launch files in this order: Panda driver -> Panda moveit -> Main

How to "fix" the error:

  1. In the minimal example code, set publish_apples_here to true.
  2. In the main launch file, remove the apple spawner node from the launch description.
  3. Run the launch files in the same order.

Expected behaviour

Objects are picked and placed and then removed.

Actual behaviour

Removed objects linger on somewhere and collide with the robot.

@skaeringur97 skaeringur97 added the bug Something isn't working label Dec 2, 2022
@tylerjw tylerjw added the E-medium Medium Effort label Mar 10, 2023
@github-actions
Copy link

This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.

@github-actions github-actions bot added the stale Inactive issues and PRs are marked as stale and may be closed automatically. label Sep 11, 2023
Copy link

github-actions bot commented Apr 9, 2024

This issue was closed because it has been stalled for 45 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working E-medium Medium Effort stale Inactive issues and PRs are marked as stale and may be closed automatically.
Projects
None yet
Development

No branches or pull requests

2 participants