zrzk
/
px4_autopilot
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
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.
27763 Commits
14 Branches
0 Tags
306 MiB
 
 
 
 
 
 
Tree: 3228e494bd
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '3228e494bd'
${ noResults }
TSC21 3228e494bd
radio_status: change 'fixed' field name to 'fix' so it does not clash with 'fixed' floating-point notation on the IDL generation 		6 years ago
.ci Improve the use of ubsan in SITL pipeline 6 years ago
.github Github templates add support question and documentation issue (#10613) 6 years ago
Documentation Correct trailing whitespaces. 7 years ago
ROMFS mc_pos_control_params: remove unused MPC_MANTHR_MAX params 6 years ago
Tools Clarify SDLOG_MODE bit for thermal calibration 6 years ago
cmake px4fmu-v2: disable camera_trigger 6 years ago
integrationtests/python_src/px4_it mission test temporarily increase landed timeout 60s -> 120s (#10596) 6 years ago
launch ROS multi-vehicle simulation: fixed udp port overlap issues 6 years ago
mavlink/include/mavlink Update submodule v2.0 to latest Wed Oct 3 18:37:52 UTC 2018 6 years ago
msg radio_status: change 'fixed' field name to 'fix' so it does not clash with 'fixed' floating-point notation on the IDL generation 6 years ago
platforms Edited aerofc-v1 file comments to not reference tap-v1. 6 years ago
posix-configs bebop 2 improved gains, disable rangefinder 6 years ago
src radio_status: change 'fixed' field name to 'fix' so it does not clash with 'fixed' floating-point notation on the IDL generation 6 years ago
test module_schema.yaml: move from test/ to validation/ 6 years ago
test_data rc: add unit test for CRSF RC 7 years ago
validation module_schema: enforce serial config param names to end in _CONFIG or _CFG 6 years ago
.ackrc ack: add .ackrc to ignore the Documentation directory 9 years ago
.clang-tidy px4_daemon: fixes for clang-tidy 7 years ago
.github_changelog_generator Changelog generator default params 7 years ago
.gitignore python scripts code coverage (#10157) 7 years ago
.gitmodules Point nuttx submodule to PX4-NuttX 7 years ago
.travis.yml travis-ci coverity properly run and submit scan 7 years ago
.ycm_extra_conf.py Removed PX4FMUv1 auto completions 8 years ago
CMakeLists.txt deactivate catkin build of dynamic libs 6 years ago
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 8 years ago
CONTRIBUTING.md Update CONTRIBUTING.md 7 years ago
CTestConfig.cmake gather test results 8 years ago
Firmware.sublime-project astyle scripting move to Tools/astyle 8 years ago
Jenkinsfile add Jenkins catkin build 6 years ago
LICENSE Update LICENSE 7 years ago
Makefile Jenkins: add module config validation to CI 6 years ago
PULL_REQUEST_TEMPLATE.md Create PULL_REQUEST_TEMPLATE.md 7 years ago
README.md README.md update Jenkins build status icon and url 6 years ago
appveyor.yml appveyor: switch to toolchain 0.4 6 years ago
eclipse.cproject eclipse project add paths for new params 7 years ago
eclipse.project uORB generation move to msg/ 7 years ago
package.xml PX4 package depends on mav_msgs 10 years ago

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.