ArduPilot is one of the most capable open-source autopilots in the world. It flies multirotors, planes, VTOLs, helicopters, boats and rovers, and it is used by hobbyists, universities and professional operators. It can also feel overwhelming the first time you connect a board. This ArduPilot setup guide walks you through a first multirotor setup step by step, from installing firmware to a safe first hover, in the order experienced builders actually do it.
Before you start
- A supported flight controller. Check that your exact board is listed in the ArduPilot documentation. Boards with an H7 or F7 processor and at least 1 MB of flash are a good choice; see our H7 vs F7 flight controller guide.
- A ground control station (GCS). Mission Planner (Windows) is the most common choice for ArduPilot. QGroundControl works on Windows, macOS, Linux and Android.
- A GPS with compass, a radio receiver, and a battery monitor (usually built into the flight controller or power module).
- Propellers removed. Keep the props off for every step until the first flight. This is the most important safety rule on the bench.
Step 1: Install the firmware
- Install Mission Planner and open it.
- Connect the flight controller by USB. Do not press Connect yet.
- Go to Setup → Install Firmware and choose your vehicle type, for example Copter for a multirotor.
- Follow the prompts. Mission Planner downloads the right firmware for your board and flashes it.
If your board came with Betaflight or INAV installed, it may not have an ArduPilot bootloader yet. In that case, the first install is done in DFU mode with the “with bootloader” firmware file for your board. The ArduPilot documentation for your board explains the exact steps.
Step 2: Connect and choose the frame
- Select the board’s COM port and a baud rate of 115200, then click Connect.
- Go to Setup → Mandatory Hardware → Frame Type.
- Choose your frame class and type, for example Quad and X. These are saved in the parameters
FRAME_CLASSandFRAME_TYPE. - Reboot the board when asked.
Step 3: Calibrate the accelerometer
Go to Mandatory Hardware → Accel Calibration and click Calibrate Accel. Mission Planner asks you to hold the drone level, then on its left side, right side, nose down, nose up and upside down. Hold each position still and press a key when asked. Then run Calibrate Level with the drone sitting flat.
Do this with the flight controller already mounted in the frame, so the calibration matches how it will fly.
Step 4: Calibrate the compass
- Go to Mandatory Hardware → Compass.
- Check the GPS/compass module is detected and its orientation is correct, usually with the arrow pointing forward.
- Click Start and rotate the drone slowly through all directions until the progress bars complete.
- Reboot when finished.
Calibrate outdoors or away from metal desks, computers and cars. Large metal objects nearby will spoil the calibration.
Step 5: Calibrate the radio
Turn on your transmitter and go to Mandatory Hardware → Radio Calibration. Click Calibrate Radio and move every stick and switch through its full range. Check the bars move in the right direction: for roll and yaw, right stick should increase the value; for pitch, the bar should go down when you push the stick forward (this is the ArduPilot convention). If a channel is reversed, reverse it in your transmitter.
If your receiver uses a serial protocol such as CRSF or SBUS, set the correct serial port protocol first. Many boards detect common protocols automatically.
Step 6: Set flight modes
Go to Mandatory Hardware → Flight Modes and assign modes to a three-position switch. A safe beginner setup is:
- Stabilize: self-levelling, manual throttle. Good for the first hover.
- AltHold: holds altitude using the barometer; you control position.
- Loiter: holds position and altitude using GPS. Very useful once everything is tuned.
Put RTL (Return to Launch) on a separate switch you can reach quickly.
Step 7: Set up the ESCs and test the motors
- Choose your ESC protocol. For modern ESCs, DShot is common and needs no calibration; it is set with the parameter
MOT_PWM_TYPE. For older PWM ESCs, run the ESC calibration in Mission Planner. - With propellers removed, go to Optional Hardware → Motor Test.
- Test each motor at low throttle. ArduPilot tests motors in order A, B, C, D, starting with the front-right motor and going clockwise around the frame.
- Check each motor spins in the right direction for your frame layout. Swap any two motor wires (or reverse in the ESC settings) to fix a wrong direction.
Motor order and direction mistakes are the most common cause of a drone flipping on take-off, so do not skip this step.
Step 8: Battery monitor and failsafes
Under Optional Hardware → Battery Monitor, select your board’s voltage and current sensor and check the reading against a multimeter. Then set up the failsafes:
- Radio failsafe: if the radio link is lost, the drone should return home or land. This is set with
FS_THR_ENABLE. Test it on the bench by switching off the transmitter with props removed. - Battery failsafe: set a low-voltage level (
BATT_LOW_VOLT) and an action (BATT_FS_LOW_ACT), such as RTL or Land. - Arming checks: keep the default arming checks enabled. They stop you arming with a bad compass, no GPS lock or an uncalibrated radio.
Step 9: The first flight
- Choose a large open area away from people, buildings and roads, and follow your local drone regulations.
- Fit the propellers, checking each one is on the correct motor and tightened.
- Wait for a good GPS lock, then arm in Stabilize.
- Take off gently to about 2 meters and hover. Check the drone is stable and does not drift strongly.
- Try AltHold. If both are stable, try Loiter at a safe height.
- Land, disarm and check motor temperatures.
Step 10: Review the logs and tune
ArduPilot records detailed logs. After the first flights, download them in Mission Planner and look at vibration levels and how well the drone follows its commanded attitude. Then run ArduPilot’s AutoTune in calm weather to tune the PID gains for your exact frame.
Common beginner problems
- “PreArm: Compass not calibrated” or “inconsistent compasses”: recalibrate away from metal and check the compass orientation.
- “PreArm: Need 3D Fix”: wait longer for GPS lock, and move the GPS away from the video transmitter. See our GPS module guide for mounting tips.
- Drone flips on take-off: almost always wrong motor order, wrong motor direction or wrong propeller direction.
- Toilet-bowling in Loiter: usually a compass problem, caused by interference or a bad calibration.
Frequently asked questions
Is ArduPilot good for beginners?
Yes, if you follow the setup steps in order and take your time. It has more settings than Betaflight, but its safety features such as arming checks, failsafes and return-to-launch make it a good choice for learning autonomous flight.
Mission Planner or QGroundControl?
Both work with ArduPilot. Mission Planner has the most ArduPilot-specific tools and is the usual choice on Windows. QGroundControl is cross-platform and has a simpler interface.
Do I need a GPS for ArduPilot?
Not for Stabilize or AltHold, but you need a GPS for Loiter, RTL, missions and most safety features. For a first multirotor, a GPS with compass is strongly recommended.
How long does a first ArduPilot setup take?
Plan for one to three hours for your first build, including calibrations and checks. With experience, the same setup takes less than an hour.