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 2 · Intermediate›Lesson 21
Level 2 · Lesson 21 · EV3-L02-2160 minutes · Ages 8+ · Model: Forklift with Pulley
The Forklift with Pulley: a driving base with a tall mast. A string lifts the fork. A Medium Motor under the Brick winds the string onto a drum.
The Forklift back in Lesson 14 lifted with gears. This one lifts with string. String is lighter and smoother, and much better for lifting high. But it is much worse at knowing where the fork is.
By the end of the lesson, your forklift will move a pallet three times over. You will also measure how far it drifts off. That is the question this whole level has been asking.
A warehouse is built so things can happen the same way every time. Pallets are all one size. The shelves sit at fixed heights. The gap the fork must go into is a few centimetres wide. A driver hits it hundreds of times a day.

All those fixed sizes are not there to help the forklift. They are there so that the same movement works every time. A pallet is 1,200 mm across everywhere in the world. So the space between the forks never changes. So the way in never changes.
Robot warehouses go even further. A robot does not look at the shelves. It goes to the height it was told, because the shelf is sure to be there. That only works if the machine is repeatable. That means the same command always gives the same result. Run one thousand is the same as run one.
And they all home before work starts. They drive to a set stopping point, reset everything to zero, and count from there. Your forklift will do this too.
A machine that is accurate gets it right once. A machine that is repeatable gets it the same every time. If a repeatable machine is a little wrong, you fix it once, and it stays fixed. A machine that drifts cannot be fixed at all. By the time you change it, it has moved on.
The same and wrong is a machine you can fix. Right only on average is a machine you cannot.
Level 1 asked if you could make it move. Level 2 has been asking something harder all along: does it do the same thing every time? Now you find out.
| To make it the same every time | You use |
|---|---|
| Start from the same place every run | homing — new today, in Make it move |
| Stop where you meant to, not where it drifted to | hold position at stop — Lesson 4, the Strong Lifter |
| Go a set distance, not just run a motor | wheel distance maths — Lesson 16, the Card Dealer |
| Arrive gently, not fast | lower speeds — Level 1, Lessons 47 and 48 |
| Know how bad it is | measure it, many times — Lesson 20, the Racecar |
A string winding onto a drum does not have a fixed ratio. Gears and wheels do. The first turn winds string onto the bare drum. The next turn winds on top of the first. So the drum is now fatter, and the same turn pulls in more string. The higher the fork goes, the further it rises for each degree.
A pair of gears has a ratio you can work out once. A wheel has a distance round it that you can work out. The pulley has neither. Its ratio changes as it works.
Run the same program five times from the same start. Mark where it ends each time. Two different things can go wrong:
Measure the spread before you change anything. If the machine is not repeatable, changing it just moves the middle of the mess.
A pulley is a wheel with a rope over it. On its own that sounds like it could not possibly matter, and yet the right arrangement lets a small motor lift something it has no business lifting. The whole of it comes down to one question: how many pieces of rope are holding the load up?
Look at the load and count the rope segments running down to it. If the load hangs from two segments, each of them carries half the weight, so you only have to pull half as hard. Four segments, a quarter each.
effort = load ÷ number of supporting ropes
And the price, which is exactly as large as the saving:
rope you must pull = distance lifted × number of supporting ropes
Count the blue rope segments running down to the load. That number divides the force and multiplies the rope you have to pull.
| Type | Supporting ropes | What it gives you |
|---|---|---|
| Fixed — the wheel is bolted to something solid | 1 | No force saved at all. What it changes is the direction you pull in — down instead of up, or round a corner — which is very often the whole reason it is there. |
| Movable — the wheel travels with the load | 2 | Half the force, twice the rope. The pull direction is unchanged. |
| Combined — fixed and movable together (a block and tackle) | 2, 4, 6… | Both at once: the force divided by the count and a convenient direction to pull in. |
A fixed pulley being “no help” is worth dwelling on, because it is where the counting rule proves itself. One rope, one whole load — and it is still the pulley you reach for most often, because pulling downwards with your weight behind it beats pulling upwards every time.
Multiply the two formulas together and the gain cancels the cost exactly: half the force over twice the distance is the same amount of work. A pulley system does not create effort out of nothing — it lets you spend the same effort in a form you can actually manage, a little at a time instead of all at once.
That is the same bargain gears and levers make, in three different shapes. Once you have seen it in one of them, the other two stop being new.
Cranes, lifts, sailing boats, gym machines and window blinds all count ropes for a living. The counterweight on a lift is a pulley system; so is the tackle a single person uses to raise an engine out of a car.
Telling a motor to stop does not say how it should stop. There are two very different behaviours, and which one you want depends entirely on what the mechanism is holding up.
Both arms below are lifted by the same program and stopped at the top. The only difference is one word in the stop block. Everything worth seeing here happens after the movement has finished.
the only change on the other arm
If a mechanism you just lifted sags the moment it stops, the stop action is the first thing to check — not the lifting movement.
The coasting arm does not slide down steadily — it starts slowly and picks up speed, because it is gravity pulling it and not a motor lowering it. That is also why a coasting robot rolls a little past where its measured movement ended.
If gravity is pulling on the mechanism, you almost always want brake — otherwise the thing you just lifted comes back down on its own. If you want a smooth, natural halt, or you want to be able to push the robot by hand afterwards, coast is friendlier.
Coasting also makes a robot travel slightly further than its measured movement, because it keeps rolling after the motor has finished. On a precise task that error matters.
A crane must brake — a coasting crane drops its load. A train coasts into a station rather than stopping dead, because passengers would be thrown forward. The same choice, made differently, for good reasons.
First find out if it does the same thing twice. Only then find out if that thing is right.
Telling a motor to stop does not say how it should stop. There are two very different behaviours, and which one you want depends entirely on what the mechanism is holding up.
Both arms below are lifted by the same program and stopped at the top. The only difference is one word in the stop block. Everything worth seeing here happens after the movement has finished.
the only change on the other arm
If a mechanism you just lifted sags the moment it stops, the stop action is the first thing to check — not the lifting movement.
The coasting arm does not slide down steadily — it starts slowly and picks up speed, because it is gravity pulling it and not a motor lowering it. That is also why a coasting robot rolls a little past where its measured movement ended.
If gravity is pulling on the mechanism, you almost always want brake — otherwise the thing you just lifted comes back down on its own. If you want a smooth, natural halt, or you want to be able to push the robot by hand afterwards, coast is friendlier.
Coasting also makes a robot travel slightly further than its measured movement, because it keeps rolling after the motor has finished. On a precise task that error matters.
A crane must brake — a coasting crane drops its load. A train coasts into a station rather than stopping dead, because passengers would be thrown forward. The same choice, made differently, for good reasons.
Say this back before you move on: “Spread first, then aim.”
Look at your forklift. Compare it with the Forklift you built in Lesson 14. What does the lifting now? What has that changed?
| Part | What it is doing here |
|---|---|
| EV3 Intelligent Brick | The body, and the weight that stops it tipping. A real forklift’s heaviest part sits behind the back axle for just this reason. |
| Large Motor ×2 — the drive | A matched pair. Your distances come from the size of their wheels. |
| Medium Motor — the lift | Winds the string. It must hold position at stop. If not, a loaded fork slides down every time the program pauses. |
| The string and drum (not electronic) | This is where “the same every time” gets lost. The string stretches, it slips, and it winds on top of itself. |
| The mast and fork (not electronic) | Must slide freely. A sticky mast turns a smooth lift into jerks. Jerks are never the same twice. |
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 drive wheel (Large) | B | The pair. Two motors, one job. |
| Right drive wheel (Large) | C | The other half of the pair. |
| Lift (Medium) | A | Its own job. It is the only motor with a load hanging off it. |
| Sensors | none | Nothing on this machine can see how high the fork is. The program has to trust its own count. |
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. This time you must. Today you measure how much the robot drifts between runs. A cable trailing behind pulls a bit differently every run. That adds drift that you made yourself.
Stuck? The long version, with a photograph of every screen, is in the Brick & Bluetooth guide.
This is the most important measurement today. Draw a table. Put tape on the floor. Run, mark, measure, repeat.
hold position at stop and do all five runs again. The spread gets worse. One block makes a difference you can measure.If you can measure a machine, you can make it better. Measure the spread before you change a number.
Look at your program again. Do not look at what it does. Look at what it looks like.
The five blocks inside repeat (3) are one idea: fetch a pallet. You wrote it once and asked for it three times. That worked because all three trips were the same.
Now try to make the second trip go somewhere else. A different shelf, or a different height. Straight away, the repeat is no use. You have to write those five blocks out again, in full, with new numbers. Three shelves means fifteen blocks. Six shelves means thirty. And if you ever change how a pallet is fetched, you must change it in six places. You will miss one.
What you want is to give those blocks a name, like fetch pallet. Then you can use it three times with different numbers. That is a My Block. Level 2 does not have it. It is the first thing Level 3 gives you. Right now, you can feel why you need it.
There is a second thing missing. You met it in step 10. Nothing on this forklift can see the fork. The string’s ratio changes as it winds. The program cannot know, because it cannot check the real height. The answer is calibration. That means measuring the machine against something real, and fixing it as you go. That is in Level 3 too.
Feeling what is missing is part of the lesson.
Now you can build a machine that does the same thing every time. Next, the Speed Bot measures its own trip and works out how fast it went.

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.
Move a pallet, three times. Home the fork, drive out, lift, drive back, lower.
when program starts :: events hat set movement motors to [B v] and [C v] :: movement [A v] set motor to [hold position v] at stop :: motors [A v] run [counterclockwise v] for (2) [rotations v] at (20) % speed :: motors [A v] reset degrees counted :: motors clear display :: display write [CYCLE] at line (1) :: display repeat (3) move [forward v] for (2.8) [rotations v] at (30) % speed :: movement [A v] run [clockwise v] for (400) [degrees v] at (30) % speed :: motors move [backward v] for (2.8) [rotations v] at (30) % speed :: movement [A v] run [counterclockwise v] for (400) [degrees v] at (30) % speed :: motors write ([A v] degrees counted) at line (3) :: display end play sound [Communication / Goodbye v] until done :: sound
hold position at stop before anything moves. You used it on the Strong Lifter, in Lesson 4. Without it, the fork slips down a little at every pause. Three trips of slipping is a mistake you can see.What success looks like: the fork winds to the bottom. Then the robot drives out, lifts, drives back and lowers. It does this three times. It ends on your tape mark, facing the way it started. Line 3 reads 0.
If the fork ends up higher every trip, the lower is hitting its stop. The motor counted moves that did not happen. Make the 400 smaller. Does the robot creep forward over the three trips? Then the moves out and back are not equal on the floor. That is just what you are about to measure.
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.
Run three pallet cycles. Finish on your tape mark. The fork's count must be back at zero.
Measure how repeatable your machine is. Repeatable means it does the same thing every time. Do five runs that are just the same. Make five marks on the floor. Then say how far apart the marks are.
Get the marks closer together with ONE change. Use homing, hold position, or a slower speed. Prove it worked with another five runs.
Carry a load from the station your teacher names to a second station. Put it down at the height you are given. Then go back to the start. Do it five times. Do not change anything between runs. Then give two numbers. How far apart were the places where it finished? How far apart were the heights where it put the load?