Drone Board Integration

flux

Not safely as-is. The Instructables design may teach basic STM32F030 sensorless six-step commutation, but it provides no verifiable 4S voltage margin, 20 A continuous thermal data, MOSFET/gate-driver specifications, protection behavior, or PCB current-path validation.
For this board, use ST’s STEVAL-ESC002V1 as the ESC baseline instead:
  • 2S–6S LiPo
  • 20 Arms rated output
  • STSPIN32F0A integrated MCU/gate driver
  • Six 60 V, 2.8 mΩ STL140N6F7 MOSFETs
  • Sensorless six-step commutation with available firmware
  • BEMF and battery-voltage sensing
  • Hardware overcurrent protection
  • Published schematic, BOM, and Gerbers
Even that reference needs adaptation and testing for 20 A continuous / 30 A burst, DShot/CRSF integration, shared-PDB transients, cooling, and four channels operating simultaneously. The IWDF guidance reinforces separating the ESC switching loops from the FC/IMU/RF region, using heavy copper and thermal vias, local bulk capacitance, uninterrupted reference planes, filtered low-noise rails, and accessible test points.
My recommendation is to treat the Instructables circuit as a learning reference only and derive each of the four ESC channels from STEVAL-ESC002V1.
Develop ESC reference channel
Compare ESC reference designs
Document ESC adaptation
Define 8-layer stackup
Sign up to send
No schematic yet

Talk to Flux to get started.

Refine this doc
Ask about this doc
Reference Design Review
Source
  • Upstream project: https://github.com/pms67/HadesFCS
  • License: BSD 3-Clause; derivative work must preserve the required copyright and license notices.
  • User-supplied manufacturing BOM reviewed on 2026-08-13.
What HadesFCS Provides
HadesFCS is a strong flight-controller and navigation-computer reference, but it is not documented as an integrated four-channel ESC/PDB. The source includes KiCad hardware, firmware, FreeRTOS-based control software, simulator and ground-control tooling.
The supplied BOM confirms these major blocks:
  • STM32H753VIT6 primary flight-control MCU.
  • STM32F405RGT6 navigation MCU.
  • BMI088 inertial sensor.
  • IIS2MDCTR magnetometer.
  • MPRLS0025PA pressure sensor and TMP100 temperature sensor.
  • MAX-8Q GNSS module and SMA RF connector.
  • W25N01 serial NAND, two 24CW1280 EEPROMs, PCA9685 I/O/PWM expander, and INA219 current monitor.
  • MIC26903-based switching regulator and LD39200 3.3 V LDO.
  • Two 10-pin 1.27 mm SWD headers and multiple Micro-USB connectors.
Blocks Worth Reusing
  • Dual-MCU functional partition and independent SWD access.
  • Sensor and nonvolatile-memory functional set.
  • External GNSS, RC input, UART, I2C, ADC, and PWM connectivity concepts.
  • Input voltage/current monitoring concept.
  • Firmware and test infrastructure where licensing and pin mapping remain compatible.
Blocks Requiring Redesign or Review
  • Four ESC power stages, motor connectors, gate drivers, MOSFETs, shunts, bulk capacitance, transient suppression, and thermal design are new.
  • The PDB must be sized only after battery and motor-current requirements are fixed.
  • Micro-USB should be reconsidered in favor of USB-C for data/bench power, without a flight-pack charging path.
  • MAX-8Q and other older components require lifecycle and availability review.
  • INA219 is suitable for modest bus monitoring but may not be the best device for fast high-current propulsion measurements.
  • PCA9685 is not the preferred path for high-rate DShot; H753 timers/DMA should drive the ESC interface directly.
  • Existing power conversion must be recalculated for the expanded avionics loads and battery range.
Signal- and Power-Integrity Learning Targets
  • Controlled 90-ohm USB differential routing using the fabricator's real 8-layer stackup.
  • 50-ohm RF routing and antenna-launch practice.
  • Solid reference planes and return-via placement at every signal-layer transition.
  • Separation of IMU/analog regions from high di/dt ESC loops.
  • Gate-drive loop minimization, switch-node containment, and Kelvin current sensing.
  • Plane impedance, decoupling hierarchy, anti-resonance awareness, and rail isolation.
  • Inter-processor SPI timing, source damping, and length/return-path discipline.
  • High-current copper, via-array, connector, thermal, and transient validation.
Use the HadesFCS schematic as a reference baseline rather than a literal copy. First recreate and modernize the compute/sensor/debug core, then add one fully validated ESC channel and replicate it four times only after electrical and thermal review. Keep RF module-based in revision A so the project teaches controlled RF routing without making radio certification and discrete matching the dominant risk.
Critical Inputs Still Required
  1. Flight pack: 4S or 6S.
  2. Continuous and peak motor current per channel.
  3. Target ESC control architecture: BLHeli_32-compatible dedicated ESC MCUs, a custom STM32G0/C0 per channel, or direct experimental control.
  4. RF standard/module: ExpressLRS, external telemetry radio, Wi-Fi/BLE, or another link.
  5. Target board dimensions and mounting pattern.

  • Source

  • What HadesFCS Provides

  • Blocks Worth Reusing

  • Blocks Requiring Redesign or Review

  • Signal- and Power-Integrity Learning Targets

  • Recommended Architecture Direction

  • Critical Inputs Still Required

Hades Integrated Drone Controller

Hades Integrated Drone Controller thumbnail
An 8-layer HadesFCS-derived drone electronics platform combining an STM32H753 flight controller, STM32F405 navigation computer, RF/telemetry, four ESC power stages, and high-current power distribution, with emphasis on signal integrity and power integrity practice.

Properties

USB 2.0

BSD-3-Clause derivative

STM32 FreeRTOS

Drone Flight Control

8-layer integrated FC ESC PDB

Pricing & Availability

See prices from popular manufacturers for your project.

Controls