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 29
Level 1 · Lesson 29 · EV3-L01-2960 minutes · Ages 7+ · Model: Tricycle
The Tricycle: two wheels at the back, and one wheel at the front. Each back wheel has its own motor. Like the Driving Base in Lesson 1, it really drives around a room.
And it has no steering wheel. Nothing points the front wheel anywhere. So how does it turn?
It makes one back wheel go faster than the other. That is all! Almost every robot you build will steer like this. Today you learn to control it with a number, not a guess.
The trishaw: a bicycle with three wheels that carries passengers. You can see them in many cities in Asia. They have three wheels, a rider, and seats for people. They are still used every day.

Three wheels always sit flat. A tricycle never rocks on a bumpy road, like a cart with four wheels can. That really helps on a road that is not flat.
A trishaw steers with handlebars, which turn the front wheel. Your robot cannot do that. But watch a trishaw turn. The outside back wheel goes further than the inside one, because it goes round a bigger circle. In every turn, one wheel goes further than the other. The trishaw does it by pointing the front wheel. Your robot does it by driving the back wheels.
A robot that only goes straight must be picked up and pointed again every time it changes direction. That is no use on a course. It is no use for finding its way anywhere.
Turning is not different from driving. It is driving, with the two wheels going different amounts.
One block, two numbers: the speed of the left wheel and the speed of the right wheel. The difference between them is the steering.
move for (1) [rotations v] at (50) (50) % speed :: movement
| Left / right | What the robot does |
|---|---|
| 50 / 50 | Straight ahead. Both wheels go the same distance. |
| 50 / 25 | A gentle curve to the right, towards the slower wheel. |
| 50 / 0 | A tight turn round the stopped wheel. That wheel stays where it is, and the robot turns round it. |
| 50 / −50 | A spin on the spot. The wheels go opposite ways. The robot turns, but does not go anywhere. |
That table is really one idea, not four. The robot always curves towards the slower wheel. The bigger the gap between the two numbers, the tighter the curve. Going straight is nothing special. It is just when the gap is zero.
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.
Drag the two numbers in the lab, and watch the trail. There is no “turn” command. There is only a left speed and a right speed.
Remember Lesson 25? On the Toddle Bot, two different speeds would break the model. Its motors were joined by one axle. Here, each motor drives its own wheel. So it is safe for them to disagree. The wheels just go different distances. The blocks are the same, but the advice is the opposite. The build makes the difference.
The robot curves towards the slower wheel. That one sentence explains all of steering.
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: “It turns towards the wheel that is going slower.”
| Part | What it is doing here |
|---|---|
| EV3 Intelligent Brick | Runs the program, and sits on the frame. Where its weight sits changes how well each wheel grips. |
| Large Motor ×2 | One for each back wheel, in ports B and C. They drive different wheels, so they are allowed to disagree. |
| The front wheel (no cable) | No motor drives it, and nothing steers it. It goes where the back wheels send it. Check it rolls and turns freely. |
If a tricycle will not drive straight, it is nearly always the build, not the program.
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 is always left. Today this matters more than ever. The first number in the block is B. If B is on the right, your robot will turn the wrong way every time. |
| Right rear motor | C | C is right. It is the second number in the block. |
| Sensors | none | The tricycle cannot see. You plan everything it does before it starts. |
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 if you can. A USB cable is like a rope tied to one side of the robot. The tricycle will curve towards the cable. Then you will spend the lesson fixing a steering problem that is not in your program.
Make one change at a time, and guess before each run. Today, guess which way it will go first. Then guess how far.
Keep step 5. Forward, spin, forward: almost every competition robot moves like this. It is easier to plan than a curve. A spin does not move the robot anywhere while it happens.
Curves look nice. But you always know where straight lines and spins will end up. On a course with things in the way, that wins.

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.
When Center Button is pressed:
When Center Button is released:
Fullscreen it while you build — you can pause and scrub with the player's own controls.


Motors B (left) and C (right), large · Speed -30, both · Sensors none
The tricycle drives forward only while the centre button is held. Pressing it starts both wheels at -30%; letting go stops them.
The sign of a speed is its direction. On this build the motors face the way that makes minus drive forward. So -30 is forward at 30%, and 30 would be backward.
pressed, the second
says released. That last dropdown is the whole difference.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.
- When Up Button is pressed, it will move forward. - When Down Button is pressed, it will move backward. - When Center Button is pressed, it will stop moving.
Fullscreen it while you build — you can pause and scrub with the player's own controls.
Log in to see hints.
Create a variable named "speed". - Set speed to 0. - When Left Button is pressed, clear display, decrease speed by 5, play "Speed down" sound, limit minimum speed to -100, and display current speed. - When Right Button is pressed, clear display, increase speed by 5, play "Speed up" sound, limit maximum speed to 100, and display current speed. - When Center Button is pressed, start moving using the speed as the movement speed for 2 seconds, then stop moving.
Fullscreen it while you build — you can pause and scrub with the player's own controls.
Log in to see hints.
Create a variable named "speed". - set the speed to -10 (start from the speed -10%) When the center button is pressed, clear display and start a continuous loop: - start moving using speed as the movement speed. - display current speed on screen - decrease speed by 10 and play a beep sound every 1 second. - if speed goes below -100, it will play a sound "three", "two", "one", stop moving and stop and exit the program.
Fullscreen it while you build — you can pause and scrub with the player's own controls.
Log in to see hints.
Drive a route somebody else chooses, first time. Your teacher will name three stations on the mat in an order you have not practised. Your tricycle must visit them in that order without being picked up, repositioned or nudged, starting from HOME. Plan on paper before you drive. Work out your route as a list of straights and turns first, and note beside each one the numbers you will use. Programming a route you have not planned is how robots end up in the wrong half of the mat. Two questions when you demonstrate it. Which wheel is slower during your turn, and how does that match the direction it goes? And where does your error build up most — in the straights or the turns — and what is your evidence?