Bruce Posted July 12, 2017 Share Posted July 12, 2017 Hi everyone, My group is working on a human-robot collaboration project. We are trying to use a Microsoft Xbox 360 Kinect with the Sawyer robot. The Kinect is functioning properly and, in fact, when we run roslaunch sawyer_moveit_config sawyer_moveit.launch Kinect:=true electric_gripper:=true, it brings up Rviz and we can visualize the point-cloud generated by the Kinect. However, the octomap does not show up in Rviz. We tried to remove the name space “move_group” in the “sawyer_moveit_sensor_manager.launch.xml” under “moveit_sawyer_config” directory as suggested by this thread: https://groups.google.com/forum/#!topic/moveit-users/Fz-Hxhjr5zI. It didn’t work for us. Next, we looked on the Baxter Research Robot Community forum and found similar, if not identical questions, that were asked back in 2013. The supposed issue is that clock time on the robot computer and time on my development PC are desynchronized. (as suggested by this thread: https://groups.google.com/a/rethinkrobotics.com/forum/#!searchin/brr-users/lookup$20would$20require/brr-users/9z3h8etJkp0/Pkn4p-J0t3gJ). When we run the launch file, we get the warning: [ WARN ] [1499805321.709597996]: Unable to transform object from frame ‘camera_link’ to planning frame ‘/base’ (Lookup would require extrapolation into the past. Requested time 1499805321.720482463 but the earliest data is at time 1499805348.802233425, when looking up transform from frame [camera_link] to frame [base]) Also mentioned in the thread, there was a patch released to fix this issue. However, our softwares are up to date on both the robot computer and our development PC and we are still having this clock desynchronization issue. We are out of ideas as to how to fix this problem. Could anyone please give us some guidance with this issue? Thanks in advance for the help. Bruce Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.