ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

/explore_server" requires "base_scan" to have "sensor_msgs/PointCloud" data type and not "sensor_msgs/LaserScan".

This suggests that frontier_exploration's costmap is configured to expect the wrong sensor type (pointcloud instead of laserscan). This will likely prevent the costmap from updating with your sensor data.


If your hope is for someone to debug your configuration, you'll be much better off if you put the entire bringup into a github repo, as well as provide complete logs of your launches.

It's also better to test your setup in simulation first, until you're at a point that things are working and it's time to bring hardware into the mix. If your simulation doesn't work, it's easy for someone else to start it and try to identify a problem.

Scan Matching error, using odometery is a gmapping error, meaning your mapping is likely not working properly. Try to get your mapping working via teleop, in isolation from move_base and exploration.

/explore_server" requires "base_scan" to have "sensor_msgs/PointCloud" data type and not "sensor_msgs/LaserScan".

This suggests that frontier_exploration's costmap is configured to expect the wrong sensor type (pointcloud instead of laserscan). This will likely prevent the costmap from updating with your sensor data.


If your hope is for someone to debug your configuration, you'll be much better off if you put the entire bringup into a github repo, as well as provide complete logs of your launches.

It's also better to test your setup in simulation first, until you're at a point that things are working and it's time to bring hardware into the mix. If your simulation doesn't work, it's easy for someone else to start it and try to identify a problem.