🧪 Parent & Teacher Guide

M.A.S.S. Trap — Science Fair Experiment Helper

SCAN THE QR ON YOUR KID'S DASHBOARD
← Back to M.A.S.S. Trap Home

Quick Jump

🤔 What Is This Thing? ✏️ Why This Matters (A Story for Every Parent) 🎯 The 6 Phases (What Your Kid Sees) 📚 Vocabulary Cheat Sheet 1️⃣ Phase 1: Experiment Setup 2️⃣ Phase 2: Vehicle Intake 3️⃣ Phase 3: Evidence Prep 4️⃣ Phase 4: Pre-Flight Check 5️⃣ Phase 5: Data Collection (The Racing!) 6️⃣ Phase 6: Results & Report 💬 Questions to Ask Your Kid 🔧 Troubleshooting 🏆 What the Judges Want 💬 Community Feedback

🤔 What Is This Thing?

Your kid is using a M.A.S.S. Trap (Motion Analysis & Speed System) — a device built from a $7 microcontroller that turns a Hot Wheels track into a real physics laboratory.

It measures how fast toy cars roll down a track with microsecond precision (that's millionths of a second). The system then calculates speed, momentum, and kinetic energy — the same physics NASA uses to plan rocket launches.

The science fair experiment uses this to test a question like: "Does adding weight to a car make it go faster?"

✅ Your job: You don't need to understand the technology. You just need to ask the right questions and help your kid think about why they're doing each step — not just what they're doing.

✏️ Why This Matters

When Ryan was a kid in Utah, his class got an assignment based on Gulliver's Travels — the one with the Lilliputians. Build something tiny and scale it up ginormous. That was it. That was the whole prompt.

His father Richard was a general contractor. They were flat broke. But Richard dropped everything, and that weekend Ryan watched the master at his craft — picking out a huge piece of timber at the lumber yard, sitting on the curb outside while his dad struggled through the complex math of angles and hexagons (the bestagons, you know), laying the entire thing out on the edge of a ten-foot beam.

Then came the sawdust. The thin strips gently falling to the floor, covering them both in a cloud of progress. And through the haze emerged a dad standing at least a foot taller — holding a seven-foot-long #2 pencil, complete with a #10 coffee can and green florist foam for the eraser.

To this day, Ryan believes that pencil still hangs in the lobby of Park City Middle School.

That's what a science fair project actually is. It's not the grade. It's not the rubric. It's the sawdust cloud. It's the weekend your kid watched you drop everything and build something impossible together. Richard did it for Ryan. Ryan built M.A.S.S. Trap for Ben. And Ben will do it for his kid someday.
— In memory of Richard Massfeller, General Contractor, Formula Vee racer, and the original builder.
💡 The point: You don't need to understand microcontrollers or physics formulas. You just need to show up, clear the weekend, and be the one standing in the sawdust with your kid. The M.A.S.S. Trap handles the science. You handle the being there.

🎯 The 6 Phases

The system walks your kid through 6 phases, like a detective processing a crime scene. Here's the big picture:

1

Experiment Setup

Pick what you're testing and define your variables. Like choosing which case to investigate.

2

Vehicle Intake

Select which cars to use and check their weights. Like booking suspects into the precinct.

3

Evidence Prep

Each test run gets a case number. Print tags and take photos BEFORE testing — like documenting a crime scene before you touch anything.

4

Pre-Flight Check

Review the test plan one last time. Like a pilot's checklist before takeoff — once data collection starts, you're committed.

5

Data Collection

THE RACING! The system tells your kid which car to use, when to add weight, and records everything automatically.

6

Results & Report

Export data, see the summary, and generate the science fair report. The evidence tells the story.

📚 Vocabulary Cheat Sheet

These are the science words your kid needs to know (and the judges will ask about):

Independent Variable (IV)
The ONE thing you change on purpose in the experiment.
💡 "For us, it's the weight we add to the car."
Dependent Variable (DV)
What you measure to see if the change made a difference.
💡 "For us, it's the speed (or time) the car goes down the track."
Controlled Variables (CV)
Everything you keep the SAME so the test is fair.
💡 "Same track, same height, same release method, same car model."
Trial
Running the same test multiple times to make sure the result isn't a fluke.
💡 "We run each car 3 times with the same weight to be sure."
Hypothesis
An educated guess about what will happen, written BEFORE you test.
💡 "I think heavier cars will go faster because gravity pulls them harder."
Case Number
A unique ID assigned to each test run (like MASS26-0001). Tracks the chain of evidence.
💡 "Every run is its own case file — we can trace any data point back to exactly when and how it was collected."
Momentum
Mass × Velocity. How hard something is to stop.
💡 "A heavier car at the same speed has more momentum — like how a truck is harder to stop than a bicycle."
Kinetic Energy (KE)
½ × Mass × Velocity². Energy of motion.
💡 "Speed matters WAY more than weight for energy — double the speed = 4x the energy!"

1️⃣ Phase 1: Experiment Setup

1 Pick a Template
Your kid will see three choices: Mass vs Speed (recommended for science fair), Car vs Car, or Custom. The template auto-fills the variables so they don't have to type them.
💡 Why this matters: The template ensures the experiment has properly defined variables — the #1 thing judges check.
2 Set Weight Conditions
"No added weight" (baseline) is already there. Your kid adds conditions like "+14g tungsten" or "+7g tungsten." Each condition is a different amount of weight added to the car.
💡 Why this matters: Multiple conditions let the experiment show a PATTERN, not just a single comparison. Three or more conditions is ideal.
3 Set Trials Per Condition
Default is 3 trials. This means each car runs 3 times per weight condition. More trials = more reliable data.
💡 Why this matters: If you only test once, maybe the car hit a bump. Three times proves it wasn't a fluke. Scientists call this reproducibility.
💬 Ask Your Kid
"What do you THINK will happen when we add weight? Will the car go faster, slower, or stay the same?"
This is their hypothesis. It's OK if they're wrong — science is about testing, not guessing right. Write it down BEFORE running any tests.
💬 Ask Your Kid
"What are we keeping the same every time? Why does that matter?"
They should name the controlled variables: same track, same height, same release. If you change two things at once, you can't tell which one caused the result. This is called a fair test.

2️⃣ Phase 2: Vehicle Intake

1 Select Test Cars
Check the boxes next to each car that will be part of the experiment. The car's weight should already be in the system from the garage.
💡 Why this matters: The exact weight of each car (measured to the milligram) is recorded in the data. This is real science — not "about 30 grams," but "34.833 grams."
⚠ Important: If a car's weight shows as 0g, it hasn't been weighed yet. Use a scale that reads to at least 0.1 grams (a kitchen scale works). For best results, use a milligram scale (0.001g).
💬 Ask Your Kid
"Why do we need to know the exact weight of each car?"
Because we're adding weight TO the car. The total weight = car weight + added weight. Without knowing the base weight, we can't calculate anything.

3️⃣ Phase 3: Evidence Prep

This is where the forensic theme really kicks in. Every test run gets assigned a case number (like MASS26-0001).

1 Review the Case Table
You'll see a table listing every test run with its case number, car, weight condition, and trial number. This is the test matrix — it tells the system (and your kid) exactly what to do and in what order.
2 Print Evidence Tags (optional but awesome)
If you have a label printer, print the evidence tags. Each tag has a QR code, case number, and car info. Stick them on the car or next to it for photos.
💡 Why this matters: Judges LOVE physical evidence. A photo of a car on a scale with an evidence tag next to it screams "this kid takes science seriously."
3 Snap Evidence Photos
Take a photo of each car on the scale BEFORE testing begins. The system uploads the photo and links it to the case number automatically. This creates a chain of custody — proof that the data is legit.
💡 Why this matters: In real forensics, you photograph evidence BEFORE you touch it. Same principle here — document the setup before collecting data.
💬 Ask Your Kid
"Why do we take photos BEFORE the experiment, not after?"
Because after the experiment, you can't prove what the setup looked like. Photos before = proof. It's the same reason police photograph a crime scene before they move anything.

4️⃣ Phase 4: Pre-Flight Check

1 Review the Full Test Plan
The system shows every run in order. Look it over — once you start data collection, the plan is locked in.
2 Read the How-To Steps
The screen shows step-by-step instructions for what to do during each run. Read through them together so your kid knows the drill.
💡 Why this matters: Consistent procedure is a controlled variable. If your kid pushes the car one time and releases it gently another time, the data is tainted.
✅ Pro tip: This is a great moment to do a practice run with a car that ISN'T in the experiment. Let your kid get comfortable with the release technique before real data collection begins.
💬 Ask Your Kid
"How are you going to release the car each time? Show me."
They should place the car at the same spot and let go (NOT push). Consistency matters. If they can describe their procedure, they can write it in their report.

5️⃣ Phase 5: Data Collection

This is the fun part — the actual racing! But it's STRUCTURED racing.

🟢 The System Runs the Show
The screen shows a big banner telling your kid: which car, which weight condition, which trial number. Your kid just follows the instructions. After each run, the system automatically loads the next one.
⚠ Sanity Checks: If a run looks weird (too fast, too slow, or suspicious), the system will pop up a yellow alert with two buttons: KEEP (save it anyway) or RETRY (do it again). Help your kid decide.
When to KEEP vs RETRY
KEEP if: the car ran normally and the time just seems unusual. Outliers happen in real experiments and can be analyzed later.
RETRY if: the car got stuck, your kid pushed it instead of releasing it, something blocked the sensor, or the car went backwards through the finish.
💡 Why this matters: Scientists don't throw away data just because they don't like it. But they DO redo a run if the PROCEDURE was wrong. Teach your kid the difference!
💬 Ask Your Kid (during testing)
"Do you notice any pattern? Are the heavier cars going faster or slower?"
Don't tell them the answer. Let them observe. They might say "I think the heavy ones are faster" or "they all seem the same." Both are valid observations they can write about later.
💬 Ask Your Kid (when adding weight)
"Why do you think weight might change the speed?"
Guide them toward: heavier things have more gravitational pull (more force pulling them down the ramp). But also more friction and inertia. The experiment reveals which effect wins!

6️⃣ Phase 6: Results & Report

1 Review the Summary Table
The system calculates averages for each condition. Look at whether the average speed went up, down, or stayed the same as weight increased.
2 Export the Data
Two export buttons: RAW CSV (every single run, for spreadsheets) and SUMMARY (averages, for the report). The CSV opens in Google Sheets or Excel.
💡 Why this matters: The raw data is your proof. The summary is your story. You need both for a science fair.
3 Generate the Report
The Science Fair Report button generates a complete lab report with all the right sections: Title, Abstract, Hypothesis, Variables, Materials, Procedure, Data Tables, Analysis, and Conclusion.
💬 Ask Your Kid
"Was your hypothesis right? How do you know?"
They need to point to specific numbers. Not "I think so" but "The car with 14g added went 1.23 m/s versus 1.18 m/s with no weight, so yes, heavier was faster." DATA is the answer.
💬 Ask Your Kid
"If you could do this experiment again, what would you change?"
This is the "Application" section of the report. Maybe: test more weight levels, use a longer track, try different car shapes, or measure acceleration instead of just final speed. There is no wrong answer here — this shows scientific thinking.

💬 Quick Questions for Every Phase

Don't know what to say? Pick any of these. They're designed to get your kid THINKING, not just clicking.

Before Starting
"What question are we trying to answer today?"
They should be able to state the testable question: "Does adding weight to a car change its speed?"
During Setup
"How many times should we test each condition? Why not just once?"
Multiple trials. One test could be a fluke. Three tests show if the result is consistent.
During Testing
"If we changed TWO things at once — like the weight AND the car — could we still tell what caused the difference?"
No! That's why we have controlled variables. Change one thing, measure the result. This is the foundation of the scientific method.
After a Weird Run
"That run looked different. Was it the CAR that was different, or something WE did?"
This teaches them to distinguish between experimental error (procedure problem) and natural variation (real data). If THEY did something wrong, retry. If the car just had a weird run, keep it.
After All Tests
"Look at your data. Tell me a story about what happened."
This is the conclusion. They should describe the trend: "As weight increased, speed increased" or "Weight didn't change the speed much." Have them point at specific numbers in the table.
Big Picture
"Where in the real world does this matter? When does weight + speed actually matter?"
Car crashes (heavier = more damage), roller coasters, delivery trucks vs sports cars, rockets (fuel weight vs thrust). This is the "Application" section judges love.

🔧 Troubleshooting

The screen says "Disconnected"

The phone/tablet lost WiFi connection to the M.A.S.S. Trap. Check that you're connected to the right WiFi network and refresh the page. Your data is saved — it will pick up where you left off.

A run shows 0.000 seconds

The car didn't break the finish sensor, or something was blocking it. Hit RETRY. Make sure nothing is sitting on or near the sensors.

The system says "too fast"

Something triggered both sensors almost simultaneously. Usually means the car was pushed, bounced, or something flew through the sensor. RETRY if the car wasn't released properly. KEEP if the car was just genuinely fast.

My kid accidentally closed the browser

No panic! Open the dashboard again and it will restore exactly where you left off. All data is saved after every run, both on the phone and on the ESP32 device.

The case numbers jumped (DRY26 instead of MASS26)

Dry Run mode is enabled. Case numbers starting with "DRY" are test runs that don't save real data. Look for the orange "DRY RUN" banner at the top. Turn it off for the real experiment.

Photos won't upload

The photo upload needs an internet connection (it uploads to a cloud service). The M.A.S.S. Trap itself doesn't need internet for timing and data — only photos require it. You can always add photos later.

🏆 What Science Fair Judges Want

Here's the rubric breakdown and how M.A.S.S. Trap helps hit every point:

Testable Question (10 pts)
"Does adding mass to a Hot Wheels car change its speed on a fixed-length track?"
The template auto-generates this.
Hypothesis (10 pts)
Your kid writes this BEFORE testing. "I predict that adding weight will make the car faster because gravity pulls heavier objects with more force."
Variables (10 pts)
Phase 1 defines IV (added weight), DV (speed/time), and CV (track, height, release). The export labels them clearly.
Materials List (10 pts)
M.A.S.S. Trap ESP32 system, Hot Wheels track (6.01m), test vehicles with known weights, tungsten weights, milligram scale, label printer (optional).
Procedure (10 pts)
The 6-phase workflow IS the procedure. Phase 4 has written step-by-step instructions. The Science Fair Report auto-generates this section.
Quantitative Data in Metric (10 pts)
All data is recorded in metric: time (seconds), speed (m/s), mass (grams). Multiple trials per condition. Automatically.
Analysis with Trends (10 pts)
Phase 6 summary table shows averages per condition. Your kid describes the pattern: "Speed increased as weight increased."
Conclusion (10 pts)
Was the hypothesis correct? Cite specific numbers. What would you do differently? The Science Fair Report has fill-in sections for this.
💡 Bonus points strategy: Evidence photos, printed evidence tags with QR codes, and a chain-of-custody approach will set your kid's project apart from every other poster board. It shows process, not just results.

💬 Community Feedback

Got a tip? A question? Just want to drop a ❤? Leave a comment below — powered by GitHub Discussions.