What students build
- A repeatable patrol
- An obstacle signal
- At least one response state
- A correction and recheck
- A stop rule
- A demonstration scenario
Computer Lab Project
Computer Lab ProjectRobot Patrol Challenge
Patrol a route until an obstacle appears, then choose a response that does not involve turning forever in a corner.
Visible system / hidden curriculum
Build something clear enough to test.
What students learn
- Sense-Decide-Act
- Feedback loops
- State
- Recovery logic
- Edge-case testing
- Limits of autonomy
What students need
- Paper state machine or browser simulation
- Optional robot platform and teacher-arranged sensors
Simulation-friendly. Physical robot hardware is optional and not promised; the project remains valid as logic, state, and simulation work.
Computer Lab character
Mission, constraints, and several correct solutions.
This is not a complete teacher-led recipe. Students choose an implementation path, use checkpoints, test the system, and explain the decisions.
Required systems
What must exist.
- A repeatable patrol
- An obstacle signal
- At least one response state
- A correction and recheck
- A stop rule
- A demonstration scenario
Suggested build order
One useful route through the problem.
- Define the patrol Choose a short route and what counts as one cycle.
- Define the sensor question Choose what obstacle evidence the system reads.
- Create response state Stop, turn, signal, or choose another route.
- Recheck after acting Sense again before returning to patrol.
- Test traps Try corners, repeated obstacles, and sensor noise.
Checkpoints
Evidence that the system is becoming reliable.
- 1The normal route repeats reliably.
- 2The normal and blocked readings are distinguishable.
- 3Obstacle input changes state once.
- 4The correction is tested rather than assumed.
- 5At least one recovery failure is repaired.
Challenge cards
Change the lesson idea without repeating its first form.
Choose one card, combine compatible cards, or propose an equivalent challenge. More than one implementation can satisfy the mission.
Add a second recovery route.
Count patrol cycles.
Signal for human help after repeated failure.
Compare two feedback strategies.
Test it
Try the edges, not only the easy success.
- Does patrol repeat from a known state?
- What exact signal means obstacle?
- Can recovery loop forever?
- Does the system recheck?
- Is there a human stop rule?
Common mistakes
Read the clues before changing code.
- Obstacle checks happen outside the patrol loop.
- Recovery has no exit condition.
- State is changed in several places.
- Successful movement is called intelligence without explaining rules.
Improve it
Preserve the core system while changing the project.
- Add a second recovery route.
- Count patrol cycles.
- Signal for human help after repeated failure.
- Compare two feedback strategies.
Challenge levels
Choose meaningful difficulty.
Builder
Stop and signal reliably at an obstacle.
Inventor
Correct course and rejoin patrol after checking again.
Boss Level
Track failed options and request human help at a defined limit.
Show-teacher checkpoint
Demonstrate the working decisions.
- Normal patrol
- Sensor question
- Decision rule
- Correction
- Recheck
- One stated autonomy limit