Write the code for a lesson, run it, and see what the robot does. You get telemetry, checks against what the lesson asked for, and simulated hardware to test against.
1
Write Java
Complete the lesson code in the browser editor.
2
Run the OpMode
Press Init and Start, then use the gamepad or scene controls.
3
Read the robot
Compare telemetry, visual motion, requirements, and hints.
4
Fix and retry
Change the code and reinitialize until the behavior matches the goal.
Fix a drivetrain with the wrong motor direction.Stop a slide at an encoder target.Diagnose unsafe or unreliable sensor data.
The browser can test code and simulated behavior. A physical robot is recommended to verify wiring, motor direction, friction, and tuning.
Checking simulator access…
Design tools
Check the design before you cut
16 calculators for the numbers that decide whether a mechanism will work, and a check that reads your exported CAD file and measures it.
Write the lesson's Java, run the FTC lifecycle against simulated hardware, and read the telemetry back. On 47 software lessons.
Design calculators
Twelve of them, covering gear ratios, arm torque, drivetrain limits, slide rigging, wire gauge, and beam deflection. Each one draws the result, not just the number.
Progress that follows you
Sign in and completed lessons are recorded across both tracks and every device. No streaks, no badges.
Open source
Read it, adapt it for your team, or send a fix. Built by FTC team 30450.
Start here
Start with the fundamentals. Build toward competition.
Write the code in the browser, design the robot with the calculators, and bring both to the field.