Robot localization dual_ekf_navsat example
Why doesn't the example at https://github.com/cra-ros-pkg/robot_... fuse yaw on the imu?
ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Why doesn't the example at https://github.com/cra-ros-pkg/robot_... fuse yaw on the imu?
I'm assuming you meant to link this:
https://github.com/cra-ros-pkg/robot_...
The short answer is because it doesn't need to. The robot's estimate of where it is in its own map
coordinate frame doesn't require any kind of earth-referenced heading. navsat_transform_node
needs it, but the EKF doesn't care. Magnetometers are notoriously erroneous, e.g., near metal, so I tend to leave it out. But if you prefer to fuse it, you can.
Asked: 2021-11-19 13:31:40 -0500
Seen: 108 times
Last updated: Dec 22 '21
move_base could not find package manifest
Include marker position update into robot localization
PID control of original robot in Gazebo
Action client not connected: manipulator_controller/follow_joint_trajectory
Action Server Compiler Error => error: no match for call to ‘(boost::_mfi........
Moveit teleoperation of 3DOF arm with 3D mouse
Starting a node twice, with differend parameters