Closed meghdeepj closed 4 years ago
This is because the noise_variance is very small compareed to your T_variance of your wheel odometry. Of course the T265 will simply ignore all your odometry values
Thanks @stevemartinov, setting it to 0.02 has improved it, I'll tune it further.
Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):
All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)
Issue Description
I am trying to perform 2D odometry with T265 and wheel odometry for an autonomous mobile robot. The robot moves fairly slowly ~0.15m/s. The wheel odometry shows perfect 0 m/s when stationary and accurate in linear and angular velocity readings but accumulates significant drift in orientation (yaw) and X,Y pose and there is always a change of slippage. But, the twist data from wheel odometry fused T265 odom shows linear velocity of about 2mm/s when the robot is not moving (there are no vibrations when the robot is stationary) which is leading to growing X,Y drift even when the robot is stationary, but the twist data during motion is good. The orientation (yaw) from T265 pose is near perfect.
Below is the realsense-ros launch file contents:
And the "calibration_odometry.json" file:
{ "velocimeters": [ { "scale_and_alignment": [ 1.0, 0.0, 0.0, 0.0, 1.0, 0.0, 0.0, 0.0, 1.0 ], "noise_variance": 0.0044, "extrinsics": { "T": [ 0.0, -0.37, 0.36 ], "T_variance": [ 9.999999974752427e-7, 9.999999974752427e-7, 9.999999974752427e-7 ], "W": [ -1.2091996, 1.2091996, 1.2091996 ], "W_variance": [ 9.999999974752427e-5, 9.999999974752427e-5, 9.999999974752427e-5 ] } } ] }
Thanks for the help.