Welcome to ROSMASTER R2 repository

9. Cartographer mapping algorithm

Cartographer: https://google-cartographer.readthedocs.io/en/latest/

Cartographer ROS: https://google-cartographer-ros.readthedocs.io/en/latest/

map_server: https://wiki.ros.org/map_server

9.1. Introduction

Cartographer is a 2D and 3D SLAM (simultaneous localization and mapping) library supported by Google's open source ROS system. A graph-building algorithm based on graph optimization (multi-threaded backend optimization, problem optimization of ceiling construction). Data from multiple sensors (such as LIDAR, IMU, and cameras) can be combined to simultaneously calculate the sensor's position and map the environment around the sensor.

The source code of cartographer mainly includes three parts: cartographer, cartographer_ros and ceres-solver (back-end optimization).

• cartographer

Cartographer uses the mainstream SLAM framework, which is a three-stage structure of feature extraction, closed-loop detection, and back-end optimization. A certain number of LaserScans form a submap, and a series of submaps constitute the global map. The cumulative error in the short-term process of using LaserScan to construct a submap is not large, but the long-term process of using a submap to construct a global map will have a large cumulative error. Therefore, closed-loop detection is needed to correct the positions of these submaps. The basic unit of closed-loop detection is submap, closed-loop detection uses the scan_match strategy. The focus of cartographer is the creation of submap subgraphs that integrate multi-sensor data (odometry, IMU, LaserScan, etc.) and the implementation of the scan_match strategy for closed-loop detection.

• cartographer_ros

The cartographer_ros package runs under ROS and can accept various sensor data in the form of ROS messages. After processing, it can be published in the form of messages to facilitate debugging and visualization.

9.2. Use

Note: When building a map, the slower the speed, the better the effect (note that the rotation speed should be slower). If the speed is too fast, the effect will be poor.

According to different models, you only need to set the purchased model in [.bashrc], X1 (normal four-wheel drive) X3 (Mailun) Take X3 as an example

xxxxxxxxxx
#Raspberry Pi 5 master needs to enter docker first, please perform this step
#If running the script into docker fails, please refer to ROS/07, Docker tutorial
~/run_docker.sh

Open the [.bashrc] file

xxxxxxxxxx
sudo vim .bashrc

Find the [ROBOT_TYPE] parameters and modify the corresponding car model

xxxxxxxxxx
export ROBOT_TYPE=X3 # ROBOT_TYPE: X1 X3 X3plus R2 X7

To replace the configuration file, copy the launch file and lua file required by cartographer to the specified directory. It is configured before leaving the factory.

xxxxxxxxxx
sudo bash ~/yahboomcar_ws/src/yahboomcar_nav/scripts/copy_carto.sh

9.2.1. Start

Start the command (robot side). For the convenience of operation, this section takes [mono + laser + yahboomcar] as an example.

xxxxxxxxxx
roslaunch yahboomcar_nav laser_bringup.launch # laser + yahboomcar
roslaunch yahboomcar_nav laser_usb_bringup.launch # mono + laser + yahboomcar
roslaunch yahboomcar_nav laser_astrapro_bringup.launch # Astra + laser + yahboomcar

Mapping command (robot side)

<PI5 needs to open another terminal to enter the same docker container

xxxxxxxxxx
roslaunch yahboomcar_nav yahboomcar_map.launch use_rviz:=false map_type:=cartographer

• [use_rviz] parameter: whether to enable rviz visualization.

• [map_type] parameter: Set the mapping algorithm [cartographer].

Turn on the visual interface (virtual machine side)

xxxxxxxxxx
roslaunch yahboomcar_nav view_cartographer.launch

The gap at the back of the robot is due to the obstruction caused by the installation position of the display screen, so a certain range of radar data is blocked. The shielding range can be adjusted, or it can not be blocked according to the actual situation. For specific operations, see [01. Radar Basic Course].

9.2.2. Controlling the robot

• Keyboard controls robot movement

xxxxxxxxxx
rosrun teleop_twist_keyboard teleop_twist_keyboard.py # System integration
roslaunch yahboomcar_ctrl yahboom_keyboard.launch # Custom

• Control the robot movement with the handle

Make the robot cover the area to be mapped and the map should be as closed as possible.

There may be some scattered points during the mapping process. If the mapping environment is well closed, relatively regular, and the movement is slow, the scattering phenomenon will be much smaller.

9.2.3. Map saving

xxxxxxxxxx
bash ~/yahboomcar_ws/src/yahboomcar_nav/maps/carto_map.sh

The map will be saved to the ~/yahboomcar_ws/src/yahboomcar_nav/maps/ folder, a pgm image and a yaml file.

map.yaml

xxxxxxxxxx
image: map.pgm
resolution: 0.05
origin: [-15.4,-12.2,0.0]
Negate: 0
occupied_thresh: 0.65
free_thresh: 0.196

Parameter analysis:

• image: The path of the map file, which can be an absolute path or a relative path.

• resolution: resolution of the map, meters/pixel

• Origin: 2D pose (x, y, yaw) in the lower left corner of the map. The yaw here is rotated counterclockwise (yaw=0 means no rotation). Many parts of the current system ignore the yaw value.

• negate: whether to reverse the meaning of white/black and free/occupied (the interpretation of the threshold is not affected)

• occupied_thresh: Pixels with an occupation probability greater than this threshold will be considered fully occupied.

• free_thresh: Pixels with occupancy probability less than this threshold will be considered completely free.

9.2.4. Node View

xxxxxxxxxx
rqt_graph

9.2.5. View tf tree

xxxxxxxxxx
rosrun rqt_tf_tree rqt_tf_tree

9.3. Configuration parameters

lua file