FAQ

A ROS 2 framework for building autonomous aerial systems, from one drone to a swarm. Your mission talks to a standard set of interfaces, and each drone sits behind an aerial platform that hides the hardware. The overview shows how the pieces fit.

No. Aerostack2 ships with two simulators, so you can fly your first mission on a laptop. The Quickstart takes about ten minutes.

Yes. Aerostack2 is under the BSD 3-Clause license, which allows use in open and closed projects as long as you keep the copyright notice. Some components are research prototypes, so test them thoroughly before relying on them.

Cite the paper that introduces it. Citations has the reference and a BibTeX entry.

Aerostack2 runs on Ubuntu with the current ROS 2 long-term support releases. Installation lists them, along with what each install method supports.

Yes, on Apple silicon, through Pixi. You don't need a system-wide ROS 2 install. The multirotor simulator runs there too.

Not natively yet. It's on the roadmap. Until then, use the Docker images or a Linux machine.

Use binary packages to fly with Aerostack2 as it is. Build from source to change it, to write your own components or to get the newest features. The example projects follow the latest code, so with binary packages, check out the project version that matches your install.

Drones with a PX4 autopilot, Bitcraze Crazyflies, the Ryze Tello and several DJI Matrice models, among others. Aerial platforms lists every one.

There are two platforms. Pixhawk talks to PX4 directly over uXRCE-DDS and is the usual choice. MAVLink goes through MAVROS, for when MAVLink is what you already have, such as older PX4 firmware or a telemetry radio.

Write a platform for it. A platform is one node with a handful of methods, and the platform guide walks through one.

Start with the multirotor simulator. It starts in a second and runs anywhere. Move to Gazebo when a mission needs cameras, lidars or a 3D world.

Yes. Each drone runs its own stack in its own namespace, so a swarm is several stacks side by side. The architecture page explains how.

With the Python API, a behavior tree or the mission interpreter. Missions shows the same mission written all three ways.

Yes. Most components load plugins, and the Develop section has a guide for each kind.

Start a thread in GitHub Discussions. Search there first, since your question may already have an answer.

Open an issue. Opening an issue explains what to include so it gets fixed quickly.

Fix a bug, add a feature, write a platform or improve these docs. The Develop section covers setting up and opening a pull request. Regular contributors can join the core team, whether or not they're part of CVAR.