The Gyro Launcher: a motor spins a gear up to speed. A stretched rubber band waits on a trigger. When you pull the trigger, the spinning top flies out to battle.
You built the Dual Gyro in Lesson 3. It launched two tops at once. This one is the big version. Like the Elastic Car, it stores energy in a rubber band. It holds it until you choose to let go.
This whole machine depends on one thing: being at full speed before the release. Say the top leaves at half speed. Then it stops in three seconds. So today’s idea is a block that does nothing when it runs. But it decides everything that happens next.
In the real world 5 min
Where you have seen it
Spinning tops are very old. Below is a Japanese beigoma. It is a small iron top. Players spin them into a bowl to battle other tops. Beyblades, with their launchers, come from tops like this.
Beigoma — cast-iron Japanese spinning tops. Photo: Σ64 / Wikimedia Commons (CC BY 3.0).
Why it is built that way
A top stays up for the same reason a bike does. When something spins fast, it is hard to tip over. The faster it spins, the harder it is to tip. And the longer it lasts before rubbing slows it down.
So a launcher has just one job, and it is not aiming. It is getting the top as fast as it can go before letting go. Every real launcher does this and nothing else. A pull cord, a winder and a geared handle all do the same job.
What would go wrong without it
Let go too early, and you waste the launch. And not just a bit! A top at half speed does not last half as long. It wobbles over almost at once. Below a certain speed, it cannot stay up at all.
Some machines must be ready for a moment. Getting ready too late is the same as not getting ready.
Before you build 1 min
This model has no step-by-step guide. The video below is not a guide. The video shows a finished Gyro Launcher working. It shows what you are aiming for. It does not show which beam goes where. Watch it to see the goal. Then build from your teacher’s model, or from a photo of a finished one. If you get stuck, ask. You are not missing a page. There is no page.
The main concept — blocks that do, and blocks that set 6 min
Not every block makes something happen. Some blocks only change what the next blocks will do. In the stack, they look just the same.
Block
When it runs, it…
[A v] start motor [clockwise v] :: motors
Does something. The motor turns. You can see it and hear it.
[A v] set speed to (100) % :: motors
Sets something. Nothing moves, and nothing makes a sound. It saves a number. The motor uses it the next time it turns.
You have used this since Lesson 3, the Dual Gyro. Today it matters where the block goes. Put set speedafterstart motor. Then the motor spins at the speed it had before. Your new number just waits. It does nothing until the motor is asked to move again.
speed first — works
A set speed to 25 %
A run clockwise for 2rotations
speed last — does nothing
A run clockwise for 2rotations
A set speed to 25 %
0.00rotations · slow0.00rotations · fast
Speed first: the movement was slowSpeed last: it only affects the NEXT movement
Two programs. Same two blocks in each — only the order is different.Both are running — and the right-hand one is already finished. The left is barely a third of the way.Its speed block runs now, far too late to affect the movement above it. The left motor is still going, slowly, as it was told to.Both turned exactly 2 rotations. Only one of them did it at the speed the program asked for.Finished — it will run again in a moment.
stopped
Both shafts turn exactly 2 rotations. Only the time they take is different — and the right-hand program never gets the slow movement it was written to have.
Both programs in that demo have the same two blocks. That is why this bug is so hard to spot. Neither block is wrong, and nothing is missing. Only the order is different.
A setting must come before the thing it changes. Set the speed, then start the motor. Never the other way round.
Some blocks you already know are like this too. set volume and set movement motors are settings. None of them does anything by itself.
▶Speed and power, and the Touch SensorAll about the speed block, and the switch this model uses. Open one if it is not clear yet.Show meHide
ComponentMotion4 min
Speed and power
Speed is set separately from movement. You tell the motor how fast it should go, and then you tell it to go — two blocks, in that order.
Speed is a percentage of what this motor can do, not a real-world unit — the same 50 % moves a light arm quickly and a heavy one slowly.
Blocks reference
Block
What it does
[A v] set speed to (25) % :: motors
Sets the speed for this motor from now on. Nothing moves — it only changes what the next movement will do.
[A v] run [clockwise v] for (2) [rotations v] :: motors
Now moves, at whatever speed was last set.
Set it first
when program starts :: events hat
[A v] set speed to (25) % :: motors
[A v] run [clockwise v] for (2) [rotations v] :: motors
Swap those two blocks round and the program still contains a speed of 25 % — it just never gets used. Both shafts below are asked for exactly 2 rotations; watch how long each one takes.
speed first — works
A set speed to 25 %
A run clockwise for 2rotations
speed last — does nothing
A run clockwise for 2rotations
A set speed to 25 %
0.00rotations · slow0.00rotations · fast
Speed first: the movement was slowSpeed last: it only affects the NEXT movement
Two programs. Same two blocks in each — only the order is different.Both are running — and the right-hand one is already finished. The left is barely a third of the way.Its speed block runs now, far too late to affect the movement above it. The left motor is still going, slowly, as it was told to.Both turned exactly 2 rotations. Only one of them did it at the speed the program asked for.Finished — it will run again in a moment.
stopped
Both shafts turn exactly 2 rotations. Only the time they take is different — and the right-hand program never gets the slow movement it was written to have.
The right-hand movement is over before the left is a third of the way round, because it ran at the default speed. Its set speed to () block does run — you can see it light up — but by then the movement it was meant to slow down has already happened. A speed block only ever affects the movements after it. This catches people out constantly.
Slow is often better
A high speed is not a better program. Slow movements are gentler on the gears, easier to watch and debug, and look more like the real machine — a barrier that snaps up in a fraction of a second reads as broken rather than fast.
ComponentSensing5 min
The Touch Sensor
The Touch Sensor is the simplest input the EV3 has: a button that is either pressed or not. That sounds trivial, but it is how a robot knows it has hit a wall, reached the end of a track, or been told to start by a person.
released
pressed
The red button out, and the same sensor with it pushed in. These two states are the entire output of this sensor — there is nothing in between.
Blocks reference
Block
What it does
wait until <[1 v] is pressed? :: sensors>
Holds the program here until somebody presses the sensor.
<[1 v] is pressed? :: sensors>
Reports true or false. Drop it into a condition to make a decision rather than a wait.
[1 v] when [bumped v] :: events hat
Starts a whole stack of its own. The dropdown chooses the moment: pressed, released or bumped.
Three different events
A button is not only “pressed”. One press is three things: the moment it goes down, the time it stays down, and the moment it comes back up. Watch what a single press does to three programs at once.
when program starts
forever
if 1 is pressed? then
change count by 1
versus two hat blocks
1 when pressed
1 when bumped
0is pressed? in a loop0when pressed0when bumped
In a loop: 0 answers from one pressBumped: exactly one
Nobody is touching the sensor. All three programs are watching it.A finger presses the button. Watch the red button go in — a couple of millimetres is the sensor's entire movement.The finger is still down. The loop checking «is pressed?» has already run hundreds of times, and every one of them counted.The finger lifts. Only now does «bumped» count, because bumped means pressed AND released.One press. Three completely different answers.Finished. The same press, counted three ways.
released
The middle counter is the one that surprises people. Nothing is wrong with it — a loop really does check that fast, and every check really is a separate answer.
Nothing there is broken. A loop really does get round hundreds of times a second, and each time it asks is pressed? the honest answer is still yes — so if that loop plays a sound or counts something, it does it hundreds of times from one finger. The two hat blocks each fire once, and they fire at different moments: pressed the instant the button goes down, bumped only when it comes back up.
The three options, and what each is for:
Pressed — the button is down right now. Good for “hold to run”.
Released — it is up again. Good for acting when somebody lets go.
Bumped — pressed and released. This is what you want for “click to start”, because it will not fire repeatedly while a finger stays down.
The classic bumper
when program starts :: events hat
set movement motors to [B v] and [C v] :: movement
start moving [straight: 0] :: movement
wait until <[1 v] is pressed? :: sensors>
stop moving :: movement
The robot drives until something presses the sensor. Note that the movement is started unmeasured on purpose — the sensor decides when to stop, not a distance.
Why it matters
Touch sensors are everywhere in machines you cannot see into: a lift knows the doors are shut, a printer knows the lid is closed, a washing machine will not spin until it is latched. They are safety devices as much as inputs.
Say this back before moving on: “Set speed does not move anything. It decides how fast the next movement will be.”
What’s in this build 4 min
Find the parts with cables. There are three. And you have to tell us which motor it is. This model has no parts list to check.
Large Motor
Medium Motor
Which one is in your build? The Large Motor is long, with a big red round end. The Medium Motor is short and flat. It has a small red knob on its end.
Part
What it is doing here
EV3 Intelligent Brick
Runs the program and holds the launcher steady.
One motor — you decide which
Spins the gear that spins the top. Whichever motor it is, it goes in port A. Every program below says A.
Touch Sensor
Starts the spin. It is the same part you used on the Timber Saw in Lesson 16.
The rubber band and trigger (no cable)
Holds stored energy and lets the top go. You measured this stretchy energy on the Elastic Car in Lesson 14.
The launch itself is not programmed. The motor spins the gear up. A person pulls the trigger. The program does the getting ready. Your hand picks the moment. Know which part does what, and you understand half of this machine.
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
The motor (spins the gear)
A
One motor goes in A. Notice that the programs say A, not “the Medium Motor”. The Brick only knows the port.
Touch Sensor (starts the spin-up)
1
Touch is always port 1 in this course, just like on the Timber Saw.
Check your own build now:
Motor cable in A. A letter.
Touch Sensor cable in 1. A number.
Spin the launcher gear by hand. Does it turn freely, with no rubbing? Anything that drags here makes the top spin for less time.
Is the rubber band hooked on? Is the trigger holding? Check that it holds with no finger on it.
Point the launcher at a clear space. Not at a person, and not at a window. This one really throws something.
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.
Keep the computer out of the firing line. Set up the launcher so the top flies away from the desk. It must not fly across it.
Confirm the connection 2 min
Check the Brick icon: connected, or not.
Port A shows a motor. Read which kind the tile says it is. Does it match what you decided in section 5?
Port 1 shows a Touch Sensor. Press the red button and watch the reading change.
Spin the gear by hand and watch degrees counted move.
Press the button. If the port 1 tile does not change, stop. Nothing you write will start.
Change it and test 8 min
One change at a time, and predict before each run. Time how long the top spins after each launch. That is your measurement, and it beats a guess.
Move set speed so it sits immediately afterstart motor. Predict what changes. Run it and time the spin.
Run step 1 twice in a row without stopping the Brick. The first launch is weak, and the second is strong. Why? On the second run, the motor already had the number. It kept it from last time.
Put it back at the top and try 50 %. Time the spin. Half the speed should cost you much more than half the spin time.
Back to 100 %, and change the wait to 1 second. Pull the trigger as it stops. Did it have time to reach full speed? A motor does not get to 100 % at once.
Now 6 seconds. Is it any better than three? After a while, the motor is as fast as it can go. Then you are just waiting.
Step 2 is the trickiest bug in this lesson. Think about it. The program was wrong, but it worked on the second try. Some bugs go away when you run it again. They are the hardest kind to find. This is just how those bugs happen.
“It worked the second time” does not mean it is fixed. It means a setting came too late.
This is what you are building: the Gyro Launcher.
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
Six blocks. Set the speed, wait for a click, spin up, keep spinning, stop. You pull the trigger by hand while it is at full speed.
when program starts :: events hat
[A v] set speed to (100) % :: motors
[1 v] wait until [bumped v] :: sensors
[A v] start motor [clockwise v] :: motors
wait (3) seconds
[A v] stop motor :: motors
The speed is set at the very top, long before anything turns. It must be ready by the time the motor starts.
Walk it in the order the Brick runs it:
set speed to 100 % — nothing happens. No noise, no movement. It just saves the number.
wait until bumped — the program waits here. It can wait as long as you like. It waits until a finger presses and lets go. The speed is already set and ready.
start motor clockwise — the gear spins up at 100 %. That was set two blocks ago.
wait 3 seconds — time to get up to speed. The motor turns the whole time. This is when you pull the trigger.
stop motor — the launcher winds down.
What success looks like: a click, then three seconds of a whine getting higher. The top flies out hard and stays up for a good while. Time it. Use that number to judge every change you make next.
If the top wobbles over almost at once, it left too slowly. Maybe the trigger went early. Maybe the gear did not turn freely. Or the speed never reached 100. The next section is about that.
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
Prove the order matters, with numbers. Launch three times with set speed above start motor. Then launch three times with it below. Time how long the top spins each time. That gives six times and two averages. Write one sentence. Say which order won, and by how much.
Challenge 2
Find how long your launcher really needs to spin up. To spin up means to get to full speed. Try 1, 2, 3, 4 and 6 seconds between the click and pulling the trigger. Time the spin each time. Find the point where waiting longer does not help any more. Say what is going on at that point.
Challenge 3
Make the launcher tell you when it is ready. It must warn you before it starts to spin. It must show or play something while it speeds up. It must clearly show when it gets to full speed. Then a person knows just when to pull the trigger. They do not need to count in their head.
Extra challenge
Build a launcher that gives the same launch every time.
Your launches must be close enough to each other to compete. Do five launches in a row. Their spin times must be close. The person using it does nothing but pull the trigger when told. Being the same each time is the goal, not a record. A launcher that is great once and poor four times is no use in a contest.
Plan on paper before you build. List everything that could change from one launch to the next. Include things a program cannot control. Then decide which of them you can remove.
Two questions when you show it. What is the biggest thing still making your launches different? How do you know? And which parts of your program are settings, not actions? Point at each one.