PX4 Autopilot Software
Go to file
Julian Oes 95ab984f4c commander: fix toggling datalink lost and regained
When using QGC and/or the Dronecode SDK it was possible to get in a
state where the two mavlink instances were both publishing their last
heartbeat_time and cause commander to consistently toggle between
data link lost and regained. With this fix, we only ever look at the
very last heartbeat time and therefore seem to avoid this issue.
2019-04-05 09:25:40 -04:00
.ci Obstacle Avoidance testing in CI (#10780) 2019-03-15 00:37:23 -04:00
.github Probot attempt to fix configuration (#11243) 2019-01-19 14:13:58 -05:00
.vscode vscode: move vscode specific .gitignore entries to the folder 2019-04-03 14:52:46 -04:00
Documentation Correct trailing whitespaces. 2018-08-18 15:15:41 -04:00
ROMFS ROMFS: don't check for UAVCAN_ENABLE param in SITL 2019-04-05 08:18:17 +02:00
Tools Fix @property and super function does not work properly if the 'NewStyle' class type is not used. 2019-04-03 22:53:10 -04:00
boards fmu-v5: Move stage 0 dcache disable to later in boot (#11791) 2019-04-04 11:07:28 -04:00
cmake cmake enable -Wcast-align and disable per module 2019-03-16 11:47:15 -04:00
integrationtests/python_src/px4_it Obstacle Avoidance testing in CI (#10780) 2019-03-15 00:37:23 -04:00
launch add mavlink_tcp_port for multiple uav simultation 2019-02-19 08:12:12 +01:00
mavlink/include/mavlink Update submodule mavlink v2.0 to latest Wed Apr 3 12:38:14 UTC 2019 2019-04-03 17:08:46 -04:00
msg added aux6 RC channel 2019-04-03 08:20:47 -04:00
platforms NuttX delete accidental tone_alarm copy 2019-04-03 23:57:51 +02:00
posix-configs position_estimator_inav: move to examples (start deprecation) 2019-01-27 22:15:39 +01:00
src commander: fix toggling datalink lost and regained 2019-04-05 09:25:40 -04:00
test Obstacle Avoidance testing in CI (#10780) 2019-03-15 00:37:23 -04: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
.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: 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 NuttX cmake support optional compressed defconfigs 2019-01-30 10:54:53 -05: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 Jenkins re-enable Catkin and Colcon builds 2019-03-09 15:38:15 -05:00
LICENSE license: account for 2019 2019-01-31 17:43:35 +01:00
Makefile Obstacle Avoidance testing in CI (#10780) 2019-03-15 00:37:23 -04:00
PULL_REQUEST_TEMPLATE.md Create PULL_REQUEST_TEMPLATE.md 2018-07-08 23:19:24 +02:00
README.md deprecate gumstix aerocore - no longer supported by mfg 2019-02-12 20:53:45 -05:00
appveyor.yml appveyor: only build px4_sitl_tests (avoid building SITL twice) 2019-02-05 14:34:01 -05: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.