The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Well, when you look at your tf tree, is it actually connected? What does rosrun tf tf_echo /camera_depth_frame /odom_combined output?
I'm not familiar with the moveit_object_sender, but I got the same warning messages with a different setup where one of my nodes published a transform once, but didn't keep it updated. The problem was that the move_group node has a check where it asks for _all_ the frames in tf, and checks that it can transform between all of them and its planning frame. If any of them fail, even if they're not required for the current task, it prints out that message.
| | 2 | No.2 Revision |
Well, when you look at your tf tree, is it actually connected? What does rosrun tf tf_echo /camera_depth_frame /odom_combined output?
I'm not familiar with the moveit_object_sender, but I got the same warning messages with a different setup where one of my nodes published a transform once, but didn't keep it updated. The problem was that the move_group node has a check where it asks for _all_ the frames in tf, and checks that it can transform between all of them and its planning frame. If any of them fail, even if they're not required for the current task, it prints out that message.
EDIT: OK, this wasn't the same problem I had seen - it looks like you're publishing entirely independent trees. You probably have one of your nodes configured incorrectly, or are not publishing a required static transform. To debug this, I'd use rosrun tf view_frames to figure out what those trees are and which node is publishing each link. My first guess would be that you need to change the camera name argument in one of your launch files.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
