Revision history [back]

Answers:

1. I publish the transform /odom -> /base_link only with the information of odometry, so it doesnt have any global information. I cloud change this with the information of the imu, but actually im not interested in global positioning.

   Don't do that. robot_localization (ekf_localization_node or ukf_localization_node) will publish the odom->base_link transform for you.

   Here my first question, where should I set the transform for the IMU, I am trying with a transform /base_link -> /imu where imu_frame is just base_link_frame but with the rotation reported from the IMU.

   Just use a static transform. You don't need to constantly update the base_link->imu transform. If your IMU is really mounted at the center of your robot, just use the tf2 (or tf) static_transform_publisher and give it a transform of all zeros.

2. You mis-spelled "false" in your odom0 configuration for yaw velocity. You have:

   <rosparam param="odom0_config">[false, false, false,
                                   false, false, flase,
                                   true,  true, false,
                                   false, false, true,
                                   false, false, false]</rosparam>
   

   You want:

   <rosparam param="odom0_config">[false, false, false,
                                   false, false, false,
                                   true,  true, false,
                                   false, false, true,
                                   false, false, false]</rosparam>
   

Answers:

1. I publish the transform /odom -> /base_link only with the information of odometry, so it doesnt have any global information. I cloud change this with the information of the imu, but actually im not interested in global positioning.

   Don't do that. robot_localization (ekf_localization_node or ukf_localization_node) will publish the odom->base_link transform for you.

   Here my first question, where should I set the transform for the IMU, I am trying with a transform /base_link -> /imu where imu_frame is just base_link_frame but with the rotation reported from the IMU.

   Just use a static transform. You don't need to constantly update the base_link->imu transform. If your IMU is really mounted at the center of your robot, just use the tf2 (or tf) static_transform_publisher and give it a transform of all zeros.

2. You mis-spelled "false" in your odom0 configuration for yaw velocity. yaw. You have:

   <rosparam param="odom0_config">[false, false, false,
                                   false, false, flase,
                                   true,  true, false,
                                   false, false, true,
                                   false, false, false]</rosparam>
   

   You want:

   <rosparam param="odom0_config">[false, false, false,
                                   false, false, false,
                                   true,  true, false,
                                   false, false, true,
                                   false, false, false]</rosparam>
   

Answers:

1. I publish the transform /odom -> /base_link only with the information of odometry, so it doesnt have any global information. I cloud change this with the information of the imu, but actually im not interested in global positioning.

   Don't do that. robot_localization (ekf_localization_node or ukf_localization_node) will publish the odom->base_link transform for you.

   Here my first question, where should I set the transform for the IMU, I am trying with a transform /base_link -> /imu where imu_frame is just base_link_frame but with the rotation reported from the IMU.

   Just use a static transform. You don't need to constantly update the base_link->imu transform. If your IMU is really mounted at the center of your robot, just use the tf2 (or tf) static_transform_publisher and give it a transform of all zeros.

2. You mis-spelled "false" in your odom0 configuration for yaw. You have:

   <rosparam param="odom0_config">[false, false, false,
                                   false, false, flase,
                                   true,  true, false,
                                   false, false, true,
                                   false, false, false]</rosparam>
   

   You want:

   <rosparam param="odom0_config">[false, false, false,
                                   false, false, false,
                                   true,  true, false,
                                   false, false, true,
                                   false, false, false]</rosparam>
   

Answers:

1. I publish the transform /odom -> /base_link only with the information of odometry, so it doesnt have any global information. I cloud change this with the information of the imu, but actually im not interested in global positioning.

   Don't do that. robot_localization (ekf_localization_node or ukf_localization_node) will publish the odom->base_link transform for you.

   Here my first question, where should I set the transform for the IMU, I am trying with a transform /base_link -> /imu where imu_frame is just base_link_frame but with the rotation reported from the IMU.

   Just use a static transform. You don't need to constantly update the base_link->imu transform. If your IMU is really mounted at the center of your robot, just use the tf2 (or tf) static_transform_publisher and give it a transform of all zeros.

2. You mis-spelled "false" in your odom0 configuration for yaw. You have:

   <rosparam param="odom0_config">[false, false, false,
                                   false, false, flase,
                                   true,  true, false,
                                   false, false, true,
                                   false, false, false]</rosparam>
   

   You want:

   <rosparam param="odom0_config">[false, false, false,
                                   false, false, false,
                                   true,  true, false,
                                   false, false, true,
                                   false, false, false]</rosparam>
   

EDIT in response to update:

If no output is being produced, then see my comment above about turning on debug mode. Right now, I am actually suspecting an issue with the transforms. You have forward slashes in the frame_ids in your messages, and you also put them in the configuration for ukf_localization_node. This would normally be correct. However, robot_localization uses tf2, and we strip all forward slashes from the frame_ids to be compliant with it. In other words, you should do two things

1. Remove the forward slashes from the frame_ids in your messages.
2. (Optional, but you should do it anyway) Remove the forward slashes from the frame_ids in your ukf_localization_node launch file.

By the way, if you're only fusing velocities (like you are for odom0), then you don't need to turn on relative mode. That's only for fusing absolute position or orientation data.