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.
 
 
 
 
 
 
Peter Barker 5175d23cc1 AP_NavEKF2: move logging in from AP_Logger 6 years ago
.azure azure: fix builds 6 years ago
.github github: add support file 6 years ago
APMrover2 Rover: ServoRelayEvents uses Relay singleton 6 years ago
AntennaTracker Tracker: add sanity check when fetching GCS_MAVLink instance 6 years ago
ArduCopter Copter: ServoRelayEvents uses Relay singleton 6 years ago
ArduPlane Plane: Added Quadplane option for QRTL failsafe action 6 years ago
ArduSub Sub: ServoRelayEvents uses Relay singleton 6 years ago
Tools Tools: added an example gpio.sh for the disco 6 years ago
benchmarks
docs
libraries AP_NavEKF2: move logging in from AP_Logger 6 years ago
mk
modules mavlink: added MAV_CMD_BATTERY_RESET 6 years ago
tests
.dir-locals.el
.editorconfig
.flake8
.gitattributes
.gitignore Tools: add support for GCOV code coverage tool and HTML reporting with LCOV. 6 years ago
.gitmodules
.pydevproject
.travis.yml Travis: Run CubeOrange bootloader to run a >2 MB bootloader 6 years ago
BUILD.md
COPYING.txt
Dockerfile Tools: Update Docker to new pre-reqs folder 6 years ago
Doxyfile.in
Makefile
README.md README: add Azure Pipelines 6 years ago
Vagrantfile Vagrant: quieten vagrant/virtualbox window 6 years ago
appveyor.yml CI: fixed appveyor python install 6 years ago
reformat.sh
uncrustify_cpp.cfg
uncrustify_headers.cfg
waf
wscript waf: coverage: run the 'examples', 'unit_test' and heli tests 6 years ago

README.md

ArduPilot Project

Gitter

Build Travis Build SemaphoreCI Build Status

Coverity Scan Build Status

Autotest Status

The ArduPilot project is made up of:

User Support & Discussion Forums

Developer Information

Top Contributors

How To Get Involved

License

The ArduPilot project is licensed under the GNU General Public License, version 3.

Maintainers

Ardupilot is comprised of several parts, vehicles and boards. The list below contains the people that regularly contribute to the project and are responsible for reviewing patches on their specific area. See also the list of developers with merge rights.