Hi Andreas, This may or may not help, but one thing I notice is in your costmap yaml, topic field is missing, i.e. base_scan: {sensor_frame: base_laser_link,* topic: /base_scan*, data_type: LaserScan, expected_update_rate: 0.2, observation_persistence: 0.0, marking: false, clearing: true, min_obstacle_height: -0.08, max_obstacle_height: 2.0} John On Mon, May 17, 2010 at 2:42 AM, Andreas Vogt < andreasv@informatik.uni-bremen.de> wrote: > Hi, > > I receive this message if I start my launch file: > > [ERROR] 4.264000000: Client [/move_base] wants topic /base_laser to have > datatype/md5sum > [sensor_msgs/PointCloud/d8e9c3f5afbdd8a130fd1d2763945fca], but our > version has [sensor_msgs/LaserScan/90c7ef2dc6895d81024acba2ac42f369]. > Dropping connection. > > > I use a simulated laser my launch file look like this: > > > > > > > > > > > > > args="-p robot_description spawn -z 2" respawn="false" output="screen" /> > > > > > command="load" /> > > args="my_controller_ns" name="my_controller_spawner" /> > > > > args="$(find my_controller_pkg)/config/office.png 0.05"/> > name="base_laser_to_base_link" args="0 0 0 1.57 0 0 base_link base_laser > 100" /> > name="base_footprint_to_base_link" args="0 0 0 0 0 1.57 base_link > base_footprint 20" /> > > > > > name="move_base" output="screen"> > ns="global_costmap" /> > ns="local_costmap" /> > > > > > > > and my laser is here in the costmap yaml: > > observation_sources: base_scan > > base_scan: {sensor_frame: base_laser_link, data_type: LaserScan, > expected_update_rate: 0.2, > observation_persistence: 0.0, marking: false, clearing: true, > min_obstacle_height: -0.08, max_obstalce_height: 2.0} > > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users >