ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Most ot the time the imu data is fused with odometry and thus influences the odom->base_link transform. Usually via ekf_localization_node ekf_localization_node
I checked learover github (link text). It seems all should work fine, but in the
odometry.launch
you might want to change Line 3
<arg name="three_d" default="false"/>
set this to "true", the odometry is in 2d mode by default.
2 | No.2 Revision |
Most ot the time the imu data is fused with odometry and thus influences the odom->base_link transform. Usually via ekf_localization_node ekf_localization_node
I checked learover github (link text). It seems all should work fine, but in the
odometry.launch
you might want to change Line 3
<arg name="three_d" default="false"/>
set this to "true", the odometry is in 2d mode by default.
3 | No.3 Revision |
Most ot the time the imu data is fused with odometry and thus influences the odom->base_link transform. Usually via ekf_localization_node
I checked learover leorover github (link text). It seems all should work fine, but in the
odometry.launch
you might want to change Line 3
<arg name="three_d" default="false"/>
set this to "true", the odometry is in 2d mode by default.