
Assembly review
OAK-WJR/rocket-flight-computer
Amateur rocket flight computer: single-board KiCad PCB (STM32H743), firmware and diagnostics

Amateur rocket flight computer: single-board KiCad PCB (STM32H743), firmware and diagnostics
M1 power actuator is an open-source printed circuit board by OAK-WJR, from the OAK-WJR/rocket-flight-computer repository on GitHub. It is a 4-layer board of 46 × 66 mm with 36 parts on 27 nets, routed with 84 tracks and 76 vias.
It is built around the AO3400A, AON6403 and SMBJ12CA. Its parts include 19 resistors, 7 connectors, 5 capacitors, 4 transistors and 1 diode. It belongs with the robots and motor control boards of this library.
Status: design only. No board has been built, powered or flown. Every result below comes from CAD checks, circuit simulation or software tests on a computer, never from hardware.
This is a flight computer for a student high-power rocket. It is one 46 × 238 mm, four-layer circuit board that slides into a 54.66 mm inside-diameter airframe. It runs from a 2-cell LiPo battery, uses an STM32H743 microcontroller, reads an IMU (ICM-45686), a barometer (MS5611) and GPS (SAM-M10Q), logs to flash memory, talks over USB, powers a camera, drives four fin servos for roll control, and has two separately fused circuits to fire the parachute charge. The current design is revision M3-ASSY-R2 (28 Sep 2026).

KiCad 3D render of the top side of M3-ASSY-R2 (46 × 238 mm).
There is no video, because the board has not been built. What can be shown and re-run today:
tools/check.sh runs KiCad's design-rule check, electrical-rule check and schematic-vs-PCB check. Output on 2026-11-01 (KiCad 10.0.6):
DRC violations 0 unconnected 0 schematic parity 0 ERC 0
metadata / 3D model audit: OKm3_design/sim_r2/ found a flaw in the design: with a fresh 8.4 V battery, firing into a shorted igniter pulled the battery below 5 V for 3.9 ms (long enough that the computer could reset and miss the second parachute charge) and pushed 131 A through a transistor rated for 112 A. Adding a 2 Ω pulse resistor to each channel fixed it in simulation (4.1 A, battery stays above 8.2 V).
Simulated, not measured. Grey: before the fix. Black: with the 2 Ω resistors. The 20 ms pulse length is a rule the future firmware must follow.
The portfolio page for this project is 8a ("Rocket Flight Computer Design").
flowchart LR
BAT[2S LiPo battery] --> PWR[power switch, reverse and over-voltage protection, 3.3 V supply]
PWR --> MCU[STM32H743 microcontroller]
SEN[IMU, barometer, GPS] --> MCU
MCU --> LOG[flash log]
MCU --> USB[USB diagnostics]
MCU --> CAM[camera power and UART]
BAT --> ACT[actuator power switch]
ACT --> SRV[four fin servos]
ACT --> ARM[arming plug: a full break] --> PYRO[two fused parachute channels]
MCU --> SRV
MCU --> PYROreference/m1_power_actuator/.m3_design/check_actuators.py) reads the PCB copper and fails if anything bypasses it.diagnostics/ turn a report into a list of likely faults.docs/R2_VERIFICATION.md).No hardware is needed for any of these. Tested on macOS with KiCad 10.0.6, ngspice 46 and Python 3.9 on 2026-11-01.
git clone https://github.com/OAK-WJR/rocket-flight-computer.git
cd rocket-flight-computer
tools/check.sh # DRC + ERC + schematic parity + 3D/metadata audit (needs KiCad 10.0.x)
python3 m3_design/check_actuators.py # arming / pyro / servo safety contract -> "actuator safety contract: OK"
python3 m3_design/sim_r2/run.py # ngspice suite -> {'PASS': 135, 'OLD-FAIL': 6, 'INFO': 8, 'DEMO': 2}
python3 m3_design/sim_r2/plot_short.py # redraws docs/images/shorted_igniter_sim.png (needs matplotlib)
python3 tools/export_fab.py # Gerber zip + JLCPCB BOM/CPL into m3_design/assembly_review/fab/
python3 -m venv .venv && .venv/bin/pip install -r diagnostics/requirements-lock.txt
.venv/bin/python -m unittest discover -s diagnostics -t . -p 'test_*.py' # 173 tests, OK (1 skipped)
(cd m3_firmware && PYTHONPATH=.. python3 -m unittest test_firmware test_gnss test_usb) # 41 tests, OK
open m3_design/assembly_review/m3.kicad_pro # open the design in KiCad 10KICAD_CLI=/path/to/kicad-cli before tools/check.sh.OLD-FAIL rows in the simulation are the pre-fix design, kept on purpose for comparison.m3_firmware/build.py needs the Arm GNU Toolchain 15.2.rel1 in m3_firmware/toolchain/ and the maker datasheet PDFs it hash-checks (not committed, for copyright). It also refuses to build for R2 on purpose, because no R2 firmware exists yet. Prebuilt bench images for the older R1 board are in m3_firmware/build_assembly_*/. Do not run them on an R2 board.tools/export_fab.py (see docs/ORDERING.md), then need a 2S LiPo, an ST-Link/SWD probe and a USB-C cable. None of this has been done.| Path | What is in it |
|---|---|
m3_design/assembly_review/ | The KiCad 10 project (the single source of truth): 14 schematic sheets, PCB, local footprints, symbols and 3D models, schematic PNG/SVG exports in sheets/, review notes |
m3_design/sim_r2/ | ngspice suite for the actuator and parachute circuits (run.py, RESULTS.md, FINDINGS.md, plot_short.py) |
m3_design/check_actuators.py | Safety check that reads the PCB netlist |
m3_firmware/ | Bench diagnostic firmware v0.8.1 (C, STM32 HAL + TinyUSB) for the R1 board, pin bindings, host-side tests |
diagnostics/ | Python host tools: USB/SWD readout, log recovery, fault localisation, test-point map |
docs/ | Ordering guide, part-by-part verification, actuator merge record, design rationale, FMEA, simulation notes, design history |
quality_audit/ | Board audit: conflicting part numbers, 3D model paths, DRC/ERC evidence |
reference/ | Older boards kept for comparison: M1 power/actuator board, M3-ASSY-R1 |
tools/ | check.sh (board gate), export_fab.py (fabrication files), JLCPCB stock and orientation helpers |
STATUS.md | Every requirement and what is and is not verified |
AGENTS.md, CLAUDE.md | The rules given to the AI coding assistants (see Credits) |
What is done (on a computer only):
What is not done:
STATUS.md, docs/R2_VERIFICATION.md §4).Other branches: m3-assy-r11 is the development line. It holds the later redesigns R3 to R10 (Oct 2026) and the compact R11 candidate (Nov 2026), committed by a collaborator, and the R10 bench diagnostics; each earlier revision is in its history. They are not part of the R2 design described here.
Jerry Wu (Jiarui Wu): the project and its requirements: one board that fits the 54.66 mm airframe, built-in USB diagnostics, at most three PCB iterations. I chose to merge the two earlier boards into one, set the system constraints, made the design decisions recorded as "owner rulings" (for example two independently fused parachute channels, and keeping the backup altimeter fully separate), and reviewed the layout, flagging routing problems such as unwanted zigzag traces.
AI coding assistants: they produced most of the schematics, PCB layout, simulations, firmware and scripts from my requirements and decisions.
Co-Authored-By: Claude line. AGENTS.md (read by Codex, and by Claude Code through CLAUDE.md) holds the safety and routing rules they had to follow.Collaborator and existing work:
m3_firmware/vendor/; KiCad library 3D models (CC-BY-SA 4.0 with exception); footprints and 3D models converted from the EasyEDA/LCSC library with easyeda2kicad. Details and licences: THIRD_PARTY_NOTICES.md.| Qty | Value | Footprint | References |
|---|---|---|---|
| 8 | 10k | R0402 | R2, R14, R18, R22, R40, R41, R42, R43 |
| 4 | 220R | R0805 | R24, R25, R26, R27 |
| 2 | 0R | R0805 | R50, R51 |
| 2 | 100k | R0402 | R1, R44 |
| 2 | 10nF | C0603 | C35, C36 |
| 2 | 1k | R0402 | R17, R21 |
| 2 | 22uF | C0805 | C2, C3 |
| 2 | AO3400A | SOT-23-3_L2.9-W1.3-P1.90-LS2.4-BR | Q3, Q4 |
| 2 | AON6403 | PDFN-8_L5.6-W5.2-P1.27-LS6.1-BL | Q1, Q2 |
| 1 | 470uF/25V | CAP-SMD_BD8.0-L8.3-W8.3-LS9.0-FD_H10.5 | C1 |
| 1 | ARM/PYRO | CONN-TH_6P-P5.08_DIBO_DB128V-5.08 | J4 |
| 1 | BAT+/BAT-/SW/SW | CONN-TH_4P-P5.08_DIBO_DB128V-5.08 | J1 |
| 1 | DNP | R0402 | R52 |
| 1 | J-IF1 power+drive | CONN-TH_12P-P2.00_S12B-PH-K-S-LF-SN | J10 |
| 1 | J-IF1 solder/test row | HDR-TH_12P-P2.54-V-M-1x12 | J10T |
| 1 | J-IF2 sense+ID | CONN-TH_9P-P2.00_S9B-PH-K-S-LF-SN | J11 |
| 1 | J-IF2 solder/test row | HDR-TH_9P-P2.54-V-M-1x9 | J11T |
| 1 | SERVO 3x4 | HDR-TH_12P-P2.54-V-M-R3-C4-S2.54 | J5 |
| 1 | SMBJ12CA | SMB_L4.6-W3.6-LS5.3-BI | D1 |

OAK-WJR/rocket-flight-computer
Amateur rocket flight computer: single-board KiCad PCB (STM32H743), firmware and diagnostics

OAK-WJR/rocket-flight-computer
Amateur rocket flight computer: single-board KiCad PCB (STM32H743), firmware and diagnostics

misko/prompt2device
The separate vNext PCB skill and orchestrator package is available alongside the reference workflow below; existing projects keep their accepted toolchain until an explicit migration.



potpurri/LiPo_Charger_TP4056_BuckBoost_TPS63020
This PCB is designed to safely charge a lithium-ion cell and provide a selectable 3.3V or 5V output. It's equipped with components that ensure safe charging and protection for the battery and supports flexible output…

ConquerToFreedom/SwasthEdge
Low-cost self-diagnosing edge controller for industrial sensor reliability



It measures 46 × 66 mm and has 4 copper layers, 1.6 mm thick.
36 parts, built around the AO3400A, AON6403 and SMBJ12CA. 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.
From the OAK-WJR/rocket-flight-computer repository on GitHub, at the commit this page was made from: the board is reference/m1_power_actuator/m1.kicad_pcb and its schematic m3_design/assembly_review/actuator_power.kicad_sch. PCBKit opens the board in the browser, with nothing to install.
Its repository states no licence, so its author keeps all rights: ask OAK-WJR before reusing the design.