Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

set_pose Breaks robot_localization

asked 2020-10-05 15:38:20 -0600

JackB

977 ●10 ●76 ●33

updated 2020-10-05 15:38:44 -0600

Running the ekf_se_odom node with test1.bag I run into a problem when I publish /set_pose from RVIZ.

Upon publication to the set pose topic the odometry (viewable in RVIZ) stops moving. It remains fixed at the point where I initialized the new pose, and when I echo /odometry/filtered I see new messages are being published, but the pose is not changing, while the covariance continues to explode. This is a problem I ran into across two separate robot_localization setups I have, which usually work under all other conditions.

I imagine this maybe has something to do with RVIZ itself, but if someone has run into this before, or has some ideas to throw around, please let me know! And also if you need more information I can post that ASAP. This is something I have experienced in both melodic and kinetic.

Thanks, Jack

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2020-10-07 04:40:40 -0600

Tom Moore

flag of United Kingdom of Great Britain and Northern Ireland

13689 ●74 ●240 ●232 http://github.com/ayrton04

updated 2020-10-07 04:41:03 -0600

How are you playing back your bag file? What command are you using? My first guess is that you aren't using --clock (or maybe it's that you are). Then you send a set_pose command, and the filter resets itself, but the filter will not allow any measurements that are older than your set_pose time stamp, so all the bagged messages are ignored.

In any case, the time stamp in your set_pose publication needs to be based on the same clock as the bag.

edit flag offensive delete link

Comments

That was it, thanks!

JackB ( 2020-10-08 08:17:45 -0600 )edit

Hey.

I'm dealing with the same issue. What exactly solved the problem? Did you set use_sim_time to be True, or did you set explicitly the time stamp when executing set_pose?

florian ( 2022-02-22 02:23:35 -0600 )edit

add a comment

Question Tools

1 follower

Stats

Asked: 2020-10-05 15:38:20 -0600

Seen: 368 times

Last updated: Oct 07 '20

set_pose Breaks robot_localization edit

1 Answer

Comments

Question Tools

Stats

Related questions

set_pose Breaks robot_localization