Julian Oes 35223a381e fix(drivers): keep file descriptors on the task that opened them (#29858)
* fix(heater): open and use the PX4IO fd only on the work queue thread

File descriptors on NuttX are per task group. Since the multi-instance
rework (#26325) the PX4IO heater fd was opened in the constructor, i.e.
in the shell task running `heater start`, but used in Run() on
wq:lp_default. There the fd number refers to whatever that task group has
open, so the heater ioctls silently failed (heater never driven on
PX4IO boards) or hit an unrelated file. On a Cube Orange+ this ended in a
hardfault in fat_ioctl() when the number matched an SD card file.

stop() also issued an ioctl from the shell, and the exit path closed the
fd before turning the heater off with it.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Julian Oes <julian@oes.ch>

* fix(cyphal): close the CAN fd on the work queue thread

The CAN socket/device is opened in Run() on wq:uavcan, but was only
closed from the destructor, which runs in the shell calling
`cyphal stop`. File descriptors are per task group on NuttX, so that
close did nothing and the SocketCAN socket stayed bound, keeping
received frames queued in the shared IOB pool. The NuttX CAN device was
never closed at all.

Close the interface in Run()'s exit branch and make close() idempotent.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Julian Oes <julian@oes.ch>

* fix(uavcannode): close the DroneCAN shell pipes on the work queue thread

The shell pipes are created from a service callback on wq:uavcan, but on
`uavcannode stop` they were closed by the destructor in the shell task.
File descriptors are per task group on NuttX, so the work queue ends
stayed open and the spawned shell task never got EOF.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Julian Oes <julian@oes.ch>

* fix(distance_sensor): close serial ports on the work queue thread

CM8JL65, uLanding, LeddarOne, Sony AS-DT1 and Lightware serial open
their UART in Run() on the work queue, but stop() closed it from the
shell calling `<driver> stop`. File descriptors are per task group on
NuttX, so the UART stayed open in the work queue group, leaking it on
every start/stop cycle. stop() also deleted the driver without waiting
for a Run() in progress.

stop() now asks Run() to close the port and waits for it. Error paths
reset the fd so a stale number is not reused, and ports opened in the
shell (LeddarOne init probe, Sony -p mode) are closed there.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Julian Oes <julian@oes.ch>

* fix(uwb_sr150): schedule only after init succeeded

On init failure the instance is deleted in the shell, whose destructor
closes the UART. If Run() had already opened it on the work queue, that
closed an unrelated fd number, as file descriptors are per task group
on NuttX.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Julian Oes <julian@oes.ch>

* fix(sagetech_mxs): schedule only after init succeeded

On init failure the instance is deleted in the shell, whose destructor
closes the serial port. If Run() had already opened it on the work
queue, that closed an unrelated fd number, as file descriptors are per
task group on NuttX.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Julian Oes <julian@oes.ch>

---------

Signed-off-by: Julian Oes <julian@oes.ch>
2026-11-19 12:48:08 +13:00
…

PX4 Autopilot

The autopilot stack the industry builds on.

Release DOI Discord

OpenSSF Best Practices LFX Health Score LFX Contributors LFX Active Contributors


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
Multicopter
Fixed Wing
Fixed Wing
VTOL
VTOL
Rover
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

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.

Dronecode Logo

Languages
C++ 49.7%
C 36%
Python 4.9%
CMake 4.4%
Linker Script 3.3%
Other 1.5%