SSTM

Smart Safety & Telemetry Module (SSTM) — Small Autonomous Rover

24-hour embedded systems design challenge submission.

What this module does

Monitors battery voltage, current draw, internal temperature, motion/orientation (IMU), and one external proximity sensor. Fuses this into a fault state, streams telemetry to the rover's main computer over UART, and drives a local RGB status LED + buzzer for stand-alone warning even if the main computer is down or not listening.

Folder guide

RoverSafetyModule/
├── README.md                    <- you are here
├── docs/
│   ├── 01_architecture.md       <- block diagram, data/power/comm flow
│   ├── 02_component_selection.md<- every part + why, with datasheet links
│   ├── 03_calculations.md       <- power budget, dividers, shunt, decoupling, thermal
│   ├── 04_electronics_design.md <- schematic description, protection, pin maps
│   ├── 05_pcb_design.md         <- stack-up, placement, routing, dimensions
│   ├── 06_firmware.md           <- architecture, RTOS rationale, fault handling
│   ├── 07_testing_plan.md       <- bring-up + fault diagnosis plan
│   └── 08_tradeoffs.md          <- priorities, risks, V2 plan
├── firmware/                    <- FreeRTOS/STM32 HAL source (buildable skeleton)
├── bom/BOM.csv                  <- full bill of materials
├── datasheets/links.md          <- every datasheet referenced
└── pcb/                         <- floorplan + stack-up notes (no KiCad GUI here — see below)

Honest scope note

Everything here is real, defensible engineering content: component choices, calculations, pin-level connection tables, and working firmware architecture. The one thing I could not produce in this environment is an actual .kicad_pcb/.kicad_sch file, because that needs the KiCad GUI/EDA engine, which isn't available here. Instead docs/04_electronics_design.md and docs/05_pcb_design.md give you exact net-by-net connection tables and a placement floorplan — this is normally the slow part (part selection + deciding connections); transcribing it into KiCad schematic/PCB editor is comparatively fast (roughly 1–2 hrs) and I'd suggest doing that next while the rest of the report is fresh. I can also walk you through KiCad step-by-step in real time if useful.

Suggested order of attack for your remaining time

1. Skim 01_architecture.md and 02_component_selection.md — make sure you can defend every choice out loud (that's what's being graded).
2. Enter schematic in KiCad using 04_electronics_design.md (connection tables).
3. Lay out PCB using 05_pcb_design.md (floorplan, stack-up, keepouts).
4. Skim/compile firmware/ — it's a working task-based skeleton you can extend.
5. Read 07_testing_plan.md and 08_tradeoffs.md — these are pure writing, fastest points to bank.