34d305083d
Jaime did the hard work on this one. He reworked notify device selection to take place on init rather than on compile like before. The notify decivces are mostly set on compile using preprocessor directives based on board type. I created NTF_OREO_THEME. This will allow the user to enable/disable the OreoLED driver. And it also allows you to select between aircraft and rover lighting themes. This allows the Solo to use the OreoLEDs, and doesn't waste the memory on vehicles not equipped with Oreo LEDs. The OreoLED driver is restricted to Pixhawk 2 FCs by proprocessor directive due to memory constraints. So it will never work by accident on another board. There is also a new notify flag for GPS Fusion. This flag is true when the EKF is happy with the GPS, actively using it for position information. |
||
|---|---|---|
| .github | ||
| AntennaTracker | ||
| APMrover2 | ||
| ArduCopter | ||
| ArduPlane | ||
| ArduSub | ||
| benchmarks | ||
| docs | ||
| libraries | ||
| mk | ||
| modules | ||
| tests | ||
| Tools | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .pydevproject | ||
| .travis.yml | ||
| BUILD.md | ||
| COPYING.txt | ||
| Doxyfile.in | ||
| eclipse.cproject | ||
| eclipse.project | ||
| Makefile | ||
| Makefile.waf | ||
| README.md | ||
| reformat.sh | ||
| uncrustify_cpp.cfg | ||
| uncrustify_headers.cfg | ||
| Vagrantfile | ||
| waf | ||
| wscript | ||
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 email group: drones-discuss@googlegroups.com
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
- Robert Lefebvre
- Vehicle: TradHeli
- Grant Morphett:
- Vehicle: Rover
- Tom Pittenger
- Vehicle: Plane
- Paul Riseborough
- Subsystem: AP_NavEKF2
- Lucas De Marchi
- Subsystem: Linux
- Peter Barker
- Subsystem: DataFlash
- Subsystem: Tools
- Michael du Breuil
- 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
- Georgii Staroselskii
- Board: NavIO
- Emile Castelnuovo
- Board: VRBrain
- Julien BERAUD
- Board: Bebop & Bebop 2
- Pritam Ghanghas
- Board: Raspilot
- 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