Base Mission
7 points Live judgedA robot is Botguy.
Introductory · EV3 Coding Project 11
Same checking as last time — but now it watches a number instead of a switch. Two numbers, actually.
Student PIN:
Back in Project 3 you turned a wheel with your hand and watched a number change in Port View. You were told to remember it. Here it is.
Open Port View on a wheel motor’s port. Do not run anything — just roll that wheel with your hand and watch its number.
| Question | What I saw |
|---|---|
| What happens to the number when I roll the wheel forward? | |
| What happens when I roll it backward? |
Every Motor Has Been Counting This Whole Time
Since Project 3, your motors have been keeping track of exactly how far they turned — in degrees. Every move for rotations block you have ever run was secretly this count — one rotation is just 360 of these degrees. And degrees are about to earn their keep.
Degrees are the motor’s own unit. To connect them to the real world you need to know how many make an inch on your robot.
| Try | Degrees for 24 inches | Degrees per inch (divide by 24) |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 | ||
| Average |
⚠ Measure Long, Not Short
Use 24 inches, not 3. A small error in a short push turns into a big error per inch. Anything under about a foot is not worth measuring.
Your three numbers are not identical. Why not — and which one should you use?
Wheel Size Decides the Number
One full wheel turn is 360 degrees no matter what wheel is bolted on. But a bigger wheel travels further in that turn — which is exactly why your degrees-per-inch is yours and not somebody else’s. Change your wheels, and this number changes with them.
Check the curtain: multiply your degrees-per-inch by 24. Is that close to what a move for 24 in. block must be counting to? What does that tell you about how the move block works?
Project 10’s checking watched a switch. The exact same checking can watch a number — and the brick hands you two of them as round reporter ovals that fit into any hexagon.
| Code / part | What it means |
|---|---|
| A degrees counted | How far that wheel has rolled since its count was reset. This is the counter from Try It. |
| angle | How far the whole robot has turned. Not the wheels — the robot. It comes from the gyro sensor, a small sensor that feels rotation the way your inner ear does when you spin with your eyes shut. Ours plugs into sensor port 2. |
Both reporters are on the regular shelf: degrees counted in the Motors category, angle in the light-blue Sensors category.
⚠ The Gyro's One Demand: Hold Still
Mount the gyro sensor flat on the robot and plug it into port 2 — while the robot is sitting perfectly still. The gyro learns what “not turning” feels like at the moment it wakes up. Plug it in, or power the brick on, while the robot is moving and the angle will slowly drift all by itself for the rest of the session. If your angle wanders while the robot sits still: unplug the gyro, hold the robot still, and plug it back in.
Look at these two side by side. Only the question changed.
Read the new one out loud: “keep checking the robot’s heading — the moment it has turned past 89 degrees, move on.” The green > hexagon from Project 10 finally gets its job.
In Project 5 you tuned a 90° turn by trial and error, because wheel degrees are not robot degrees. The angle is robot degrees. Here is the turn, rebuilt:
Why This Beats a Wall
A touch sensor only helps where there is something to touch. The angle works anywhere on the field — open floor, mid-run, anywhere. And unlike wheel counting, it does not care if a wheel slipped. It feels the robot itself.
Run that turn and then read the angle in Port View on port 2. You asked to stop past 89. You will see something like 96.
Nothing is broken. Your robot has inertia — it is spinning, and when the checking succeeds and the motors stop, it keeps swinging a little further.
The Fix Is Subtraction
Ask for 89. Land on 96. The is 96 − 90 = 6.
So ask for 89 − 6 = 83 instead, and you will land on 90. Every robot has its own overshoot, and faster speed means more of it.
Turning right, the angle climbs. Turning left, it falls — through zero and into negative numbers. That flips your hexagon:
| Code / part | What it means |
|---|---|
| right turn | steering 100 · wait until angle > 83 |
| left turn | steering −100 · wait until angle < −83 |
⚠ Get the Direction Right or the Checking Never Ends
Spin left while waiting for the angle to pass > 83 and you have a check that can never succeed — the number is falling, away from 83, forever, while the robot spins on the spot like a figure skater who forgot the rest of the routine.
Turning right, count up with >. Turning left, count down with <. Check this before every run.
New project called Gyro Turn. Build the Learn It turn — reset angle, spin at steering 100, wait until past 89, stop. Run it, then read the final angle in Port View on port 2.
| Speed (%) | Asked to pass | Actually landed on | Overshoot |
|---|---|---|---|
| 30 | 89 | ||
| 50 | 89 | ||
| 100 | 89 |
What is the relationship between speed and overshoot? Which speed will you use for turns, and why?
Subtract your overshoot from the target and run again. Keep adjusting until the robot lands on 90.
| Try | Number in my hexagon | Where the angle actually landed |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 |
Copy the turn, flip the steering to −100, flip the hexagon to < −83 (your corrected number, negative). Run it.
In Project 5 you drove a square with four wheel-counted turns and it did not close. Do it again — same square, distances with move for rotations, but every corner turned by the gyro.
| Question | Project 5 | Now |
|---|---|---|
| How close to the starting spot? | ||
| Facing the same way? |
This Is the Whole Point of the Project
Same robot. Same square. The only thing that changed is what the robot was measuring — and suddenly it can come back to where it started.
Your wheel-counted square drifted a little more with every corner. Why does a gyro-turned square not do that?
One more trick with the wheel counter, so you have it when you need it. Reset the count, start moving, wait until A degrees counted passes your degrees-per-inch times 12, stop. That is a 12-inch drive built out of raw checking — the thing move for inches does for you.
| I want | Degrees (inches × DPI) | How far it really went |
|---|---|---|
| 6 inches | ||
| 12 inches |
When would you build a drive this way instead of using a plain move for inches block? (Hint: what if you wanted to check two things at once while driving?)
Mission 9
A robot is Botguy.
Botguy is outside the enclosure AND is touching the warehouse floor.
Your claw can still be holding him. He just has to be clear of the enclosure and down on the floor at the same instant.
Mission 18
Botguy is the Loading Zone.
Botguy is the Loading Zone AND at least one Traffic Cone is the Loading Zone.
Botguy is the Loading Zone AND both Traffic Cones are the Loading Zone.
One Trip, Two Missions, Twenty Points
You just lifted Botguy out of the enclosure for Mission 9. Do not put him down — carry him to the Loading Zone and Mission 18’s base scores too.
This is exactly the kind of thing to look for when you plan a full match: one action, more than one mission.
Mission 18 is final position, so Botguy has to still be when the match ends. Set him down properly and back straight away.
Mission 8
The pallet with the Large Red Cube is the Loading Dock.
One or more Small Red Cubes are the Large Red Cube while the pallet is on the Loading Dock.
⚠ The Pallet and the Cube Travel Together
Read the failures carefully. The Large Red Cube on the Loading Dock without the pallet does not score. Neither does a pallet on the dock with the cube fallen off.
They both have to end up there, cube on pallet, pallet on dock.
Look at What You Already Did to These Cubes
In Project 6 you shoved the Large Red Cube and its pallet off the black line. In Project 9 you stacked Small Red Cubes on top of it for Mission 5.
Mission 8’s bonus asks for a Small Red Cube on the Large Red Cube again — this time with the pallet on the dock. Plan Missions 2, 5, and 8 as one sequence rather than three separate problems, and check with your judges how the scoring overlaps.
| Run | M9 bonus | M18 base | M8 base | M8 bonus | Points |
|---|---|---|---|---|---|
| 1 | |||||
| 2 | |||||
| 3 | |||||
| 4 | |||||
| 5 |
| Mission part | Scored? | Points |
|---|---|---|
| Mission 9 — Bonus (Botguy out and on the floor) | 9 | |
| Mission 18 — Base (Botguy in the Loading Zone) | 11 | |
| Mission 8 — Base (pallet + cube on the dock) | 11 | |
| Mission 8 — Bonus (small red cube on top up there) | 9 | |
| My total | 40 |
These join your motor card. Every precise move from here on uses them.
| Measurement | Value |
|---|---|
| Degrees per inch | |
| Turning speed I use | |
| My turn overshoot at that speed | |
| Hexagon number for a 90° right turn | |
| Hexagon number for a 90° left turn | |
| Inches from my starting box to the loading dock |
| I want the robot to… | The wait-until hexagon says |
|---|---|
| Spin right until it has turned past 45° | |
| Spin left until it has turned past 90° the other way | |
| Drive until the left wheel has rolled 8 inches, using my DPI |
Your battery is half flat, so the robot turns slower. What happens to a turn tuned by wheel degrees in Project 5? What happens to a turn that waits for the angle?
Wheel degrees tell you how far the wheels turned — not how far the robot moved. Name a situation where those two are different.
You have now built the reset-spin-wait-stop turn several times, in several projects. What would you rather do than keep rebuilding it?
You have a robot that can measure. You also have a program that says the same twenty lines over and over.
In Project 12 — Teaching Your Robot New Moves, you give that whole stack a name — and then you just say the name.
Download saves a local copy of your answers. It does not turn in your work automatically; give the downloaded file to your teacher.
KIPR · Botball Explorer — Introductory Projects · © KISS Institute for Practical Robotics 1997–2026