- Choosing an Autopilot
- Edit on GitHub
ArduPilot runs on many different autopilot boards. Selecting the right board depends on the physical constraints of thevehicle, features desired, and the applications that you want to run.Factors to consider are:
Sensor Redundancy: ArduPilot supports redundant IMUS, GPS, etc. Many controllers have multiple IMUs integrated on board for applications requiring this level of reliability.
Number of Servo/Motor Outputs.
Number of UARTs: Telemetry radios, GPS’s, Companion Computers, etc can be attached via these ports.
External Buses: I2C, CAN, etc. allow many types of devices, such as airspeed sensors, LED controllers, etc. to be attached to the autopilot.
Number of Analog I/O: Some controllers have analog I/O available for such features as inputting receiver signal strength (RSSI) or battery voltage/current or other analog sensors.
Integrated Features: Such as on-board OSD (On Screen Display), integrated battery monitoring sensors.
Vibration Isolation: Internal mechanical vibration isolators for IMUs for high vibration applications.
IMU Heaters: On board temperature control of IMUs for applications in harsh environments or widely varying temperatures during a flight to provide the highest possible precision.
Size: Many vehicles have limited space for the autopilot.
Expense: Controller prices range from ~$25 to much more, depending on feature set.
The sections below provide information about ArduPilot autopilot hardware options. The list below is sorted by manufacturer and product name.
Tip
There are also numerous clones and minor variants of the boards linked below. Many of these may be perfectly capable replacements. Help in selecting an autopilot can also be obtained in the user forums (ArduPilot Discuss or RC Groups ).
Note
The APM2.6 board is no longer supported for Copter or Plane. Thelast firmware builds that can be installed on these boards are AC v3.2.1 and Plane3.3.0.
Note
Not all of these autopilots have been directly tested by ArduPilot development team members and while firmware is provided by ArduPilot, it does not constitute an endorsement by ArduPilot. However, most boards developed by ArduPilot Partners have been provided to the ArduPilot development team to aid in any possible support issues that might arise.
Open Hardware¶
- ARKV6X DS-10 Pixhawk6
- CUAV V5 Plus
- CUAV V5 Nano
- CUAV Nora
- CUAV Pixhawk v6X
- CUAV X7/X7Pro/X7+/X7+ Pro
- CUAV-7-Nano
- Drotek Pixhawk3
- F4BY
- CubePilot Cube Black
- CubePilot Cube Orange/+
- CubePilot Cube Purple
- CubePilot Cube Yellow
- CubePilot Cube Green
- Holybro Durandal H7
- Holybro Pix32 v5
- Holybro Pixhawk 4
- Holybro Pixhawk6X/6X Pro
- Holybro Pixhawk6C/ 6C Mini
- Holybro Pix32v6(Pixhawk6C variant)
- mRo Pixhawk
- mRo Pixracer
- mRo X2.1
- mRo X2.1-777
- OpenPilot Revolution
- TauLabs Sparky2
- ZeroOneX6
* due to flash memory limitations, these boards do not include all ArduPilot features. See Firmware Limitations for details.
Closed Hardware¶
- 3DR Control Zero H7 OEM
- Aerotenna Ocpoc-Zynq
- Airvolute DroneCore
- AnyleafH7
- AocodaRC H743Dual
- AtomRC F405-NAVI
- BetaFPV F4 1S 12A AIO V3
- brainFPV RADIX2 HD
- Emlid NAVIO2 (Linux)
- Flywoo F405 Pro
- Flywoo F745 AIO BL_32/ Nano
- Foxeer F405v2
- Foxeer H743 MPU600
- Foxeer Reaper F745-AIO V2/V3/V4
- Furious FPV F-35 Lightning and Wing FC-10
- HeeWing F405/F405V2
- Holybro Kakute F4
- Holybro Kakute F4 Mini
- Holybro Kakute F7 AIO
- Holybro Kakute F4 Wing
- Holybro Kakute F7 Mini (only V1 and V2 are compatible)
- Holybro Kakute H7 V1
- Holybro Kakute H7 V2
- Holybro Kakute H7 Mini v1.3
- Holybro Kakute H7 Wing
- Holybro Pixhawk 4 Mini
- Holybro Pixhawk5X
- Horizon31 PixC4-Jetson
- iFlight Beast F7 45A AIO
- iFlight BeastH7 AIO
- iFlight Blitz F745/F745 Mini
- iFlight Blitz Whoop F7 AIO
- iFlight Blitz Wing H743
- iFlight Thunder H7
- JAE JFB-110
- Mamba F405 MK2
- Mamba MK4 F405Mini
- Mamba Basic F405 mk3
- Mamba H743 v4
- MakeFlyEasy PixSurveyA1
- MakeFlyEasy PixSurveyA1-IND
- MakeFlyEasy PixSurveyA2
- MakeFlyEasy PixPilot-C3
- MakeFlyEasy PixPilot-V3
- MakeFlyEasy PixPilot-V6
- Mateksys F405 TE Family
- Mateksys H743-Wing/MINI/SLIM/WLITE
- MFT-SEMA100
- MicoAir405v2/Mini
- ModalAI Flight core
- mRo ControlZero Classic
- mRo ControlZero F7
- mRo ControlZero H7
- mRo COntrolZero H7 OEM
- mRo Pixracer Pro (H7)
- mRo Nexus
- Omnibus F4 AIO/Pro
- OmnibusNanoV6
- Omnibus F7V2
- OrcaF405
- Parrot Bebop Autopilot
- Parrot C.H.U.C.K
- PixFlamingo- F767
- RadioLink MiniPix
- RadioLinkPIX6
- QioTek Zealot F427
- QioTek Zealot H743
- SDMODEL SDH7V1
- SDMODEL H7 V2
- Sky-Drones AIRLink
- SkystarsH7HD
- SPRacing H7 Extreme
- SPRacing H7 RF
- Swan-K1
- SpeedyBee F4 (this board currently is non-verified)
- SpeedyBee F4 V3/V4
- SpeedyBee F405 Mini
- SpeedyBeeF405WING/WING Mini
- ThePeach FCC-K1
- ThePeach FCC-R1
- TmotorH7Mini
- VR Brain 5
- VR uBrain 5.1
- YJUAV A6SE
- YJUAV A6SE H743
- YJUAV-A6Ultra
Note
due to flash memory limitations, most F4 based, and some other boards, do not include all ArduPilot features. See Firmware Limitations for details.
Linux Based Autopilots¶
These autopilots use an underlying Linux OS. Linux boards usually have more CPU power and memory many of the other boards listed on this page, but do not support DShot, Bi-Directional DShot, BLHeli ESC passthrough, many of the ArduPilot GPIO based features, and easy upload from the ground stations. They do allow experimentation and development of advanced control and navigation algorithms (see also Companion Computers).
- BBBMini** (Linux)
- Beagle Bone Blue (Linux)
- Blue Robotics Navigator** (Linux)
- Obal Board (Linux)
- PocketPilot** (Linux)
** these devices are sensor add-on boards for a Linux-based microcomputer. See board links for details.
Note
For more information on using ArduPilot on Linux based boards, see Building the code
Firmware Limitations¶
Some boards have features removed in order to fit the firmware into their memory capacity. See the section below:
- Firmware Limitations
Note
If a board has a missing feature that is required by the user, building a custom firmware using the ArduPilot Custom Firmware Build Server can be used to create firmware which drops features not needed and adding desired features back into the firmware in that freed space.
Discontinued Boards¶
The following boards are no longer produced, however, documentation is still available in the wiki or online, and recent builds are still expected to work. These boards are not recommended for new projects.
- CUAV V5
- Emlid Edge
- Erle PXFmini RPi Zero Shield
- Erle ErleBrain
- Holybro Kakute H7 Mini
- Intel Aero
- Intel Aero RTF vehicle
- Mateksys F405-SE
- Mateksys F405-STD and variants*
- Mateksys F405-Wing
- Mateksys F765-Wing
- Mateksys F765-WSE
The following boards are no longer supported. The documentation is archived, butavailable if you’re still working on those platforms:
APM 2.x (APM 2.6 and later) are no longer supported for Copter, Plane or Rover. The last firmware builds that fit on this board are Copter 3.2.1, and Plane 3.4.0, and Rover 2.5.1.
NAVIO+
PX4FMU
Qualcomm Snapdragon Flight Kit
Schematics¶
Schematics for some of the “Open Hardware” autopilots can be found here