Hi all,
I have a mobile robot and I would like it to navigate in a room, I already have a map of the room. I am using wheel encoders for the odometry, [robot_pose_ekf](http://wiki.ros.org/robot_pose_ekf) for fusing data from wheel encoders and IMU and to get the `odom_combined -> base_footprint` transformation. Then , I have [amcl](http://wiki.ros.org/amcl) for localization and [move_base](http://wiki.ros.org/move_base) is doing the planning.
I am able to start everything smoothly and give the goal through RVIZ and the tf tree looks correct:
After I give the goal, robot starts moving towards it and on the way, its localization gets messed up. Once, it is close to the goal it starts rotating in a random manner which also messes up the localization of the robot. The problem is more common when it is near to the goal, it starts rotating randomly and gets lost. Also sometimes, I get the warning:
Clearing costmap to unstuck robot (3.000000m).
Rotate recovery behavior started.
but I dont see the robot being stuck. I think there is some issue with amcl but I am not sure.
I saved all the data in a bag file and ran it and made two videos for two different goal positions. In first two cases, the correct orientation should be pi/2 (south direction) and in the last case the robot should point right:
[Video - 1](https://www.youtube.com/watch?v=sImBoaYiECs)
[Video - 2](https://www.youtube.com/watch?v=_OELo4rNPU8)
[Video - 3](https://youtu.be/rUrzx-wlFXE)
The parameters for amcl is shown below:
**amcl.launch**
↧