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 31
Level 1 · Lesson 31 · EV3-L01-3160 minutes · Ages 7+ · Model: Shock Absorber Car
The Shock Absorber Car: a car with four wheels and two Large Motors. Each wheel hangs on its own rubber band. So each wheel can move up and down by itself.
The Tricycle in Lesson 29 had its wheels fixed straight to the frame. That is fine on a table. But on a bumpy floor it hops. And a wheel in the air is not driving.
This car has suspension, and today you find out what that is really for. It is not to make the ride comfy. There is nobody inside! It keeps all four wheels on the floor.
Under every car on the road. Each wheel has a coil spring, and a damper next to it. They let the wheel move up and down. The body of the car stays almost level. On bumpy roads, they work very hard.

Here is the surprising part. Suspension is not mainly there to stop people being shaken. It is there to stop the wheels leaving the road.
Picture a wheel fixed hard to a car. It hits a bump, and the whole car jumps up. While it is in the air, that tyre touches nothing. So it cannot drive, stop or steer. Springs let the wheel jump on its own. The heavy body carries on. Then the spring pushes the wheel back down onto the road, almost at once.
A car does not always have grip. It only has grip while the tyre is on the ground. The engine, the brakes and the steering are no use while a wheel is in the air. Even for a tiny moment.
A wheel off the ground does nothing at all. Suspension makes that tiny moment as short as it can be.
A rubber band between the wheel and the body does two jobs. It lets the wheel move. And it pushes the wheel back.
Your rubber bands do the same job as the coil springs in the photo. They stretch as the wheel goes up, and store energy. It is the same stretchy energy you measured on the Elastic Car in Lesson 14. Then they give it back, and pull the wheel down again.
There is one real difference. A car has a damper as well as a spring. The damper soaks up the energy, so the car does not keep bouncing. Your model has springs but no dampers. So it will bounce a few times after each bump. Your build is not wrong. It just does not have that part.
Springs are not for the people inside. They are for the tyres. A tyre that stays down still works.
A stretched rubber band is a store. Pull it and you put energy in; let go and it gives the energy back. Nothing about that is obvious from looking at the band, and two things about it are genuinely surprising.
While it is stretched and held, the energy is not doing anything — it is potential energy, stored in the shape of the material. Release it and that becomes kinetic energy: the energy of something moving. A pull-back car is a machine for making that swap at a moment of your choosing.
The same store shows up all over a LEGO set:
This is the first surprise. Energy stored in a spring or a band goes as the square of how far it is stretched — pull back twice as far and you have stored four times as much, not twice.
Which sounds like excellent news, and leads directly to the second surprise: the car does not go four times as far. Find out where the two part company.
Drag the car back, or use the arrow keys. Watch the two curves come apart.
Every bit of the extra stretch is still turning into distance. Double this stretch and you store four times the energy — energy goes as the SQUARE of how far you pull.
Find the place where the green curve stops rising as fast as the orange one. That is the setting worth building for — and it is a number you measure, not one you can reason out.
Past a certain stretch the wheels can no longer grip hard enough to turn all that force into movement, so they spin. The energy still leaves the band — it goes into noise, heat and rubber marks on the table instead of into distance.
That ceiling is a property of your car on that surface: its weight, its tyres, how much of it is over the driven wheels. It is not something to look up. It is something to measure, and finding it is one of the most satisfying things a mechanical build has to offer.
Three things move the ceiling up, and all of them are build changes rather than bigger bands: more weight over the driving wheels, grippier tyres, and gearing the launch down so the same energy arrives as more force over more time.
Change one thing at a time and run each setting three times, not once. Pull back 5 cm, then 10, then 15, measuring from the same starting line every time and recording every run. Three readings tell you whether a difference is real; one reading tells you nothing at all.
That is the discipline the whole of Mechanisms without motors is built around, and it is the same habit that makes debugging a program work.
Bows, clockwork, suspension springs and the recoil mechanism in a car door all store energy and give it back on demand. Storing energy slowly and releasing it quickly is how a small muscle — or a small motor — produces a large, brief force.
Some models have no motors and no sensors at all. They are not lesser lessons — they are where the physics lives. A build that stores energy, changes a force, or turns one kind of motion into another explains why the powered models later need the gearing and the speeds they do.
Gears, pulleys and levers look like three different topics and are three shapes of the same deal: whatever you gain in force, you pay for in distance. Halve the effort and you move twice as far; move half as far and you need twice the effort. No arrangement of anything gives you both, and recognising that saves a great deal of time hunting for one.
What a mechanism actually does is let you spend the same effort in a form you can manage — a little at a time instead of all at once, or all at once instead of a little at a time.
| Tutorial | The question it answers |
|---|---|
| Gearing up and gearing down | How do I trade turns for force? |
| Changing the direction of a turn | Why is it going backwards, and how do I drive an axle at 90°? |
| Pulley systems | How does a rope let a small motor lift a big load? |
| Levers — effort, load and pivot | Where should the pivot go? |
| Elastic and stored energy | How much further does pulling back twice as far actually get me? |
| Scissor mechanisms | How do I make something extend a long way — and why won’t it start? |
| Oscillatory motion | How do I turn going round into going back and forth? |
| Centre of gravity | Why does it keep falling over? |
| Biomimetic mechanisms | How does a machine walk without ever being told to? |
Friction is what makes wheels grip and also what wastes effort. Every mesh, pin and rope turn loses a little to it, so a mechanism with more parts delivers less than the arithmetic promises. A build that binds — that is stiff to move by hand — is losing far more than that, and no amount of extra motor power fixes a mechanism that is rubbing.
Before measuring anything, turn the mechanism by hand. It should move smoothly and coast a little. If it does not, fix the build first; numbers taken off a binding mechanism describe the binding, not the idea you were trying to test.
Since there is nothing to program, the work is measuring. Change one thing, keep everything else the same, and record what happened — pull the car back 5 cm, then 10, then 15, and measure how far each one travels. Three readings at each setting, not one, because a single run is not evidence.
That is genuinely how engineers test, and it is the same discipline that makes debugging a program work: change one thing at a time.
Say this back before moving on: “A wheel in the air is not driving. Springs push it back down.”
| Part | What it is doing here |
|---|---|
| EV3 Intelligent Brick | Runs the program. It is also the car’s body, the weight the springs hold up. |
| Large Motor ×2 | One drives the front wheels, and one drives the back wheels. Ports B and C. They are mounted facing each other, which matters below. |
| Four rubber bands (no cable) | The springs, one for each wheel. The photo in the manual shows where they go. |
Pick the car up and look at the two motors. They face each other. So “clockwise” on one and “clockwise” on the other send the car in opposite directions.
Nearly every driving robot is built this way. The move blocks already know about it. That is part of what “a pair” means. Use them, and it just works. If you use two separate run blocks and you must turn one of them round yourself. If not, the wheels will fight.
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 |
|---|---|---|
| One Large Motor (front pair) | B | B and C are the pair. On this car they are front and back, not left and right. The block does not mind. It just drives both together. |
| Other Large Motor (rear pair) | C | Same reason. Write down which is which. |
| Sensors | none | The car cannot feel a bump. You have to notice it. |
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.
Bluetooth, for the same reason as the Tricycle. A cable trailing behind pulls one side of the car. Today you measure how straight the car drives. So a cable would spoil your results.
Do that check in the air, not on the floor. If the wheels fight on a table, they drag the tyres. A wheel arm can pop off.
This is an experiment, so it has rules. Change one thing, run it three times, use the middle result. Predict before each set.
Set up a bump. Tape a ruler or a pencil across the middle of the path. Add a tape start line, so every run starts in the same place.
Step 5 often surprises people. Stiffer is not better. A very stiff spring acts almost like no spring at all. The wheel cannot move up easily, so the whole car gets thrown again.
Too soft, and the car wobbles about. Too stiff, and it may as well be fixed solid. The best answer is in the middle. You find it by measuring.
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: out, pause, back. We keep it simple on purpose. Today we test driving over a bump, not the program.
when program starts :: events hat set movement motors to [B v] and [C v] :: movement set movement speed to (60) % :: movement move [forward v] for (5) [rotations v] :: movement wait (1) seconds move [backward v] for (5) [rotations v] :: movement
Read it in the order the Brick runs it:
What success looks like: a straight drive out and back on a flat floor. The body stays level, and all four wheels stay down.
If the car judders and goes nowhere, the two ends are fighting. Check you are using the
moveblocks and not two separate motor blocks. That is the problem from section 5, and the Movement block fixes 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:
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.
Cross a bump and stay straight. Lay something across the route to make a bump. Drive over it. End within a hand's width of the line you started on. Do three runs. All three must end inside that width. The suspension must do the work, not luck. Suspension is the springy part that lets the wheels move up and down.
Find out what the springs are worth. Run the same course over the same bump. Do it with the bands on, and with the bands off. Do three runs each. Measure how far sideways the car ends up. Tell us all six numbers. Tell us the gap between the two averages.
Find the best stiffness. Try one band on each corner. Then try two. Then two on one axle and one on the other. Test each one over the bump three times. Tell us which was best. Then say why stiffer stopped helping at some point.
Build a car you can trust on a rough route. Your car must drive a route on the mat with at least two bumps to cross. It must reach a station your teacher names. It must stop inside it. It must work as well on the rough route as on a flat one. That is the whole test. Plan on paper before you build. Decide what you will change on the suspension, and why. Guess what difference it will make. Do this before you touch the model. Two questions when you show it. What does suspension really do for a robot with no one riding in it? And which part of your route makes your robot miss the most? What did you change to fix it?