Yaw_degree data of odometry fustion have error than IMU and odom of yaw _degree data

I have made a fusion between sensor odom and imu, but the result of yaw degree value has a lot of errors compared to sensors odom and imu as a the picture given. I would like to help analyze the cause of this and provide solutions. Thank you.

Parameter Config

frequency: 10

two_d_mode: true

publish_tf: false

odom_frame: odom
base_link_frame: base_footprint
world_frame: map
map_frame: map

odom0: /odom
odom0_config: [true, true, false,
false, false, false,
true, true, false,
false, false, false,
false, false, false]

initial_state: [0.0,0.0, 0.0,
0.0, 0.0, 0.0,
0.0, 0.0, 0.0,
0.0, 0.0, 0.0,
0.0, 0.0, 0.0]

imu0: /imu

imu0_config: [false, false, false,
false, false, true,
false, false, false,
false, false, false,
false, false, false]

initial_state: [0.0,0.0, 0.0,
0.0, 0.0, 0.0,
0.0, 0.0, 0.0,
0.0, 0.0, 0.0,
0.0, 0.0, 0.0]

imu0_differential: false

process_noise_covariance: [0.05, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0.05, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0.06, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0.03, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0.03, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0.06, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0.025, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0.025, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0.04, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0.01, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.01, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.02, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.01, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.01, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.015]

initial_estimate_covariance: [1e-9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 1e-9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 1e-9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 1e-9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 1e-9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 1e-9, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 1e-9, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 1e-9, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 1e-9, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 1e-9, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1e-9, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1e-9, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1e-9, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1e-9, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1e-9]

Links Pictures





[/quote]

I’m assuming you are using robot_localization. Remember that by default the simulation will have perfect imu and odom values, so what’s the reason to fuse those two?

You can try adding noise to the gazebo sensor plugins and see if the kalman filter improves from the noisy sensors?

I don’t know the parameters off the bat, but here is the page for them:

http://docs.ros.org/en/melodic/api/robot_localization/html/configuring_robot_localization.html

1 Like

It’s surprising that the odom and imu sensors they don’t have noise but they’re combined which has a lot of noise, maybe I setting a parameter wrong or maybe the reference frame of odom_filter is wrong .

Yes, my assumption is that it would need to be a perfect square as well.

What is your goal fusing two sensors with no noise?

I want to prove the system config and working correctly .

Shouldn’t be the matrix you use for odom and imu be set different, or did I not understand one of the live classes?

https://www.youtube.com/live/QZ5q59H2qaI?si=Kq0snZ25TPvOmsPB

By accident I was watching this live class two days ago. And I think the matrices were setup different. Maybe this helps

Br

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.