Drone Board Integration


I’ll reconcile the redesign against the live schematic, fix any discovered electrical or pin-mapping issues, rerun ERC, and update the ArduPilot hardware definition, power budget, and bring-up plan.
Created a thread
Hades H753 Redesign
Completed
View Thread
The live reconciliation is still running through the pin-capability, PMU calculation, and ERC fix loops. I’m waiting for that pass to settle before independently checking the final results.
Thought for 6 mins 13 sec
Awaiting 1 background task
Received notification from "Hades H753 Redesign" that it finished — picking the work back up.
The H753 redesign executor completed and the live project changed to 138 components and 107 nets, consistent with the single-MCU cleanup and PMU/interface work.
Still required
  • Independently reconcile the executor’s detailed report against the live schematic.
  • Confirm complete STM32F405 removal and validate every H753 peripheral assignment.
  • Verify PMU, external-shunt, TMP36, ESC-header, and camera-trigger calculations.
  • Run a fresh ERC fix/verify pass.
  • Confirm the ArduPilot hwdef, power budget, and bring-up files were correctly updated.
I cannot complete those verification steps because no ACUs are currently available. The executor’s completion should therefore be treated as unverified, not final schematic approval.
Reconcile redesign changes
Resolve ERC issues
Verify MCU migration
Verify interface calculations
Review project documentation

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