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

Planning Scene is missing TF frames #646

Closed
schornakj opened this issue Aug 27, 2021 · 1 comment · Fixed by #654
Closed

Planning Scene is missing TF frames #646

schornakj opened this issue Aug 27, 2021 · 1 comment · Fixed by #654
Assignees
Labels
bug Something isn't working

Comments

@schornakj
Copy link
Contributor

Description

I think there's a regression in #310 that prevents the planning scene from tracking frames that are published to TF but aren't associated with links in the URDF.

Your environment

  • Rolling
  • Ubuntu 20.04
  • Source build, main branch at 974a7a174.

Steps to reproduce

  • ros2 launch run_move_group run_move_group.launch.py
  • Create a node with a TF publisher and publish "world" to "test_frame".
  • ros2 service call /get_planning_scene moveit_msgs/srv/GetPlanningScene '{}'

Expected behaviour

Planning scene should contain info about a transform from "world" to "test_frame".

Actual behaviour

After #310, the planning scene service response does not contain info about this transform. A practical result of this is that MoveIt Task Constructor's GeneratePose stages fail while finding IK solutions for named target poses published through TF.

@schornakj schornakj added the bug Something isn't working label Aug 27, 2021
@JafarAbdi JafarAbdi self-assigned this Aug 27, 2021
@jrgnicho
Copy link
Contributor

jrgnicho commented Sep 2, 2021

I think I'm getting errors related to this issue. I basically run the move_group node with the occupancy_map_updater expecting to see the octomap in rviz but no octomap is shown and in the terminal I get the following error messages:

Do not call canTransform or lookupTransform with a timeout unless you are using another thread for populating data. Without a dedicated thread it will always timeout.  If you have a separate thread servicing tf messages, call setUsingDedicatedThread(true) on your Buffer instance.
[move_group-1] [ERROR] [1630597665.236855007] [tf2_buffer]: Do not call canTransform or lookupTransform with a timeout unless you are using another thread for populating data. Without a dedicated thread it will always timeout.  If you have a separate thread servicing tf messages, call setUsingDedicatedThread(true) on your Buffer instance.
[move_group-1] [ERROR] [1630597665.236945719] [moveit_ros.planning_scene_monitor.planning_scene_monitor]: Transform error: "world_frame" passed to lookupTransform argument target_frame does not exist. 
[move_group-1] [ERROR] [1630597665.236971975] [moveit.ros.occupancy_map_updater]: Transform cache was not updated. Self-filtering may fail. If transforms were not available yet, consider setting robot_description_planning/shape_transform_cache_lookup_wait_time to wait longer for transforms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants