glim icon indicating copy to clipboard operation
glim copied to clipboard

Lidar Points moving opposite direction to the robot direction

Open vickzk opened this issue 6 months ago • 3 comments

Robot Type: Mobile robot Sensor Setup: Separate LiDAR and IMU sensors Transform (T_lidar_imu): Set as identity (translation: zero, rotation: [0, 0, 0, 1]) Data Flow: All sensor data is transformed to the base_link frame and passed to GLIM

Issue Observed: While running SLAM with GLIM, the map appears accurate, and the odometry is mostly stable. However, there is a noticeable drift behavior during continuous motion:

As the robot moves forward, the LiDAR point cloud appears to move backward relative to the robot’s motion.

This drift accumulates and remains while the robot is in motion.

Once the robot stops, the LiDAR data snaps back or settles into the correct pose.

Request for Help: What could be causing this drift during motion and sudden correction on stopping? Any insights or suggestions to resolve this behavior would be appreciated

vickzk avatar Jul 01 '25 06:07 vickzk

https://github.com/user-attachments/assets/33a53ddf-0ff1-4c70-9ec3-3aee5c6a4ee5

vickzk avatar Jul 01 '25 06:07 vickzk

There may be IMU-related issues. Can you check if 1) the LiDAR-IMU is correct, 2) IMU data has a reasonable frequency (about 100Hz)?

koide3 avatar Jul 07 '25 04:07 koide3

I've verified the TF and it looks correct. Regarding the IMU rate, I'm running in simulation with a configured update rate of 100 Hz. However, due to Gazebo's real-time factor, the effective rate I'm observing is around 90 Hz.

vickzk avatar Jul 07 '25 04:07 vickzk