* feat(commander): when disarmed, do not report ESC offline on battery blocking preflight checks * fix(commander): keep the ESC checks with the supply check circuit breaker set With CBRK_SUPPLY_CHK set the battery check returns without reporting a missing required battery, so skipping the ESC checks let a vehicle arm with that battery missing and its ESCs unpowered. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Matheo-13 <matheo.taillandier@gmail.com> * fix(commander): clear the ESC failure state while a required battery is missing The skip only cleared the motor failure mask, leaving fd_motor_failure, fd_esc_arming_failure and the ESC arming hysteresis at their last values: after a battery dropped in flight and the vehicle disarmed, failsafe_flags and failure_detector_status disagreed until the battery reconnected. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Matheo-13 <matheo.taillandier@gmail.com> * feat(commander): give the ESCs time to boot once a required battery connects Once the battery reconnected the checks resumed against ESC timestamps from before it was unplugged, so "ESC N offline" still showed while the ESCs booted. Reuse the boot grace already given to ESC telemetry at startup. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Matheo-13 <matheo.taillandier@gmail.com> * perf(commander): only read the batteries in the ESC checks when disarmed The battery skip only applies on ground, so the armed path no longer copies every battery instance each cycle. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Matheo-13 <matheo.taillandier@gmail.com> * test(commander): cover the ESC checks with a required battery missing Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Matheo-13 <matheo.taillandier@gmail.com> * fix(commander): block arming while the ESCs boot after a required battery connects * test(commander): keep the failsafe flags across ESC check runs Commander keeps the failsafe flags across check cycles, so zeroing them before every run hid any flag the ESC checks forget to clear. Cover the skip while a required battery is missing clearing a motor failure that was latched in flight. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Matheo-13 <matheo.taillandier@gmail.com> * fix(commander): clear the motor stuck flag while a required battery is missing The skip for a missing required battery returned before the motor stuck flag was cleared, so a stuck motor flagged at spool-up stayed set on the ground, unlike the other failure flags the skip clears. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Matheo-13 <matheo.taillandier@gmail.com> --------- Signed-off-by: Matheo-13 <matheo.taillandier@gmail.com>
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.