robot don't try to match it's real position
The navigation stack was running quite well in navigation stage with my navigation config file. From my understanding, the robot will try to match it's real position gradually, as long as it move around. But, in my physical robot, the robot don't try to match it's real position, when i give it a goal. The tf tree is OK. What is the problem maybe?
In addition, I can use my robot to built a good map. Does that means my odometry data is sensible ?
Comments
Have you set the initialpose for your robot manually for AMCL?
eitan
(
2011-05-03 05:08:27 -0600
)edit
What does it actually do when you give it a goal? Does it attempt to move at all? Does it just sit? Does move_base throw any errors to the terminal window or rxconsole? Did you write your own drivers for the physical robot or are you using existing drivers such as p2os?
Eric Perko
(
2011-05-03 07:00:56 -0600
)edit
I have set the initialpose. I can use rviz to set the initialpose and send a goal to the robot. The robot move to the goal, when i give it a goal. But the laser scan line don't try to match the walls and the corners automatically.
Charles
(
2011-05-03 14:54:45 -0600
)edit
It seems that AMCL didn't work, but the /map frame to /odom frame transformation was OK.
Charles
(
2011-05-03 14:55:20 -0600
)editadd a comment
