Session by session
- Session 16 · Ask & understandWeek 8
Map predictions to named commands only
Evidence: a question, sketch or new vocabulary
- Session 17 · Build & designWeek 9
Rehearse the link in a simulator first
Evidence: a design draft, dataset or build
- Session 18 · ImplementWeek 9
Validate every command on the controller
Evidence: a working version, explained once
- Session 19 · Test & improveWeek 10
Test stale, unknown and low-confidence input
Evidence: a test log with at least one failure
- Session 20 · Explain & reflectWeek 10
Show that the manual switch always wins
Evidence: an individual explanation
- P02 and P03 builds
- USB or simulator
- manual override switch
Twenty recorded patterns plus invalid, stale and low-confidence cases.
A laptop model sends named commands only after bench tests, with a simulator as fallback.
Completion needs the artefact, an honest test log, an individual explanation and no open safety or privacy issue.
Projects in the same block
- RoboticsG12-P01
Sound-Sensor Characterisation Bench
A characterised sound-sensor channel with a measured noise floor and a justified trigger threshold.
Sessions 01-05All plans - RoboticsG12-P02
Fail-Safe Relay Switch
A relay-switched low-voltage lamp that is off by default and always obeys a manual switch.
Sessions 06-10All plans - AIG12-P03
Knock-Pattern Classifier
A classifier that tells three knock patterns from background noise using timing features, not recordings.
Sessions 11-15All plans - IntegratedG12-P04
Knock-to-Light Link
A laptop model that sends named lamp commands to a relay controller that rejects unknown, stale or unsure input.
Sessions 16-20All plans
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.