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

AMCL odometry and drift question

asked 2014-09-09 22:56:58 -0500

jseal gravatar image

I'm using AMCL and it does a good job of estimating my position and accounting for drift, looking at the particles cloud. The odometry is periodically updated from AMCL but then reverts back to the drifted solution. Am I supposed to subscribe to amcl_pose and update my odometry node? or something else?

edit retag flag offensive close merge delete

Comments

amcl_pose should contain the robots position in the map. So you have to subscribe to this or to tf and get the 'map' -> 'robot' transform. What do you mean with updating the odometry node?

Sebastian Kasperski gravatar image Sebastian Kasperski  ( 2014-09-10 02:21:25 -0500 )edit

My odometry node publishes a transform from base_link to odom, which is still being updated from the drifted odometry. It also publishes a static transform from odom to map.

jseal gravatar image jseal  ( 2014-09-10 09:48:16 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
1

answered 2014-09-11 06:37:46 -0500

Sebastian Kasperski gravatar image

Ah okay, then this is the problem. You have to remove this static transform from map -> odom, because this will be provided by amcl. If two nodes publish the same transformation, you get this "jumping" behaviour between your amcl and the static transform.

edit flag offensive delete link more

Comments

Thanks Sebastian, that fixed it.

jseal gravatar image jseal  ( 2014-09-11 14:31:34 -0500 )edit

Question Tools

2 followers

Stats

Asked: 2014-09-09 22:56:58 -0500

Seen: 911 times

Last updated: Sep 11 '14