* feat(simulator_sih): add a GeoTIFF terrain elevation model for SITL SIH only simulates flat ground. This adds the loader for a terrain elevation model (DEM) in a GeoTIFF file, the base for non-flat terrain in SITL. The DEM is read with libtiff and libgeotiff. A DEM in a projected CRS is resampled once at load time with PROJ onto a WGS84 lat/lon grid, so a lookup in the simulation loop is a plain bilinear interpolation. It is built only for px4_sitl and only when the three libraries are found, so hardware builds and SITL without them are unchanged. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Beniamino Pozzan <beniamino.pozzan@auterion.com> * feat(simulator_sih): use the terrain DEM for ground contact and the rangefinder With PX4_SIH_TERRAIN set to a GeoTIFF DEM, SIH in SITL places the vehicle on the terrain at start, lands it on the terrain, ray-casts the downward distance sensor against it, and publishes it as the groundtruth terrain_alt. Outside the DEM the ground stays flat at SIH_LOC_H0. Terrain is only used for multicopters, VTOLs and fixed-wing; other vehicle types keep flat ground. The DEM is loaded in task_spawn() so a bad file fails the start command, and because the SIH task stack is too small for libtiff and PROJ. The groundtruth terrain_alt now holds the WGS84 terrain altitude, as the message documents, instead of the height above the origin. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Beniamino Pozzan <beniamino.pozzan@auterion.com> * build(setup): install the SIH terrain dependencies with the simulation tools Install libtiff, libgeotiff and PROJ so SITL builds SIH with terrain elevation (DEM) support. They are optional: without them SIH builds as before. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Beniamino Pozzan <beniamino.pozzan@auterion.com> * docs(sim_sih): document terrain elevation from a GeoTIFF DEM Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Beniamino Pozzan <beniamino.pozzan@auterion.com> * docs(sim_sih): fix and clarify the terrain elevation section Address review findings on the new terrain section: list the sample types the loader actually reads, note that the prebuilt px4 package and px4io/px4-sitl container are built without terrain support, and say when SIH_LOC_H0 still sets the start altitude. Also add a version badge, link GeoTIFF, EPSG and GDAL, mention the dist_bottom groundtruth field, and correct the GLO-30 coverage. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Hamish Willee <hamishwillee@gmail.com> * fix: cast to double for MAC builds Signed-off-by: Beniamino Pozzan <beniamino.pozzan@auterion.com> * chore: implement TerrainBase interface Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Beniamino Pozzan <beniamino.pozzan@auterion.com> * chore: improve isolation of terrain logic from sih core Signed-off-by: Beniamino Pozzan <beniamino.pozzan@auterion.com> * refactor(simulator_sih): move DEM handling into the terrain classes SIH should only use the terrain, not manage it. TerrainFlat becomes the base class, since flat ground is what every terrain model builds on, and TerrainDem falls back to it until a DEM is loaded. Terrain.hpp picks the model at compile time, so SIH holds the terrain by value with no #ifdef, new/delete or pointer handover, and NuttX builds only get the flat model. Tracking whether the vehicle is inside the DEM, and the matching warnings and status, move from SIH into TerrainDem. The DEM is still loaded in task_spawn() because the SIH task stack is too small for libtiff and PROJ, so the terrain is a static member that the instance uses directly instead of moving it. A terrain file with an unsupported vehicle type now fails the start like a bad file instead of silently using flat ground. --------- Signed-off-by: Beniamino Pozzan <beniamino.pozzan@auterion.com> Signed-off-by: Hamish Willee <hamishwillee@gmail.com> Co-authored-by: Hamish Willee <hamishwillee@gmail.com> Co-authored-by: Matthias Grob <maetugr@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.