This custom version of ArduPilot Plane 4.4 is being developed to achieve the mission objectives for the AIAA DBF 2025 competition.
- Added a new mode called "CARRIED" for when the X-1 is carried by the mother ship/plane.
- Release and installation of the X-1 is monitored with the analog airspeed sensor pins.
- Default parameters are changed for SpeedyBee F405.
-
When powered up, it automatically starts in CARRIED flight mode disarmed
-
LED lights turn on indicating following meaning
- Ready to arm and has 3D fix, show the no of GPS sats with BLUE
- Ready to arm but has NO 3D fix, show the no of GPS sats with GREEN
- Ready to arm but has NO 3D fix with zero GPS sats, only 1st and 4th from the beginning and the end turn GREEN
- Not ready to arm and has NO 3D fix, show no of GPS sats with RED with the last LED light in BLUE
- Not ready to arm and has NO 3D fix, show no of GPS sats with RED
- Not ready to arm and no 3D fix with zero GPS sats, only 1st and 4th from the beginning and the end turn RED
-
Not ready to arm means there's a problem which is not about GPS. Open the Mission Planner and investigate.
-
When the X-1 is installed on the carrier plane, ALL of the LEDs turn OFF. The flight mode changes to CARRIED (if it is not in it already) and ARMS the plane even if there are pre-arming checks that are failing.
-
When the X-1 is released, LEDs turn on with GREEN and RED and they will not turn off until the flight mode is changed to CARRIED MANUALLY (or power cycled). The flight mode is changed to AUTO and we have to hope that it will come back and land on the target.
-
A mission needs to be designed and pre-loaded via the Mission Planner.
- The mission should include a Rally Point where the plane will return to, rather than the HOME point which is where the plane was armed at.
-
If a RC controller is connected, the flight mode switch is set to AUTO, FBWA and MANUAL. The switch should be in AUTO, so if something goes wrong after the X-1 is released, the switch should be flipped to gain the control of the X-1 and hopefully the situation too. While in the AUTO mode, the sticks can be moved and that will alter the movement of the plane without disengaging the mission (aka stick mixing). All of these are disabled when RC controllers are not connected.
- GPS HolyBro Micro M10 in UART 3
- Digital Airspeed Sensor Mateksys ASPD-4525 in I2C
- LED SpeedyBee Programable 2812 Arm LEDs in series (any LED port is fine)
- RC receiver Spektrum SRXL2 DSMX Serial Micro Receiver SPM4650 in TX1 (optional)
- HolyBro SiK Telemetry Radio V3 in UART 4
If you have any questions, ask Koji (email:dbf@koji.space)
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.
-
Support Forum: https://discuss.ardupilot.org/
-
Community Site: https://ardupilot.org
-
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
- Flight code contributors
- Wiki contributors
- Most active support forum users
- Partners who contribute financially
-
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
The ArduPilot project is licensed under the GNU General Public License, version 3.
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
- 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
- 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