Official LEGO Education Build

LEGO Grabber Robot

This page is built around LEGO Education's official SPIKE Prime Super Cleanup lesson. Instead of a vague robot teaser, you get a specific grabber mission, real source links, and a clear explanation of why the robot stays balanced, grabs objects, and responds to code.

Medium2-3 hoursSPIKE Prime Set #45678

Build focus

Grabber robot

A wheeled robot that reaches out and picks objects up.

Logic type

Programmed

Built for the SPIKE Prime hub with a motor routine.

Sensors

Force sensor

Useful for detecting contact and testing the grabber.

Difficulty

3/5 gears

Not a first snap-together toy, but very doable with patience.

Optimized for

Set #45678

LEGO Education SPIKE Prime set.

Big idea

Mechanics + code

Balance, motion transfer, sensors, and functions all work together.

Source-backed, not made up

The official build books contain the exact snapping order. This page acts like the engineering coach beside them, showing what each subsystem is doing and why the design choices matter.

Mission Previewanimated concept view

cleanup lane

Spec

mode = programmed grabber

sensor = force sensor

goal = pick, carry, release

Official lesson

LEGO Education Super Cleanup

Build Book 1

Piece-by-piece assembly PDF

Build Book 2

More official assembly steps

Python lesson

Clean Up with Multiple Functions

Part Catalog

The exact pieces you should be thinking about.

"LEGO bricks" is too fuzzy for a robot project. This build makes the most sense when you think in subsystems: brain, motor, sensor, frame, connectors, and grabber.

SPIKE Prime Hub

1 controller brick

This is the robot brain. It runs the program and powers the mission.

Large Angular Motor

1 motor

This supplies the spinning force that the grabber turns into jaw motion.

Force Sensor

1 sensor

A touch-style sensor that helps the robot notice presses and contact.

Technic Beams

Assorted liftarms

These are the skeleton of the robot. They keep the frame strong and aligned.

Pins and Axles

Lots of connectors

Tiny but important. These let beams pivot, lock, and transfer force.

Wheels and Grabber Pieces

Drive and claw parts

The wheels make it mobile and the front end does the actual cleanup job.

How It Works

The robot feels smarter when you can see the hidden engineering.

A good robotics guide should not stop at "attach the arm." Pick a lens below to see how balance, motion, and code work together in this specific grabber build.

Physics of stability

A wide base fights tipping.

When the grabber reaches forward, the robot's weight shifts. A low, wide base gives the center of gravity more room to stay above the wheels instead of falling outside them.

Wide wheel spacing gives the robot a bigger support area.

Heavy parts mounted low make tipping less likely.

If the claw sticks way out front, the base has to work harder to stay balanced.

Engineering clue

Think of it like leaning forward with a backpack. If your feet are too close together, you wobble.

Ghosted Diagram

center of gravity stays between the wheels

1

Mission Prep

Open the official guides and sort the key parts

Start with the official LEGO Education lesson and build books open in another tab. Then lay out the hub, motor, force sensor, wheels, beams, axles, and pins so you can see the system before you snap it together.

Blueprint view

Lesson

Book 1

Book 2

Why this stage matters

Sorting parts is not busywork. It helps you notice which pieces belong to the chassis, the arm, and the control system, which makes the whole robot feel less mysterious.

Official source note

The exact piece placement lives in LEGO Education's build PDFs. This page is your engineering coach beside those official instructions, not a replacement for them.

Checkpoints

Hub, motor, and sensor are easy to reach

You can tell beams, axles, and pins apart

Official lesson plus Build Books 1 and 2 are open

part IDsystem map

2

Chassis

Build a wide rolling base first

Assemble the low frame that holds the wheels and gives the robot a strong platform. Keep the footprint broad so the robot can reach forward without becoming tippy.

Blueprint view

keep the heavy parts low

Why this stage matters

This is the center-of-gravity step. A narrow base might look sleek, but a wider one is much more stable once the grabber arm swings out.

Official source note

In the official build flow, this is where the robot stops being a pile of parts and becomes a stable machine body.

Checkpoints

Base sits flat on the table

Both wheels turn without rubbing

There is room for the hub to sit low and centered

stabilitycenter of gravity

3

Structure

Raise the front tower and arm support

Add the upright structure that gives the grabber a place to pivot. This tower is what lets the robot reach outward instead of only pushing objects.

Blueprint view

pivot point for reach

Why this stage matters

Tall structures can wobble if they are not braced well. The trick is giving the arm enough reach while keeping the frame stiff and connected back into the base.

Official source note

Watch how the official build uses Technic geometry to lock the tower into the chassis instead of balancing it on a single weak point.

Checkpoints

Tower does not twist when you press it gently

Pivot point feels deliberate, not floppy

Arm support lines up with the front of the base

triangulationreach

4

Grabber

Mount the motor, sensor, and front jaws

This is the exciting part. Add the pieces that actually pinch, hold, and respond during cleanup tests, then connect them to the hub with tidy cable routing.

Blueprint view

jaw shape decides the grip

Why this stage matters

The motor supplies rotational motion. The linkage and jaws decide how that motion becomes a squeeze, while the sensor helps the robot react instead of guessing.

Official source note

The official Super Cleanup lesson is about comparing grabber designs, so pay close attention to jaw shape, spacing, and how well the front end traps each object.

Checkpoints

Motor cable reaches the hub comfortably

Grabber opens and closes without scraping the frame

Sensor is mounted firmly and easy to trigger

motion transfersensor feedback

5

Control Logic

Load a simple cleanup routine

Program the robot in short chunks like drive, grab, and release. That keeps the code easier to understand and matches the official Python lesson's focus on multiple functions.

Blueprint view

grab()

drive()

release()

cleanup mission

Why this stage matters

Robotics feels less overwhelming when you separate jobs. If the robot grabs badly, you can fix the grab step without rewriting the whole mission.

Official source note

LEGO Education's Python lesson uses a grabber cleanup challenge to show why splitting code into multiple functions is powerful.

Checkpoints

The hub is connected and ready to run code

Each movement has one clear job

You can test one function at a time

functionsdebugging

6

Fair Test

Run cleanup trials and compare what works

Now test the robot with different objects and notice which shapes are easy or tricky. The real goal is not only making the robot move. It is learning why one design works better than another.

Blueprint view

object

success?

notes

compare results

Why this stage matters

Engineers do not just say, 'It worked once.' They create test criteria, compare results, and then adjust only one variable at a time.

Official source note

The official Super Cleanup lesson specifically asks students to test grabber designs and judge efficiency using clear criteria.

Checkpoints

You have at least two kinds of test objects

You are recording observations, not guessing

You can explain one thing you would improve next

fair testingiteration

Control Logic

Code is easier when the mission is split into small jobs.

The official Python lesson focuses on multiple functions for this cleanup robot. That is the right instinct: one job for grabbing, one for moving, one for releasing.

Drag-and-drop thinking

when program starts

drive_to_trash()

close_grabber()

drive_to_bin()

open_grabber()

This is the mission broken into robot-sized jobs. The names are simple on purpose so you can see the logic before you worry about syntax.

Deep dive

A force sensor gives your program a way to react to the world. Without sensing, the robot just hopes the object is in the right spot. With sensing, it can check before it grabs or after it bumps into something.

Test Lab

Choose a test object and think like an engineer.

The official lesson is about comparing grabber designs using test criteria. Pick an object below and let it tell you what the robot is good at or still needs to fix.

Selected object

Crumpled paper

Challenge: Light, squishy, and easy to push away by accident.

Engineer question: Do the jaws trap the paper, or do they shove it forward instead of holding it?

What this test reveals

This is a great object for checking claw shape and closing speed.

Fair-test rule

Change only one thing at a time. If you change the claw shape, object, and code all at once, you will not know what caused the result.

Score sheet idea

Track success, speed, and whether the object slipped out. Real robot testing is about evidence, not just vibes.

Level Up

Bonus missions that feel like real robotics upgrades.

Once the official build is working, do not stop at "cool, it moves." Upgrade the mission by making your tests fairer, your mechanics smarter, or your code more modular.

Bonus mission

Grabber Showdown

Compare two jaw shapes

Build a slightly wider or narrower front jaw and test both versions on the same objects. Which one is best for round items? Which one wins on rigid blocks?

Bonus mission

No-Motor Remix

Mechanical-only challenge

Rebuild the claw so a rubber band supplies the closing force. You lose the automatic motion, but you gain a cleaner look at linkages and spring energy.

Bonus mission

Going Pro

Make the code modular

Add separate functions for grab(), drive(), and release(), then test each one alone before you run the full cleanup mission.

Want the shortest version of the mission? Build the official robot first, test it on two different objects, then explain one mechanical change and one coding change you would try next. That answer proves you are thinking like a roboticist.