Challenge 1
Fire every arrow in a full magazine with no jams. The magazine is the box that holds the arrows. Write down how many arrows came out, and how many you put in.
Quick Learn — the model, the instructions, the program and the challenges. The theory is in Full Lesson.
EV3 Robotics›Level 2 · Intermediate›Lesson 27
Level 2 · Lesson 27 · EV3-L02-2760 minutes · Ages 8+ · Model: Chu Ko Nu Chinese Crossbow · Mechanical only
The Chu Ko Nu: a crossbow that fires again and again. A box of short beams sits on top. That box is called the magazine. A lever on the side does everything else.
There is no Brick in this model. No motor, no sensor, no cable, no program. We did not forget them. That is the lesson. Push the lever forward and back. The machine loads a beam, pulls the bow back and lets it go. It does it in that order, every single time.
By the end, you will measure how fast it shoots and how far. And you will say just where its “program” is kept.
Safety first. This machine shoots a beam. Point it at a wall or a cardboard box. Never at a person, an animal or a window. Everyone within two metres wears safety glasses. That rule stays all lesson.
The chu ko nu is a Chinese crossbow that fires again and again. Old stories say a war leader called Zhuge Liang made it, about 1,800 years ago. But people have found older ones. One was found in a tomb that is hundreds of years older still.

A normal crossbow is strong but slow. To load it, you brace it on the ground. You haul the string back with both hands. You put an arrow in and aim. That takes about twenty seconds, even with practice. Both hands are busy the whole time.
The chu ko nu gives up a lot of that power to get speed. A magazine sits over the groove. The next arrow drops into place by itself. Its weight pulls it down. You push the lever forward and back, and that pulls the string. At the end, a peg pushes up through a slot. It lifts the string off, and the arrow flies.
One hand. One movement. Maybe ten shots in fifteen seconds. It was used to guard walls. It was not exact, and not strong. But a wall full of them could fill the air with arrows very fast.
The order must be right. Pull before the arrow has dropped, and you shoot nothing. Let go before the pull is done, and the arrow falls out of the groove. Every step needs the one before. And there is no computer in the machine to check.
The order is not written down. It is built into the shape of the parts.
There is no printed manual for this model. But the video above shows you how to build it. It is not just a demo. It is Lau Mo’s build video for the 45544 set. You can build straight from it. Pause it often. A video does not wait for you the way a book does.
Before you start, watch the finished machine run slowly, and more than once. Look for two moments. First, the beam drops into the groove. Then the peg lifts the string off. Those two are the whole machine.
Here is what your machine does each time you push the lever. Read it like a program, because it is one.
Three steps, always in that order. They never mix up. Nothing checks. Nothing decides. There is no if, no wait until, and nothing that could fail to run.
| In your EV3 programs | In this machine |
|---|---|
| Blocks in a stack, top to bottom | The lever’s path, front to back |
A wait until that holds the next step back | A peg that is not under the slot yet, because the lever has not got there |
| To change the order, you drag blocks | To change the order, you rebuild the machine |
| A mistake stops the program | A mistake jams the machine, loudly |
Both ways work. Each one has a good side and a bad side. You can change a program in ten seconds. But it can go wrong in ways nobody expected. You cannot change a machine without tools. But it cannot get the order wrong at all. The wrong order just cannot happen.
This is not just old history. Many cars will not start while they are in gear. A microwave cannot run with the door open. No program checks that. Opening the door breaks the electric path. A lift door cannot open between floors.
Each time, someone decided the rule was too important to leave to a program. You met this in Lesson 19. There, the Archery Robot had to refuse to fire a bow that was not pulled back. You built that safety lock in blocks. The machine did not do it for you.
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.
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.
If the order really matters, build it into the shape. A machine part cannot forget.
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.
Say this back before moving on: “Load, cock, release — and the lever is the program.”
Look at your model. Which electronic parts can you find? Look carefully before you read on. This is only the second model in the whole course where the answer is none.
| Part | What it is doing here |
|---|---|
| The magazine | Holds the beams and drops them down one by one. Its height sets how many shots you get. It must be just wide enough for one beam. |
| The lever | The only input. Everything the machine does depends on how far the lever has moved. |
| The bow and its band | Stores the energy. It is like Level 1’s Elastic Car in a new shape. Slow in, fast out. |
| The release peg and slot | The cleverest part. It is a wait until made of plastic. It cannot lift the string until the lever has come far enough. |
| The groove | Guides the beam. If it is too loose, the beam sits crooked and jams. If it is too tight, the beam rubs and does not fly as far. |
The Elastic Car was the first, in Level 1. Very few models have nothing electronic. These two show the same idea in different ways. The Elastic Car stores energy with no program. This one stores steps in order with no 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.
This model uses none of them. But the rule is still worth saying. The fun question is: what would it take to add one?
| If you wanted to… | You would need | And it would go in |
|---|---|---|
| Count the shots | a Touch Sensor pressed by the lever at the end of its push | port 1 |
| Know when the magazine is empty | a Colour Sensor looking into the magazine | port 3 |
| Move the lever without your hand | a Large Motor and a handle to turn | port A |
| Refuse to fire when someone is in the way | an Ultrasonic Sensor looking down the range | port 4 |
Each of those is a real challenge for later today. See what they all share: they let the machine know things. But it already does its job fine without them. The machine does not need a sensor. A person who wants to count, or keep a record, or get a warning does.
Check your own build now:
In every other lesson, you check the Brick’s screen here. There is no screen. So check the machine instead, with the magazine empty.
Step 1 is like reading the port tiles. You check the machine can do its job before you ask it to. On an EV3 model, you check a screen. Here, you watch a peg.
This is the main part of the lesson. It is a real test where you measure things. Draw a table with three columns: what I changed, shots that fed, distance. Fill it in as you go. Change one thing at a time. Fire three shots for each setting before you believe anything.
Step 6 is the surprise at the end. The machine makes sure the three steps come in the right order. But it cannot tell whether each step worked. A shape can keep steps in order. Only a sensor can notice when something goes wrong. That is why so many of your lessons use sensors. This machine is very clever, and 2,000 years old. But it still cannot count.
Build the order into the shape. Build the checking into the program. Do not expect one to do the other’s job.
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.
The same build on Google Drive — sometimes a video, sometimes a scan:
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.

There is no program in this lesson. Not even a short one. The lever is the program. Your hand gives the power.
Run the machine properly. Notice what your hand is doing.
What success looks like: you move the lever back and forth without stopping. Each push fires one shot. You do not fiddle between shots. The magazine empties with no jam.
Stop and notice what is not happening. You are not telling it when to load. You are not telling it when to let go. You give the movement. The machine gives the order. Every EV3 model so far has needed you to give both.
If a push fires nothing, the beam did not drop. Check the magazine is not stuck. If a beam falls out of the groove, it lets go too early. The peg reaches the slot before the pull is done. That is a building problem. It is not about how you move the lever.
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.
Fire every arrow in a full magazine with no jams. The magazine is the box that holds the arrows. Write down how many arrows came out, and how many you put in.
Pull the string back to three different lengths. Fire three shots at each length. Measure how far each shot goes. Say which length lands closest to the same spot each time.
Change the magazine or the groove so the arrows feed out better. Then prove it is better. Fire ten shots before the change and ten shots after.
This machine has no motors or sensors. Add ONE EV3 part to it. Then it can count its own shots. It can also tell you when the magazine is empty. The old machine could never do that. Choose the part and the port yourself. Write down why you chose them. Then show it counting right through a full magazine.