Welcome to MicroROS-Pi5 repository

Multi-machine navigation

Note: The ROS_DOMAIN_ID of the Raspberry Pi and the microROS control board need to be consistent. You can check [MicroROS Control Board Parameter Configuration] to set the microROS control board ROS_DOMAIN_ID. Check the tutorial [Connect MicroROS Agent] to determine whether the IDs are consistent.

1、Program function description

After the program is started, the target points of the two cars can be given in rviz. After receiving the instruction, the two cars calculate the path based on their own posture and move to their destinations.

2、Multi-machine function basic settings

Taking two robots as an example, it is recommended to use two robots equipped with Raspberry Pi and change the config_robot.py files respectively. Change the config_robot.py files respectively, and set robot.set_ros_namespace() to robot1 and robot2 respectively. And the ROS_DOMAIN_ID of the two cars needs to be set to the same. Then open the terminal in the /home/pi directory and enter sudo python3 config_robot.py to run this program (you need to change it back and re-run this program to run other programs except multi-car).

3、Start and connect to the agent

After the Raspberry Pi is successfully powered on, open the terminal and enter the following command to open the agent.

sh ~/start_agent_rpi5.sh

Press the reset button on the microROS control board and wait for the car to connect to the agent. The connection is successful as shown in the figure below.

4、Enter the car docker

Open another terminal and enter the following command to enter docker.

xxxxxxxxxx
sh ros2_humble.sh 

When the following interface appears, you have successfully entered docker. Now you can control the car through commands.

Check the currently started node. Choose one of the two Raspberry Pis, open the terminal and enter the following command.

xxxxxxxxxx
ros2 node list

As shown in the picture above, the nodes of both cars have been started.

5、Start rviz and load the map

5.1、Start rviz display

Choose one of the two Raspberry Pis at random, open the terminal and input, (it is recommended to use the matching virtual machine to open the map, opening it on the Raspberry Pi will be very laggy)

xxxxxxxxxx
ros2 launch yahboomcar_nav multi_nav_display_launch.py

The functions of the signs in Figure 1-4 above are as follows:

【1】：robot1 calibrate initial pose

【2】：robot1 gives a target point

【3】：robot2 calibrate initial pose

【4】：robot2 given target point

4.2、Load map

Choose one of the two Raspberry Pis at random, open the terminal and input, (it is recommended to use the matching virtual machine to open the map, opening it on the Raspberry Pi will be very laggy)

xxxxxxxxxx
ros2 launch yahboomcar_multi map_server_launch.py

Note: The map may fail to load here. If the map is not loaded, just ctrl c to close and rerun the program. The map path loaded here is as follows.

xxxxxxxxxx
/root/yahboomcar_ws/src/yahboomcar_multi/maps/yahboom_map.yaml

If you need to modify the default loading of other maps, copy the map's yaml file and pgm file to

/root/yahboomcar_ws/src/yahboomcar_multi/maps/ directory. Then modify the map_server_launch.py program, which is located in /root/yahboomcar_ws/src/yahboomcar_multi/launch. The modification places are as follows

Replace the red box with the name of your own map, save and exit, and then enter the following instructions to compile.

xxxxxxxxxx
cd ~/yahboomcar_ws
colcon build

Then enter the following command to resource the environment variables.

xxxxxxxxxx
source ~/.bashrc

5、Start the car's underlying data processing program

Enter the following command in the Raspberry Pi terminal that starts robot1

xxxxxxxxxx
ros2 launch yahboomcar_multi yahboomcar_bringup_multi.launch.xml robot_name:=robot1

Enter the following command in the Raspberry Pi terminal that starts robot2

xxxxxxxxxx
ros2 launch yahboomcar_multi yahboomcar_bringup_multi.launch.xml robot_name:=robot2

yahboomcar_bringup_multi.launch.xml source code path,

xxxxxxxxxx
/root/yahboomcar_ws/src/yahboomcar_multi/launch/yahboomcar_bringup_multi.launch.xml

xxxxxxxxxx
<launch>
    <arg name="robot_name" default="robot1"/>
    <group>
        <push-ros-namespace namespace="$(var robot_name)"/>
        <!--imu_filter_node-->
        <node name="imu_filter" pkg="imu_filter_madgwick" exec="imu_filter_madgwick_node" output="screen">
            <param name="fixed_frame" value="$(var robot_name)/base_link"/>
            <param name="use_mag" value="false"/>
            <param name="publish_tf" value="false"/>
            <param name="world_frame" value="$(var robot_name)/enu"/>
            <param name="orientation_stddev" value="0.00"/>
            <remap from="imu/data_raw" to="imu"/>
            
        </node>
        <!--ekf_node-->
        <node name="ekf_filter_node" pkg="robot_localization" exec="ekf_node">
            <param name="odom_frame" value="$(var robot_name)/odom"/>
            <param name="base_link_frame" value="$(var robot_name)/base_footprint"/>
            <param name="world_frame" value="$(var robot_name)/odom"/>
            <param from="$(find-pkg-share yahboomcar_multi)/param/ekf_$(var robot_name).yaml"/>
            <remap from="odometry/filtered" to="odom"/>
            <remap from="/odom_raw" to="odom_raw"/>
        </node>
        <node pkg="tf2_ros" exec="static_transform_publisher" name="base_link_to_base_imu"
          args="-0.002999 -0.0030001 0.031701 0 0 0  $(var robot_name)/base_link $(var robot_name)/imu_frame " />
    
    <include file="$(find-pkg-share yahboomcar_description)/launch/description_multi_$(var robot_name).launch.py"/>
    
</launch>

A pair of tags are used here. The command space of all programs within this tag will be robot_name, which is the robot1 or robot2 we defined. Among them, there are also some parameter files or topic names that are automatically selected and loaded through this robot_name. You can view the content in the code for details.

6、Start the AMCL positioning program of the car

Enter the command in the Raspberry Pi terminal that starts robot1

xxxxxxxxxx
ros2 launch yahboomcar_multi robot1_amcl_launch.py

Enter the command in the Raspberry Pi terminal that starts robot2

xxxxxxxxxx
ros2 launch yahboomcar_multi robot2_amcl_launch.py

As shown in the figure above, "Please set the initial pose..." appears. You can use the corresponding [2D Pose] tool to set the initial poses for the two cars respectively. According to the position of the car in the actual environment, Click and drag with the mouse in rviz, and the car model moves to the position we set. As shown in the figure below, if the area scanned by the radar roughly coincides with the actual obstacle, it means that the pose is accurate.

Red represents robot1, blue represents robot2.

Note: If "Please set the initial pose..." cannot be printed on the terminal, it may be due to the data timestamp being out of sync. Press the reset button of the car and let the car reconnect to the agent to ensure that the data timestamp is correct. , and try again several times until "Please set the initial pose..." appears.

Source code location：/root/yahboomcar_ws/src/yahboomcar_multi/launch

robot1_amcl_launch.py

​x
import os
from ament_index_python.packages import get_package_share_directory
from launch import LaunchDescription
from launch.actions import DeclareLaunchArgument
from launch.actions import IncludeLaunchDescription
from launch.launch_description_sources import PythonLaunchDescriptionSource
from launch.substitutions import LaunchConfiguration
from launch_ros.actions import Node

def generate_launch_description():
    #package_path = get_package_share_directory('yahboomcar_multi')
    #nav2_bringup_dir = get_package_share_directory('nav2_bringup')
    lifecycle_nodes = ['map_server']
    param_file = os.path.join(get_package_share_directory('yahboomcar_multi'),'param','robot1_amcl_params.yaml')
    amcl_node = Node(
        name="robot1_amcl",
        package='nav2_amcl',
        executable='amcl',
        parameters=[os.path.join(get_package_share_directory('yahboomcar_multi'),'param','robot1_amcl_params.yaml')],
        remappings=[('/initialpose', '/robot1/initialpose')],
        output = "screen"
    )
    
    life_node = Node(
        name="robot1_amcl_lifecycle_manager",
        package='nav2_lifecycle_manager',
        executable='lifecycle_manager',
        output='screen',
        parameters=[{'use_sim_time': False},{'autostart': True},{'node_names': ['robot1_amcl']}]
        )
        
    base_link_to_laser_tf_node = Node(
        package='tf2_ros',
        executable='static_transform_publisher',
        name='base_link_to_base_laser',
        namespace = 'robot1',
        arguments=['-0.0046412', '0' , '0.094079','0','0','0','robot1/base_link','robot1/laser_frame']
    )
    
    return LaunchDescription([
        #lifecycle_nodes,
        #use_sim_time,\
        amcl_node,
        life_node,
        base_link_to_laser_tf_node
    ])

amcl_node：Start the amcl node program, which is used to estimate pose and achieve positioning.

life_node：amcl node lifecycle manager

base_link_to_laser_tf_node：Static transformation of chassis and radar data

7、Start the car navigation program

Enter the command in the Raspberry Pi terminal that starts robot1

xxxxxxxxxx
ros2 launch yahboomcar_multi robot1_navigation_dwb_launch.py

Enter the command in the Raspberry Pi terminal that starts robot2

xxxxxxxxxx
ros2 launch yahboomcar_multi robot2_navigation_dwb_launch.py

As shown in the picture above, if "Creating bond timer..." appears, it means that the program loading is complete. Then you can give the target points of the two cars through the corresponding [2D Goal Pose] on riviz. The cars combine their respective poses and poses. If there are surrounding obstacles, a path will be generated to autonomously navigate to their respective destinations.

The yellow route is the route planned by robot1, and the green line is the route planned by robot2.

8、Multi-vehicle navigation expansion

The tutorial takes two cars as an example. If you want to add other cars, you need to make the following modifications.

8.1、Add the URDF model of the car and add the urdf model loader

• Added car model

  You can refer to /root/yahboomcar_ws/src/yahboomcar_description/urdf/MicroROS_robot1.urdf. Change the name and robot1 that appears in the urdf file to another car name, such as robot3.

• Added urdf model loader

  You can refer to /root/yahboomcar_ws/src/yahboomcar_description/launch/description_multi_robot1.launch.py. Change the name and robot1 that appears in the launch file to another car name. The name needs to be consistent with the new urdf.

8.2、Added car ekf parameter table

You can refer to /root/yahboomcar_ws/src/yahboomcar_multi/param/ekf_robot1.yaml. Change the name and robot1 that appears in the file to another car name. The name needs to be consistent with the new urdf.

8.3、Added car amcl parameter table and launch file to start amcl

• Added car amcl parameter table

  You can refer to /root/yahboomcar_ws/src/yahboomcar_multi/param/robot1_amcl_params.yaml. Change the name and robot1 that appears in the file to the name of other cars. The name needs to be consistent with the new urdf.

• Add the launch file of amcl that is started

  You can refer to /root/yahboomcar_ws/src/yahboomcar_multi/launch/robot1_amcl_launch.py. Change the name and robot1 that appears in the file to the name of other cars. The name needs to be consistent with the new urdf.

8.4、Added car nav2 parameter table and launch file to start nav2

• Added car nav2 parameter table

  You can refer to /root/yahboomcar_ws/src/yahboomcar_nav/params/robot1_nav_params.yaml. Change the name and robot1 that appears in the file to the name of other cars. The name needs to be consistent with the new urdf.

• Added new launch file of nav2

  You can refer to /root/yahboomcar_ws/src/yahboomcar_multi/launch/robot1_navigation_dwb_launch.py. Change the name and robot1 that appears in the file to the name of other cars. The name needs to be consistent with the new urdf.

8.5、Added [2D Pose Estimate] and [2D Goal Pose] in the rviz toolbar

Modify the multi_nav.rviz file. The directory of this file is /root/yahboomcar_ws/src/yahboomcar_nav/rviz. Find the following section,

- Class: rviz_default_plugins/SetInitialPose
  Covariance x: 0.25
  Covariance y: 0.25
  Covariance yaw: 0.06853891909122467
  Topic:
    Depth: 5
    Durability Policy: Volatile
    History Policy: Keep Last
    Reliability Policy: Reliable
    Value: /robot1/initialpose
- Class: rviz_default_plugins/SetGoal
  Topic:
    Depth: 5
    Durability Policy: Volatile
    History Policy: Keep Last
    Reliability Policy: Reliable
    Value: /robot1/goal_pose

The above are the two tools of robot1. You can make a copy and put it behind. Change the robot1 that appears to the name of other cars. The name needs to be consistent with the new urdf.

After completing the above 5 steps, return to the yahboomcar_ws workspace, use colcon build to compile, and then run the test according to the tutorial. After running successfully, you can add the car model and radar data to display in rviz.