aerostack2 / project_gazebo

BSD 3-Clause "New" or "Revised" License
0 stars 7 forks source link

Project Gazebo

Please refer to https://aerostack2.github.io/_02_examples/gazebo/project_gazebo/index.html for more information.

Installation

To install this project, clone the repository:

git clone https://github.com/aerostack2/project_gazebo

To start using this project, please go to the root folder of the project.

Execution

1. Launch aerostack2 nodes for each drone

To launch aerostack2 nodes for each drone, execute once the following command:

./launch_as2.bash

The flags for the components launcher are:

2. Launch aerostack2 nodes for the ground station

To launch aerostack2 nodes for the ground station, execute once the following command:

./launch_ground_station.bash

The flags for the components launcher are:

3. Launch a mission

There are several missions that can be executed:

4. End the execution

If you are using tmux, you can end the execution with the following command:

./stop.bash

You can force the end of all tmux sessions with the command:

tmux kill-server

If you are using gnome-terminal, you can end the execution by closing the terminal.

Developers guide

All projects in aerostack2 are structured in the same way. The project is divided into the following directories:

Both python and bash scripts have a help message that can be displayed by running the script with the -h option. For example, ./launch_as2.bash -h will display the help message for the launch_as2.bash script.

Note: For knowing all parameters for each launch, you can execute the following command:

ros2 launch my_package my_launch.py -s

Also, you can see them in the default config file of the package, in the config folder. If you want to modify the default parameters, you can add the parameter to the config file.