Arm and Claw Together

Try It — Be the Robot

A claw is an effector — the part of the robot that does work on the world. In Project 6 your effector was the front of the robot, and it could only shove. A claw can hold.

Two motors, two jobs

Now act it out

Put a cube on the table in front of you. Pick it up with one hand, move it, and set it back down.

Do it again — slowly this time — and write down every separate movement, in order. Do not skip anything, even the parts that feel too obvious to write.

Try swapping any two of your steps. Pick a pair and describe what would go wrong.

Learn It — Five Numbers and an Order

You already know every block you need. Nothing new gets introduced here — you just use two motors instead of one.

Write down all five positions

Write them on your Robot Card, in name = number form — your numbers will be different from everyone else’s:

Notice the first entry of each group is the port, not a degree number. You now have a whole card of numbers to keep straight — and every one of them is typed into some block, somewhere in your program.

Start in a safe shape

Project 7 gave you the arm rules — gentle speed first, arrows chosen on purpose, and the Start Pose Rule. With two motors, the Start Pose Rule grows by one item: arm down, claw open, both set by hand before you press run. Those are the two home poses now, and both counts start at 0 there.

And every claw program starts with the same three blocks — speeds for both motors, then the arm up out of the way. The claw needs no block at all: it is already open, because you put it there:

Speeds set, arm up, claw open from the start pose. The robot begins every run in a known, safe shape — every single time.

The grab sequence

Every single grab in this project is that sequence. You will build it four times today. Remember how that feels — Project 12 is about fixing it.

Live judged or final position — this changes your strategy

Look at how a mission is scored, not just what it asks for. Two missions can want the same thing and mean very different things by it.

Setting an object down is harder than picking it up

Opening the claw is easy. Opening the claw without dragging, tipping, or flicking the object is the actual skill.

• Lower the arm before you open, so the object has a short drop, not a long one.
• Open, then pause, then back away. Backing off while still opening drags the object with you.
• Back straight away, not on a curve. A curve sweeps the claw sideways through what you just placed.

Do It — Grab, Carry, Stack

Step 1 — Find your claw positions

Same trick as Project 7: claw fully open by hand — that is its home — then open Port View on port D, squeeze the claw gently shut by hand, and write down how far the number moves from open. Your arm numbers are already on your card — now add the claw.

A pom squashes, a cube does not. That is why they get different numbers.

Step 2 — Grab it

New project called Grab. No driving at all — place a cube inside the open claw by hand.

Write the pseudocode first. Two rules: the arm starts up and the claw starts open.

• The cube comes up off the table when the arm rises

Did you need a wait block between every step, or only some of them? How did you decide?

Step 3 — Go grab

New project called Go Grab. Now add driving — the cube sits a short distance away.

• My robot drives to the cube and lifts it
• It does not knock the cube over on the way in

What happened the first time? Most robots either stop too early, stop too late, or push the cube away before the claw gets down.

Step 4 — Put it down without wrecking it

Add to the end of your program: carry the cube somewhere, set it down, and back away leaving it standing.

• The cube stays upright after I let go
• Backing away does not drag or knock it

What did you have to change to stop dragging the cube when you backed off?

Step 5 — Mission 13 Bonus — your first stack7 pts

Start here because it is the easiest stack on the field — the cubes are close together, and it is live judged, so your claw can still be holding the top cube when the judge looks.

• One Unstraight Cube is ON TOP OF another

Step 6 — Mission 12 — complete it16 pts

You already know how to get here — that was Project 5. Reuse your approach code and add the grab.

• Two spilled cubes are stacked
• The stack stands on its own with the lower cube on the black line

Read the “does not score” list again. Why does the lower cube have to be the one touching the line?

Step 7 — Mission 3 — Mixed Freight7 pts

Either order works for the base. Green on yellow, yellow on green — both score. Same colour on same colour scores nothing.

• I have one mixed-colour stack

Step 8 — Mission 11 — Hazard Disposal7 pts

A different grip problem. Poms squash, so your closed position for a pom is not the same as for a cube.

• An orange pom is IN a basket and stays there

Step 9 — Run the whole thing five times

Chain all four missions into one program, same as Project 6 — each mission built in its own small project first, then added to the big run one section at a time.

Which grab was least reliable, and what made that one harder than the others?

Score It — Checkpoint

My best run

My full motor card

Seven numbers now. Copy them somewhere you will not lose them.

Live or final?

Say how each one is judged, and what that means for whether your claw can still be holding it.

Can you do it again?

• I can find and record open and closed positions for different objects
• My programs always start in the safe shape — speeds set, arm up, claw open
• I can write the grab sequence in the right order without looking it up
• I can set an object down and back away without knocking it over
• I can stack one cube on another
• I can tell a live-judged mission from a final-position one and change my plan to match
• I never close the claw past the point where the object stops it

Think about it

Count how many times the six-step grab sequence appears in your program. Now imagine your claw’s closed position changes by 30. How many separate places would you have to edit?

A judge tells your team the Mission 12 stack scored the base but not the bonus. Your robot did everything you programmed. What most likely happened between the judge seeing it and the end of the match?

Your robot can now drive, turn, grab, carry, stack, and release — and it does every bit of it blind. It never checks the world; it just follows the plan. What would change if it could notice things — a line, a wall, a color — while it runs?

Next

You are carrying seven numbers around on a paper card, retyping them into blocks everywhere, and one rebuild would break all of it.

In Project 9 — Names for Your Numbers, those comments become real. You give each number a name once, and the whole program starts using it.