Programming a Floor Robot

Programming a Floor Robot

1 / 31
next
Slide 1: Slide
New lesson editorComputingPrimary Education

This lesson contains 31 slides, with interactive quizzes and text slides.

time-iconLesson duration is: 50 min
Report this lesson

Items in this lesson

Programming a Floor Robot

Open with the idea that a robot only moves when we give it clear instructions. Keep language concrete and linked to movement in the classroom.

Our learning goal

I can give clear directional commands to program a floor robot and improve my instructions if they do not work.

This item has no instructions

What words make you think of giving a robot instructions?

Use this as a prior-knowledge activation after the learning goal. Accept everyday words such as go, stop, left, right, robot, buttons and instructions, then connect them to programming vocabulary.

About this lesson

This KS1 computing lesson explores Programming a Floor Robot. Pupils use directional commands to program a simple floor robot, test a route and improve the instructions when the robot does not reach its target. It is suitable for classroom teaching, independent practice or a clear recap of the topic.

The user requested this SEO introduction verbatim on its own slide near the start, so keep it exactly as written.

What is programming?

Programming means giving instructions.


A floor robot follows the instructions in order. It cannot guess what we mean.

Stress that computers and robots are precise. Link to everyday instructions such as getting ready or brushing teeth.

What we already know

Before we program a floor robot, it helps if we can:

  • follow simple instructions

  • use words like forwards, backwards, left and right

  • take turns and watch carefully

  • notice when something has gone wrong

This slide covers prior knowledge without turning into an activity. Briefly check understanding through teacher talk if needed.

Direction words

We use direction words to tell the robot how to move.

  • forwards

  • backwards

  • left

  • right

Clarify that turning left or right is different from moving forwards or backwards. Model with your own body if helpful.

Commands

A command is one instruction.


Examples:

  • move forwards one step

  • turn left

  • turn right

  • move backwards one step

Use the exact word 'command' consistently through the lesson. Keep examples short and concrete.

Instructions must be in order

The order matters.


forwards, turn right, forwards is not the same as turn right, forwards, forwards.


A robot follows each command one by one.

This is a key computing idea: sequence. Emphasise that changing the order changes the result.

A sequence

A sequence is a set of commands in the right order.


Good programming means choosing the right commands and putting them in the right sequence.

If you use physical command cards in class, link them directly to the idea of a sequence.

What is one instruction called?

A

a target

B

a command

C

a robot

D

a test

Checks the key vocabulary from slides 3 to 6. Distractors come from nearby lesson words pupils may confuse.

Complete the programming ideas

Programming means giving instructions. One instruction is a command. Commands in the right order make a sequence.

instructions
command
sequence
target
testing
robot
route

Reinforces the load-bearing vocabulary: instructions, command and sequence.

Planning a route

Before pressing go, we can plan.

  • look at the start

  • look at the target

  • count the moves

  • think about any turns

  • say the commands aloud

Planning before running the robot helps pupils avoid random guessing and supports debugging later.

Start and target

When we plan a route, we need to know:

  • where the robot starts

  • which way it is facing

  • where we want it to finish

Facing direction is often missed by younger pupils. Point it out clearly because it affects the first command.

Testing the program

After we enter the commands, we test the program.


Testing means watching what the robot really does, not just what we hoped it would do.

Use precise but age-appropriate wording. Testing is observing the actual result.

Checking each step

When we test, we can check:

  • Did the robot move the right way?

  • Did it turn at the right time?

  • Did it stop at the target?

  • Did it follow every command?

Encourage careful observation rather than rushing to press buttons again.

What should you check before pressing go?

A

the target only

B

the colours only

C

start, facing, target

D

the robot's name

Based on planning slides 9 to 12. The correct answer combines the three things named on the content slides.

Fill in the planning and testing words

Before we press go, we can plan the route. After we enter the commands, we test the program. Then we check each step carefully.

plan
test
step
guess
jump
turn
button

This echoes the lesson wording: plan, test and check each step.

When the route goes wrong

Sometimes the robot does not reach the target.


That does not mean we have failed. It means we need to look again at our commands.

Normalise mistakes as part of programming. This prepares pupils for debugging.

Debugging

Debugging means finding and fixing a mistake in a program.


We might need to:

  • change a command

  • add a missing command

  • remove a wrong command

  • put commands in a better order

Use the word 'debugging' repeatedly so pupils hear it in context, not as an isolated vocabulary item.

Improve and try again

Program → Test → Check → Fix → Test again


Programmers often try more than once. Each new try helps make the program better.

This simple cycle captures the core process of programming for KS1 without overcomplicating it.

Using what we know

To program a floor robot well, we:

  • choose clear commands

  • put them in order

  • test the route

  • debug if needed

This is a summary slide before application. Use it to connect all the key vocabulary into one routine.

Application task

Use a start point and a target on a mat.


Plan a sequence of commands for the floor robot. Test the route. If the robot does not reach the target, debug the program and improve it.

The user asked for an application activity. Keep it broad so it fits different classroom resources, such as Bee-Bots, Blue-Bots or paper grids.

Making it fit everyone

Extra support

  • use arrow cards

  • work with a shorter route

  • say each command aloud

  • have an adult model the first step

  • plan a longer route

  • include more turns

  • spot and fix a mistake independently

  • explain why the new sequence works

Extra challenge

The user requested differentiation. Present it as support and challenge options rather than labels for children.

If the robot misses the target, what do we do next?

A

start dancing

B

put it away

C

debug the program

D

ignore the mistake

Checks understanding of debugging from slides 13 to 16 in simple child-friendly language.

What might help fix the program?

1

change a command

2

add a command

3

remove a command

4

change the order

This item has no instructions

What does debugging mean?

Expected answer elements: pupils should mention that you look for the mistake and fix it, such as changing, adding, removing or reordering commands.

What is one thing you learned today?

Encourage pupils to say one thing they learned, such as command, sequence, testing or debugging. No single correct answer.

One word for what helped you most today

Useful for quick reflection on supports such as watching, planning, saying commands aloud, testing or using arrow cards.

How do you feel about programming a floor robot now?

This item has no instructions

Glossary

programming - giving instructions to a computer or robot

floor robot - a robot that moves across the floor by following commands

command - one instruction

sequence - commands put in the right order

test - try the program to see what happens

debugging - finding and fixing mistakes in a program

target - the place the robot is trying to reach

This item has no instructions