Why odom/filtered output on map frame is moving? [closed]

asked 2022-03-14 13:13:02 -0500

Johart24
3 ●5 ●8 ●13

Hello, im working on a navigation system.

I am using two instances of ekf filter from robot_localization package. I am obteinig that in the "odom" frame, i receive the gps signal with the odometry_map signal with a good performance, the signals are near enough to the robot whe it is static.

But when i visualice what is happening in the "map" frame, the robot is constantly moving around the ground, and the gps, and the /odometry/global signals are moving together with the robot.

So, the idea that i have is that the "odom -> map" trasnform frame is constantly moving alone. Why i am getting that? Is it becuase the GPS signal ? I am watching that sometimes the robot move in a area that more than 3m of error, which is usually the average gps error.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Johart24
close date 2022-05-24 10:42:23.744317

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2022-03-14 13:35:44 -0500

Nikodem
61 ●4 ●1

This is normal behavior if you configured it according to the documentation.

Idea is that local EKF handles wheel odometry and IMU to provide continuous vehicle trajectory (odom->base transform). Global EKF takes global position from GPS and uses it to provide map->odom transform. This can (and most probably will) jump around due to GPS inaccuracies.

edit flag offensive delete link

Comments

Hey thanks for answer. I have a concern. If i want to publish a gps coordinate waypoint, this inaccuracies in the map_frame are gonna interfere on the trajectory path creation?

Johart24 ( 2022-03-14 13:58:10 -0500 )edit

I share you a capture of how it looks like. https://ibb.co/D5Jv1tZ

Johart24 ( 2022-03-14 15:21:19 -0500 )edit

add a comment

answered 2022-03-14 13:55:06 -0500

Johart24
3 ●5 ●8 ●13

LOCAL EKF

#Configuation for robot odometry EKF LOCAL # frequency: 10 sensor_timeout: 0.1 two_d_mode: true transform_time_offset: 0.0 transform_timeout: 0.0 print_diagnostics: true debug: false

map_frame: map
odom_frame: odom
base_link_frame: base_link
world_frame: odom

# -------------------------------------
# Wheel odometry:

odom0: /odom_enc
odom0_config: [false, false, false,
             false, false, false,
             true,  true,  true,
             false, false, true,
             false, false, false]
odom0_queue_size: 10
odom0_nodelay: true
odom0_differential: false
odom0_relative: false
# imu configure:


imu0: /imu/data_front
imu0_config: [false, false, false,
            false,  false,  false,
            false, false, false,
            false,  false,  true,
            false,  false,  false]
imu0_nodelay: false
imu0_differential: false
imu0_relative: false
imu0_queue_size: 10

#  imu configure:--------------------------------------
imu0: /imu/data
imu0_config: [false, false, false,
            true,  true,  true,
            false, false, false,
            true,  true,  true,
            true,  true,  true]
imu0_nodelay: false
imu0_differential: false
imu0_relative: false
imu0_queue_size: 10
imu0_remove_gravitational_acceleration: false

process_noise_covariance: [1e-3, 0,    0,    0,    0,    0,    0,     0,     0,    0,    0,    0,    0,    0,    0,
                         0,    1e-3, 0,    0,    0,    0,    0,     0,     0,    0,    0,    0,    0,    0,    0,
                         0,    0,    1e-3, 0,    0,    0,    0,     0,     0,    0,    0,    0,    0,    0,    0,
                         0,    0,    0,    0.3,  0,    0,    0,     0,     0,    0,    0,    0,    0,    0,    0,
                         0,    0,    0,    0,    0.3,  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.5,   0,     0,    0,    0,    0,    0,    0,    0,
                         0,    0,    0,    0,    0,    0,    0,     0.5,   0,    0,    0,    0,    0,    0,    0,
                         0,    0,    0,    0,    0,    0,    0,     0,     0.1,  0,    0,    0,    0,    0,    0,
                         0,    0,    0,    0,    0,    0,    0,     0,     0,    0.3,  0,    0,    0,    0,    0,
                         0,    0,    0,    0,    0,    0,    0,     0,     0,    0,    0.3,  0,    0,    0,    0,
                         0,    0,    0,    0,    0,    0,    0,     0,     0,    0,    0,    0.3,  0,    0,    0,
                         0,    0,    0,    0,    0,    0,    0,     0,     0,    0,    0,    0,    0.3,  0,    0,
                         0,    0,    0,    0,    0,    0,    0,     0,     0,    0,    0,    0,    0,    0.3,  0,
                         0,    0,    0,    0,    0,    0,    0,     0,     0,    0,    0,    0,    0,    0,    0.3]
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,    1.0,  0,    0,    0,    0,    0,    0,     0,     0,     0,    0,    0,
                            0,    0,    0,    0,    1.0,  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,    1.0,  0,    0,    0,     0,     0,     0,    0,    0,
                            0,    0,    0,    0,    0,    0,    0,    1.0,  0,    0,     0,     0,     0,    0,    0,
                            0,    0,    0,    0,    0,    0,    0,    0,    1.0,  0,     0,     0,     0,    0,    0 ...

(more)

edit flag offensive delete link

add a comment

Why odom/filtered output on map frame is moving? [closed]

Closed for the following reason the question is answered, right answer was accepted by Johart24
close date 2022-05-24 10:42:23.744317

2 Answers

Comments

Question Tools

Stats

Related questions

Why odom/filtered output on map frame is moving? [closed] edit

Closed for the following reason the question is answered, right answer was accepted by Johart24 close date 2022-05-24 10:42:23.744317

2 Answers

Comments

Question Tools

Stats

Related questions

Why odom/filtered output on map frame is moving? [closed]

Closed for the following reason the question is answered, right answer was accepted by Johart24
close date 2022-05-24 10:42:23.744317