> For the complete documentation index, see [llms.txt](https://gi-ata.gitbook.io/ros-arducopter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gi-ata.gitbook.io/ros-arducopter/user-manual.md).
# User Manual
Brief description about how to launch the main simulation nodes
Once all required dependencies and packages were installed the user is ready to test the dummy fly with the iris quad-rotor, which model is already loaded in the gazebo models. The demo flight is executed with the following lines in order:
1. Launch the gazebo simulation node
cd catkin_ws
source devel/setup.bash
roslaunch iq_sim runway.launch
The demo environment looks like:
Gazebo environment for iris quadrotor
2. Launch the arducopter communication protocol
{% code overflow="wrap" lineNumbers="true" %}
```bash
cd ~/ardupilot/ArduCopter/
sim_vehicle.py -v ArduCopter -f gazebo-iris --console
```
{% endcode %}
If the quad-rotor us successfully linked, you will see green messages as follows:
Successful communication
3. Execute the QGroundControl App
{% code overflow="wrap" lineNumbers="true" %}
```bash
cd ~/path/to/QGroundControl
./QGroundControl.AppImage
```
{% endcode %}
The command will open the QGroundControl interface to prepare and plan the navigation.
QGround Control app
## Testing the quad-rotor
Is it possible to test all quad-rotor components like motors, sensors, etc. To this end, in QGroundControl clic on the **top-left Q icon** and select **Vehicle Setup.**
Vehicle setup
Afterwards you will all testing options, for instance, we can test each motor by clicing the "Motors" option. The app allows testing each individual motor, and as in real life, the propellers will move in the gazebo simulation as well.
## Create a flight plan
By clicking in the **Plan** option in the top-left side we can edit the navigation route.
Planning mode
The first point we must set is the **take off,** were we set the attitude for all the trajectory. Afterwards we will be able to set the waypoints to trace the quad-rotor trajectory.
Waypoints creation
The final waypoint can be configured as a **landing** or r**eturn to the initial position** by clicking the downside arrow next to the Waypoint indicator in the right side.
Final action
Furthermore, we should return to the main window and arm the quad-rotor by clicking the **Ready to flight** option and pressing arm.
Arm the quadrotor
The arm confirmation should be done in the slide that appear in the bottom section. Now the quad-rotor is ready to flight, so we can select the **take off** option and confirming the slider.
Take off
The quad-rotor will follow that planned path and we can see it in QGroundControl in 2D and in Gazebo in 3D
{% embed url="" %}
##
***
## Fast execution via bash file
The above mentioned packages could be executed at once by using a bash file. The script could be downloaded below, and adjusted to your needs.
{% file src="/files/iD845g7IBoOCxpNFzbUL" %}
In this file we first should set the **workspace\_path** , **arducopter\_path** and **QGcontrol\_path** according to our configuration.
Bash file execution:
{% code overflow="wrap" lineNumbers="true" %}
```bash
cd /path/to/launch_simulation/
chmod +x launch_simulation.sh
./launch_simulation.sh
```
{% endcode %}
***
## Visualize Flight Logs
Ardupilot as an open source tool provides a log viewer to visualize all logging data captured by QGroundControl. The log viewer can be found in the next link.
{% embed url="" %}
Ardupilot log viewer
{% endembed %}
The log data can be downloaded from QGroundControl by clicking in the top left Q icon and selecting **Analyze Tools.**
Downloading log file
Once we have the flight log we are able to load and visualize all parameters in ardupilot.org, like the 3D trajectory
