You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
mcsauder 3b72f3b641 Create publish_status() method in the heater driver, add a status field to indicate if the temperature setpoint has been met within 2.5C, breakout update_params() method from the Heater::Run() method and simplify logic. 4 years ago
.ci boards: move testing to dedicated test variants 4 years ago
.devcontainer UAVCAN v1 GPS demo with MAVCAN autoconfigure 4 years ago
.github boards: move testing to dedicated test variants 4 years ago
.vscode boards: move testing to dedicated test variants 4 years ago
Documentation DriverFramework purge 5 years ago
ROMFS VTOL mixer: Correct alt rate channels 4 years ago
Tools Update submodule sitl_gazebo to latest Mon Apr 12 12:45:32 UTC 2021 4 years ago
boards Create publish_status() method in the heater driver, add a status field to indicate if the temperature setpoint has been met within 2.5C, breakout update_params() method from the Heater::Run() method and simplify logic. 4 years ago
cmake cmake: embed param metadata if not CONSTRAINED_FLASH and not "test" LABEL 4 years ago
integrationtests/python_src/px4_it fw_pos_control_l1: add takeoff minimum pitch parameter 4 years ago
launch Fix roslaunch multivehicle regression caused by #16497 4 years ago
mavlink/include/mavlink Update submodule mavlink v2.0 to latest Tue Apr 6 00:39:07 UTC 2021 4 years ago
msg Create publish_status() method in the heater driver, add a status field to indicate if the temperature setpoint has been met within 2.5C, breakout update_params() method from the Heater::Run() method and simplify logic. 4 years ago
platforms NuttX with SDMMC Backport 4 years ago
posix-configs posix-configs: rpi multi-EKF defaults 4 years ago
src Create publish_status() method in the heater driver, add a status field to indicate if the temperature setpoint has been met within 2.5C, breakout update_params() method from the Heater::Run() method and simplify logic. 4 years ago
test mavsdk_tests: losen time limit for VTOL mission 4 years ago
test_data ghst: keep the previous values for channels that are not updated 4 years ago
validation config: cleanup ethernet configuration 4 years ago
.ackrc ack: add .ackrc to ignore the Documentation directory 9 years ago
.clang-tidy clang-tidy: enable readability-braces-around-statements 5 years ago
.gitattributes gitattributes eol=lf for nearly all file types 5 years ago
.github_changelog_generator Changelog generator default params 7 years ago
.gitignore parameters: merge generated files ito single static constexpr header 4 years ago
.gitmodules Update .gitmodules 4 years ago
.travis.yml travis: change coverity to run on master 5 years ago
.ycm_extra_conf.py update C++ standard (c++11 -> c++14) 5 years ago
CMakeLists.txt git: ignore git tags starting with 'ext/' when getting the version tag 4 years ago
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 8 years ago
CONTRIBUTING.md Update CONTRIBUTING.md 5 years ago
CTestConfig.cmake gather test results 8 years ago
Firmware.sublime-project boards new split VENDOR_MODEL naming convention 6 years ago
Jenkinsfile Jenkins: fetch all tags before generating Airframe & Parameter documentation (master only) 4 years ago
LICENSE Update current year in LICENSE 4 years ago
Makefile Makefile: uorb_graphs exclude src/lib from graph_full 4 years ago
PULL_REQUEST_TEMPLATE.md PULL_REQUEST_TEMPLATE: change order of titles (#13174) 5 years ago
README.md README: remove redundant autogyro, add High altitude balloons 4 years ago
appveyor.yml appveyor: switch to Cygwin toolchain v0.9 5 years ago
eclipse.cproject boards new split VENDOR_MODEL naming convention 6 years ago
eclipse.project boards new split VENDOR_MODEL naming convention 6 years ago
package.xml Remove eigen leftovers 5 years ago

README.md

PX4 Drone Autopilot

Releases DOI

Nuttx Targets SITL Tests

Slack

This repository holds the PX4 flight control solution for drones, with the main applications located in the src/modules directory. It also contains the PX4 Drone Middleware Platform, which provides drivers and middleware to run drones.

PX4 is highly portable, OS-independent and supports Linux, NuttX and QuRT out of the box.

Building a PX4 based drone, rover, boat or robot

The PX4 User Guide explains how to assemble supported vehicles and fly drones with PX4. See the forum and chat if you need help!

Changing code and contributing

This Developer Guide is for software developers who want to modify the flight stack and middleware (e.g. to add new flight modes), hardware integrators who want to support new flight controller boards and peripherals, and anyone who wants to get PX4 working on a new (unsupported) airframe/vehicle.

Developers should read the Guide for Contributions. See the forum and chat if you need help!

Weekly Dev Call

The PX4 Dev Team syncs up on a weekly dev call.

Note The dev call is open to all interested developers (not just the core dev team). This is a great opportunity to meet the team and contribute to the ongoing development of the platform. It includes a QA session for newcomers. All regular calls are listed in the Dronecode calendar.

Maintenance Team

See also maintainers list (px4.io) and the contributors list (Github).

Supported Hardware

This repository contains code supporting Pixhawk standard boards (best supported, best tested, recommended choice) and proprietary boards.

Pixhawk Standard Boards

Manufacturer and Community supported

Additional information about supported hardware can be found in PX4 user Guide > Autopilot Hardware.

Project Roadmap

A high level project roadmap is available here.