You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This picture is my /odom data, I pub topic cmd_vel line.x = 0.03 at first then it turn, but about timestamp is 90, I pub topic cmd_vel line.x = 0.06, then it go straight perfect.
I think the joint or task space controller maybe have bugs!?
Can any one help!? thanks a lot
I don't quite understand the issue. Are you saying that when given a small forward velocity that the robot is turning instead of driving straight? Judging by your plots, it appears you are commanding the robot to turn (twist.twist.angular.z is angular velocity). To me, the odometry plot seems to correlate with the velocity plot correctly.
I have similar data showing a negative bias with the odometry.
The plot above shows the reference commanded velocity is 0.5 m/s. The /odom twist linear x velocity is the orange line at about 0.35 m/s. The distance is calculated by the Euclidean distance for the /odom (x, y) position.
Edit: Some more testing shows the max speed of my Create 2 is actually 0.33m/s. I set this max speed in my application.
I'm not convinced the odometry error is caused by the software driver.
The wheel encoders on the Create platform will not give very good odometry. I would not be surprised to see systematic odometry error vary significantly from one robot to the next.
Activity
jacobperron commentedon Mar 11, 2021
I don't quite understand the issue. Are you saying that when given a small forward velocity that the robot is turning instead of driving straight? Judging by your plots, it appears you are commanding the robot to turn (
twist.twist.angular.zis angular velocity). To me, the odometry plot seems to correlate with the velocity plot correctly.Bscout2011 commentedon Jul 16, 2021
Hi @jacobperron,
I have similar data showing a negative bias with the odometry.
The plot above shows the reference commanded velocity is 0.5 m/s. The
/odomtwist linear x velocity is the orange line at about 0.35 m/s. The distance is calculated by the Euclidean distance for the/odom(x, y) position.Edit: Some more testing shows the max speed of my Create 2 is actually 0.33m/s. I set this max speed in my application.
jacobperron commentedon Jul 22, 2021
I'm not convinced the odometry error is caused by the software driver.
The wheel encoders on the Create platform will not give very good odometry. I would not be surprised to see systematic odometry error vary significantly from one robot to the next.