PX4 Autopilot Software
Go to file
bresch 2307c7c390 Geofence - Rename _warning_action_on to _geofence_warning_action_on
since it is only set by the geofence logic. Simplify conditions in IF
statements.
2019-06-04 08:35:56 +02:00
.ci Jenkins SITL tests temporarily disable tiltrotor 2019-05-27 15:23:08 +02:00
.github Probot attempt to fix configuration (#11243) 2019-01-19 14:13:58 -05:00
.vscode vscode add linker script extension to recommended 2019-05-25 14:21:45 -04:00
Documentation Correct trailing whitespaces. 2018-08-18 15:15:41 -04:00
ROMFS simulator move to PX4Accelerometer, PX4Gyroscope, PX4Magnetometer, PX4Barometer helpers (#12081) 2019-05-30 21:07:26 -04:00
Tools cmake and Tools/setup.sh default to python3 2019-05-29 20:48:22 -04:00
boards fxas21002c move to PX4Gyroscope and cleanup 2019-05-31 18:20:32 -04:00
cmake Testing: Clean up unit_test target because test_results does all tests now 2019-05-09 09:42:46 +02:00
integrationtests/python_src/px4_it mc_att_ctrl: added yawrate control from offboard. 2019-06-04 08:26:09 +02:00
launch launch: count multi UAVs from 0 2019-05-13 10:33:17 +01:00
mavlink/include/mavlink Update submodule mavlink v2.0 to latest Thu May 30 13:05:26 UTC 2019 (#12127) 2019-05-30 21:01:47 -04:00
msg mc_att_ctrl: added yawrate control from offboard. 2019-06-04 08:26:09 +02:00
platforms posix: restore original SEGV signal handler upon first entry of our handler 2019-05-29 08:30:52 +02:00
posix-configs simulator move to PX4Accelerometer, PX4Gyroscope, PX4Magnetometer, PX4Barometer helpers (#12081) 2019-05-30 21:07:26 -04:00
src Geofence - Rename _warning_action_on to _geofence_warning_action_on 2019-06-04 08:35:56 +02:00
test rostest_avoiance_run: bump to avoidance stable release 0.2.0 2019-04-10 16:36:18 -04:00
test_data
validation module_schema: enforce serial config param names to end in _CONFIG or _CFG 2018-09-27 23:39:20 +02:00
.ackrc
.clang-tidy px4_daemon: fixes for clang-tidy 2018-08-08 21:09:39 +02:00
.github_changelog_generator
.gitignore vscode: move vscode specific .gitignore entries to the folder 2019-04-03 14:52:46 -04:00
.gitmodules update all submodules to PX4 forks (#11407) 2019-02-10 15:48:59 -05:00
.travis.yml travis-ci (coverity scan) update to xenial 2018-12-26 11:04:36 -05:00
.ycm_extra_conf.py boards new split VENDOR_MODEL naming convention 2018-11-26 14:40:14 -08:00
CMakeLists.txt Testing: correct license headers 2019-05-09 09:42:46 +02:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md CONTRIBUTING:Fix up code.html link to goto master 2019-03-03 22:23:59 -05:00
CTestConfig.cmake
Firmware.sublime-project boards new split VENDOR_MODEL naming convention 2018-11-26 14:40:14 -08:00
Jenkinsfile CI: move no-ninja builds to Jenkinsfile 2019-04-11 10:07:00 +02:00
LICENSE license: account for 2019 2019-01-31 17:43:35 +01:00
Makefile Testing: Clean up unit_test target because test_results does all tests now 2019-05-09 09:42:46 +02:00
PULL_REQUEST_TEMPLATE.md pull_request_template: order and phrasing 2019-05-16 09:43:34 +02:00
README.md Update README.md 2019-05-25 20:08:36 +02:00
appveyor.yml appveyor: cleanup unnecessary leftovers 2019-04-07 18:56:51 +02:00
eclipse.cproject boards new split VENDOR_MODEL naming convention 2018-11-26 14:40:14 -08:00
eclipse.project boards new split VENDOR_MODEL naming convention 2018-11-26 14:40:14 -08:00
package.xml

README.md

PX4 Drone Autopilot

Releases DOI

Build Status

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 Users

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

PX4 Developers

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 About Us (px4.io) and the contributors list (Github).

Supported Hardware

This repository contains code supporting these boards:

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

Project Roadmap

A high level project roadmap is available here.