ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
On rtabmap side, you may set subscribe_scan
to false here to not subscribe to missing laser scan. Otherwise, to fix depthimage_to_laserscan
, you may have to remap the name of the topic used by that nodelet here, by the depth image generated by the r200 (which may have different name than other 3d sensors like kinect/xtion).
2 | No.2 Revision |
On rtabmap side, you may set subscribe_scan
to false here to not subscribe to missing laser scan. Otherwise, to fix depthimage_to_laserscan
, you may have to remap the name of the topic used by that nodelet here, by the depth image generated by the r200 (which may have different name than other 3d sensors like kinect/xtion).
EDIT
In turtlebot_bringup package, change these lines in 3dsensor.launch so that $(arg camera)/$(arg depth)/image_raw
is $(arg camera)/$(arg depth)/sw_registered/image_rect_raw
instead OR set depth_registration
argument to false
here.
The problem is that r200 launch file doesn't provide the hardware registered depth image /camera/depth_registered/image_raw
, instead it provides only the software registered version /camera/depth_registered/sw_registered/image_rect_raw
Other option, I updated demo_turtlebot_mapping.launch to be able to use software registration, that way you don't have to change anything from turtlebot_bringup launch files. With this new launch file and r200:
export TURTLEBOT_3D_SENSOR=r200
roslaunch turtlebot_bringup minimal.launch
export TURTLEBOT_3D_SENSOR=r200
roslaunch rtabmap_ros demo_turtlebot_mapping.launch args:="--delete_db_on_start" rgbd_odometry:=true depth_topic:=/camera/depth_registered/sw_registered/image_rect_raw sw_registered:=true
roslaunch rtabmap_ros demo_turtlebot_rviz.launch