224ea744e3
A number of the config steps make the assumption they are running from the sensors default power on state. If you do a soft reset of the vehicle without killing power to the sensor this means the second time you configure the sensor you will start from a state which didn't match the base assumptions and can lead to the sensor preforming signficantly differently then it was intended to. This issues a soft reset, and waits for it to reboot before proceeding with configuration. If it's a watchdog reset we don't want to spend long enough to have ensured the sensor reset, so we say the sensor setup completely failed and don't use it, as not using it will be less erroneous then using a misconfigured sensor. |
||
|---|---|---|
| .azure | ||
| .github | ||
| APMrover2 | ||
| AntennaTracker | ||
| ArduCopter | ||
| ArduPlane | ||
| ArduSub | ||
| Tools | ||
| benchmarks | ||
| docs | ||
| libraries | ||
| mk | ||
| modules | ||
| tests | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .flake8 | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .pydevproject | ||
| .travis.yml | ||
| .valgrind-suppressions | ||
| .valgrindrc | ||
| BUILD.md | ||
| COPYING.txt | ||
| Dockerfile | ||
| Doxyfile.in | ||
| Makefile | ||
| README.md | ||
| Vagrantfile | ||
| appveyor.yml | ||
| reformat.sh | ||
| uncrustify_cpp.cfg | ||
| uncrustify_headers.cfg | ||
| waf | ||
| wscript | ||
README.md
ArduPilot Project
The ArduPilot project is made up of:
User Support & Discussion Forums
-
Support Forum: https://discuss.ardupilot.org/
-
Community Site: https://ardupilot.org
Developer Information
-
Github repository: https://github.com/ArduPilot/ardupilot
-
Main developer wiki: https://dev.ardupilot.org
-
Developer discussion: https://discuss.ardupilot.org
-
Developer chat: https://gitter.im/ArduPilot/ardupilot
Top Contributors
- Flight code contributors
- Wiki contributors
- Most active support forum users
- Partners who contribute financially
How To Get Involved
-
The ArduPilot project is open source and we encourage participation and code contributions: guidelines for contributors to the ardupilot codebase
-
We have an active group of Beta Testers especially for ArduCopter to help us find bugs: release procedures
-
Desired Enhancements and Bugs can be posted to the issues list.
-
Help other users with log analysis in the support forums
-
Improve the wiki and chat with other wiki editors on Gitter
-
Contact the developers on one of the communication channels
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.
- Andrew Tridgell:
- Vehicle: Plane, AntennaTracker
- Board: APM1, APM2, Pixhawk, Pixhawk2, PixRacer
- Francisco Ferreira:
- Bug Master
- Grant Morphett:
- Vehicle: Rover
- Jacob Walser:
- Vehicle: Sub
- Lucas De Marchi:
- Subsystem: Linux
- Michael du Breuil:
- Subsystem: Batteries
- Subsystem: GPS
- Subsystem: Scripting
- Peter Barker:
- Subsystem: DataFlash, Tools
- Randy Mackay:
- Vehicle: Copter, Rover, AntennaTracker
- Tom Pittenger:
- Vehicle: Plane
- Bill Geyer:
- Vehicle: TradHeli
- Chris Olson:
- Vehicle: TradHeli
- Emile Castelnuovo:
- Board: VRBrain
- Eugene Shamaev:
- Subsystem: CAN bus
- Subsystem: UAVCAN
- Georgii Staroselskii:
- Board: NavIO
- Gustavo José de Sousa:
- Subsystem: Build system
- Julien Beraud:
- Board: Bebop & Bebop 2
- Leonard Hall:
- Subsystem: Copter attitude control and navigation
- Matt Lawrence:
- Vehicle: 3DR Solo & Solo based vehicles
- Matthias Badaire:
- Subsystem: FRSky
- Mirko Denecke:
- Board: BBBmini, BeagleBone Blue, PocketPilot
- Paul Riseborough:
- Subsystem: AP_NavEKF2
- Subsystem: AP_NavEKF3
- Pierre Kancir:
- Subsystem: Copter SITL, Rover SITL
- Víctor Mayoral Vilches:
- Board: PXF, Erle-Brain 2, PXFmini
- Amilcar Lucas:
- Subsystem: Marvelmind