20027bad17
AP_RPM: move PX4 IRQ handling into AP_HAL_PX4 AP_RPM: correct RPM sensor initialisation The initialisation code used the type from the wrong configuration parameters (if the first rpm sensor wasn't configured then the sensing for the second sensor would use the type from the first). The packing of drivers[...] was done in a non-sparse manner - i.e. if a sensor wasn't detected then it would not take up space in the array. The PX4 PWM backend relies on the instance number (offset in the drivers array) corresponding to the parameters, so making this sparse is required. The main detection block fills in drivers based on the number of instances detected so far, but the nullptr check checks based on the number of detected backends. If the second instance wasn't configured we wouldn't attempt to configure a third. AP_RPM: add error reporting for attaching of interrupts AP_RPM: use detach_interrupt method AP_RPM: use (uint8_t)-1 in place of 255 |
||
---|---|---|
.github | ||
APMrover2 | ||
AntennaTracker | ||
ArduCopter | ||
ArduPlane | ||
ArduSub | ||
Tools | ||
benchmarks | ||
docs | ||
libraries | ||
mk | ||
modules | ||
tests | ||
.dir-locals.el | ||
.editorconfig | ||
.flake8 | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.pydevproject | ||
.travis.yml | ||
BUILD.md | ||
COPYING.txt | ||
Doxyfile.in | ||
Makefile | ||
Makefile.waf | ||
README.md | ||
Vagrantfile | ||
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: http://discuss.ardupilot.org/
-
Community Site: http://ardupilot.org
Developer Information
-
Github repository: https://github.com/ArduPilot/ardupilot
-
Main developer wiki: http://dev.ardupilot.org
-
Developer discussion: http://discuss.ardupilot.org
-
Developer email group: drones-discuss@googlegroups.com. Deprecated November 2016. Included for historical reference.
Contributors
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.
-
Helping other users with log analysis on http://discuss.ardupilot.org/ is always appreciated:
-
There is a group of wiki editors as well in case documentation is your thing: ardu-wiki-editors@googlegroups.com
-
Developer discussions occur on drones-discuss@google-groups.com
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 CONTRIBUTING.md for more information.
- Andrew Tridgell:
- Vehicle: Plane, AntennaTracker
- Board: APM1, APM2, Pixhawk, Pixhawk2, PixRacer
- Randy Mackay:
- Vehicle: Copter, AntennaTracker
- Grant Morphett:
- Vehicle: Rover
- Tom Pittenger:
- Vehicle: Plane
- Chris Olson and Bill Geyer:
- Vehicle: TradHeli
- Paul Riseborough:
- Subsystem: AP_NavEKF2
- Subsystem: AP_NavEKF3
- Lucas De Marchi:
- Subsystem: Linux
- Peter Barker:
- Subsystem: DataFlash
- Subsystem: Tools
- Michael du Breuil:
- Subsystem: SMBus Batteries
- Subsystem: GPS
- Francisco Ferreira:
- Bug Master
- Matthias Badaire:
- Subsystem: FRSky
- Eugene Shamaev:
- Subsystem: CAN bus
- Subsystem: UAVCAN
- Víctor Mayoral Vilches:
- Board: PXF, Erle-Brain 2, PXFmini
- Mirko Denecke:
- Board: BBBmini, BeagleBone Blue, PocketPilot
- Georgii Staroselskii:
- Board: NavIO
- Emile Castelnuovo:
- Board: VRBrain
- Julien BERAUD:
- Board: Bebop & Bebop 2
- Matt Lawrence:
- Vehicle: 3DR Solo & Solo based vehicles
- Gustavo José de Sousa:
- Subsystem: Build system
- Craig Elder:
- Administration: ArduPilot Technical Community Manager
- Jacob Walser:
- Vehicle: Sub