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

move_base with own localization

asked 2013-03-26 22:52:05 -0600

funas1 gravatar image

updated 2013-03-27 03:03:02 -0600

Hello together

This is my first attempt at using the navigation stack. I have written my own node to localize my robot using a laser scanner and kalman fitler,the odometry is not reliable enough. The localization gives me the pose of the robot. I would now like to use move_base with my determined pose to drive to certain goals. I wouldlike, that move_base relies only on my localization, because the odometry is ot reliable enough. How can I tell the move_base node to use my own pose?

Thanks allot in advance!

---------Update-------------- After yout post I looked into AMCL and saw, that this could as well solve my problem. I have a map consisting of four landmarks and I know the starting position. The laser will register at least two of those landmarks, which is sufficient for a localization in 2D (afaik...). The problem is, that the laser will as well register allot of "noise" inside and outside the desired area (people and robots moving). But if I limit the region of interest for amcl to the area without noise, which contains all the landmarks, shouldn't it be possible to use AMCL as it is? If so, how can I limit the information provided by the topic scan to the region of interest? Can I write a node, which takes the scan informations, eliminates all unneeded scans and passes the filtered data?

P.s.(should i post this as a knew question?)

Thanks in advance

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
3

answered 2013-03-27 02:06:43 -0600

The standard way to do achieve this is by using tf. Approaches that are able to localize the robot like gmapping or AMCL publish the map -> odom transform. If you follow this convention with your localization approach, you should be able to use it as a drop-in replacement for the other mentioned approaches. I did that myself with hector_mapping and it works without problems.

In fact, move_base doesn't care at all which localization approach is used, as it only uses tf to do queries about transforms. See REP 105 for an overview of coordinate frames for mobile robots. Again, the job of your localization node would be providing the map -> odom transform.

edit flag offensive delete link more

Comments

Thank you very much for your answer. So if I understood correctly I just need to provide my pose estimated by the localization node via tf? I will try this give an update. Thanks!

funas1 gravatar image funas1  ( 2013-03-27 02:30:34 -0600 )edit

Question Tools

1 follower

Stats

Asked: 2013-03-26 22:52:05 -0600

Seen: 940 times

Last updated: Mar 27 '13