ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Hernan's profile - activity

2020-11-06 10:39:19 -0500 received badge  Student (source)
2015-08-20 13:21:51 -0500 received badge  Enthusiast
2015-08-11 08:31:50 -0500 commented question Question regarding tf2 static_transform_publisher

Hi,

did you solve the problem? I'm having the same issue.

2015-08-11 08:30:35 -0500 answered a question Question regarding tf2 static_transform_publisher

Hi,

did you solve the problem? I'm having the same issue.

2015-04-17 09:15:00 -0500 received badge  Taxonomist
2014-12-20 20:11:01 -0500 received badge  Famous Question (source)
2014-11-26 12:33:40 -0500 commented question robot_localization: imu ignored

Tom, I was able to fix the problem and now everything integrates. A suggestion: would it be possible to add the reason of integration failure in the debug output? In any case, thanks a lot.

2014-11-26 12:28:40 -0500 received badge  Scholar (source)
2014-11-26 12:28:39 -0500 received badge  Supporter (source)
2014-11-26 12:06:07 -0500 received badge  Notable Question (source)
2014-11-26 09:42:04 -0500 received badge  Editor (source)
2014-11-26 09:32:47 -0500 commented answer robot_localization: imu ignored

Thanks, I did it that way. I'm deleting this post.

2014-11-26 09:30:15 -0500 received badge  Popular Question (source)
2014-11-26 08:32:00 -0500 answered a question robot_localization: imu ignored

Tom,

thanks for taking the time to take a look at this. I'm attaching the debug output of ekf_navigation. Replying to your comments and questions:

  • I don't see any error or warning in the debug output.
  • There is no prepareTwist printed in the debug output.
  • This is the imu sample:

    header: seq: 2540 stamp: secs: 6478 nsecs: 433795000 frame_id: imu orientation: x: 0.0 y: 0.0 z: 0.0 w: 1.0 orientation_covariance: [100.0, 0.0, 0.0, 0.0, 100.0, 0.0, 0.0, 0.0, 100.0] angular_velocity: x: 0.0 y: 0.0 z: 0.0872664611111 angular_velocity_covariance: [1.0, 0.0, 0.0, 0.0, 0.0001, 0.0, 0.0, 0.0, 0.0001] linear_acceleration: x: 10.0 y: 0.0 z: 0.0 linear_acceleration_covariance: [0.002, 0.0, 0.0, 0.0, 1.0, 0.0, 0.0, 0.0, 1.0]

  • I have tried to include only the imu and it is the same, ignored.

Hernan

2014-11-26 08:27:31 -0500 answered a question robot_localization: imu ignored

Tom,

thanks for taking the time to take a look at this. I'm attaching the debug output of ekf_navigation. Replying to your comments and questions:

  • I don't see any error or warning in the debug output.
  • There is no prepareTwist printed in the debug output.
  • This is the imu sample:

    header: seq: 2540 stamp: secs: 6478 nsecs: 433795000 frame_id: imu orientation: x: 0.0 y: 0.0 z: 0.0 w: 1.0 orientation_covariance: [100.0, 0.0, 0.0, 0.0, 100.0, 0.0, 0.0, 0.0, 100.0] angular_velocity: x: 0.0 y: 0.0 z: 0.0872664611111 angular_velocity_covariance: [1.0, 0.0, 0.0, 0.0, 0.0001, 0.0, 0.0, 0.0, 0.0001] linear_acceleration: x: 10.0 y: 0.0 z: 0.0 linear_acceleration_covariance: [0.002, 0.0, 0.0, 0.0, 1.0, 0.0, 0.0, 0.0, 1.0]

  • I have tried to include only the imu and it is the same, ignored.

Hernan

2014-11-25 20:15:33 -0500 asked a question robot_localization: imu ignored

Hi All,

I'm beginner with robot_localization and ROS in general so would greatly appreciate your help. I've configured the robot_localization launch file to receive an odometry and a imu. The sensor data is actually simulated, so I'm providing only a global position estimate on the odometry message:

  <param name="odom0" value="/head/fake_gps"/>
  <rosparam param="odom0_config">[true, true, true, 
                                  false, false, false, 
                                  false, false, false, 
                                  false, false, false]</rosparam>
  <param name="odom0_differential" value="false"/>

and only a positive yaw velocity and x acceleration on the imu:

  <param name="imu0" value="/head/can_imu"/>
  <rosparam param="imu0_config">[false, false, false, 
                                 false, false, false, 
                                 false, false, false, 
                                 false, false, true,
                                 true, false, false]</rosparam>
  <param name="imu0_differential" value="false"/>

The odometry message is indeed received by robot_localization and the filter initializes and track the position. My problem is that the imu0 is completely ignored. It is not incorporated into the filter, even when the debug output of robot_localization is indeed reporting the reception of the measurement:

----- /FilterBase::integrateMeasurements ------
------ RosFilter::imuCallback (imu0) ------
IMU message:
header: 
  seq: 174
  stamp: 6474.783371000
  frame_id: imu
orientation: 
....

Furthermore, I have the corresponding transformation:

<node pkg="tf" type="static_transform_publisher" name="vehicle_to_head" args="1.70 0 1.40 0 0 0 vehicle head 20" />
<node pkg="tf" type="static_transform_publisher" name="head_to_imu" args="0 0 0 0 0 0 head imu 20" />
<node pkg="tf" type="static_transform_publisher" name="head_to_fakegps" args="0 0 0 0 0 0 head fakegps 20" />

<node name="ekf_localization_node" pkg="robot_localization" type="ekf_localization_node" clear_params="true">
  <param name="odom_frame" value="odom"/>
  <param name="base_link_frame" value="vehicle"/>
  <param name="world_frame" value="odom"/> 
  ....

I know it is not integrating the imu data because no matter what values I assign to the yaw velocity or x acceleration, the filter output is always the same. The assigned covariances are in the order of 0.01*2 for rotation speed and 0.0012 for translation acceleration.

Does anyone can give me a hint of what I might be doing wrong?

I would highly appreciate any help.


EDIT 1: (11/26/2014)

  • I don't see any error or warning in the debug output.
  • There is no prepareTwist printed in the debug output.
  • This is a imu sample: header: seq: 2540 stamp: secs: 6478 nsecs: 433795000 frame_id: imu orientation: x: 0.0 y: 0.0 z: 0.0 w: 1.0 orientation_covariance: [100.0, 0.0, 0.0, 0.0, 100.0, 0.0, 0.0, 0.0, 100.0] angular_velocity: x: 0.0 y: 0.0 z: 0.0872664611111 angular_velocity_covariance: [1.0, 0.0, 0.0, 0.0, 0.0001, 0.0, 0.0, 0.0, 0.0001] linear_acceleration: x: 10.0 y: 0.0 z: 0.0 linear_acceleration_covariance: [0.002, 0.0, 0.0, 0.0, 1.0, 0.0, 0.0, 0.0, 1.0]
  • I have tried to include only the imu and it is the same, ignored.

EDIT 2:

Yay, Tom, it seems that you are right. It is a problem with the tf.

transforms: 
  - 
    header ...
(more)