Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Revision history [back]

Looking at the driver source, I think it's just using the data straight off the IMU. If it is, then the data is in NED frame, which does not follow the ROS standards, and is therefore not compatible with robot_localization. To fix it, you'll need to negate the Y and Z axes for everything the IMU produces, including the quaternion.

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.