Session by session
- Session 21 · Ask & understandWeek 11
Latency, bounce and why timing matters
Evidence: a question, sketch or new vocabulary
- Session 22 · Build & designWeek 11
Add timestamps at every stage
Evidence: a design draft, dataset or build
- Session 23 · ImplementWeek 12
Implement debounce and a refractory window
Evidence: a working version, explained once
- Session 24 · Test & improveWeek 12
Measure delay under repeated triggers
Evidence: a test log with at least one failure
- Session 25 · Explain & reflectWeek 13
Report the median and worst-case delay
Evidence: an individual explanation
- UNO
- sound module
- relay module
- LED
- logging computer
Fifty timed triggers; delay reported as a median and a worst case.
A physical circuit, sensor or mechanism, built and tested on the bench.
Completion needs the artefact, an honest test log, an individual explanation and no open safety or privacy issue.
Projects in the same block
- RoboticsG12-P05
Trigger Timing and Latency Lab
A debounced trigger window and a measured end-to-end delay for the sound channel.
Sessions 21-25Builder and up - RoboticsG12-P06
Power-Budget Bench
A measured power budget for the model room, with a battery-life estimate checked against a timed run.
Sessions 26-30Builder and up - AIG12-P07
False-Trigger Budget Study
An operating threshold justified by the cost of false triggers against missed knocks.
Sessions 31-35Builder and up - IntegratedG12-P08
Confidence-Gated Smart Room
A smart-room link that acts only on confident, fresh predictions and logs every decision.
Sessions 36-40Builder and up
For school leadersChoose a starting point.
Build from evidence.
Pick the classes and a plan. We map the timetable, kit and safety checks with you, then pilot one class first.
- Prospectus and class-wise plan
- Kit and readiness check
- Pilot one class first
- Evidence at every milestone
Let's plan your pilot.
Share a few details and we will send the right plan for your classes.