Peter BarkerandClaude Fable 5
cd5c3b458b
Each of these "define NAME value" lines creates a macro which no code, script or ChibiOS source references, so they have no effect: - ALLOW_ARM_NO_GPS (AeroCogito-H7Digital): no such macro (unlike ALLOW_ARM_NO_COMPASS, which is consumed by AP_Arming_Copter.cpp) - AP_BATTERY_TIBQ76952_I2C_DEVICE (VM-L431-BMS): driver uses AP_BATTMON_TIBQ76952_BUS/_ADDR - AP_COMPASS_IST8308_DEFAULT_ROTATION (GreenSightUltraBlue): no such macro; rotation comes from the COMPASS line - HAL_BLHELI_PASSTHROUGH_ENABLED/_UART and HAL_ESC_TELEMETRY_UART/_ENABLED (NucleoH753ZI): no such macros - HAL_CAN_ENABLED, HAL_CAN_NUM_DRIVERS (SkyRukh_Surge_H7): obsolete; CAN interface count is derived from the CAN pin definitions - HAL_HEATER3_GPIO_PIN, HAL_HEATER4_GPIO_PIN (rFCU): IMU_heater.cpp only supports HAL_HEATER_GPIO_PIN and HAL_HEATER2_GPIO_PIN - HAL_BL_IOMCU_FW_DETECT and HAL_IO_FMU_COMMS_TX_DMA_CHANNEL/ _RX_DMA_STREAM/_RX_DMA_CHANNEL (CubeRedSecondary-IO): iofirmware only consumes HAL_IO_FMU_COMMS_TX_DMA_STREAM and HAL_IO_FMU_COMMS_TX_IRQ_PRIORITY, which are retained - HAL_LED_OFF (OrqaH7QuadCore, SkystarsH7HD bootloaders): bootloader uses HAL_LED_ON and derives off as !HAL_LED_ON - HAL_BOOTLOADER_NAME, HAL_BOOTLOADER_BOOT_FROM_SDCARD (PilotGaeaSH7V1-bdshot): no such macros; SD-card boot would be AP_BOOTLOADER_FLASH_FROM_SD_ENABLED - HAL_BUZZER_ON (SIMPLIFLYH7): no buzzer-polarity macro exists - HAL_NEOPIXEL_COUNT (KakuteF4): no such macro; LED count comes from the NTF_LED_LEN parameter - VDD_BRICK2_VALID (sparknavi-blue): only meaningful as a pin label, which this board does not have; as a bare define it does nothing - HAL_HEATER_MAG_OFFSET_RM3100 (ZeroOneX6): the consuming HAL_HEATER_MAG_OFFSET define is commented out, and the offset vector is zero in any case All affected boards still process cleanly through chibios_hwdef.py. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ArduPilot Project
ArduPilot is the most advanced, full-featured, and reliable open source autopilot software available. It has been under development since 2010 by a diverse team of professional engineers, computer scientists, and community contributors. Our autopilot software is capable of controlling almost any vehicle system imaginable, from conventional airplanes, quad planes, multi-rotors, and helicopters to rovers, boats, balance bots, and even submarines. It is continually being expanded to provide support for new emerging vehicle types.
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://ardupilot.org/dev/
-
Developer discussion: https://discuss.ardupilot.org
-
Developer chat: https://discord.com/channels/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 to help us improve our code: 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 Discord #documentation
-
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.
- Andrew Tridgell:
- Vehicle: Plane, AntennaTracker
- Board: Pixhawk, Pixhawk2, PixRacer
- Francisco Ferreira:
- Bug Master
- Grant Morphett:
- Vehicle: Rover
- Willian Galvani:
- Vehicle: Sub
- Board: Navigator
- Michael du Breuil:
- Subsystem: Batteries
- Subsystem: GPS
- Subsystem: Scripting
- Peter Barker:
- Subsystem: DataFlash, Tools
- Randy Mackay:
- Vehicle: Copter, Rover, AntennaTracker
- Siddharth Purohit:
- Subsystem: CAN, Compass
- Board: Cube*
- Tom Pittenger:
- Vehicle: Plane
- Bill Geyer:
- Vehicle: TradHeli
- Emile Castelnuovo:
- Board: VRBrain
- 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
- Víctor Mayoral Vilches:
- Board: PXF, Erle-Brain 2, PXFmini
- Amilcar Lucas:
- Subsystem: Marvelmind
- Samuel Tabor:
- Subsystem: Soaring/Gliding
- Henry Wurzburg:
- Subsystem: OSD
- Site: Wiki
- Peter Hall:
- Vehicle: Tailsitters
- Vehicle: Sailboat
- Subsystem: Scripting
- Andy Piper:
- Subsystem: Crossfire
- Subsystem: ESC
- Subsystem: OSD
- Subsystem: SmartAudio
- Alessandro Apostoli:
- Subsystem: Telemetry
- Subsystem: OSD
- Rishabh Singh:
- Subsystem: Avoidance/Proximity
- David Bussenschutt:
- Subsystem: ESP32,AP_HAL_ESP32
- Charles Villard:
- Subsystem: ESP32,AP_HAL_ESP32