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 1
Level 1 · Lesson 1 · EV3-L01-0160 minutes · Ages 7+ · Model: Driving Base
The Driving Base: a small robot on two wheels. Each wheel has its own motor. A little wheel at the back, called a castor, stops it tipping over.
It is the simplest model in the course. It is also the one that matters most. Almost every robot you build after today sits on it. Sensors, arms and grabbers all fix onto this same base. Build it well once. Then you can use it all year.
By the end, it will drive as far as you choose. Then it will come back. It will turn to face where you point. And it has no steering wheel!
Some wheelchairs have a motor. They have one big wheel on each side. Each wheel has its own motor. There is no steering wheel. The driver pushes a small stick. The chair works out how fast to spin each wheel.

This is called differential drive. The two wheels can turn at different speeds. So the chair can turn on the spot. A car needs lots of space to turn. Its front wheels only tilt a little. A wheelchair must turn in a small doorway. Two wheels with a motor each can spin it round its middle.
What if the chair had one motor and a steering wheel? To turn round in a hall, it would go back and forth. Your robot is the same. With one motor, it can only drive in curves. You could not do many of this year’s challenges.
A robot with a motor on each wheel needs no steering wheel. To turn, it makes one wheel do something different.
That is the big idea of this lesson. Say it out loud before you touch a brick:
Same speed on both wheels → straight. Different speeds → a curve. Opposite directions → it spins on the spot.
The rest of today is about making that happen every time. The EV3 has blocks just for this. The box below shows how they work. You will come back to it all year.
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.
Say this back before moving on: “My robot has one motor per wheel. If I want it to turn, I change what one wheel is doing.”
Before reading on: look at your model and find the electronic parts. Not the beams, axles or wheels — the parts with cables. How many are there?
Three. Here they are:
The Large Motor is the big, strong one. It is strong enough to move the whole robot. So we use it to drive. The Medium Motor is smaller and faster. It does other jobs. You will meet it in the next lesson, the Wipers.
No sensors today. This robot cannot see or feel anything yet. It does just what it is told, for as long as it is told. Remember that when it drives into a table leg!
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.
The number ports are at one end of the Brick. The letter ports are at the other end. Today you only need two letter ports.
| Part | Port | Why this one |
|---|---|---|
| Large Motor, left wheel | B | B and C are the usual pair for driving. Every movement block in this course uses them. |
| Large Motor, right wheel | C | Everyone uses left = B and right = C. Then another group’s program will work on your robot too. |
Check your own wiring now, before going further:
This is the main reason a driving base does nothing at all. You cannot see it in the program. The blocks are all right. But the robot still will not drive. Watch what happens when the cables and the block do not match:
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.
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.
Two things often go wrong here. First, the Brick may have gone to sleep. Press the centre button and try again. Second, you may connect to the next group’s robot. That is why your Brick’s name matters. Does a robot across the room drive when you press play? Then that is what happened!
A plugged-in cable does not mean the Brick is connected. Before you run anything, check what the app can see.
Check: does the screen match the robot in front of you?
Two motors in B and C should show as two motors in B and C. If a port shows nothing, the problem is the wire, not the program. Go back to the port check above. Fix it now. From here on, the app must see both motors.
Now change one thing at a time, and predict before each run. Predict means guess what will happen. A wrong guess teaches you something. Watching without guessing teaches you nothing.
That last one tricks almost everybody. Rotations count how far the wheels turn, not for how long. So a slow robot goes just as far. It just takes longer. Try it in the lab below first. Then try it on the floor.
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.

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.
The same build on Google Drive — sometimes a video, sometimes a scan:
Fullscreen it while you build — you can pause and scrub with the player's own controls.
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.
This is the smallest program that makes the robot do its job. It has three blocks:
when program starts :: events hat set movement motors to [B v] and [C v] :: movement move [forward v] for (2) [rotations v] :: movement
Read it in the order the robot runs it:
What success looks like: the robot drives in a straight line. It goes about 35 cm and stops by itself. It should not drift left or right. You should not need to touch it.
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:
Switch mats above and every route below is redrawn on the mat you chose.
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.
Start at HOME. The whole robot must be inside the start area. Drive to A and stop. The whole robot must be inside A. Do it three times from the same spot. It must land in A on all three runs, not just once.

Fullscreen it while you build — you can pause and scrub with the player's own controls.
Start at HOME and drive to A. Then turn and drive to B. The robot must end fully inside B. Nothing on the mat may be pushed out of place. To make the turn, change what ONE wheel does. Do not lift the robot and point it by hand.

Fullscreen it while you build — you can pause and scrub with the player's own controls.
Start at HOME. Go to A, then B, then back to HOME. End facing the way you began. Use rotations, not time. A program that uses waits will drift on the second run. You will see it.

Your robot is a delivery trolley. The drop-off keeps moving. You will be told the stop: A, B or C. But you are told only AFTER your program is written. You may not change it once you are told. Plan on paper before you build. What is the same about each route? What changes? Make the change one number that you set in one place. You will be asked two questions when you show it. How do you know it will reach the stop? What would you change if the mat were half the size? Have your answers ready.

Fullscreen it while you build — you can pause and scrub with the player's own controls.