What the board has to do
- Run a Teensy 4.0 flight computer and its sensors from a single battery for the whole flight.
- Measure altitude and motion, so the flight software can detect apogee and the main-deploy altitude.
- Log everything to a microSD card for analysis after recovery.
- Fire two deployment charges, drogue and main, only when armed and only when commanded, and report beforehand whether each charge is actually connected.
That last point drove the design more than anything else. A deployment circuit that fires early is dangerous, and one that doesn't fire loses the rocket.
Architecture
Click a block to see what it does and why I chose it.
Copper lines carry power. Thin dashed lines are data buses.
How I chose components
For the sensors I compared candidates side by side in a decision matrix weighted toward reliability and noise performance. The matrices went into the design documentation, so reviewers could see why a part was chosen and not just which one.
Alongside the schematic I produced the wiring diagrams, pin maps and BOM, plus a list of validation checkpoints (continuity and signal-path checks) for when the board is built.
PCB layout
Status and next steps
Next comes fabrication and assembly, then bring-up: verifying each power rail under load, checking every bus with a scope and logic analyzer, and testing the continuity and fire circuits with dummy loads long before any real charge is connected. I'll update this page as each step happens.