I've noticed that (at least) in pure rotation, odometry accumulates error. Steps to recreate:
Send cmd_vel msg with an angular twist of 0.1.
Wait for full 360 deg rotation to occur on physical iRobot Create 2.
Check odometry, notice that twist is not back to the same spot (this is easy to see in rviz by placing iRobot_0/base_link axes on a fixed frame)
Also, if you send a cmd_vel msg with a greater ang twist of ~1.0 or so, this issue doesn't occur. (maybe it's time related so moving faster accumulates less error?)
My setup: Raspberry Pi 2, ROS indigo, Ubuntu 14.04.
If I rollback to code before the "New Odometry" pull req, then the issue seems to disappear.
I've noticed that (at least) in pure rotation, odometry accumulates error. Steps to recreate:
cmd_vel
msg with an angular twist of 0.1.rviz
by placingiRobot_0/base_link
axes on a fixed frame)cmd_vel
msg with a greater ang twist of ~1.0 or so, this issue doesn't occur. (maybe it's time related so moving faster accumulates less error?)My setup: Raspberry Pi 2, ROS indigo, Ubuntu 14.04.
If I rollback to code before the "New Odometry" pull req, then the issue seems to disappear.