Awesome

madflight is a toolbox to build high performance flight controllers with Aduino IDE or PlatformIO for ESP32-S3 / ESP32 / RP2350 / RP2040 / STM32. A functional DIY flight controller can be build for under $10 from readily available development boards and sensor breakout boards.

Flight tested example programs for quadcopter and airplane are included. The example programs are only a couple hundred lines long, but contain the full flight controller logic. The nitty-gritty low-level sensor and input/output management is done by the madflight library.

The source code and website have extensive documentation explaning what the settings and functions do.

<img src="extras/img/madflight RP2040 flight controller.jpeg" title="madflight RP2040 flight controller" width="38%" /> <img src="extras/img/madflight drone.jpeg" title="madflight drone" width="30%" /> <img src="extras/img/madflight ESP32 flight controller.jpeg" title="madflight ESP32 flight controller" width="29%" />

Required Hardware

• Development board:
  • RP2350/RP2040 (e.g. Raspberry Pi Pico/Pico2)
  • ESP32-S3/ESP32 (e.g. Espressiv ESP32/ESP32-S3 DevKitC)
  • STM32 (e.g. Black Pill or a commercial flight controller)
• SPI IMU sensor (BMI270, MPU9250, MPU6500, or MPU6000), if not available then use an I2C IMU sensor (MPU6050 or MPU9150)
• RC Receiver: ELRS, CRSF, SBUS, DMSX, or PPM
• BEC or DC-DC converter to power your board from a battery
• ESC (OneShot125 or 50-490Hz PWM) and/or servos (50-490Hz PWM)

Optional Hardware

• GPS Module (Serial)
• Barometer (I2C BMP390, BMP388, BMP280, MS5611)
• Magnetometer (I2C QMC5883L)
• Current/Voltage Sensor (ADC or I2C INA226)
• Optical Flow Sensor (I2C)

Getting Started

1. Connect the required hardware to your controller board:
   • See RP2350/RP2040 pinout and instructions
   • -or- ESP32-S3/ESP32 pinout and instructions
   • -or- STM32 pinout and instructions
   • Connect your IMU (gyro/acceleration) sensor as shown here.
   • Connect your radio receiver according to the configured pins.
2. Install the madflight library in Arduino IDE. (Menu Tools->Manage Libraries, then search for madflight)
3. Open Examples for custom libraries->madflight->Quadcopter.ino in the Arduino IDE.
4. Edit the HARDWARE section in madflight_config.h to enable the connected peripherals.
5. If you're not using the default pinout then setup your board pinout in the CUSTOM PINS section.
6. Compile Quadcopter.ino and upload it to your board. Connect the Serial Monitor at 115200 baud and check the messages. Type help to see the available CLI commands.
7. Type calradio and follow the prompts to setup your RC radio receiver.
8. IMPORTANT: Use CLI calimu and calmag to calibate the sensors.
9. Use CLI commands pimu, pahrs, pradio, pmot, etc. and check that IMU sensor, AHRS and RC Receiver are working correctly.
10. Connect motors (no props) and battery and check that motors are spinning correctly.
11. Mount props, go to an wide open space, and FLY!

Safety First!!!

By default madflight has these safety features enabled:

• Motors only rotate when armed.
• Arming Procedure: set throttle low then flip the arm switch from disarmed to armed.
• Kill Switch: when the arm switch is in the disarm position, disarm and stop motors until re-armed.
• Failsafe: when radio connection is lost, disarm and stop motors until re-armed.
• Armed Low Throttle: motors run at low speed, to give visible armed indication.
• LED armed/disarmed indicator.

Software Design

• Keep it simple!!!
• Based on dRehmFlight
• Coded primarily for readability, then for speed and code size.
• No external dependencies, all modules are included in the src/madflight directory.
• The madflight flight controller runs standard setup() and loop().
• It mainly uses plain Arduino functionality: Serial, Wire, and SPI. One custom hardware dependent library is used for PWM. Therefor, it can fairly easily ported to other 32 bit microcontrollers that support the Arduino framework. Also porting to other build environments like PlatformIO or CMake should not be a huge effort.
• The following modules are used:
  • ahrs Attitude Heading Reference System, estimates roll, yaw, pitch
  • baro Barometer sensor
  • bat Battery monitor
  • bb Black Box data logger
  • cfg Read and save configuration to flash
  • cli Command Line Interface for debugging, configuration and calibration
  • gps GPS receiver
  • hw Hardware specific code for STM32, RP2040 and ESP32
  • imu Inertial Measurement Unit, retrieves accelerometer, gyroscope, and magnetometer sensor data
  • led LED driver
  • mag Magnetometer sensor (external)
  • out Output to motors and servos
  • rcin RC INput, retrieves RC receiver data
• Most modules are interfaced through a global object, for example the imu object has property imu.gx which is the current gyro x-axis rate in degrees per second for the selected IMU chip.
• For a quick overview of the objects, see header src/madflight/interfaces.h which defines the module interfaces.
• The module implementations are in subdirectories of the src/madflight directory. Here you find the module header file, e.g. src/madflight/imu/imu.h. In the extras directory your find test programs for the modules, e.g. extras/TestMadflight/imu.ino.
• The module files are usually header only, that is, the header also includes the implemention.

Disclaimer

This code is a shared, open source flight controller for small micro aerial vehicles and is intended to be modified to suit your needs. It is NOT intended to be used on manned vehicles. I do not claim any responsibility for any damage or injury that may be inflicted as a result of the use of this code. Use and modify at your own risk. More specifically put:

THIS SOFTWARE IS PROVIDED BY THE CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Logo image copyright (c) 1975 Deutsches MAD Magazine. This project is not associated with MAD Magazine.