In development · Hardware and firmware
Button Box
A sim-racing control box designed properly — board, enclosure and firmware, not a hot-glued panel.
Sim racers who would rather build the good one than buy the third mediocre one.
- Built on
- KiCad + STM32
- No vendor code
- Every layer in the build is one you can read
- History
- 13 commits, in a private repository
What it is
The electrical and mechanical design for the Mission City Motorsport button box: schematic, board layout and enclosure, drawn against the in-house KiCad library so footprints and symbols stay consistent with the rest of the hardware portfolio.
Capabilities
What it actually does.
Sim racers who would rather build the good one than buy the third mediocre one.
KiCad schematic
KiCad schematic and PCB layout with matching mechanical design
Built on the
Built on the shared in-house symbol and footprint libraries
How it works
3 moves, end to end.
This is how Button Box works, not a set of steps you can follow yet — it is in development and not distributed.
Start from the platform
The build has no generated vendor code in it, so the first layer is already readable.
Bring up the board
Drivers, clock tree and peripherals are hand-written and unit-testable off-target.
Ship and debug it
When something is wrong, the layer that is wrong is one you can open.
Specification
Made of, and made when.
Read from the repository at build time rather than typed onto a marketing page.
- State
- In development
- Discipline
- Hardware systems
- Shape
- Hardware and firmware
- Started
- Aug 2026
- Last change
- Aug 2026
- Commits
- 13
- KiCad
- STM32
- Mechanical CAD
- Python 100%
Next
Build on Button Box
Ask about licensing the platform, a board bring-up, or contract firmware work.