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

Revision history [back]

It looks like you're running a source-built version of navigation, I assume there's a good reason to not use debs?

First step for diagnosing would be to set the log level to debug for move_base and post that output as well.

It looks like you're running a source-built version of navigation, I assume there's a good reason to not use debs?

First step for diagnosing would be to set the log level to debug for move_base and post that output as well.


EDIT: From the log file, you're having an error where the observations (i.e. laserscan ray endpoints or pointcloud) received by the obstacle layer of your map are not within the costmap bounds. This is probably a misconfiguration somewhere, either with your map size (maybe your static map which overrides your map size), or your tf transforms.

Since you already have navigation being build from source, I would recommend hooking it up to a debugger, or just adding some additional ROS_DEBUGs in the problem area to try to figure out where the calculations are going wrong.

It looks like you're running a source-built version of navigation, I assume there's a good reason to not use debs?

First step for diagnosing would be to set the log level to debug for move_base and post that output as well.


EDIT: From the log file, you're having an error where the observations (i.e. laserscan ray endpoints or pointcloud) received by the obstacle layer of your map are not within the costmap bounds. This is probably a misconfiguration somewhere, either with your map size (maybe your static map which overrides your map size), or your tf transforms.

Since you you're already have building navigation being build from source, I would recommend hooking it up to a debugger, or just adding some additional ROS_DEBUGs in the problem area to try to figure out where the calculations are going wrong.