create a poor map with lidars
I encountered a problem using the Lidar to create the map. Map is not closed. I am using the Gmapping method.
Does anyone know why this is? Or give me some advice? Thank you!
ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
I encountered a problem using the Lidar to create the map. Map is not closed. I am using the Gmapping method.
Does anyone know why this is? Or give me some advice? Thank you!
To me it looks like the laser scanner is working well, but the ODOM drift is too high, so the robot loses it's sense of direction over time. Can I assume your robot has wheel encoders? If it does, you should redo the calibration, especially for encoder counts on each wheel during rotating. If your odom is based on a calculation of counts and wheel measurements, I suggest instead you determine the counts/meter and counts/radian through measurement instead of calculating. See section 1.2 of this: http://wiki.ros.org/navigation/Tutori... Once you are confident in the calibration, remap and make sure any rotation during mapping is done very slowly.
Asked: 2017-11-18 09:55:00 -0500
Seen: 128 times
Last updated: Nov 20 '17
Gmapping - pgm to svg - Autotrace
Converting ultrasound range to a Laser Scan
Is the robot always centered in a local costmap?
Require help mapping using TurtleBot 2 and an RP-LiDAR A2
Localization issue using gmapping and odom data.
How to get a real-time map using the laser tf and laser scans
Closed Loop Detection gmapping & Hector SLAM
Scan matching failed, using odometry
turtlebot estimates wrong 2D pose on rviz when using amcl_demo