Basic
Follow the black line from the start box to Home. Stop fully inside Home.

Quick Learn — the model, the instructions, the program and the challenges. The theory is in Full Lesson.
EV3 Robotics›Level 1 · Beginner›Lesson 28
Level 1 · Lesson 28 · EV3-L01-2860 minutes · Ages 7+ · Model: Road Roller
The Road Roller: two Large Motors drive the back wheels. At the front, three big tyres are squeezed together on one axle. They make a heavy roller.
A roller does the same job again and again. It goes up a strip of road, then comes back down. Then it goes up again. It keeps going until the road is flat.
This model will catch out something you have believed since the Folding Fan in Lesson 4. You have often written “out four rotations, back four rotations”. You called it equal and opposite. Today you do it five times in a row. You will find the robot is nowhere near where it started!
Wherever workers are fixing a road. The new road surface goes down hot and loose. The roller goes over it again and again. Then it is hard enough to drive on.

The roller is heavy, and it is wide and smooth. Its weight presses the loose surface together. Being wide, it covers a big strip each time. Being smooth, it leaves no marks.
And one trip is never enough. It takes lots of trips to press it flat. So a roller driver spends all day going back and forth. Most people would think the road was already finished!
Now for the real problem in today’s lesson. Each trip must go over the same strip. Say the roller drifts a few centimetres to the side each time. After ten trips, it is rolling somewhere else! One strip got rolled ten times. A strip at the edge got missed.
You would never notice a small mistake once. But repeat it, and it becomes a big mistake. The machine is not broken. It is just maths.
Every real movement is a tiny bit wrong. Repeat it, and the mistakes do not cancel out. They add up.
Say a motor block says 4 rotations. The motor really does turn four times. The Brick counts them, and it is right. The problem is between the motor and the floor. The tyre grips a little differently each time. The floor is not perfectly flat. And the cable gives the machine little pushes.
| What you assumed | What actually happens |
|---|---|
| Out 4, back 4, so it comes back to the start. | It comes back to nearly the start. It is a few millimetres off. |
| Do that five times, and it is still at the start. | Those few millimetres have become a few centimetres. They are all in the same direction. |
The important words are same direction. Say the mistakes went any old way. Some would go too far. Some would go too short. They would roughly cancel out. But they do not go any old way. Maybe one tyre grips a bit less, or a cable pulls one way. That cause pushes the same way every time. So the mistakes add up.
Measure your robot after ten runs, not one. One run tells you very little about how a machine really works.
A driving base has two Large Motors, one per wheel. You could drive them with two separate motor blocks — but they would never start at quite the same instant, and the robot would curve away. EV3 has a separate family of Movement blocks that treat the pair as a single driving base.
| Block | What it does |
|---|---|
set movement motors to [B v] and [C v] :: movement | Tells the Movement blocks which two ports are the driving wheels. Put it at the top of the program, before any movement. |
move [forward v] for (2) [rotations v] :: movement | Drives both wheels together, so the robot travels in a straight line. |
move for (1) [rotations v] at (75) (25) % speed :: movement | Drives the two wheels at different speeds, which makes the robot curve. |
set movement speed to (50) % :: movement | Sets how fast the driving base travels from now on. |
set movement motors to [B] and [C] is the block that decides which two motors every Movement block after it will drive. It does not look at the robot. It drives the two ports you name, whether or not there is a motor in them — so those two letters have to be the two sockets the cables are actually in.
This is the single commonest reason a driving base does nothing, and it is invisible in the program: every block is spelled correctly and the robot still will not go.
the same program on both robots
The yellow outline marks the two ports the block is driving. A robot only goes straight when both of them have a motor in them.
Both robots run the identical program. The left one has its motors in B and C, so both named ports have a motor and the robot drives straight. The right one is plugged into A and B: the block drives B, finds nothing in C, and never mentions the motor in A at all — so one wheel turns, one wheel sits there, and the robot swings round the dead one instead of driving.
If neither named port has a motor in it — cables in A and D, say, with the block still set to B and C — the robot does not move at all. The program runs happily to the end and the Brick reports nothing wrong, because as far as it is concerned it did exactly what it was told.
So before you look for a bug in the program, look at the cables: read the port letters off the Brick, then make the block say those two. B and C are only the usual choice, not a rule — if your build has the driving motors in A and D, set the block to A and D and everything works.
Everything a driving base can do comes from those two speed numbers. Try each button below and watch the trail the robot leaves.
The path is worked out from the two wheel speeds in the block, not drawn by hand — so changing the preset changes the numbers and the shape together.
Notice there is no steering block anywhere in that program, and no steering part anywhere on the robot. The turn is made entirely by driving the two wheels different amounts.
when program starts :: events hat set movement motors to [B v] and [C v] :: movement move [forward v] for (2) [rotations v] :: movement move for (1) [rotations v] at (50) (-50) % speed :: movement
“Move forward 2 rotations” says nothing about the floor — it says how many times the wheels go round. How far the robot actually travels depends on how big the wheels are, and once round a standard EV3 driving wheel is about 17.5 cm.
Before doing any sums, get a feel for it. Drag the robot along and watch both scales at once — rotations on top, centimetres underneath, the same line. Land on the half marks: there is a number between 1 and 2, and it is 1.5.
Drag the robot, or use the arrow keys — it moves in half rotations. Rotations above the line, centimetres below.
1.5 — a half rotation past 1. Half a turn of the wheels is 8.75 cm, so halves matter.
35 ÷ 17.5 = 2. That is a number you can type straight into the block.
set movement motors to [B v] and [C v] :: movement set movement speed to (30) % :: movement move [forward v] for (2) [rotations v] :: movement
Steering at right 100 or left 100 drives the two wheels in opposite directions, so the base stops travelling and pivots where it stands. The angle it sweeps is a simple doubling of the rotations:
Half a rotation is the one worth remembering: a square corner, 90°.
| Rotations | The robot turns |
|---|---|
| 0.25 | 45° — half a corner |
| 0.5 | 90° — a square corner |
| 1 | 180° — turn round and face back |
| 2 | 360° — all the way round |
The one to memorise is 0.5 rotations = 90°. Everything else follows from doubling or halving it.
set movement speed to (20) % :: movement move [right: 100] for (0.5) [rotations v] :: movement
Turn slowly. The wheels on a driving base are big and the robot carries a lot of weight, so at full speed it keeps going after the motors stop and lands past the angle you asked for. Somewhere between 15% and 30% speed is where turns become repeatable. A turn that overshoots is almost always a turn taken too fast, not a wrong number.
These figures belong to your robot. The distance depends on the wheels and the angle depends on how far apart they are, so a wider base needs a different number for 90°. Test it, measure what actually happened, and adjust — the same discipline as the Gyro Sensor tolerance.
Every wheeled vehicle steers this way — a tank, a digger, an office chair with two driven castors. Cars use a steering rack instead, but a robot that turns by driving its wheels at different speeds needs no steering mechanism at all.
There are two ways to tell an EV3 motor how much to move: give it a length of time, or give it an amount of turn. Only the second one is repeatable, and that difference decides whether a machine works reliably or only sometimes.
| Block | What it does |
|---|---|
[A v] run [clockwise v] for (1) [rotations v] :: motors | One full turn of the motor shaft, then stop. The program waits for it. |
[A v] run [clockwise v] for (180) [degrees v] :: motors | Half a turn. 360 degrees is one rotation. |
The counters below tick up in step with the shaft, so you can watch a rotation being counted rather than take it on trust.
the same movement, written in degrees
The two motor read-outs are the same measurement — 1 rotation is 360°. Use whichever makes the number easier to read.
Notice that the two motor counters finish together: 2.00 rotations and 720° are the same instant, because they are the same measurement in different units. So pick whichever makes the number easier to read. A winch that needs eight full turns is clearest in rotations. A gate that lifts a quarter turn is clearest in degrees — 90 rather than 0.25.
The third counter is the one that catches people out. The block counts turns of the motor, not of the thing it drives — and the gear in the demo is three times the size, so two motor rotations move it only 0.67 of a turn. Ask for two rotations and the mechanism does not move two rotations’ worth unless the gearing is one to one.
That is why a number that works on one build has to be retuned when the gearing changes — the program is right, the mechanism is different.
A printer feeds paper an exact distance; a lift stops level with the floor; a robot arm returns to the same place a thousand times. None of that is possible by timing a motor — they all count turns.
Say this back before moving on: “A small mistake, the same way every time, becomes a big mistake.”
| Part | What it is doing here |
|---|---|
| EV3 Intelligent Brick | Runs the program. It also adds the weight the roller needs. |
| Large Motor ×2 | Ports B and C. They drive the back wheels. |
| The roller drum (no cable) | Three tyres squeezed onto one axle. No motor turns it. It is pulled along, and it is heavy on purpose. |
Do not blame the program yet. First find out which way your roller wants to go.
Sensors go in ports 1, 2, 3, 4. Motors go in ports A, B, C, D. You cannot swap them. If you do, nothing warns you. The robot just will not work.
| Part | Port | Why this one |
|---|---|---|
| Left rear motor | B | B and C are the pair. B is always on the left. |
| Right rear motor | C | To find right, stand behind the machine, facing the way it drives. |
| Sensors | none | Notice this today: the roller cannot tell that it has drifted. Only you can. |
Check your own build now:
Two routes, and either is fine. USB is the reliable one and the one to fall back on when a room’s Bluetooth is busy; Bluetooth leaves the robot free to move, which some models need.
Do these in order. Naming the Brick after you go looking for it in the list is how groups end up driving each other’s robots.
EV3 until somebody changes it.EV3.The two failures, every class, every time. The Brick has gone to sleep while you were building — press the centre button to wake it. Or you have paired with the group at the next table, which is why the name matters.
The long version, including Port View and how to read the port tiles, is in the Brick & Bluetooth guide.
Use Bluetooth. Today you must. Today you measure drift in millimetres. A dragging USB cable makes much more drift than that. Then your measurements would be useless.
This is a measuring lesson, so keep a table. Use three columns. Write what you changed, how far off it stopped, and which way.
Step 5 tells the truth. You did not get rid of the mistake. You only cancelled it out for one number of runs. To really fix it, the robot must check where it is. It could use a sensor, or read its own motors. You will learn that in the next levels.
A robot that cannot check where it is can only guess. That is true however carefully you tune it.

Build the model before you read any further. Everything after this is about making it do something, and none of it will make much sense with nothing on the table in front of you.
One page at a time — use Next and Previous, or the ← → keys. Fullscreen makes it big enough to build from.
Check the finished build against the picture before you switch anything on. A motor mounted the wrong way round is far easier to spot now than it is to debug later, when it looks like a program fault.
Six blocks: five trips up and down the same strip. Watch where it stops, not how it looks while it runs.
when program starts :: events hat set movement motors to [B v] and [C v] :: movement set movement speed to (40) % :: movement repeat (5) move [forward v] for (3) [rotations v] :: movement move [backward v] for (3) [rotations v] :: movement end
Read it in the order the Brick runs it:
What success looks like. Read this carefully! Today, success is not the roller stopping on the line. Success is running it and measuring how far off it is. Then you say which way the mistake went. Say a roller misses by two centimetres, and you measured it. That is better than a lucky run that nobody checked.
Measure both ways. How far in front of or behind the line did it stop? And how far to the left or right? These are two different mistakes, with two different causes.
This model drives, so its challenges are run on a mat. Mats differ between branches — check you are looking at the one in your room.

WRO 2019 RoboMission Elementary — Smart Passenger Transport · official WRO game mat, 2362 × 1143 mm
The challenges name these places rather than distances, so the same challenge works on any mat:
Written for the WRO 2019 RoboMission Elementary mat. Each one is a single program run that starts in the ✕ box.
Follow the black line from the start box to Home. Stop fully inside Home.

In one program run, follow the black line to Home, then on to School.

In one run, go to Home, then School, then the Zoo. Stay on the black line all the way.

In one run, go to Home, School and the Zoo, then the Shopping Center. Stay on the black line all the way.

In one run, charge at the Battery Area first. Then go to the Shopping Center, the Cinema, and finish at Home. Stay on the black line all the way.

Work through them in order — each is harder than the last. The extra challenge comes after all three, and it is meant to make you plan before you build.
Measure your drift truly. Drift is when the robot slowly ends up off its line. Run the out-and-back program ten times. Then measure how far from the start line the roller ended up. Note which way it went. Do all of this three times. Tell us all three results. If the numbers are close, the error has a cause.
Show that error builds up. See how far off it ends after 1 run, after 5 runs and after 10 runs. Do three tries of each. Tell us the three averages. Did ten runs really give about ten times the error of one?
Fix it, then break your fix. Change your forward and back numbers. Keep going until the roller comes back to the line after five runs. Then run the fixed program for fifteen runs. Measure again. Tell us both results. Say why a fix for five runs does not hold for fifteen.
Roll a strip well, and be truthful about how well you did it. Your roller must cover a marked strip on the mat. It goes over it again and again. It must end at a station your teacher names. It must stop within a hand's width of the right spot. You must also hand in your measurements. The run is only half the work. Plan on paper before you drive. Decide how many passes the strip needs. Then decide how you will know, at the end, that it stopped where you meant. Near is not the same as there. Two questions when you show it. Which way does your robot drift? What part of the build do you think causes it? And what would your robot need to fix the drift by itself?