PX4 Autopilot Software
Go to file
Daniel Agar 755eb6a2e9
Update submodule mavlink v2.0 to latest Mon Jan 21 00:38:11 UTC 2019
- mavlink v2.0 in PX4/Firmware (ee517afb7c8b34e88daf656834a3315be72a4f40): 339abb5f4c
    - mavlink v2.0 current upstream: e302e1b735
    - Changes: 339abb5f4c...e302e1b735
2019-01-20 20:15:12 -05:00
.ci Jenkins more aggressively discard large builds 2019-01-19 12:37:05 -05:00
.github Probot attempt to fix configuration (#11243) 2019-01-19 14:13:58 -05:00
.vscode vscode add lldb SITL debug launch targets 2018-12-05 18:25:58 -05:00
Documentation Correct trailing whitespaces. 2018-08-18 15:15:41 -04:00
ROMFS ROMFS rcS execute (optional) rc.board_defaults after AUTOCNF set 2019-01-18 11:23:01 -05:00
Tools sitl_run.sh: fix for debugger & valgrind invocation: use eval 2019-01-14 11:08:48 +01:00
boards boards sync fmu-v2 sensors start with fmu-v3 2019-01-15 23:52:46 -08:00
cmake Use correct path when looking up df wrapper. 2018-12-11 09:21:15 -05:00
integrationtests/python_src/px4_it mission test temporarily increase landed timeout 60s -> 120s (#10596) 2018-09-28 10:28:07 -04:00
launch CI: add rostest to 'px4' and MAVROS in caktin and colcon builds 2018-12-13 02:09:31 +00:00
mavlink/include/mavlink Update submodule mavlink v2.0 to latest Mon Jan 21 00:38:11 UTC 2019 2019-01-20 20:15:12 -05:00
msg uorb_rtps_message_ids: for now, remove vehicle_global_position send 2019-01-07 12:46:36 +01:00
platforms lockstep_scheduler cmake: spaces -> tabs 2019-01-14 11:08:48 +01:00
posix-configs move dyn_hello to examples and restore testing 2018-11-26 14:40:14 -08:00
src MK BL CTRL: Fix startup routine to be compliant with signature. 2019-01-20 10:29:13 -05:00
test boards new split VENDOR_MODEL naming convention 2018-11-26 14:40:14 -08:00
test_data rc: add unit test for CRSF RC 2018-07-28 15:23:09 +02:00
validation module_schema: enforce serial config param names to end in _CONFIG or _CFG 2018-09-27 23:39:20 +02:00
.ackrc ack: add .ackrc to ignore the Documentation directory 2016-04-11 11:23:01 +02:00
.clang-tidy px4_daemon: fixes for clang-tidy 2018-08-08 21:09:39 +02:00
.github_changelog_generator Changelog generator default params 2017-12-30 11:27:57 +01:00
.gitignore vscode initial configuration (#10911) 2018-12-04 23:11:36 -05:00
.gitmodules platforms: removed lockstep_scheduler submodule 2018-12-22 10:32:18 +01: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 platforms: use define for lockstep scheduler 2018-12-22 10:32:18 +01:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2017-07-30 19:18:49 +02:00
CONTRIBUTING.md Update CONTRIBUTING.md 2018-02-19 12:23:56 +01:00
CTestConfig.cmake gather test results 2017-01-02 10:14:41 +01:00
Firmware.sublime-project boards new split VENDOR_MODEL naming convention 2018-11-26 14:40:14 -08:00
Jenkinsfile CI: update container tags to '2019-01-01' (#11128) 2019-01-04 16:34:02 -05:00
LICENSE Update LICENSE 2018-06-03 10:21:56 +02:00
Makefile Makefile: use px4_sitl_test board for `make tests` 2018-12-22 10:32:18 +01:00
PULL_REQUEST_TEMPLATE.md Create PULL_REQUEST_TEMPLATE.md 2018-07-08 23:19:24 +02:00
README.md README add FMUv5 pixhawk 4 and pixhawk 4 mini 2018-11-28 12:23:42 -05:00
appveyor.yml appveyor: fix mkdir on existing directory 2018-11-27 15:43:45 +01: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 PX4 package depends on mav_msgs 2015-07-13 14:52:39 -07:00

README.md

PX4 Drone Autopilot

Releases DOI

Build Status Coverity Scan

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.