Skip to content

Parent & teacher guide

Week 1: What Makes Something a Robot?

Session length: 60-75 minutes

Learning purpose

Students figure out what actually makes something a robot instead of just a machine. They learn that a robot senses the world, decides what to do, and then acts - the input, processing, output loop - and that a program is what makes it repeat the job on its own. They investigate real devices, map one as a robot system, and sketch a helpful robot of their own.

Expected student outcomes

By the end of this week, students can:

  • Explain what makes something a robot rather than a simple machine
  • Describe the input, processing, output loop in a real device
  • Explain the role of the controller as the robot's brain
  • Identify the sensors and actuators in a robot
  • Tell the difference between autonomous and remote-controlled systems
  • Design a robot system for a useful task
  • Sketch a helpful robot and label its inputs, processing, and outputs

Suggested pacing

About 60-75 minutes. Adjust to your group - these are guides, not limits.

StepFocusMinutes
What makes a robot a robotSense, decide, act, and the input-processing-output loop.15 min
Robot-or-Not investigationSort real devices using the sense/decide/act test.15 min
Robot System MapperMap one device's input, processing, output, and parts.15 min
Helpful Robot design challengeSketch a helper robot with labeled parts.15 min
Knowledge checkFive questions on robots, parts, and the loop.8 min
ReflectionWrite about machines vs robots and a helper you'd want.7 min

Before you start

Set up

  • Gather three or four everyday devices that range from clearly-a-machine to clearly-a-robot.
  • Print the Robot System Mapper worksheet, one per student or pair.
  • If using kits, charge them and pre-load a simple sensor behavior; if using the simulator, open it on each device.

Prepare ahead

  • Try the robot-or-not sort yourself so you can guide borderline cases.
  • Have a robot vacuum or automatic-door example ready as a familiar autonomous system.

Materials

  • Three or four everyday devices to investigate (toy, phone, flashlight, robot vacuum, etc.)(Kit, Simulator, Unplugged)
  • Robot System Mapper worksheet (printable)(Kit, Simulator, Unplugged)
  • Pencil and paper for sketching(Kit, Simulator, Unplugged)
  • A programmable robot kit, if available(Kit)
  • Computer or tablet with a browser(Simulator)
  • Recycled boxes, markers, and craft supplies for a robot modelOptional(Unplugged)

Safety

  • cautionKeep fingers, hair, and loose clothing away from moving wheels and gears on kit robots.(Kit)
  • cautionDo not open or take apart real appliances; investigate by watching them work.(Unplugged)
  • infoTake a short screen break if your eyes get tired using the simulator.(Simulator)

Running the session

  1. 1.Start with the sense/decide/act test and the input-processing-output loop before any devices come out.
  2. 2.Run the Robot-or-Not investigation, pushing students to justify each placement.
  3. 3.Model one Robot System Mapper together, then let pairs map a second device.
  4. 4.End with the Helpful Robot sketch and the knowledge check.

Common misconceptions

  • 'Anything electronic is a robot' - a flashlight is electronic but can't decide.
  • 'If it moves, it's a robot' - a wind-up toy moves but doesn't sense or decide.
  • Mixing up sensor and actuator - one measures, one acts.

Questions to ask

  • How does this device know when to act?
  • What would happen if we removed its sensor?
  • Is a person deciding here, or is the device deciding?

Classroom & group adaptations

Make it easier

Use picture cards of devices and sort them as a group instead of mapping the full loop.

Make it harder

Have students map a device that can be both autonomous and remote-controlled, and explain when it is each.

Groups & whole class

In pairs or small groups, give each student a role that rotates - driver (builds or types), navigator (reads the plan), and recorder (fills the worksheet) - so everyone participates. For a whole-class demo, run one shared robot or simulator on the board, have students predict together, then let groups repeat it on their own path. Groups can also mix paths: one builds on the kit while another checks the same idea in the simulator or unplugged, then they compare results.

Hardware and no-hardware notes

Every activity this week runs three ways - all three teach the same core idea, so pick whichever fits your room. No specific product is required.

Kit

  • Three or four everyday devices to investigate (toy, phone, flashlight, robot vacuum, etc.)
  • Robot System Mapper worksheet (printable)
  • Pencil and paper for sketching
  • A programmable robot kit, if available

Simulator

  • Three or four everyday devices to investigate (toy, phone, flashlight, robot vacuum, etc.)
  • Robot System Mapper worksheet (printable)
  • Pencil and paper for sketching
  • Computer or tablet with a browser

Unplugged

  • Three or four everyday devices to investigate (toy, phone, flashlight, robot vacuum, etc.)
  • Robot System Mapper worksheet (printable)
  • Pencil and paper for sketching
  • Recycled boxes, markers, and craft supplies for a robot model

Troubleshooting

Common problems from this week's activities and what to try.

  • The robot just drives straight and never reactsKitTry: Load a behavior that uses a sensor (like stop-at-wall) so students can see it decide.
  • Not sure what the simulator robot is sensingSimulatorTry: Point out the sensor read-out in the sim and match it to the robot's action.
  • Everything looks like 'just a machine'UnpluggedTry: Ask which device changes what it does without a person - that is the sensing-and-deciding clue.
  • Can't tell the sensor from the actuatorKitTry: A sensor measures; an actuator moves. Ask which part causes motion.
  • Processing box is blankSimulatorTry: Write the rule as 'if the sensor says X, then do Y'.
  • Not sure what the controller isUnpluggedTry: It is the hidden 'brain' that gets the sensor's message and tells the actuator to act.
  • The robot has no sensorKitTry: Ask: how does it know when to act? That is where a sensor goes.
  • The idea is too big to drawSimulatorTry: Shrink it to one job the robot does on one small grid.
  • Model has no moving partUnpluggedTry: Add a flap, wheel, or arm to stand in for the actuator.

Knowledge-check answer key

Answers are shown here for the adult only - the student worksheet keeps them hidden.

  1. 1. Decide what kind of system this is.

    Correct answer: A remote-controlled machine

    Why: A person decides every move through the handset, so it is remote-controlled, not an autonomous robot.

  2. 2. Which of these are actuators? Select all that apply.

    Correct answer: A motor that spins a wheel; A buzzer that makes a sound; A light the robot turns on

    Why: Actuators are the parts that act - motors, buzzers, and lights. A sensor only measures, so it is not an actuator.

  3. 3. What makes something a robot instead of just a machine?

    Correct answer: It can sense, decide, and act on its own

    Why: A robot senses the world, decides what to do, and acts - and it does this on its own by following a program.

  4. 4. In the input-processing-output loop, what is the 'processing' step?

    Correct answer: The controller decides what to do with the input

    Why: Processing is the 'thinking' step: the controller takes the input and decides which output to make.

  5. 5. Which part of a robot is the actuator?

    Correct answer: The motor that turns the wheel

    Why: Actuators are the parts that act - motors, wheels, grippers, buzzers, and lights.

  6. 6. A robot vacuum cleans a room by itself with no one steering it. This is an example of a system that is:

    Correct answer: Autonomous

    Why: Autonomous systems use their own program and sensors to decide, with no person steering.

  7. 7. Why does a robot need a program?

    Correct answer: So it can do a job the same way on its own, again and again

    Why: A program is the list of instructions the controller follows so the robot can repeat a job by itself.