Session by session
- Session 16 · Ask & understandWeek 8
Map predictions to bounded state names
Evidence: a question, sketch or new vocabulary
- Session 17 · Build & designWeek 9
Use a simulator before any motor link
Evidence: a design draft, dataset or build
- Session 18 · ImplementWeek 9
Compare predicted and rule-based states
Evidence: a working version, explained once
- Session 19 · Test & improveWeek 10
Require operator approval for physical runs
Evidence: a test log with at least one failure
- Session 20 · Explain & reflectWeek 10
Test stale data and unknown states
Evidence: an individual explanation
- P02/P03
- USB or simulator
- approved stop control
Twenty recorded states plus invalid/stale 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
- RoboticsG11-P01
Line-Sensor Calibration Bench
A calibrated line-sensor array and Arduino input program.
Sessions 01-05All plans - RoboticsG11-P02
Line-Following Control Core
A low-speed line follower with a safe lost-line state.
Sessions 06-10All plans - AIG11-P03
Python Sensor-State Classifier
A reproducible classifier for recorded sensor states.
Sessions 11-15All plans - IntegratedG11-P04
AI Route-State Adviser
A laptop-based AI adviser for a line-following model; physical deployment is supervised.
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.