The circuit, written as code and rendered four ways from one source.
draftgenerated from hardware/oapogee.tsx
This is a netlist, not a pinout
It says what connects to what, which is the design decision worth reviewing. It does not say which physical pin of any package a signal lands on. The pin numbers below are structural placeholders, assigned in the order the labels were written, not read from a datasheet.
That is deliberate. This project never publishes a number it has not measured or sourced, and a datasheet pin number recalled from memory is exactly the kind of confident, plausible, wrong figure that rule exists to prevent. Mapping these functional pins onto real packages is a separate step, done against datasheets, and it has not been done.
Do not lay a board out from this, and do not send anything here to a fabricator.
Power along the bottom left, the microcontroller in the middle with every bus leaving its right side, sensors and radio in a column on the right. Arranged to read the same way the system block diagram does.
Drawing
Power along the bottom left, the microcontroller in the middle with every bus leaving its right side, sensors and radio in a column on the right. Arranged to read the same way the system block diagram does.
100%
Drag to pan, scroll or pinch to zoom. With the drawing focused: arrows pan, plus and minus zoom, 0 fits.
Netlist
The same information as text. This is the form to review a change in, because it diffs.
A layout needs real footprints, real footprints need the datasheet pin mapping this design has not done, and an autorouted board built on placeholder pins would look far more finished than it is. That is the one thing this project must not ship, so the PCB and 3D outputs are deliberately not produced rather than produced with a caveat nobody reads.
How to change it
Edit hardware/oapogee.tsx and run make hw. The build fails if the committed drawing stops matching the source, so the schematic cannot drift from the design the way a hand-drawn one does. See hardware/README.md.