How to Build and Debug a Flight Controller with Arduino Nano

Project Spec Sheet & Difficulty Rating

Building a custom flight controller with Arduino is a rite of passage for embedded hobbyists. Unlike plug-and-play stacks like Betaflight, rolling your own firmware forces you to understand sensor fusion, I2C bus timing, and PID control loops at the register level. This guide walks through a bare-bones, bench-testable quadcopter flight controller using the classic ATmega328P architecture.

Required Parts List

• Microcontroller: Arduino Nano V3.0 (ATmega328P, 16MHz) - Do not use the Nano 33 IoT or BLE for this specific codebase without modifying the Wire clock speeds.
• IMU Sensor: GY-521 Breakout Board (featuring the TDK InvenSense MPU6050 6-axis accelerometer/gyroscope).
• Barometer (Optional): BMP280 breakout (I2C address 0x76 or 0x77) for altitude hold.
• Motor Drivers: 4x IRLZ44N Logic-Level N-Channel MOSFETs (or SI2302 SMD equivalents for custom PCBs).
• Motors: 4x 8.5mm Coreless Brushed DC Motors (8520 size).
• Power: 1S 3.7V 600mAh LiPo Battery (minimum 25C discharge rating).
• Passives: 4x 10kΩ pull-down resistors (for MOSFET gates), 4x 1N4007 flyback diodes.

Hardware Pin Mapping & Wiring Guide

The MPU6050 communicates via I2C, which on the ATmega328P is hardcoded to specific analog pins. Motor PWM signals must be routed to hardware PWM-capable digital pins to ensure consistent 50Hz-400Hz ESC/motor timing without blocking the main loop.

Compilable Flight Controller Code

This code targets the Arduino Nano V3.0 (ATmega328P). It uses the standard Adafruit_MPU6050 library to handle sensor initialization and provides a safe, serial-armed motor mixing skeleton. Install the Adafruit MPU6050 and Adafruit Unified Sensor libraries via the Arduino Library Manager before compiling.

#include <Wire.h>
#include <Adafruit_MPU6050.h>
#include <Adafruit_Sensor.h>

// Pin Definitions for Quadcopter Motors (via N-Channel MOSFETs)
#define MOTOR_FL 3  // Front Left
#define MOTOR_FR 5  // Front Right
#define MOTOR_BL 6  // Back Left
#define MOTOR_BR 9  // Back Right

// Safety threshold: Motors will not spin unless serial armed
bool isArmed = false;

Adafruit_MPU6050 mpu;

void setup() {
  Serial.begin(115200);
  
  // Initialize Motor Pins
  pinMode(MOTOR_FL, OUTPUT);
  pinMode(MOTOR_FR, OUTPUT);
  pinMode(MOTOR_BL, OUTPUT);
  pinMode(MOTOR_BR, OUTPUT);

  // Safety: Ensure all motors are off at boot
  analogWrite(MOTOR_FL, 0);
  analogWrite(MOTOR_FR, 0);
  analogWrite(MOTOR_BL, 0);
  analogWrite(MOTOR_BR, 0);

  // Initialize MPU6050 with strict error handling
  if (!mpu.begin()) {
    Serial.println("Failed to find MPU6050 chip");
    // Halt execution to prevent runaway motors if sensor is blind
    while (1) { 
      delay(10); 
    }
  }
  
  // Configure sensor ranges for typical micro-quad dynamics
  mpu.setAccelerometerRange(MPU6050_RANGE_8_G);
  mpu.setGyroRange(MPU6050_RANGE_500_DEG);
  mpu.setFilterBandwidth(MPU6050_BAND_21_HZ);
  
  Serial.println("Flight Controller Initialized. Type 'ARM' to enable motors.");
}

void loop() {
  // Serial arming mechanism for bench safety
  if (Serial.available()) {
    String cmd = Serial.readStringUntil('\n');
    cmd.trim();
    if (cmd == "ARM") {
      isArmed = true;
      Serial.println("System ARMED. Props clear!");
    } else if (cmd == "DISARM") {
      isArmed = false;
      Serial.println("System DISARMED.");
    }
  }

  sensors_event_t a, g, temp;
  mpu.getEvent(&a, &g, &temp);

  // Basic telemetry output for PID tuning (50Hz loop rate)
  Serial.print("Roll:"); Serial.print(g.gyro.x);
  Serial.print("\tPitch:"); Serial.print(g.gyro.y);
  Serial.print("\tYaw:"); Serial.println(g.gyro.z);

  if (isArmed) {
    // Placeholder for PID motor mixing logic
    // Example: Hover throttle base + PID corrections
    int baseThrottle = 120; // ~50% duty cycle on 8-bit PWM
    analogWrite(MOTOR_FL, baseThrottle);
    analogWrite(MOTOR_FR, baseThrottle);
    analogWrite(MOTOR_BL, baseThrottle);
    analogWrite(MOTOR_BR, baseThrottle);
  } else {
    analogWrite(MOTOR_FL, 0);
    analogWrite(MOTOR_FR, 0);
    analogWrite(MOTOR_BL, 0);
    analogWrite(MOTOR_BR, 0);
  }

  delay(20); // Enforce 50Hz control loop rate
}

Debugging: First Three Things to Check When It Fails

I2C communication on the ATmega328P is notoriously sensitive to wiring capacitance and voltage mismatches. If your serial monitor outputs the exact error string "Failed to find MPU6050 chip", do not rewrite the code. The Arduino Wire library is failing to handshake at the hardware level. Check these three things in order:

1. VCC Voltage Mismatch (Most Common): The GY-521 breakout board includes an onboard LDO regulator, meaning it expects 5V on the VCC pin. However, if you are using a raw MPU6050 module without the LDO, feeding it 5V will instantly fry the 3.3V logic. Check your specific breakout board schematic. If it lacks an LDO, wire VCC to the Nano's 3.3V pin.
2. Missing or Failed Pull-Up Resistors: I2C requires pull-up resistors on SDA and SCL. The GY-521 has 4.7kΩ surface-mount pull-ups onboard. If you are daisy-chaining a BMP280 barometer on the same bus, the combined parallel resistance might drop too low, or if you cut the traces, you lose the pull-ups. Use a multimeter to measure resistance between SDA and VCC; it should read roughly 4.7kΩ. If it reads infinite, add external 4.7kΩ pull-ups.
3. SDA/SCL Swap or Cold Solder Joint: The Nano's A4 (SDA) and A5 (SCL) are right next to each other. A swapped connection will result in a silent I2C timeout. Furthermore, cheap Nano clones often have cold solder joints on the female header pins. Wiggle the Dupont wires while running an I2C scanner sketch to check for intermittent connections.

For deeper register-level debugging, consult the TDK InvenSense MPU-6000/6050 Register Map to verify the WHO_AM_I register (0x75) is returning 0x68.

Extending and Simplifying the Build

Once you have stable telemetry and motor output, you will quickly hit the limits of raw gyro integration. Here is how to scale the project based on your goals:

How to Extend (Adding GPS and Altitude Hold)

To add altitude hold, wire a BMP280 barometer to the same I2C bus (A4/A5). The BMP280 uses address 0x76 or 0x77, avoiding conflicts with the MPU6050 (0x68). For GPS, you will need a UART module like the u-blox NEO-6M. Because the ATmega328P only has one hardware UART (used by Serial/USB), you must use the SoftwareSerial library on pins D10 (RX) and D11 (TX). Be warned: SoftwareSerial interrupts can jitter your I2C timing, so keep GPS baud rates at 9600.

How to Simplify (The Modern Alternative)

If debugging I2C wiring and MOSFET gate drivers is eating up your weekend, simplify the hardware by switching to the Arduino Nano 33 BLE Sense. It features an onboard LSM9DS1 9-axis IMU and LPS22HB barometer, entirely eliminating external I2C wiring. You can read sensor data via the Adafruit sensor APIs or native Arduino libraries, and output motor commands directly to onboard ESCs via its extended PWM capabilities.

Frequently Asked Questions

Can I use an Arduino Uno for a drone flight controller?

Yes, the Arduino Uno uses the exact same ATmega328P microcontroller and 16MHz clock as the Nano, meaning the code above will compile and run without modification. However, the Uno's physical footprint (75 x 53mm) and weight (~25g without headers) make it impractical for micro-quads. It is highly recommended to use the Uno strictly for breadboard prototyping, then migrate the exact same code to a Nano for the actual flight frame to save weight and reduce the center of gravity shift.

Why is my Arduino flight controller drifting on the yaw axis?

Yaw drift in raw MPU6050 implementations is almost always caused by gyro bias instability and temperature drift. The MEMS gyroscope outputs a non-zero value even when perfectly still. If you simply integrate this raw value over time (angle += gyro * dt), the error accumulates, causing the drone to spin. To fix this, you must implement a complementary filter or a Madgwick/Mahony AHRS algorithm to fuse the accelerometer (which is drift-free but noisy) with the gyroscope. Alternatively, enable the MPU6050's internal Digital Motion Processor (DMP) via the I2Cdevlib library, which handles sensor fusion in hardware.

How do I tune the PID loop on an Arduino flight controller?

Do not attempt to tune all three PID terms simultaneously. Use the Ziegler-Nichols method adapted for multirotors. First, set Integral (I) and Derivative (D) gains to zero. Slowly increase the Proportional (P) gain until the drone exhibits a fast, steady oscillation on the bench (tether it down!). Note this 'ultimate gain' value, then set your actual P gain to roughly 50% of that value. Next, introduce a small D gain to dampen the oscillations. Finally, add a tiny amount of I gain to correct for steady-state wind drift. Always make adjustments in increments of 0.1 or less.