JavaScript is required for the interactive Labs experience. The full module content is below as a text reference.
Module 1 — Orientation & vocabulary
What is Launchpad Labs?
FTC Launchpad = written guides you open anytime. Launchpad Labs = this hands-on track: read slides here, answer checkpoints, play mini-games — in order is best.
How to use it: finish each module's slides, then the checkpoint, then the game. When you need a fact for a rule or score, open the Game Manual PDF; when you need setup steps, open FTC Docs (firstinspires.org → FIRST Tech Challenge → Resources).
How the robot and phone connect
Control Hub on the robot runs your program and talks to motors, servos, and sensors over the REV hub.
How it fits together: write code on a laptop → build in Android Studio or use OnBot Java → deploy (Wi‑Fi Direct or USB) to the Control Hub. The Driver Station phone or tablet only sends driver input and starts/stops OpModes — it does not run your robot program.
How tele-op and autonomous work in code
Tele-op: you create an OpMode whose class extends LinearOpMode or OpMode; in the loop you read gamepad1 / gamepad2 and set motor power. Drivers use those gamepads on the Driver Station during the match.
Autonomous: a separate OpMode runs for a fixed time with no gamepad input — only the code you wrote (sensors, timers, paths). You pick which OpMode runs from the Driver Station list before the match.
How to look things up (step by step)
Game Manual: download the season PDF from the official FIRST site → use Ctrl/Cmd+F or the table of contents to jump to field, scoring, and inspection rules.
FTC Docs: go to FTC Docs on firstinspires.org → use the left nav for Programming, Hardware, and Software — follow the install and configuration tutorials in order.
GM0 (wiki): use for mechanism ideas and build tips; for legality, always confirm in the Game Manual.
Checkpoint questions
What typically runs your robot program at the competition?
✓ Control Hub
During autonomous, what is true?
✓ Only pre-written code runs — no drivers
Mini-game pairs
- Control Hub → Runs robot code
- Tele-op → Drivers + gamepads
- Autonomous → Code only, timed
- GM0 → Community design wiki
Module 2 — Manuals, Q&A & truth
How to use each "source" in practice
Game Manual: open the PDF → bookmark the Game Definition, Robot, and Inspection sections for your season. When you argue about a rule, everyone opens the same page number — not a forum summary.
FTC Docs: start at Getting Started → install Android Studio / SDK → follow Configure Hardware step-by-step with your Control Hub connected.
GM0: search for "intake" or "drivetrain" for build patterns — then verify anything legal in the manual.
How to resolve a rule or Q&A question
Step 1: In the Game Manual, search the exact keyword (e.g. "extension", "height").
Step 2: If still unclear, open the official FIRST Q&A for the season (when published) and search; read the manual updates and team updates FIRST posts.
Step 3: For programming or wiring "how do I…", use FTC Docs tutorials, not random videos — copy the exact error message into Docs search if you get a build error.
How to read the manual fast
Open the PDF's table of contents (sidebar in most readers). Click the part that matches your question: field setup, scoring, penalties, robot rules.
Tip: keep a team bookmark list (shared doc or sheet) with page numbers your strategy depends on — update when the manual updates. Skim the "overview" figures first, then drill into the subclauses your robot touches.
Checkpoint questions
Where should you look first for whether a scoring interaction is legal this season?
✓ Game Manual
FTC Docs are mainly for…
✓ Programming, hardware, and tools
Mini-game: correct order when unsure about a rule
- Read the relevant Game Manual section
- Check FTC Docs for how-to if it's a software/hardware question
- Search official Q&A / updates if still unclear
- Ask a mentor with screenshots — not random forums first
Module 3 — Design & iteration
How to iterate a mechanism (build → test → CAD)
Start with a quick prototype: cardboard, wood, or spare channel to prove the idea moves the game piece. Measure what works.
Then CAD the version you will build: focus on function over appearance — model the plate, holes, and bolt pattern you need this week. Export or print drawings so the build team matches your numbers.
Test on the field (practice field or taped outline) and change — that loop is the design process.
How to CAD a basic FTC part (workflow)
In Onshape or Fusion: (1) Create a sketch on a plane. (2) Draw the outline with dimensions (use real game piece or COTS part sizes). (3) Extrude to create solid. (4) Add holes — match the REV hole pattern or your bolt size.
(5) Build an assembly: insert parts, use mates/constraints so plates line up. (6) Check interference before you cut metal.
How to split work without breaking the robot
Assign subsystems (drivetrain, intake, lift, sensors). For each, write down: mounting interface, max envelope, and motor/servo names that will match the Control Hub configuration.
How to hand off: short README or slide with a screenshot of the CAD assembly + list of hardware. When programming starts, those names become your DcMotor / Servo IDs in code.
Checkpoint questions
A good early-season habit is…
✓ Build a testable prototype, then refine
CAD is most useful for…
✓ Fit, planning, and team communication
Mini-game pairs
- Prototype → Quick learn test
- CAD → Plan before metal
- Iterate → Improve in loops
- Subsystem → Focused team slice
Module 4 — Programming path
How to create and run an OpMode
OpMode = one program the Driver Station can list and run (e.g. TeleOp_Main, Auto_Park).
Steps: (1) Install Android Studio and the FTC SDK (follow FTC Docs). (2) File → New → Sample OpMode or duplicate the team package. (3) Extend LinearOpMode or OpMode. (4) Use @TeleOp or @Autonomous on the class. (5) Build → connect robot → Run on the Control Hub.
How to write tele-op motor control (Java idea)
In your loop or runOpMode(), while opModeIsActive(): read sticks with gamepad1.left_stick_y (values −1…1), map to motor power, call motor.setPower(...).
Blocks: drag the same ideas — loop, gamepad blocks, motor blocks — good for learning logic without syntax. Move to Java when autos need more structure or version control.
How to configure hardware before coding
On the Driver Station phone: Configure Robot (or use the Control Hub's web/config flow per FTC Docs). Add each motor, servo, and sensor with a unique name like left_drive / intake.
In code: hardwareMap.get(DcMotor.class, "left_drive") must match the name exactly — same spelling, same case. Wrong name = null or wrong motor.
Checkpoint questions
An OpMode is best described as…
✓ A program the robot can run (e.g. tele-op or auto)
Why name devices clearly in configuration?
✓ So code references match real hardware
Mini-game pairs
- OpMode → Runnable program
- Tele-op → Driver control period
- SDK → Libraries for your code
- Config file → Named hardware map
Module 5 — Team & competition
How to prepare for judging (concrete prep)
Judges ask how you designed and tested, not only scores. Prepare a short outline: team story, robot subsystems, one big problem you solved, what you'd do next.
How to practice: time a 2-minute talk with a mentor. Draw your robot on a whiteboard from memory. Assign one student per topic so nobody is silent.
How to keep a useful engineering notebook / portfolio
Each entry: date, what you changed (or tested), why, and an outcome (photo, sketch, or a note on what you observed and what to try next).
How to start: one page per meeting — even a phone photo of a whiteboard counts. Link CAD screenshots to the part you machined. Judges can follow your story if dates and decisions are visible.
How to run a safe pit and field routine
Pit checklist: charged batteries labeled, tools in a tray, extension cords off the aisle, eye protection when cutting. Before a match: confirm which OpMode is selected, gamepads paired, and start position matches auto.
On the field: follow queue volunteers; never grab another team's robot without asking. Thank volunteers and alliance partners — that's part of the event flow.
Checkpoint questions
Gracious professionalism includes…
✓ Helping others and respecting opponents
Why keep a notebook or portfolio?
✓ To show design process and learning over time
Mini-game: sensible order for a respectful team at an event
- Check in / know your match schedule
- Keep the pit safe and tidy
- Test changes on a practice field if available
- Thank volunteers and alliance partners
