The Rickshaw: a cart with three wheels that carries people. One Large Motor drives it. A screen says where it is going. It beeps when it gets there.
A rickshaw driver does not think in seconds. Nobody ever asks to go “forward for four seconds”. They ask to go to the end of the road. That is a distance.
You have used rotations, degrees and seconds before. Today you find out why seconds can go wrong.
In the real world 5 min
Where you have seen it
The trishaw. You still see them in many Asian cities. They are bright, and often play music. It has three wheels and a rider who pedals. One or two people sit at the front.
A trishaw has low gears. The pedals turn a lot, and the trishaw moves a little. That makes it slow. But it can start from still. It can do it with two people and a hill ahead.
The rider also knows how far they have gone. They do not need to look up. Every turn of the pedals goes the same distance along the road. One full turn might be two metres. The rider may be tired. There may be one person or two. It does not matter. Being tired changes how long the trip takes. It does not change how far one turn goes.
What would go wrong without it
Think of a driver who measured in time. “The museum is four minutes away.” That is fine on an empty road. But it is no good in traffic. Or going uphill. Or with a heavy person on board. They would drop you in a new place every trip.
Time tells you how long you tried. Rotations tell you how far you got.
The big idea — three ways to say “how far” 6 min
One block, one little menu, three big promises. A promise is what the Brick says it will do.
[A v] run for (3) [rotations v] at (40) % speed :: motors
The menu after the number is the one that matters. Open it. rotations, degrees, seconds.
Unit
What the Brick really promises
Use it when…
seconds
“I will keep the power on for this long.” It says nothing about distance.
How long is what matters. A fan that runs for a minute. A light that stays on.
rotations
“I will turn the axle round this many times. It does not matter how long it takes.”
Distance matters. Use this for anything that drives.
degrees
The same promise as rotations, in smaller bits. 360 degrees is one rotation.
You need part of a turn. A quarter, a third, or an arm lifted to an angle.
Rotations and degrees are the same thing in different clothes. The real change is with seconds. Seconds does not measure the axle at all.
Why seconds go wrong
Set a motor to run for 3 seconds at 40%. It will not always go the same distance:
A full battery pushes harder. So it goes further.
A passenger in the seat slows it down. So it does not go as far.
A carpet, not a table, slows it down again.
Set it to 3 rotations. Now none of that matters. A heavy rickshaw takes longer to do 3 rotations. But it still does 3 rotations. The Brick counts the axle going round. It does not stop until it reaches the number.
ComponentMotion5 min
Rotations and degrees
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.
One rotation means one full turn of this shaft — not one turn of the wheel or gear it drives. Gearing between the two changes how far the mechanism actually moves.
Blocks reference
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.
Count it as it turns
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 program begins. Nothing has turned yet, so both counters read zero.Turning. Watch the two motor counters climb together — they are one movement counted two ways.Exactly 2 rotations, exactly 720°. The big gear has turned only two thirds of a turn.Finished — it will run again in a moment.
stopped
The two motor read-outs are the same measurement — 1 rotation is 360°. Use whichever makes the number easier to read.
Rotations or degrees?
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.
Gearing changes the answer
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.
Why it matters
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.
Seconds measure how hard you tried. Rotations measure what you got.
▶Turning part of the way — degrees360 degrees make one rotation. Sometimes you need just part of a turn. You met this in Lesson 4.Show meHide
ComponentMotion5 min
Moving to an exact angle
Everything so far has been relative: move 90 degrees from wherever you are now. Sometimes what you actually want is absolute: go to the 90-degree position, whatever position you happen to be in at the moment.
The motor counts its own turning all the time, so it always knows where this shaft is — which is what makes going to an exact position possible.
Relative drifts, absolute does not
Both pointers below do the same job over and over: swing out a quarter turn, then come home. The only difference is the block that brings them back. Watch one trip and they look identical — so let it run for several.
relative — by an amount
A run clockwise for 90degrees
A run counterclockwise for 90degrees
absolute — to a place
A run clockwise for 90degrees
A run to position 0
0°relative, off home0°absolute, off home1trip
Relative: 0° from home and growingAbsolute: home, exactly
Both pointers are at home, on the black mark.Out a quarter turn. Both use the same relative move to get there.And back home — one by moving 90° the other way, one by going to position 0.Look at the left pointer against the black mark. Then let it go round again.Finished — it will run again in a moment.
at rest
Let it loop. Nothing about the left program is wrong — it is just that every trip starts from wherever the last one finished, so a small error is never corrected, only added to.
A pointer moved relatively slowly wanders: each movement starts from wherever the last one finished, so any small error is carried forward and added to. Each orange dash is a trip that called a slightly different place “home”. Nothing about that program is wrong — it is simply that a relative move has no idea where it is supposed to end up.
An absolute movement has no memory of the error. Told to go to position 0, it goes to position 0 — the same place every time, however wrong it was beforehand. That makes it the right tool for a home position: the known place a mechanism returns to before it starts work.
Every motor knows where it is
This is possible because an EV3 motor counts its own turning all the time. Its position can be read back, and can be reset to zero — which is how you tell the motor that here is what you mean by zero, usually at the start of a program with the mechanism held at its resting place.
Why it matters
A clock hand returns to twelve; a car’s steering returns to centre; a 3D printer homes its head before every print. All of them go to a position rather than moving by an amount.
Say this out loud before you move on: “Seconds is how long. Rotations is how far.”
What’s in this build 4 min
Part
What it is doing here
EV3 Intelligent Brick
Rides on the cart and counts the motor’s rotations. That counting makes today’s program work the same every time.
Large Motor — the drive
One motor turns the back axle. There is only one motor. So the rickshaw goes where its wheels point. It cannot steer itself.
Ultrasonic Sensor
Faces forward. Today we only use it as a safety stop at the end. You read it as a number on the Radar in Lesson 41.
The Brick screen and speaker
How the rickshaw tells a passenger what is happening. It is not just for show. It is how you check the program reached the end.
Measure your wheel before you program anything
One rotation of the motor always moves the rickshaw the same distance. Find out what that distance is. Then a rotation means something real.
Put the rickshaw next to a ruler. Put the front wheel on zero.
Turn the motor by hand, exactly one full turn.
Measure how far it moved. Write it on your sheet: 1 rotation = ___ cm.
Do it twice more. Do you get the same answer? If not, a wheel is slipping. Fix that now.
Ports — and the rule 4 min
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
Drive motor (Large)
A
One drive motor does a job. It is not a steering pair. So it uses a Motor block on A. It does not use the Movement blocks.
Ultrasonic Sensor
4
In this course, Ultrasonic always goes in port 4. That is true in every lesson and level.
Check your own build now:
Find the wheels the motor turns. Follow their axle back to the motor. Put that motor in A.
Ultrasonic in 4, pointing forward and flat. If it tilts at the floor, it measures the floor.
Clear a space at least a metre long. This model moves. Rotations are easier to see over a long way.
Connect the Brick 4 min
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.
▶How to connect the BrickUSB and Bluetooth, step by step, with a photograph of every screen. Open it if you have not done this before — or if pairing is not working.Show meHide
USB — the reliable one
Switch the Brick on with the dark grey centre button.
Cable into the Brick’s PC port — the small square socket beside the numbered ports, not one of the numbered ones.
Other end into the computer.
Bluetooth — name it first
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.
Name your Brick. On the Brick: Settings (the spanner) → Brick Name. Type something nobody else will pick, then press the tick. Every Brick is called EV3 until somebody changes it.
Turn Bluetooth on. Settings → Bluetooth. Tick Bluetooth and Visibility. Leave iPhone/iPad/iPod unticked.
Connect from EV3 Classroom. Click the Brick icon at the top of the programming area, find your Brick by name, and click Connect.
Say yes on the Brick. It asks “Connect?” with the computer’s name — choose the tick, then accept the passkey, which is already 1234.
Where to read it. The name sits in the bar across the very top of the screen, on every screen — so you can check which Brick you are holding at any moment without going into a menu. This one is EV3VE. A Brick nobody has renamed says EV3.Step 3, and the reason step 1 exists. Three Bricks in range — read the name before you click Connect. Pairing with the wrong one is not an error: it works perfectly, on somebody else’s robot.
Step 2.Bluetooth switches the radio on; Visibility is what lets the computer find you. With Visibility off your Brick works perfectly and simply never appears in the list.Step 4. Look at the Brick. It asks whether to accept and names the computer. Choose the tick.Then the passkey, already 1234. Press the tick again and you are connected.
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 for this one. A USB cable pulls on a driving model. This lesson wants to prove that pulling does not matter. So prove it with no cable tied on.
Confirm the connection 2 min
Look at the Brick icon. Is it connected?
One Large Motor tile on A, one Ultrasonic tile on 4.
Push the rickshaw along the table by hand. Watch tile A’s number go up. Your program will use this same counter.
Put your hand in front of the Ultrasonic. Watch its number go down. If it stays at 255, it is facing nothing at all.
Change it and test 8 min
Today you compare two ways. So run these in pairs. Mark where it stops each time with tape. Are the two bits of tape close? Then the robot does the same thing each time. Far apart means it does not.
Change rotations to seconds. Keep the number at 5. Run it. Mark where it stops.
Now put a heavy passenger in the seat. A spare Brick or a pencil case will do. Run the seconds one again. Mark it. How far apart are the two marks?
Change back to rotations. Do both runs again, with and without the passenger. Mark both. Compare the gap with step 2.
Try degrees with the number 1800. Guess where it will stop before you press Play. (1800 ÷ 360 = 5.)
Add a stop at the side of the road. Put [4 v] wait until distance [> v] (15) [cm v] before the motor block. Hold your hand in front of the sensor. The rickshaw waits for a clear road. Then it drives its five rotations.
Step 3 is the proof. The two rotation marks should almost touch. The two seconds marks should not. It is the same robot, floor and battery. Only the menu changed.
Must your robot end up in a set place? Then never use seconds.
This is what you are building: the EV3 Rickshaw.
Build it 15 min
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.
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.
Make it move 10 min
A rickshaw trip. Say it is starting. Drive a set distance. Arrive, and say so.
when program starts :: events hat
clear display :: display
write [Go!] at line (1) :: display
[A v] run for (5) [rotations v] at (40) % speed :: motors
play beep (60) for (0.3) seconds :: sound
write [Arrived] at line (3) :: display
Five rotations. Not five seconds. That difference is the whole lesson.
clear display wipes away what the last run left. So line 1 really is line 1.
write Go! at line 1. Now the passenger knows the trip has started.
run for 5 rotations at 40%. The Brick counts the axle going round five times. On a thick carpet, it will not stop early. It will just take longer.
beep, then write Arrived at line 3. This only happens once the five rotations are really done. That is why it is a useful sign.
What success looks like: mark the start and finish with tape. Run it three times from the same start line. It should stop at the same finish line every time.
Does it stop in a different place each run? Then the wheels are slipping. The motor really did turn five times. But the wheel did not take the rickshaw with it. Rotations measure the axle. They cannot see a skid.
Challenges 27 min
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.
Challenge 1
Stop on the line three times in a row. Put a strip of tape on the floor. Pick a starting point. Make the rickshaw stop with its front wheel on the tape. Then do it twice more from the same start. Do not change the program. All three stops must be within a tyre's width of each other.
Challenge 2
Do two different trips. The rickshaw must make a short trip and a long trip, one after the other. Before each one, the screen must say which trip it is. It must beep when it gets there. The two trips must clearly be different lengths. Both must come out the same each time you run them.
Challenge 3
Carry a passenger the same distance. Run your trip with the seat empty. Mark where it stops. Put something heavy on the seat. Run just the same program. Mark it again. The two marks must be close enough to touch. If they are not, the wheels are slipping. Say what you did about it.
Extra challenge
Make your rickshaw take orders in centimetres.
A passenger does not think in rotations. They say "take me forty centimetres down the road". Your machine has to turn centimetres into rotations.
Start from what you measured in section 5. One rotation moves the rickshaw a set number of centimetres. Make a small table on paper with 20 cm, 40 cm, 60 cm and 80 cm. Work out how many rotations each one needs. Show your working.
Then build the trips and test the table. Mark each distance on the floor with tape before you run it. That way you test the machine against what you said would happen. You are not just measuring it after.
Two questions when you show it. Which distance came out worst? Is the error the same each time, or does it grow with the distance? And say someone swapped your wheels for bigger ones. Which number in your table would still be right? Which would all be wrong?