robot_localization has consistent delay
Hi all,
I am using robotlocalization and gmapping, and I am having problems. I am fusing odometry and imu measurements with the ekf node included with robotlocalization. When the robot spins in place, the odometry and the imu both report approximately the correct value as soon as the robot starts spinning. The ekf node, however, does not reflect the turn until ~2 seconds after the robot starts spinning. I have tried this multiple times and with multiple different speeds, and I get the same consistent ~2 second delay. I tried to double my filtering frequency from 30 to 60 Hz to try and fix the problem, but it didn't work.
Is this a bug with robot_localization or could this somehow be in my setup? There doesn't seem to be anything in the parameters that would cause this.
Thanks in advance
Asked by Robocop87 on 2015-07-21 18:37:09 UTC
Answers
It's hard to say without a launch file or sample data. My first suspicion is that your covariances are the culprit, but I'd need to see more information.
Asked by Tom Moore on 2015-07-24 16:28:47 UTC
Comments
Hi Tom, thank you for all of the answers you have been providing for my robot_localization questions, and I apologize again for my delay in seeing them all. I will play with my covariances and see if that changes the delay time.
Asked by Robocop87 on 2015-08-06 08:04:03 UTC
Comments