MAQUEEN LAB // Mission Ops · 12-Op Field Manual

▸ WELCOME

MAQUEEN LAB // Mission Guide

12 robot missions · 90 min each · for kids 10 and up

For: kids who like inventing Robot: Maqueen Lite v4 You'll do: build · explore · have fun

▣Maqueen

Hi inventor! Welcome to my lab.
You're about to do 12 missions with me — that's about 18 hours of robot fun. By the end, you'll know how to wake a robot up, make it drive itself, draw a path it follows, play tunes, and even battle a friend's robot.
Real engineers at NASA, MIT, and big robotics labs use the same ideas. We just made them way more fun.

▸ HOWHow each mission flows

Every mission goes through the same 4 steps: watch → try → challenge → talk about it. Repeat each lesson.

→ Same 4 steps every mission. Like a game level.

▸ LISTThe 12 missions

#	Mission	Group	What you'll learn
M-01	Wake the Robot	BASICS	How the tablet talks to the robot
M-02	Speed Lab	BASICS	Fast vs careful — when each is better
M-03	Robot Senses	BASICS	How the robot "sees" — sonar, line, IR
M-04	Robot Brain	SENSING	How the robot decides what to do
M-05	Live Map	SENSING	The robot draws a map of where it went
M-06	Draw to Code	SENSING	Your first program — by drawing!
M-07	Sound Lab	CODING	Make robot tunes · decode Morse
M-08	Servo Engineer	CODING	Precise angles · invent a robot arm
M-09	Data Detective	CODING	Be a real scientist — guess, test, prove
M-10	Path Finder	SMART STUFF	How Google Maps finds the shortest path
M-11	Robot Duels	SMART STUFF	2 robots playing together
M-12	Big Mission	SHOWCASE	Use everything you learned in 1 cool show

▸ KITStuff you need

// THE ROBOT & STUFF

1 Maqueen Lite v4 robot for every 2-3 kids (fully charged!)
1 micro:bit per robot (already programmed)
1 tablet or laptop per group (with Bluetooth)
USB-C cable (just in case the battery dies)
Power strip and chargers

// CRAFT SUPPLIES

Black masking tape (to make line tracks)
Cones or paper cups (for obstacle courses)
A4 paper and pens for every kid
Stopwatches (1 per group)
Stickers or badges (treats for finishing)

HEADS UP: charge the robots the day before. A dead robot in the middle of a mission is no fun!

▸ TIPSTips for the grown-up running this

TIP 1

Hands off the keyboard. If you click for the kids, they don't learn. Talk them through it instead.

TIP 2

Cheer mistakes. "Cool, that didn't work! What does that tell us?" Mistakes are how we learn.

TIP 3

Watch the clock. Stick to the time so we don't run out. Some kids will still be working — that's fine.

TIP 4

Ask, don't tell. "What happens if…?" works way better than just explaining the answer.

TIP 5

Praise trying. A kid who tried 5 things and they all failed learned more than a kid who got it right first try.

TIP 6

Always end with a chat. Save the last 10 minutes to talk about what we did. Don't skip this part.

▸ MISSION 01 · ★☆☆☆☆ EASY

Wake the Robot

"Connect by Bluetooth. Learn the STOP button."

Time: 90 minutes How hard: easy Need to know first: nothing

▣Maqueen

Hi inventor! I'm fully charged and waiting for you.
Today's job: connect to me with Bluetooth and practise the STOP button. Once you know how, you can drive me anywhere!

▸ GOALWhat you'll learn today

▸ THE BIG IDEA

How a tablet sends orders to a robot wirelessly.

▸ NEW SKILLS

Connect Bluetooth on your own. Steer with arrows. Hit STOP fast.

▸ HOW TO ACT

Calm, careful, safe. The robot isn't a toy car — treat it well.

UICONSOLE LAYOUT

// What you'll see: connect button (left) · arrows to drive (middle) · STOP button (right)

▸ HOWStep by step

// PART 1 · CONTACT (10 min)

Brief kids in semicircle. Display sleeping robot.
Probe: "How is order signal delivered to this robot?" Collect hypotheses (Wi-Fi, telepathy, cosmic rays, magic). Acknowledge all, validate Bluetooth.
Demo: grown-up taps ⌘ CONNECT. Unit LED responds. Drive forward 1s. Halt.
State the two inventor controls: blue ⌘ = link, red ⏹ = halt. That's the entire today.

// PART 2 · CONNECT IT YOURSELF (10 min)

Group split. Each takes a tablet + a robot.
Tap ⌘ → BLE picker → select "Maqueen…" → confirm Pair.
FAB hides on success = connection confirmed.
Each group: connect, drop, explorenect ×2. Build muscle memory.

PAIR FAILURE = device side, not robot. Toggle device BT off/on. Re-launch app.

// PART 3 · FREE SCOUT (20 min)

"You have 20 min. Drive. No goals. Don't break stuff."
HANDLER STAYS HANDS OFF. Observe. Note who needs help later.
10 min in: drop hint — "anyone tested speed slider?"
5 min remaining: "execute a perfect 360°."

// PART 4 · The STOP button (10 min)

All robots halted. Tablets down.
Drive at 100% toward instructor's foot. Half-second before impact: tap ⏹. Unit freezes.
Group repeats in unison: "RED = HALT. ALWAYS REACHABLE."
Sign Inventor Code below.

// MY ROBOT PILOT PROMISE

Agent __________________________ hereby commits to:

I always know where the red ⏹ STOP button is.
NOT directing robot at personnel, fauna, or hardware.
Defaulting to HALT in any uncertainty.

Signature: __________________________ Date: ____________

- - - - - - cut · kid retains copy - - - - - -

// PART 5 · SLALOM EXERCISE (25 min)

Set 4-6 cones in zigzag, 50 cm spacing.
Objective: clear without contact.
RD-1: single run per kid. Timed. Disqualified on contact.
RD-2: kid picks speed (10/30/50/80%). Most fail at 80% — natural lesson.
RD-3: blindfold pilot. Wingman provides verbal vector. Trust + comms drill.

// 4-marker zigzag · serpentine path

// PART 6 · SHARE (15 min)

Circle. Units OFFLINE. Tablets stowed.
Each kid reports: 1× hardest moment, 1× unexpected discovery.
Grown-up: "You are now INVENTORS. Next op: pilots."
Distribute Operator badge.

EXECFIELD CONSOLE

// LIVE UNIT SIMULATION
Click commands. Verify response. This mirrors actual hardware behaviour.

[STATUS] awaiting command

◀ HQ OP-02 ▶

▸ MISSION 02 · ★☆☆☆☆ EASY

Speed Lab

"How fast is too fast? Test the brakes."

Time: 90 minutes How hard: easy Need to know first: Mission 1

▣Maqueen

[TELEMETRY ACTIVE] You will profile my acceleration and braking envelope at multiple throttle settings. Plot the curve. Trade-off discovery: velocity vs control. Engineering 101.

▸ GOALWhat you'll learn

▸ THE BIG IDEA

Trade-off: every gain costs something. Velocity costs precision.

▸ NEW SKILLS

Throttle calibration. Read & produce data charts.

▸ HOW TO BE

"Max everything" rarely wins. Patience is cool.

UITHROTTLE CONTROL

// throttle slider · 0-100%

▸ HOWStep by step

// PART 1 · WARM-UP (5 min)

Speed-connection race. Fastest connect wins.
Safety probe: "Where is ⏹?" — all kids point.

// PART 2 · 3-VELOCITY TRIAL (15 min)

Throttle 10%. Drive forward 3s. Mark stop position with tape.
Reset. Throttle 50%. Drive 3s. Mark.
Reset. Throttle 100%. Drive 3s. Mark. Compare distances.
Same time, vastly different displacement. Discovery: throttle is non-linear distance multiplier.

// PART 3 · BRAKE PROFILING (20 min)

Tape START line. Unit behind it.
Drive forward. Trigger ⏹ when nose crosses line.
Mark actual rest position. Measure overshoot = brake distance.
Repeat at 30%, 60%, 100%. 3 trials each. Tabulate.

Throttle	Trial 1	Trial 2	Trial 3	Mean
30%	____ cm	____ cm	____ cm	____ cm
60%	____ cm	____ cm	____ cm	____ cm
100%	____ cm	____ cm	____ cm	____ cm

FINDING: doubling velocity more than doubles brake distance. Kinetic energy is non-linear (∝ v²).

// PART 4 · PRECISION DOCKING (25 min)

Tape 30×30 cm dock zone. Distance: 1m.
Objective: park fully inside the zone.
3 attempts. Agent selects throttle.
Score: 3 = fully inside. 1 = touching line. 0 = outside.
Highest score earns Velocity Specialist badge.

// PART 5 · DATA PLOT (15 min)

Each kid: graph paper.
X-axis: throttle %. Y-axis: brake distance (cm).
Plot 3 datapoints. Connect line.
Question: "Is the line straight?" (Negative.) The curve bends upward.
This is your first physics chart. Same exact technique used in F1 telemetry.

// expected curve · non-linear (∝ v²)

// PART 6 · FIELD APPLICATION (10 min)

"Why do schools have speed bumps?"
"Why F1 cars use ceramic brakes?"
"Same math at 0.5 m/s as at 90 m/s. You just measured it."

EXECVELOCITY CONSOLE

Tune throttle. Smash brake. Read overshoot.

THROTTLE: 50%

[OVERSHOOT] --

◀ OP-01 OP-03 ▶

▸ MISSION 03 · ★★☆☆☆ MEDIUM

Robot Senses

"How does the robot 'see'? Sonar, line, IR."

Time: 90 minutes How hard: medium Need to know first: Mission 1

▣Maqueen

[SENSOR ARRAY ONLINE] I have three perception channels: SONAR (acoustic ranging), LINE (optical reflectance), IR (modulated infrared). All three convert physical reality → numbers. Today: profile each.

▸ GOALWhat you'll learn

▸ THE BIG IDEA

Sensors transduce physical → digital. No magic.

▸ NEW SKILLS

Read live sensor channels. Predict before measuring.

▸ HOW TO BE

Empathy via blindfold drill. Build sensor intuition.

DOCSENSOR ARRAY MAP

// 3 input channels (SONAR/LINE/IR) · 1 output (LED) · 2 actuators (motors)

▸ HOWStep by step

// PART 1 · BLIND DRILL (10 min)

Each kid blindfolded. Wingman provides verbal vector.
Walk between two cones. No vision.
Talk about it: "What was missing?"
Frame: "This is the robot's default state — until we add sensors."

// PART 2 · CH-A: SONAR (20 min)

FACT: bats locate prey in pitch-black using ultrasonic ranging. Same physics. The robot's HC-SR04 emits 40 kHz pulse, times the echo.

Open live sensor strip. Highlight SONAR readout.
Hand at 10 cm → read value. 50 cm → read again.
Dynamic test: hand moves close-far-close. Number tracks live.
PREDICT-THEN-MEASURE: grown-up holds object, kids WRITE prediction, then measure. Closest wins.

// PART 3 · CH-B: LINE SENSORS (15 min)

Lay black tape strip on white floor (50 cm).
Slide robot manually across. Watch L/M/R values.
Black = low return. White = high return. Optical reflectance.
Calibration probe: dark cardboard, mirror, fabric. Which gives most anomalous reading?

// PART 4 · ARRAY DOCUMENTATION (25 min)

Distribute paper outline of robot (or freehand sketch).
Label every sensor with: name · channel · robots · vector (where it points).
Color code: amber=sonar, green=line, orange=IR, cyan=LED, neon=motor.
Best maps go on wall. Reference doc for the term.

// FIELD MANUAL · SENSOR ARRAY DIAGRAM

Sketch robot (top view). For each sensor record:

NAME (sonar / line / IR / LED)
CHANNEL (A / B / C / D)
MEASURES (distance / reflectance / signal)
UNITS (cm / 0-1023 / on-off)
VECTOR (front / down / omni)

- - - - cut · kid retains - - - -

// PART 5 · PREDICTION DRILL (10 min)

Grown-up presents objects sequentially: hand · book · pillow · glass.
Kids write SONAR prediction PRE-measurement.
Reveal actual. Closest = point.
ANOMALY: pillow absorbs ultrasonic → reads farther than reality. Acoustic black hole.

// PART 6 · FIELD APPLICATION (10 min)

Photo evidence: car parking sensors · drone obstacle detection · vacuum bots.
"What sensor would you ADD to this robot?"
Top 3 wildest concepts go on the wall.

EXECSONAR LAB

Drag obstacle. Read range. Channel A active.

OBSTACLE POSITION:

◀ OP-02 OP-04 ▶

▸ MISSION 04 · ★★☆☆☆ MEDIUM

Robot Brain

"Can a robot think? How does it decide what to do?"

Time: 90 minutes How hard: medium Need to know first: Missions 1 & 3

▣Maqueen

[AUTONOMY MODE] I will pilot myself today. You don't touch the controls. I read sensors, apply rules, drive motors. Loop at 10 Hz. Different rule sets = different "behaviour profiles". Today: hack all four.

▸ GOALWhat you'll learn

▸ THE BIG IDEA

Algorithm = sensor input + rule logic + motor output. Repeat 10 Hz.

▸ NEW SKILLS

Switch profiles. Observe scientifically. Verbalise rules.

▸ HOW TO BE

Critical thinking on AI. De-mystify "intelligence" claims.

DOCBEHAVIOUR PROFILES

Profile	Rule logic	Output signature
SCOUT	IF sonar < 25 cm: rotate random. ELSE: forward (low velocity).	Cautious · slow
STANDARD	IF sonar < 20 cm: rotate AWAY from contact. ELSE: forward.	Smart · balanced
FAST	IF sonar < 15 cm: snap-rotate fast. Forward at high velocity.	Aggressive · ballistic
DEMO	Pre-encoded choreography (figure-8, spiral).	Showcase · scripted

DOCAUTONOMY LOOP

// every "intelligent" kid runs this loop. Differences = the rule logic.

▸ HOWStep by step

// PART 1 · AUTONOMY DEMO (10 min)

Pre-arm a robot in STANDARD profile.
Place in arena. Tap autonomy button.
Walk in front. Unit rotates away. Pause for reaction.
Open question: "Is this thinking?" Collect answers. Don't reveal yet.

// PART 2 · PROFILE TOUR (15 min)

Run SCOUT profile · 1 min observation.
Run STANDARD · 1 min.
Run FAST · 1 min. Note: faster reactions, near-misses.
Run DEMO · 1 min. Pre-scripted moves.

// PART 3 · SCIENTIFIC OBSERVATION (20 min)

Each group assigned ONE profile.
5 min observation. Document:
· Average velocity (slow/medium/fast)?
· Reaction latency to obstacles?
· 3 descriptive adjectives.
· Stuck conditions? Where?

// PART 4 · INTEL BRIEFING (10 min)

Each group: 90 sec briefing to peers.
Demo + adjectives + critical findings.
Q&A: 1 question per briefing.

// PART 5 · DEBATE STEPS (15 min)

QUESTION: "Does autonomous wander = intelligence?"
Two camps: AFFIRM / DENY.
4 min argument per side.
Reveal rule table from above. Discuss.
FINDING: "AI = sensors + rules + speed. No magic."

Same loop powers: phone autocorrect · Netflix recs · ChatGPT · self-driving cars. Bigger rule sets, same architecture.

// PART 6 · CUSTOM PROFILE DESIGN (15 min)

Each kid designs profile #5 on paper.
Required: name, identifier, rule logic in plain language.
Bonus: cool scenario where this profile excels.

// PROFILE BLUEPRINT · AGENT CUSTOM

Designation: ____________________ ID: _______

Rule logic:

IF sonar < ____ cm → action: ____________________

IF path clear → action: ____________________

BONUS RULE: ____________________

Cool use case: ____________________

- - - - cut · kid retains - - - -

EXECPROFILE SWITCHER

Switch profile. Observe behaviour change in real-time.

[STATUS] profile inactive

◀ OP-03 OP-05 ▶

▸ MISSION 05 · ★★★☆☆ HARDER

Live Map

"The robot draws a map of where it went. Like a GPS!"

Time: 90 minutes How hard: a bit harder Need to know first: Missions 1 & 3

▣Maqueen

[ODOMETRY ONLINE] I count wheel rotations. 1 turn = 25 cm. Multiply. Add to position estimate. Repeat. This is dead reckoning. Same technique used since 1500s. Reliable... but errors compound.

▸ GOALWhat you'll learn

▸ THE BIG IDEA

Odometry · cumulative drift · why GPS fusion exists.

▸ NEW SKILLS

Read SLAM display. Compare expected vs actual paths.

▸ HOW TO BE

Healthy skepticism toward computer-generated estimates.

DOCODOMETRY MATHEMATICS

// rev_count × wheel_circumference = displacement

▸ HOWStep by step

// PART 1 · MAP SEMANTICS (10 min)

Display 3 reference maps: subway · floor plan · satellite.
Probe: "What data is encoded? What is omitted?"
List 5 maps used in past month: Maps app · mall · board game · etc.
Frame: map = simplified model of reality.

// PART 2 · LIVE BUILD (20 min)

Open MAP tab. Empty SVG canvas.
Drive forward 1 m → green vector appears.
Drive 1×1 m square → path renders.
SONAR pings appear as red obstacle markers.
Free explore: drive shapes, names, cool patterns.

// PART 3 · DRIFT PROFILING (15 min)

Mark START origin.
Drive 2×2 m square. Return to origin.
MEASURE: actual rest position. Compare to map's reported position.
The gap = drift. Measure in cm.
Repeat ×3. Drift varies each trial.

DRIFT SOURCES: wheel slip · surface inconsistency · mismatched motor calibration · sensor noise. All real-world. All cumulative.

// PART 4 · COMPARATIVE TRIAL (15 min)

Two robots · same route (forward 2m, rotate 90°, forward 2m).
Compare maps side-by-side.
"Identical?" Negative. Each robot drifts uniquely.

// PART 5 · GPS DOCTRINE (10 min)

"Imagine self-driving car using ONLY odometry."
Calculate: 1% drift × 10 km = 100 m offset. Mission failure.
SOLUTION: sensor fusion = odometry + GPS + cameras + IMU + LIDAR.
Unit's map valid for ~5 min. Real systems: hours.

// PART 6 · MY MAP (15 min)

Each kid: sketch own bedroom (or commute) as SLAM-style map.
Required elements: scale bar · north arrow · 3 labelled obstacles.

// FIELD MAP · AGENT TERRITORY

Sketch your zone. Required:

Origin marker (▮)
Path traced (green vector)
3 obstacles labelled (▲)
Scale bar (10 cm = 1 m)
North arrow (▲N)

- - - - cut · kid retains - - - -

EXECSLAM CONSOLE

Click in canvas to drop position waypoints. Watch path build.

[PATH] 0 cm

◀ OP-04 OP-06 ▶

▸ MISSION 06 · ★★★☆☆ HARDER

Draw to Code

"Draw a path · the robot follows it · that's coding!"

Time: 90 minutes How hard: a bit harder Need to know first: Mission 5

▣Maqueen

[AUTOPILOT MODULE LOADED] You sketch a trajectory. I follow it autonomously. Save the file = your first program. No keyboard. No syntax. Pure logic. Real engineers do this with code, but the principle: identical.

▸ GOALWhat you'll learn

▸ THE BIG IDEA

Programming = pre-defined ops vs real-time control.

▸ NEW SKILLS

Trajectory mode. JSON save/load. Replay.

▸ HOW TO BE

Pride: first useable program in your name.

DOCDRIVING vs PROGRAMMING

// MANUAL CONTROL

Real-time decisions.

Each command issued live.

Latency: human reflex (~200 ms).

// PRE-PROGRAMMED

Plan everything upfront.

Unit executes alone.

Latency: 0. Repeatable. Saveable.

▸ HOWStep by step

// PART 1 · AUTOPILOT DEMO (10 min)

Open MAP tab. Tap TRAJECTORY (✏️) mode.
Finger-paint a curve on canvas.
Release. Unit follows autonomously.
Demo 2-3 different shapes.

// PART 2 · PRIMITIVE SHAPES (20 min)

Each kid: draw straight vector. Execute.
Triangle. Loop.
Unit rarely matches exactly. Why? Drift (OP-05).
3-5 attempts. Failure is data.

// PART 3 · SAVE PROGRAM (10 min)

After successful path, tap SAVE.
Browser exports JSON file. Open in text editor.
OBSERVE: trajectory now = numbers.
{x:12, y:30}, {x:14, y:32}, ...
"This is exactly what code looks like under the syntax."

// PART 4 · INITIAL TRACE OP (25 min)

Objective: trajectory traces your initial letter.
Tape blank canvas on floor (or paper).
Optional: mount marker on robot. Compare drawn vs executed.
Vote: best initial. Winner gets Programmer designation.

// PART 5 · CROSS-UNIT REPLAY (10 min)

Each kid loads partner's saved JSON.
Execute on own robot.
FINDING: identical file, different robot, different result. Hardware variance + drift.
Real software faces this constantly. Portability ≠ identity.

// PART 6 · BEST-PATH COMPETITION (10 min)

Target shape defined: star · target · circuit.
Each group designs trajectory. Execute.
Score: deviation from target.
Winner: Programmer Lv.1.

EXECTRAJECTORY LAB

Drag to draw. Release. Tap PLAY. Unit follows.

◀ OP-05 OP-07 ▶

▸ MISSION 07 · ★★☆☆☆ MEDIUM

Sound Lab

"Make the robot sing! And learn to read Morse code."

Time: 90 minutes How hard: medium Need to know first: Mission 1

▣Maqueen

[PIEZO MODULE ACTIVE] My buzzer outputs square waves at any frequency I command. Frequency = pitch. Duration = rhythm. You'll synthesize a 4-tone signature and decode a Morse transmission. Real comms engineering.

▸ GOALWhat you'll learn

▸ THE BIG IDEA

Sound = vibration. Hz = vibrations/sec. Pitch is frequency.

▸ NEW SKILLS

Synthesize tones. Decode Morse. Compose signature pattern.

▸ HOW TO BE

Pattern recognition within constraints. Engineering creativity.

DOCSIGNAL FREQUENCY

// frequency in → vibration out → sound waves

▸ HOWStep by step

// PART 1 · BUZZER PROBE (10 min)

Display buzzer module. Identify physical component.
Open BUZZER panel. Output 100 Hz · 440 Hz · 2000 Hz.
"What's the smallest pitch difference you can resolve?" Test.

// PART 2 · PIANO INTERFACE (20 min)

Open piano keys.
5 min free play. Find one tonal sequence.
Hum it to wingman. Can they reproduce?
Frame: musical notation = sequence encoder.

// PART 3 · 4-TONE SIGNATURE (25 min)

Pairs. 5 min to compose 4-tone signature.
Encode on paper: C4 - E4 - G4 - C5 (250 ms each)
Designate signature: "Explore Echo", "Fast Lead", etc.
Reproduce 3× identical = signature certified.

// SIGNATURE LOG

Designation: ____________________

Tone sequence: ___ - ___ - ___ - ___

Duration each: ____ ms

Missional use: __________________________________________

- - - - cut · kid retains - - - -

// PART 4 · TRANSMISSION DRILL (15 min)

Each pair performs signature in front of group.
Audience scores: clarity / originality / mission-feel.
Top signature gets Signal Tech designation.

// PART 5 · MORSE DECODE (10 min)

CONTEXT: Morse = oldest digital steps. Used 1844-present (CW radio still missional). SOS = · · · ─ ─ ─ · · ·

Open MORSE decoder panel.
Grown-up transmits 5-letter callsign via buzzer.
Kids decode using standard chart.
First to extract callsign = point.

// PART 6 · FIELD APPLICATION (10 min)

Spotify · headphones · voice notes — all audio = digital samples.
"Why do MP3 files exist?" — compress without losing pitch info.
Buzzer skips the recording step. Same physics.

EXECSIGNAL CONSOLE

Click keys. Listen to buzzer output. Audio required.

// SUGGESTED: C - E - G - C5 = ascending major

◀ OP-06 OP-08 ▶

▸ MISSION 08 · ★★★☆☆ HARDER

Servo Engineer

"Send the arm to exact angles · invent something cool!"

Time: 90 minutes How hard: a bit harder Need to know first: Mission 1

▣Maqueen

[SERVO PORT S1/S2 ACTIVE] Servos differ from motors. Servo = precise angle. Motor = continuous rotation. You command 47°. Servo goes to exactly 47°. Used in: 3D printers, surgery robots, RC aircraft, animatronics. Today: design a payload attachment.

▸ GOALWhat you'll learn

▸ THE BIG IDEA

Position control vs velocity control. Different tools.

▸ NEW SKILLS

Send angle commands. Sweep mode. Mechanical design on paper.

▸ HOW TO BE

Mechanical empathy. Hardware has tolerances and limits.

DOCMOTOR vs SERVO

▸ HOWStep by step

// PART 1 · SERVO INTRODUCTION (10 min)

Pass real SG90 servo around. Identify connector, horn, body.
Read 0° / 90° / 180° on dial.
Open SERVO panel. Send 0°.
Snap response on screen + physical horn (if connected).

// PART 2 · ANGLE REACTION DRILL (15 min)

Grown-up calls angles: "45!" Kids tap 45° fastest.
Sequence: 75 · 135 · 0 · 180. Speed test.
BONUS: "Wave at me." Agent encodes a sweep.

// PART 3 · SWEEP MODE (10 min)

Activate continuous sweep 0↔180.
Adjust frequency.
"Industrial parallels?" → fan · sonar scanner · sprinkler · windscreen wiper.

// PART 4 · PAYLOAD DESIGN (30 min)

YOU are the engineer.
Design a paper attachment for the servo horn.
Constraints: must use 0-180° range. Must serve a cool function.
Reference designs: flag useer · indicator head · sonar tower · grip claw · card flipper.
Sketch · cut · scale to 25 mm horn · mount and execute.

// PAYLOAD BLUEPRINT

Designation: ____________________

Function: ____________________

How does it use the angle:

0° configuration: ____________________
90° configuration: ____________________
180° configuration: ____________________

Sketch (top view):

- - - - cut · kid retains - - - -

// PART 5 · DESIGN BRIEFING (15 min)

Each kid: 60 sec briefing.
Audience scores: cool utility · engineering creativity · likely failure mode.
Best design: Mechanical Engineer designation.

// PART 6 · WHERE SERVOS LIVE (10 min)

Reference imagery: 3D printer arms · robotic surgery · RC aircraft control surfaces · Disney animatronics.
"Anywhere precise angles matter, there is a servo."

EXECSERVO LAB

Drag slider. Hit waypoint buttons. Watch arm.

ANGLE: 90°

◀ OP-07 OP-09 ▶

▸ MISSION 09 · ★★★☆☆ HARDER

Data Detective

"Be a real scientist · guess · test · prove or disprove."

Time: 90 minutes How hard: a bit harder Need to know first: Missions 2 & 3

▣Maqueen

[TELEMETRY STREAM ACTIVE] You become engineers. Form a hypothesis. Test it. Read live charts. Conclude. Same steps used at JPL · CERN · Tesla R&D. Smaller scale. Identical method.

▸ GOALWhat you'll learn

▸ THE BIG IDEA

Scientific method: hypothesis → experiment → data → conclusion.

▸ NEW SKILLS

Read live charts. Export CSV. Compare runs.

▸ HOW TO BE

"I think" → "I measured." Confidence built on evidence.

DOCSCIENTIFIC METHOD · 5-STEP STEPS

// Same 5 steps · NASA · Pasteur · Tesla · YOU

▸ HOWStep by step

// PART 1 · TELEMETRY BRIEFING (10 min)

Reference imagery: F1 dashboard · ISS mission control · spacecraft data feeds.
"All this = numbers about a machine, streamed live to engineers."
Open GRAPH tab. Drive. Live chart builds.

// PART 2 · CHART READING (15 min)

Drive at 50% steady. Chart = flat line.
Drive 100% × 2s, halt. Spike + drop.
X-axis: time. Y-axis: velocity.
Match motion to chart shape. Drill.

// PART 3 · EXPERIMENT SETUP (20 min)

HYPOTHESIS: "Does carpet reduce velocity vs hard floor?"
Each kid: WRITE prediction. Yes/no? Magnitude?
Test setup: 1 m hard floor + 1 m carpet (doormat).
Steps: drive at 80% across each surface. Record peak velocity.

// PART 4 · TRIAL EXECUTION (20 min)

Each group: 3 trials per surface. 6 total.
Read peak velocity from chart per trial.
Average per surface.
Compare to hypothesis.

// Expected divergence · the data confirms or refutes

// PART 5 · CONCLUSION + EXPORT (15 min)

Each group: 1-sentence conclusion using actual numbers.
Tap EXPORT → CSV. Open file.
"This is what every doctor, weather forecaster, engineer keeps."

// EXPERIMENT LOG

Hypothesis	Carpet reduces velocity by ____%
Hard · trial 1	____ cm/s
Hard · trial 2	____ cm/s
Hard · mean	____ cm/s
Carpet · trial 1	____ cm/s
Carpet · trial 2	____ cm/s
Carpet · mean	____ cm/s
Delta	____ %
Hypothesis confirmed?	YES / NO / PARTIAL

- - - - cut · kid retains - - - -

// PART 6 · INDUSTRY PARALLELS (10 min)

Same steps: doctors with heart-rate data · weather forecasters with temperature · banks with stock prices · Tesla with Autopilot logs · NASA with rover telemetry. Identical 5-step steps.

◀ OP-08 OP-10 ▶

▸ MISSION 10 · ★★★★☆ HARD

Path Finder

"How does Google Maps find the fastest route? Same trick!"

Time: 90 minutes How hard: hard Need to know first: Missions 5 & 6

▣Maqueen

[PATH PLANNER ENGAGED] Algorithms are recipes for computers. Today: solve a maze on paper. Then watch A* algorithm solve the same map autonomously. Same algorithm runs in: Google Maps · chess engines · video games · self-driving routing.

▸ GOALWhat you'll learn

▸ THE BIG IDEA

Algorithm = step-by-step rule that always terminates.

▸ NEW SKILLS

Solve maze. Verbalise strategy. Compare to A*.

▸ HOW TO BE

De-mystify "AI". It's clever rules + compute.

DOCALGORITHM = RECIPE

▸ HOWStep by step

// PART 1 · MANUAL MAZE SOLVE (15 min)

Distribute printed 5×5 maze. Start S → Goal G.
Solve with pencil.
TIME each kid. Record fastest.

// PART 2 · STRATEGY SHARE (10 min)

Each kid: state strategy in 1 sentence.
Common: "headed toward goal" · "tried left first" · "wall-follower".
FINDING: these are all algorithms. You just invented heuristic search.

// PART 3 · A* EXECUTION (20 min)

Open Algorithm Visualizer. Requires SLAM session first.
Click A*. Pick goal coordinate.
OBSERVE:
· cyan cells = frontier (next to evaluate)
· amber cells = explored
· green path = optimal solution
"Did A* explore EVERY cell?" Negative. Only promising paths.

// A* expands most promising cells first · heuristic = manhattan distance

// PART 4 · COMPARATIVE ANALYSIS (15 min)

Side-by-side: kid's pencil path vs A* green path.
Often identical or near-identical.
"What does A* do better?" · counts every step · evaluates all options · never gives up.

// PART 5 · PHYSICAL MAZE (15 min)

Tape obstacles on floor: physical maze with cardboard walls.
Drive robot to map terrain (SLAM).
A* execute → robot navigates autonomously.

// PART 6 · INDUSTRY APPLICATIONS (15 min)

Google Maps "fastest route" = production A*.
Spotify recommendation = different algorithm, same architecture.
Chess engines = brute-force search + evaluation function.
Dishwasher cycle · phone autocomplete · ATM cash dispensing.
"You used algorithms today. No code typed."

◀ OP-09 OP-11 ▶

▸ MISSION 11 · ★★★☆☆ HARDER

Robot Duels

"2 robots playing together · battle then team up!"

Time: 90 minutes How hard: a bit harder You'll need: 2 robots · Missions 1 & 3 done

▣Maqueen

[MESH NETWORK ENABLED] Two robots enter the field. Today: multi-kid missions. Pair · sync · combat steps · comission drill. You'll discover: networks have latency. Communication beats silence. Real engineering.

▸ GOALWhat you'll learn

▸ THE BIG IDEA

Network latency · multi-kid coordination · steps design.

▸ NEW SKILLS

Pair 2 robots. Combat mode. Coordinate timing.

▸ HOW TO BE

Conduct under pressure. Win/lose with discipline.

▸ HOWStep by step

// PART 1 · UNIT PAIRING (10 min)

Both robots active. Both consoles open.
Tap PAIR on both simultaneously. WebRTC connection.
Test: drive robot-A → robot-B mirror displays the action.

// PART 2 · LATENCY OBSERVATION (10 min)

Activate sync mode: both robots execute identical commands.
OBSERVATION: sync is not perfect. ~50 ms wireless latency.
"Why does Zoom freeze? Why multiplayer games lag? Same physics."

// PART 3 · COMBAT STEPS (25 min)

Activate FENCING mode. Each robot's sonar = engagement zone.
Detection within 12 cm = HIT registered.
FIRST TO 3 HITS WINS. Best of 5.
Bonus: phone tilt = "fast velocity". Fast tilt × 2 damage.

// PART 4 · COOP MISSION (25 min)

Mark target coordinate on floor.
Objective: BOTH robots reach target within 1 sec of each other.
RD-1: SILENT MODE. Hand signals only.
RD-2: Voice authorized.
Compare: which round was harder?

// PART 5 · TALK ABOUT IT (10 min)

What enabled victory? Speed? Precision? Aggression? Patience?
What broke coordination? Comms? Latency? Misread?
Real systems facing identical problems: drone swarms · autonomous trucks · multiplayer games · stock trading networks.

// PART 6 · AWARDS STEPS (10 min)

BEST DUELLER (won the most matches)
BEST TEAM (coordination drill)
BEST CONDUCT — peer-voted. Agent who congratulated opponents most.

◀ OP-10 OP-12 ▶

▸ FINAL · MISSION 12 · ★★★★★ BIG ONE

Big Mission!

"Use everything you've learned in one cool team show."

Time: 90 minutes How hard: the big one! Need to know first: Missions 1 to 6 at least

▣Maqueen

This is the BIG ONE! Get into teams of 3 — you'll get a mission scenario, then plan · build · practise · show it. Use any skill from missions 1 to 11. There are no grades — just finish your mission and show the others what you made!

▸ GOALWhat you'll learn

▸ THE BIG IDEA

Engineering = problem → spec → design → build → use. Iterate.

▸ NEW SKILLS

Combine multiple modules into single solution. Public briefing.

▸ HOW TO BE

Ownership · pride · public speaking · accept feedback.

DOCMISSION SCENARIO POOL

Code	Mission	Brief	Required modules
SC-01	PAYLOAD DELIVERY	Drive A→B avoiding 3 obstacles. Use payload via servo.	Drive · sonar · servo
SC-02	SCOUT PATROL	Patrol zone for 60s. Count contacts. Acoustic report.	Wander · sonar · buzzer
SC-03	SIGNAL ESCORT	Drive trajectory while broadcasting custom signature.	Trajectory · buzzer
SC-04	TIME TRIAL	5-cone slalom < 20 sec. 0 contacts.	Drive · velocity
SC-05	SEARCH & EXTRACT	Locate target object in maze. Return to base.	SLAM · sonar · trajectory
SC-06	FIELD DEMO	Plan + execute 30s cool choreography. Document on video.	Any 3 modules

▸ HOWStep by step

// PART 1 · MISSION BRIEF (10 min)

Form teams of 3. Mix skill levels intentionally.
Read scenario. Display arena (taped zones, obstacles, target).
Distribute planning sheet.
Define success criteria. Post on board.

// PART 2 · MISSION PLANNING (15 min)

NO HARDWARE YET. Plan on paper first.
Draw solution architecture: which modules, in what sequence.
Assign roles: operator · analyst · presenter.
Estimate phase durations.
Grown-up validates each plan in 2 min.

// MISSION PLAN · TEAM DECLARATION

Team callsign: ____________________

Inventors: ___________________________________________

Mission code: ____________________

Plan diagram (arena + trajectory):

Modules used: □Drive □Wander □Trajectory □Servo □Buzzer □Sonar □Telemetry

Roles: Operator: ____ Analyst: ____ Presenter: ____

Contingency (if primary fails): ___________________________________________

- - - - cut · kid retains - - - -

// PART 3 · BUILD & ITERATE (35 min)

35 minutes execution window.
Grown-ups ask QUESTIONS only: "What did you try? Why didn't it work? What's next?"
T-20: "10 min to dry run."
T-30: "5 min to usement."

TIMER IS LAW. Teams over time use with whatever state they have. That is engineering.

// PART 4 · DRY RUN (10 min)

Single full rehearsal per team.
NO mid-run fixes.
Document failures. Decide: patch or accept.

// PART 5 · DEPLOYMENT BRIEFING (20 min)

Each team: 4 min MAX.
1 min plan brief · 2 min live usement · 1 min Q&A.
Audience: 1 question per briefing.
Grown-up scores per criteria below.

EVALSCORING MATRIX

Criterion	0	1	2
Mission completed	Negative	Partial	Affirmative
Modules used (≥ 2)	0-1	2	3+
Safe shutdown	Crash	Manual halt	Auto-halt
Briefing clarity	Confused	Adequate	Engaging
Team coordination	Solo	Some sharing	True team

// total /10 · plus category awards: best engineering · best presentation · most failures debugged

FINALDEPLOYMENT CEREMONY

Award final designation: FIELD COMMANDER.
Each kid receives certificate listing all 12 missions.
Group photo with robots.
Final brief: "Same skills work on real spacecraft, drones, autonomous vehicles. Use them."

◀ OP-11 ▶ HQ