Hello!

I'm trying to use robotposeekf to fuse IMU and Odometry data. Everything works well except the resulting odometry which has an oposite direction from what it should have. It has the correct robot path but it's turned 180º and I've no idea why.

Odometry topic: /diff_drive_controller/odom
IMU topic: /imu_data

robotposeekf launch info:

<node pkg="robot_pose_ekf" type="robot_pose_ekf" name="robot_pose_ekf">
      <param name="output_frame" value="odom"/>
      <param name="freq" value="30.0"/>
      <param name="sensor_timeout" value="1.0"/>
      <param name="odom_used" value="true"/>
      <param name="imu_used" value="true"/>
      <param name="vo_used" value="false"/>
      <param name="debug" value="false"/>
      <param name="self_diagnose" value="false"/>
      <remap from="/odom" to="/diff_drive_controller/odom" />
      <!-- <remap from="/imu_data" to="/imu" /> -->
      <!-- <remap from="base_footprint" to="base_link"/> -->
    </node>

This is the only node providing the tf between odom and base_footprint and that's why I don't understand why the direction is wrong since I'm not publishing 2 tf's.

I mean if I subscribe the /diffdrivecontroller/odom topic it shows the related result but the slam_gmapping map is much better with this inverted odometry even tho it does not follow the robot path.