Robotics
Guided Class Project
Robot Maze Logic
Plan, predict, and debug a robot route using paper, a grid simulation, or optional hardware.
Open projectProgram / Robotics
Teach a machine to notice, choose, and act.
Robotics is the flagship long-term direction at School of Code. The first work builds reliable thinking through paper logic, simulations, simple electronics, sensor questions, micro:bit activities, and small physical systems.
The robotics loop
Sense → Decide → Act
SenseRead a button, distance, light, time, connection, or simulated world.
DecideUse a condition, state, goal, or threshold to choose the response.
ActMove, light an LED, sound a buzzer, display a result, stop, or correct.
Then the machine senses again. Feedback is the repeated comparison between what happened and what should happen.
Topic path
From exact commands to bounded autonomy.
Some links are full public topics; unlinked entries show planned direction. Listed systems are not promises that every hardware format is currently running.
- What Is a Robot?Program foundation
- Commands and SequencesTopic connection
- Movement and DirectionTopic connection
- Input and OutputPublic topic
- Sensors as QuestionsPublic topic and lesson
- Conditions and DecisionsCross-program topic
- Loops and Patrol BehaviourCross-program topic
- State and MemoryCross-program topic
- Motors and OutputsCurriculum direction
- Feedback and CorrectionPublic topic and lesson
- AutonomyPublic topic / bounded claims
- Robot Project DesignCurriculum direction
Class format
Start with the system, then add physical friction.
A paper route can expose sequence logic. An LED makes output visible. A button becomes input. A reaction timer introduces measurement and state.
Physical systems add useful complications: wires loosen, sensors vary, motors drift, and the real floor disagrees with the diagram. Students learn to separate code, hardware, and measurement questions instead of calling every failure a coding bug.
Projects move from a clear problem through theory, guided construction, modification, testing, and demonstration. Hardware is used when it clarifies the idea.
Six public projects
Commands, circuits, sensors, and feedback.
Robotics
Guided Demonstration
LED Traffic Light
Design a timed traffic-light sequence, then add a pedestrian input or state rule.
Open project
Robotics
Guided Class Project
Button and Buzzer Alarm
Connect a button input to visible and audible outputs, then improve the alarm's state rules.
Open project
Robotics
Computer Lab Project
Conductors and Insulators Lab
Build a careful test circuit or simulation and classify materials from observable evidence.
Open project
Robotics
Guided Class Project
micro:bit Reaction Timer
Measure reaction time, store results, and decide what makes a timing test fair.
Open project
Robotics
Computer Lab Project
Robot Patrol Challenge
Design a patrol that repeats, senses a changed world, and uses feedback to recover.
Open projectComputer Lab connection
One robot rule can become several systems.
A class may establish commands, threshold decisions, or feedback. In Lab time, that idea can become a maze route, an alarm, a traffic light, a reaction timer, or a patrol challenge with multiple valid solutions.
Explore structured Lab workA sensor measures. The program decides.
Parents can look for a concrete explanation: what entered the system, what rule used that information, what output followed, and what changed after a failed test.
Read the parent guideAsk how introductory robotics begins.
Current format, device needs, and hardware arrangements are confirmed directly before a group begins.