e35171c3f9
* fix(logger): make off stop active file logging Handle logger on and off as explicit requests so logger off closes an active file log without disabling future automatic activations. Continuous logging modes fall back to arm-to-disarm sessions until reboot after their active log is stopped. Assisted-by: Codex:gpt-5 Signed-off-by: jc-works <jc-works@users.noreply.github.com> * fix(logger): keep the configured log mode on manual stop Falling back to LogMode::while_armed by overwriting _log_mode destroyed the configured mode for the rest of the boot, and nothing reported it: neither logger status nor LoggerStatus carries the mode. Only boot_until_shutdown needs the fallback at all, because its early return would otherwise keep logging disabled once the boot log is stopped. Express that with a dedicated flag so _log_mode stays the configured value, and say so on the console when it happens. arm_until_shutdown needs no fallback. After the forced stop _prev_file_log_start_state is false, so full_log_continues is false and the desired state falls back to plain arming. The next arming starts a log and sets the flag again, so the following disarm keeps logging to shutdown as configured instead of ending the log early. Assisted-by: Claude:claude-opus-5 Signed-off-by: Julian Oes <julian@oes.ch> * fix(logger): restore SDLOG_MODE 2 logging behaviour after rearming After logger off stops a boot-to-shutdown log, suspend automatic logging only until the next arming. Restore the configured lifecycle when the new log starts so it continues across subsequent disarms until shutdown. Update the logger message and documentation accordingly. Assisted-by: Codex:gpt-5 Signed-off-by: jc-works <jc-works@users.noreply.github.com> * fix(logger): make repeated off requests idempotent Regression testing found that repeating logger off after the active log had closed cleared the manual stop latch. When the arming or AUX logging condition remained active, automatic logging started a new log. Preserve the manual stop latch across repeated off requests so logging remains stopped until the automatic logging condition deactivates. The latch is also cleared explicitly by logger on. Assisted-by: Codex:gpt-5 Signed-off-by: jc-works <jc-works@users.noreply.github.com> --------- Signed-off-by: jc-works <jc-works@users.noreply.github.com> Signed-off-by: Julian Oes <julian@oes.ch> Co-authored-by: jc-works <jc-works@users.noreply.github.com> Co-authored-by: Julian Oes <julian@oes.ch>
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.
