Skip to the content
4 layers100 × 74 mmMission board, the printed circuit board in 3D

The basics needed to allow a RC plane to be turned autonomous on signal.

Size
100 × 74 mm
Copper layers
4
Thickness
1.6 mm
Parts
128
Nets
158
Pads
551
Tracks, vias
1,369, 467
Pours
16
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
20 Mar 2026
Updated
3 Nov 2026

Overview

Mission board is an open-source printed circuit board by tmb5932, from the tmb5932/fixed-wing-drone repository on GitHub. It is a 4-layer board of 100 × 74 mm with 128 parts on 158 nets, routed with 1,369 tracks and 467 vias.

It is built around the ESP32-S3-WROOM-1-N8, INA180A2IDBVR(LX) and DRV8833PW, with the PCA9685PW, CD74HC4067M and MCP23017-E/SS among its other parts. Its parts include 35 resistors, 33 capacitors, 25 connectors, 18 ICs and 7 diodes. It belongs with the robots and motor control boards and the ESP32 boards of this library.

Main components

12

README

README.md

Autonomous RC Plane

A custom flight controller for a fixed-wing RC plane, built from scratch, both the PCB and the firmware. It's built around an ESP32-S3 and runs in-between a standard RC receiver and the servos/esc, giving the plane an onboard brain capable of taking over from the pilot and flying autonomously.

All software is written in ESP-IDF (specifically v5.5). It's a personal challenge to write as much of it as possible without plug-and-play libraries (ESP-IDF's own UART/I2C drivers are fair game), mainly the device drivers and the flight control logic.

The Goal

The flight control system is a cascade of PID loops: GPS waypoint/heading navigation on the outside, commanding roll/pitch attitude loops on the inside, plus an airspeed loop on the throttle. Target milestones, roughly in order:

  • RC pass-through with working sensor drivers (IMU, GPS) and RC I/O
  • First flight (manual pass-through, October 3, 2026)
  • Stable autonomous level flight
  • Altitude hold
  • GPS-guided heading / waypoint following (implemented and SITL-tested, not flown yet)
  • Autonomous takeoff and landing

Longer term, the hopes are giving it mission-oriented capabilities like payload release or coordinated flight with a second drone.

Current Status

The plane had its first flight on October 3, 2026, in manual pass-through mode only. The RC link had signal dropouts during that flight, so that's being debugged before anything autonomous is tried in the air. Since then the firmware has gained an on-board flight event log, a longer signal-loss window, and safer behaviour when the radio drops (see Safety below).

Autonomous mode (attitude stabilization, waypoint following, return-to-home) has only been tested on the bench and in the SITL simulator. The roll/pitch/heading gains come from SITL sweeps and still need real flight tuning.

Hardware

  • ESP32-S3
  • ICM-20948 IMU (I2C), roll/pitch/yaw via a Madgwick filter, with its AK09916 magnetometer used for compass heading
  • GPS module (UART, NMEA)
  • MS4525DO differential-pressure airspeed sensor (I2C)
  • Standard PWM RC receiver and servos/ESC, running alongside the ESP32 instead of being replaced by it

Future hardware will hopefully include lidar and a barometer.

PCB

The firmware currently runs on the v2.1 board: a custom carrier PCB that an ESP32-S3-DevKitC plugs into. Everything plugs into labeled connectors on the board rather than bare GPIO pins:

  • 6 RC receiver inputs (PWM), 6 labeled servo outputs, and primary/secondary ESC signal outputs
  • Separate UBEC power inputs for the flight controller and the ESC/servo rail, each with P-FET reverse-polarity protection
  • JST-SH (STEMMA QT) connectors for the IMU, the barometer, and a spare QT port for future I2C sensors
  • A JST-GH connector for the airspeed sensor, a header for the GPS UART, and connectors for a LIDAR
  • An accessory I/O header for things like LEDs, a payload-release servo/relay, etc.
    • (obviously will require alterations to code, but software is easier to change than hardware is...)

The GPIO-to-connector mapping the firmware uses (CH1_OUT_GPIO etc. in main.c) is defined by the board's pinout, not repeated here.

The KiCad sources in kicad/ are the next revisions, which the firmware hasn't been ported to yet:

Software Architecture

  • RC input: 6 channels read via the ESP32-S3's MCPWM capture timers. Interrupt-driven edge timestamping converts rising/falling edges into pulse widths directly, no external library.
  • RC/servo output: 6 servo channels plus 2 dedicated ESC channels, driven via MCPWM comparators on a 20ms timebase. Input/output channel mapping, per-channel PWM range and reversal are all configurable at runtime.
  • IMU: ICM-20948 and its AK09916 magnetometer driven with hand-written I2C register reads/writes, fused through a ported Madgwick AHRS filter for roll/pitch/yaw, with a stillness-gated gyro bias calibration at boot.
  • GPS: UART driver with a hand-written NMEA RMC sentence parser, plus u-blox config commands to quiet down unused sentence types and set a 5Hz fix rate.
  • Airspeed: MS4525DO driver with a boot-time zero-offset calibration and a low-pass filter on the pressure reading.
  • PID: a small PID module with integral anti-windup, used for roll, pitch, heading and airspeed.
  • Navigation: a 10Hz task that steers toward GPS waypoints (or holds the heading the plane had when autonomous engaged) by commanding a bank angle, using the compass heading or, when moving, GPS course over ground.
  • Control loop: a 100Hz task that reads all RC channels every cycle and switches between manual pass-through and autonomous output based on the mode switch (below 1500us = autonomous), RC signal health and sensor availability.

Safety

  • Autonomous mode is only armed after the mode switch has been seen in manual at least once since boot, and it needs a fresh GPS fix to engage.
  • If the RC signal is lost for 1 second, the plane returns to its home point (averaged from GPS at power-on), then spirals down with the motor off. With no GPS fix or no home, it spirals down where it is. If autonomous isn't available at all, it holds the surfaces at trim with the motor off instead of replaying the last stick input.
  • After a reboot in the air, manual pass-through comes back first, before anything slow in boot.
  • A small flight event log in RTC memory records RC dropouts, signal losses, failsafe transitions and the reset reason of every boot. It survives a reset (not a power cycle) and can be read from setup mode after landing.

SITL

sitl/ holds host-side simulators that compile the firmware's own pid.c and gps_math.c against a simple airframe model, used to tune the attitude and heading gains, with an 80-scenario regression suite. See sitl/README.md.

Build / Flash

Set up ESP-IDF v5.5, then from the project root:

sh
idf.py build
idf.py flash monitor

Setup mode

Holding the board's BOOT button within 5 seconds of power-on boots into a setup mode instead of normal flight init: it hosts its own WiFi access point (plane-fc-setup by default) with a local web page for calibrating servo/ESC PWM ranges and direction, remapping RC/servo channels, capturing trim, planning the GPS mission, tuning PID gains, setting the airframe mixing mode and airspeed-hold target, running bench control tests, and reading the flight event log. Connect to the AP and browse to http://192.168.4.1/. Everything is saved to NVS immediately; a normal reset (BOOT not held) returns to flight mode with those settings applied.

Author

Travis Brown

Parts

128
QtyValueFootprintReferences
11100nFCapacitor_SMD:C_0402_1005MetricC6, C8, C10, C16, C19, C20, C21, C22, C23, C24, C29
7330RResistor_SMD:R_0402_1005MetricR1, R2, R3, R4, R28, R29, R30
60.2RResistor_SMD:R_1206_3216MetricR11, R12, R31, R32, R33, R34
6H-Bridge Ch OutConnector_JST:JST_XH_B2B-XH-A_1x02_P2.50mm_VerticalJ7, J8, J23, J24, J25, J26
51uFCapacitor_SMD:C_0402_1005MetricC7, C25, C26, C27, C28
5INA180A2IDBVReasyeda2kicad:SOT-23-5_L3.0-W1.7-P0.95-LS2.8-BLU1, U4, U5, U6, U7
40.05RResistor_SMD:R_1206_3216MetricR16, R19, R22, R25
4100KResistor_SMD:R_0402_1005MetricR15, R18, R21, R24
4220RResistor_SMD:R_0402_1005MetricR14, R17, R20, R23
422uFCapacitor_SMD:C_0805_2012MetricC3, C9, C17, C18
447uFCapacitor_SMD:C_1206_3216MetricC30, C31, C32, C33
4AO3400Aeasyeda2kicad:SOT-23-3_L2.9-W1.3-P1.90-LS2.4-BRQ2, Q3, Q4, Q5
4SS34Diode_SMD:D_SMAD5, D6, D7, D8
310KResistor_SMD:R_0402_1005MetricR13, R26, R27
310nFCapacitor_SMD:C_0402_1005MetricC4, C11, C13
32.2uFCapacitor_SMD:C_0603_1608MetricC5, C12, C14
3DRV8833easyeda2kicad:TSSOP-16_L5.0-W4.4-P0.65-LS6.4-BL-EPU3, U13, U14
3MountingHole_2.2mm_M2MountingHole_2.2mm_M2MH1, MH3, MH4
210kResistor_SMD:R_0402_1005MetricR37, R38
210uFCapacitor_SMD:C_0603_1608MetricC1, C2
24.7kResistor_SMD:R_0402_1005MetricR35, R36
25.1KResistor_SMD:R_0402_1005MetricR5, R6
2B5819WDiode_SMD:D_SOD-123D3, D4
2PCA9685PWeasyeda2kicad:TSSOP-28_L9.7-W4.4-P0.65-LS6.4-TLU12, U18
2TS-1088Button_Switch_SMD:SW_SPST_TS-1088-xR020SW1, SW2
10.005RResistor_SMD:R_2512_6332MetricR8
124MHz Oscillatoreasyeda2kicad:OSC-SMD_4P-L3.2-W2.5-BL-1U10
14.7uFCapacitor_SMD:C_0603_1608MetricC15
1Actuator Power InConnector_AMASS:AMASS_XT30UPB-M_1x02_P5.0mm_VerticalJ6
1CD74HC4067easyeda2kicad:SOIC-24_L15.4-W7.5-P1.27-LS10.3-BLU9
1Camera FPCeasyeda2kicad:FPC-SMD_24P-P0.50_FPC-05F-24PH20J13
1Debug UARTConnector_PinHeader_2.54mm:PinHeader_1x04_P2.54mm_VerticalJ17
1ESP32-S3-WROOM-1easyeda2kicad:WIRELM-SMD_ESP32-S3-WROOM-1U11
1Fast IO ExpansionConnector_PinHeader_2.54mm:PinHeader_1x05_P2.54mm_VerticalJ21
1GPIO/ADC ExpansionConnector_PinHeader_2.54mm:PinHeader_1x06_P2.54mm_VerticalJ16
1I2C ExpansionConnector_PinHeader_2.54mm:PinHeader_1x04_P2.54mm_VerticalJ14
1Inter-ESP UARTConnector_JST:JST_GH_BM03B-GHS-TBT_1x03-1MP_P1.25mm_VerticalJ18
1LOGOLOGOG***
1Limit Switch InputConnector_JST:JST_XH_B3B-XH-A_1x03_P2.50mm_VerticalJ22
1MCP23017easyeda2kicad:SOIC-28_L17.9-W7.5-P1.27-LS10.3-BLU8
1MOSFET Ch1 OutConnector_JST:JST_XH_B2B-XH-A_1x02_P2.50mm_VerticalJ9
1MOSFET Ch2 OutConnector_JST:JST_XH_B2B-XH-A_1x02_P2.50mm_VerticalJ10
1MOSFET Ch3 OutConnector_JST:JST_XH_B2B-XH-A_1x02_P2.50mm_VerticalJ11
1MOSFET Ch4 OutConnector_JST:JST_XH_B2B-XH-A_1x02_P2.50mm_VerticalJ12
1Servo 1Connector_Molex:Molex_KK-254_AE-6410-03A_1x03_P2.54mm_VerticalJ1
1Servo 2Connector_Molex:Molex_KK-254_AE-6410-03A_1x03_P2.54mm_VerticalJ2
1Servo 3Connector_Molex:Molex_KK-254_AE-6410-03A_1x03_P2.54mm_VerticalJ3
1Servo 4Connector_Molex:Molex_KK-254_AE-6410-03A_1x03_P2.54mm_VerticalJ4
1Servo 5Connector_Molex:Molex_KK-254_AE-6410-03A_1x03_P2.54mm_VerticalJ19
1Servo 6Connector_Molex:Molex_KK-254_AE-6410-03A_1x03_P2.54mm_VerticalJ20
1Status LEDLED_SMD:LED_0603_1608MetricD9
1USB-CConnector_USB:USB_C_Receptacle_GCT_USB4105-xx-A_16P_TopMnt_HorizontalJ5
1USBLC6-2SC6Package_TO_SOT_SMD:SOT-23-6U15
1XC6206P122MRPackage_TO_SOT_SMD:SOT-23-3U17
1XC6206P282MRPackage_TO_SOT_SMD:SOT-23-3U16
1XC6220B331PR-Geasyeda2kicad:SOT-89-5_L4.5-W2.5-P1.50-LS4.4-BRU2

More from tmb5932/fixed-wing-drone

3
  • 2 layers100 × 74 mmMission board.pre relayout, the printed circuit board in 3D

    Mission board.pre relayout

    tmb5932/fixed-wing-drone

    The basics needed to allow a RC plane to be turned autonomous on signal.

    105 parts
  • 4 layers91 × 61.5 mmFixed wing drone, the printed circuit board in 3D

    Fixed wing drone

    tmb5932/fixed-wing-drone

    The basics needed to allow a RC plane to be turned autonomous on signal.

    101 parts
  • 2 layers21.5 × 27.5 mmUwb radio, the printed circuit board in 3D

    Uwb radio

    tmb5932/fixed-wing-drone

    The basics needed to allow a RC plane to be turned autonomous on signal.

    9 parts

Similar boards

  • 2 layers94 × 100 mmRobocar unified integrated carrier, the printed circuit board in 3D

    Robocar unified integrated carrier

    laurigates/mcu-tinkering-lab

    This repository contains projects for various embedded platforms (ESP32, Arduino, STM32).

    98 parts7MIT
  • 2 layersADM133 - Adeept Robot, the printed circuit board in 3D

    ADM133 - Adeept Robot

    PhilipMcGaw/robot-NautiPi

    NautiPi is the physical hardware and embedded-project repository for the robot projects. It contains electronics, PCB and KiCad work, Arduino projects, component records, mechanical references, photographs, and retained…

    133 parts
  • 4 layers110 × 90 mmFilMachine Mainboard, the printed circuit board in 3D

    FilMachine Mainboard

    yesnoj/FilMachine_Reworked

    FilMachine is an automated film processing machine designed for photographic film development. It handles the entire process: chemical baths, water rinses, temperature regulation, and motor-driven film agitation — all…

    205 parts
  • 2 layers56 × 35.5 mmEsp32, the printed circuit board in 3D

    Esp32

    Infinity6542/CSI-Collection-Utility

    Suitable for use in a microwave :) (just dont turn it on).

    25 partsMPL-2.0
  • 2 layers71.5 × 33 mmCEI TOOL, the printed circuit board in 3D

    CEI TOOL

    radiostart/CEI-TOOL

    62 parts
  • 2 layers90 × 60 mmFlappy esp32c3-revb, the printed circuit board in 3D

    Flappy esp32c3-revb

    Soulboy420/BP_flappyBird

    Eigenständiger KiCad-10-Entwurf für das HAW-Bachelorprojekt. Der ursprüngliche Entwurf unter hardware/ und absichtliche Benutzerlöschungen wurden nicht überschrieben. Es wurde nichts bestellt, committed oder gepusht.

    111 parts
  • 4 layers30 × 30 mmPCIe Pie, the printed circuit board in 3D

    PCIe Pie

    vk-sahni/M.2_IMU_sensor_module

    KiCad design for an M.2 Key A RP2350B sensor module featuring an MPU-9250 IMU and BME280, intended for UAV and ArduPilot integration experiments.

    85 parts
  • 2 layers59 × 91 mmSmart doorbell, the printed circuit board in 3D

    Smart doorbell

    calebhabesh/doorlink

    Self-hosted ESP32-S3 smart doorbell with a custom PCB, Raspberry Pi gateway, and web dashboard

    108 parts1MIT

Questions

How big is the Mission board PCB?

It measures 100 × 74 mm and has 4 copper layers, 1.6 mm thick.

What parts does the Mission board use?

128 parts, built around the ESP32-S3-WROOM-1-N8, INA180A2IDBVR(LX), DRV8833PW and PCA9685PW. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the Mission board KiCad files?

From the tmb5932/fixed-wing-drone repository on GitHub, at the commit this page was made from: the board is kicad/mission-board/mission-board.kicad_pcb and its schematic kicad/flight-controller/aux.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Mission board design in my own project?

Its repository states no licence, so its author keeps all rights: ask tmb5932 before reusing the design.