Updated October 8, 2026. This guide is for builders setting up ArduPilot Copter with Mission Planner. Hardware menus and supported firmware targets vary by flight controller, so use the official documentation for your exact board before connecting or flying.
ArduPilot setup is not complete when firmware finishes uploading. You must select the correct vehicle and board firmware, configure the airframe and sensors, check radio and battery failsafes, and resolve every pre-arm warning. Work through the checks below on the bench first, then use simulation before a real flight.
Safety: Remove propellers before bench setup, motor checks, or calibration that could spin motors. Secure the aircraft, keep people clear, and follow your local aviation rules and the manufacturer instructions. Do not fly if you do not understand a warning or failsafe.
What you need
ArduPilot is open-source autopilot software for supported aircraft and other vehicles. This walkthrough focuses on ArduCopter and Mission Planner. Before starting, confirm that the exact flight-controller board is supported for your vehicle in the official autopilot hardware list.
- A supported flight controller mounted in the correct orientation for your frame.
- A data-capable USB cable and a Windows computer for the standard Mission Planner installation.
- The receiver, GPS/compass, battery monitor or power module, ESCs, motors, and battery required by your build.
- The board and frame manuals, plus a safe test area where you can keep the aircraft and bystanders clear.
1. Install Mission Planner and connect the board
Download Mission Planner from the official ArduPilot installation instructions. Install it on Windows and allow the installer to add the required drivers. Use the current installer linked by ArduPilot; avoid third-party download sites. If Windows presents a security warning, verify the publisher and file source rather than adding an antivirus exclusion.
Connect the flight controller with a data-capable cable. In Mission Planner, select the detected COM port and the appropriate baud rate, then connect. If no port appears, try a known data cable and another USB port, then follow the board vendor’s driver guidance. Do not guess at a port or firmware target.
2. Install firmware for the exact board and vehicle
Open Mission Planner’s firmware installation screen and choose ArduCopter only if you are configuring a copter. Select the firmware target recommended for the exact flight-controller board; similarly named boards can use different targets or sensor layouts. Follow the current ArduPilot firmware-loading guide and any board-specific instructions.
Keep the USB connection stable while the uploader erases, programs, and verifies the board. Wait for the successful upload message and allow the controller to reboot before reconnecting. If flashing fails, follow the board’s documented bootloader recovery process instead of repeatedly trying unrelated firmware files.
3. Complete mandatory setup in a deliberate order
Frame and board orientation
Select the frame class and type that match the physical aircraft. Confirm that the flight controller’s configured orientation matches how it is mounted. A mismatch can make sensor readings and control response incorrect; do not proceed to flight until the displayed vehicle attitude matches movements of the frame.
Accelerometer and compass
Calibrate the accelerometer with the aircraft held level and placed in the orientations requested by Mission Planner. For compass calibration, follow the official compass procedure: use a suitable outdoor location with a good GPS fix, keep away from metal and magnetic/electrical interference, and rotate the vehicle as prompted. Reboot if the ground station requests it. Do not use generic offset thresholds from an unrelated board as a substitute for diagnosing interference or orientation.
Radio, battery monitor, and failsafes
Calibrate the radio inputs and check that each stick and switch moves the correct channel in the expected direction. Configure loss-of-radio behavior for the receiver and aircraft you actually use. Set up the battery monitor for the installed power module or sensor, then verify its voltage/current readings against a trusted meter where appropriate. Use the official documentation for the receiver, battery monitor, and failsafe options; there are no safe universal parameter values for every build.
Motors, ESCs, and flight modes
With propellers removed, verify motor order and rotation against the frame diagram and the installed ESC configuration. Follow the ESC manufacturer’s instructions and ArduPilot’s board-specific setup guidance; do not run an ESC calibration procedure simply because an old tutorial recommends it. Assign flight modes only after you understand what each mode requires, and resolve all pre-arm checks rather than disabling them to make the warning disappear.
4. Test in simulation before a real flight
Use ArduPilot’s Software-in-the-Loop (SITL) simulator to learn Mission Planner, inspect mode changes, and rehearse a simple mission without a physical aircraft. Simulation is useful for finding planning mistakes, but it does not validate your specific hardware, wiring, compass environment, or local conditions.
For the first real flight, use a legal, open site and a qualified pilot who can take control. Complete the aircraft-specific pre-flight checklist, verify the home position and GPS status, test the selected failsafe behavior safely, and begin with a simple controlled flight. Do not make the first flight an autonomous mission. Only progress to autonomous operation after the aircraft has behaved predictably in simpler modes and the mission, altitude, geofence, and return behavior have been checked for the site.
Common setup problems
- No COM port: confirm the cable carries data, try another port, and install only the driver recommended for the board.
- Firmware upload fails: confirm the board is supported, use its documented bootloader/recovery steps, and do not select a target by guesswork.
- Compass or GPS warning: move away from interference, verify sensor orientation and wiring, and follow the corresponding ArduPilot pre-arm message.
- Pre-arm check remains: read the exact message in the ground station and correct its cause. Do not disable the check to force arming.
- Unexpected motor response: remove the battery, keep propellers off, re-check motor order, direction, ESC configuration, and frame type before any powered test.
Official references and next steps
Use these primary sources for board-specific and version-current instructions: ArduPilot first-time setup, Mission Planner installation, firmware loading, compass calibration, and SITL simulation. Firmware and interface details change; check those docs again when updating a build.
If you are new to the software side, continue with our drone programming development-environment guide. Keep a copy of your parameters and review the flight logs after each test; change one thing at a time and document the result.