ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Fully agree with all of your points.
Perhaps you could also have a look at the imu_tools/imu_filter_madgwick package. You only need to provide the angular velocity and linear acceleration values from your device (optionally also magnetometer readings), and they will be fused to arrive at an orientation that follows the standards you outlined above.
2 | No.2 Revision |
Fully agree with all of your points.
Perhaps you could also have a look at the imu_tools/imu_filter_madgwick package. You only need to provide the angular velocity and linear acceleration values from your device (optionally also magnetometer readings), and they will be fused to arrive at an orientation that follows the standards you outlined above.
Edit in response to Alex's comment:
I guess there's something wrong with what you visualize, but to be sure, I first tested that the IMU I use (Phidgets Spatial 3/3/3) actually follows the conventions you outlined, and it does (all on the imu/data_raw
topic):
angular_velcocity
:
linear_acceleration
:
This leaves the visualization part. What I do is:
publish_tf
to false, since IIRC it was either wrong or at least misleading, and that I set the fixed frame to imu
.imu
and add a visualization of type rviz_imu_plugin
(part of the imu_tools
package). Set imu/data
as the input topic.rqt_plot
and plot imu/data_raw/angular_velocity
and imu/data_raw/linear_acceleration
.Hope this helps!
3 | No.3 Revision |
Fully agree with all of your points.
Perhaps you could also have a look at the imu_tools/imu_filter_madgwick package. You only need to provide the angular velocity and linear acceleration values from your device (optionally also magnetometer readings), and they will be fused to arrive at an orientation that follows the standards you outlined above.
Edit in response to Alex's comment:
I guess there's something wrong with what you visualize, but to be sure, I first tested that the IMU I use (Phidgets Spatial 3/3/3) actually follows the conventions you outlined, and it does (all on the imu/data_raw
topic):
angular_velcocity
:
linear_acceleration
:
This leaves the visualization part. What I do is:
publish_tf
to false, since IIRC it was either wrong or at least misleading, and that I set the fixed frame to imu
.imu
and add a visualization of type rviz_imu_plugin
(part of the imu_tools
package). Set imu/data
as the input topic.rqt_plot
and plot imu/data_raw/angular_velocity
and imu/data_raw/linear_acceleration
.Hope this helps!