Open lkm1321 opened 1 year ago
Hello,
I did not check the behavior in melodic/gazebo9, but at least in noetic/gazebo11.11.0, the IMU is working as expected:
TF output (generated with libgazebo_ros_p3d.so)
$ rosrun tf2_tools echo.py world imu_link
At time 17.2, (current time 17.23)
- Translation: [0.107, 0.051, 0.330]
- Rotation: in Quaternion [-0.000, -0.000, 0.014, 1.000]
in RPY (radian) [-0.000, -0.000, 0.029]
in RPY (degree) [-0.000, -0.001, 1.639]
IMU output
orientation:
x: 8.324221710185843e-06
y: -2.39617195970217e-06
z: 0.013792436408627104
w: 0.9999048797875124
Thanks for getting back to me. To confirm:
Thought I'd add more background to 2: our URDF model does have an offset of 90 degrees yaw between base_link and IMU
Is world in ENU?
Yes.
Thought I'd add more background to 2: our URDF model does have an offset of 90 degrees yaw between base_link and IMU
This means, the IMU is mounted with an offset, so the values in gazebo11 are probably correct and gazebo9 ignores the mounting offset.
Hi,
I am finding that the initial orientation of the IMU is inconsistent between melodic/gazebo9 and noetic/gazebo11 by 90 degrees. Without any motion applied to the robot/IMU, melodic/gazebo9 outputs initial orientation (x, y, z, w) = (0, 0, 0, 1), and noetic/gazebo11 (x, y, z, w) = (0, 0, -0.707, 0.707)
We are using the following snippet: