ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Success! The problem goes away when I change the frame ID of my IMU message (published by https://github.com/romainreignier/rtimulib_ros) to something not contained in my TF tree. I wonder why that is, any speculation?
2 | No.2 Revision |
Success! The problem goes away when I change the frame ID of my IMU message (published by https://github.com/romainreignier/rtimulib_ros) from map
to something not contained in my TF tree. I wonder why that is, any speculation?
3 | No.3 Revision |
Success! The problem goes away when I change the frame ID of my IMU message (published by https://github.com/romainreignier/rtimulib_ros) from map
to something not contained in my TF tree. I wonder why that is, any speculation?
Why tho?
Maybe someone can teach me why a frame of map
on my IMU message caused my odom to jump around.
It is too bad rqt_tf_tree doesn't visualize this sort of problem. Maybe I'll think about how to improve on rqt_tf_tree.