* feat(simulator_sih): add orient command to pose the vehicle for calibration Accel and mag calibration need the vehicle held still on each side and rotated, which SIH could not do, so neither could be tested in simulation. `simulator_sih orient` sets the attitude kinematically, keeping the IMU and the simulated mag consistent with it, and `orient all` runs every side in turn so a calibration started from a GCS completes on its own. Assisted-by: Claude:claude-opus-5-5 * fix(commander): hand a calibration cancel to the running calibration A cancel got TEMPORARILY_REJECTED from Commander and ACCEPTED from the calibration, in either order. The calibration polled for it with a fresh vehicle_command subscription that only saw the newest command, filtered it by a per-side start time, and did not poll while waiting for the vehicle to be still or while measuring a side. Baro and level calibration never polled. A cancel could be lost or take until the vehicle was held still. Commander now hands the cancel to the running calibration, which acks it once when it stops, or rejects it if it ends without stopping. Every calibration loop checks for it, and accel calibration no longer reports a failure after a cancel. Fixes #29424 Assisted-by: Claude:claude-opus-5-5 * test(mavsdk_tests): run accel and mag calibration and cancels on SIH Covers a full accel and mag calibration, and a cancel in each place it used to be missed or delayed, checking it gets exactly one ack. Assisted-by: Claude:claude-opus-5-5 * perf(simulator_sih): build the orient command for SITL only Commander denies sensor calibration when SIH runs on flight controller hardware, so orient was about 1.8 KB of unusable code on every NuttX board that builds SIH. Assisted-by: Claude:claude-opus-5-5 * fix(commander): open calibration cancels before the worker thread starts Commander handles one command per loop and the worker thread runs at low priority, so a cancel queued right behind the start could be rejected before the worker opened it, and the calibration kept running. Assisted-by: Claude:claude-opus-5-5 * fix(commander): stop reporting a cancelled gyro calibration as failed A cancel broke out of the retry loop into the failure report, as accel calibration did before. Assisted-by: Claude:claude-opus-5-5 * test(mavsdk_tests): cover gyro cancel and remove two calibration races A retried start is rejected once the calibration runs, and that late ack could be counted against the cancel, so the start is sent once. The baro cancel landed 1 s into a 3 s calibration, about 200 ms of host time at speed factor 10; it is now sent right after the start. Assisted-by: Claude:claude-opus-5-5 * style(mavsdk_tests): wrap the calibration start assert for flake8 The 104-character line failed the Python CI checks. Assisted-by: Claude:claude-opus-5-5 * fix(commander): require param7 zero for a calibration cancel An ESC calibration (param7 = 1) or baro temperature calibration (param7 = 3) sent while a calibration ran matched the cancel test. It stopped the running calibration and was acked ACCEPTED, though the requested calibration never started. `commander calibrate esc` did the same. Assisted-by: Claude:claude-fable-5-2
The autopilot stack the industry builds on.
About
PX4 is an open-source autopilot stack for drones and unmanned vehicles. It supports multirotors, fixed-wing, VTOL, rovers, and many more experimental platforms from racing quads to industrial survey aircraft. It runs on NuttX, Linux, and macOS. Licensed under BSD 3-Clause.
Why PX4
Modular architecture. PX4 is built around uORB, a DDS-compatible publish/subscribe middleware. Modules are fully parallelized and thread safe. You can build custom configurations and trim what you don't need.
Wide hardware support. PX4 runs on a wide range of autopilot boards and supports an extensive set of sensors, telemetry radios, and actuators through the Pixhawk ecosystem.
Developer friendly. First-class support for MAVLink and DDS / ROS 2 integration. Comprehensive SITL simulation, hardware-in-the-loop testing, and log analysis tools. An active developer community on Discord and the weekly dev call.
Vendor neutral governance. PX4 is hosted under the Dronecode Foundation, part of the Linux Foundation. Business-friendly BSD-3 license. No single vendor controls the roadmap.
Supported Vehicles
|
Multicopter |
Fixed Wing |
VTOL |
Rover |
…and many more: helicopters, autogyros, airships, submarines, boats, and other experimental platforms. These frames have basic support but are not part of the regular flight-test program. See the full airframe reference.
Try PX4
Run PX4 in simulation with a single command. No build tools, no dependencies beyond Docker:
docker run --rm -it -p 14550:14550/udp px4io/px4-sitl:latest
Open QGroundControl and fly. See PX4 Simulation Quickstart for more options.
Build from Source
git clone https://github.com/PX4/PX4-Autopilot.git --recursive
cd PX4-Autopilot
make px4_sitl
Note
See the Development Guide for toolchain setup and build options.
Documentation & Resources
| Resource | Description |
|---|---|
| User Guide | Build, configure, and fly with PX4 |
| Developer Guide | Modify the flight stack, add peripherals, port to new hardware |
| Airframe Reference | Full list of supported frames |
| Autopilot Hardware | Compatible flight controllers |
| Release Notes | What's new in each release |
| Contribution Guide | How to contribute to PX4 |
Community
- Weekly Dev Call — open to all developers (Dronecode calendar)
- Discord — Join the Dronecode server
- Discussion Forum — PX4 Discuss
- Maintainers — see
MAINTAINERS.md - Contributor Stats — LFX Insights
Contributing
We welcome contributions of all kinds — bug reports, documentation, new features, and code reviews. Please read the Contribution Guide to get started.
Citation
If you use PX4 in academic work, please cite it. BibTeX:
@software{px4_autopilot,
author = {Meier, Lorenz and {The PX4 Contributors}},
title = {{PX4 Autopilot}},
publisher = {Zenodo},
doi = {10.5281/zenodo.595432},
url = {https://px4.io}
}
The DOI above is a Zenodo concept DOI that always resolves to the latest release. For a version-pinned citation, see the Zenodo record or our CITATION.cff.
Governance
The PX4 Autopilot project is hosted by the Dronecode Foundation, a Linux Foundation Collaborative Project. Dronecode holds all PX4 trademarks and serves as the project's legal guardian, ensuring vendor-neutral stewardship — no single company owns the name or controls the roadmap. The source code is licensed under the BSD 3-Clause license, so you are free to use, modify, and distribute it in your own projects.