The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
This IMU conforms to the right-hand rule when mounted on the board chips side (the side with the axis drawing on top), also the driver is taking that into consideration. So it behaves as an enu IMU when mouted as described, and it's reporting enu orientation. Everything should work fine with r_l package when setting the imu_filter_madguick parameter world_frame to enu.
This confusion was not due to a problem in the used hardware or software but it was due to lack of understanding of some ROS and localization basics.
| | 2 | No.2 Revision |
This IMU conforms to the right-hand rule when mounted on the board chips side (the side with the axis drawing on top), also the driver is taking that into consideration. So it behaves as an enu IMU when mouted as described, described above, and it's reporting enu orientation. Everything should work fine with r_l package when setting the imu_filter_madguick parameter world_frame to enu.
This confusion was not due to a problem in the used hardware or software but it was due to lack of understanding of some ROS and localization basics.
| | 3 | No.3 Revision |
This IMU conforms to the right-hand rule when mounted on the board chips side (the side with the axis drawing on top), also the driver is taking that into consideration. So it behaves as an enu IMU when mouted as described above, and it's reporting enu orientation. Everything should work fine with r_l package when setting the imu_filter_madguick parameter world_frame to enu.
This confusion was not due to a problem in the used hardware or software but it was due to lack of understanding of some ROS and localization basics.
Thanks for your help Tom!
| | 4 | No.4 Revision |
This The Phidgets IMU conforms to the right-hand rule when mounted on the board chips side (the side with the axis drawing on top), also (I was initially getting "weird" measurements because it was mounted on the flat side)
Also the driver is taking that the ROS standards into consideration. consideration allowing every axis to read +1G when it's facing up. So it behaves as an enu IMU when mouted as described above, and it's reporting enu orientation. Everything should work fine with r_l package when setting the imu_filter_madguick parameter world_frame to enu.
This confusion was not due to a problem in the used hardware or software but it was due to lack of understanding of some ROS and localization basics.
Thanks for your help Tom!
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
