Robotics StackExchange | Archived questions

Unable to detect obstacles in costmap

I am running movebase , taking scan input from hokuyo laser, using laserscan_matcher for localization, and using a blank costmap to start with. The global and local costmap params use rolling window instead of static map. My relevant launch files are dumped here :http://pastebin.com/8SArVL9p .

My problem is that I cannot see any obstacles in the costmap (I made logs in the costmap2d.cpp & costmap2dros.cpp to register obstacles). As such, movebase sends commands that go into obstacles, whenever I send it a goal. I suspect there is an issue with my costmap params, and would like to know which. I don't know if the initial, blank costmap I send causes a problem.

The robot controller computer on which I run all this has rviz segfaulting, and I'm unable to bring up rviz after exhaustive debugging ; but I was able to verify the presence of nearby obstacles by (temporarily) connecting the laser to a different computer that ran rviz.

Note:

(1) I have altered laserscanmatcher to send a tf from /map -> /odom (this agrees very well with my previous tests) instead of to map -> baselink.

(2) I am also publishing a laser->baselink and a /odom->baselink transform separately.

Asked by PKG on 2011-08-07 16:35:52 UTC

Comments

Also, is your laser data really stamped in the "map" frame? That seems strange and likely means that you'll only accumulate scans near the origin of the map.

Asked by eitan on 2011-08-08 05:47:51 UTC

Are you sure that your logging is giving you the right data? It seems strange that you saw obstacles when you hooked the laser up to rviz, but not when you use your own logging.

Asked by eitan on 2011-08-08 05:46:48 UTC

Answers