01 / Java for FTC

Methods, Classes, and Robot Helpers

Extract repeated robot behavior into readable methods and classes.

55 minFoundationsJava for FTC

You will

01Move repeated drivetrain code into a method.
02Explain why a hardware helper class reduces OpMode clutter.
03Use parameters and return values in FTC examples.

Why Methods, Classes, and Robot Helpers matters

This lesson is part of the Java foundation, so the emphasis should be on how a small language feature becomes a robot habit. Students should leave understanding the syntax, but more importantly they should understand what the robot will do differently because that syntax exists. Keep the focus on readable values, predictable flow, and code that another teammate can safely modify later.

Starting point

Methods are named robot actions

When the same motor formula appears in three places, students lose the ability to fix it once. A method gives that idea one name and one implementation, which makes code easier to test and teach.

Classes hold related state and behavior

A robot hardware class groups the motors, servos, sensors, and lifecycle helpers that every OpMode needs. Later, subsystems use the same idea at a smaller mechanism level.

Build path

Have students make one small edit, run it, observe telemetry, and explain the result before moving on. This is slower than pasting a large example, but it builds the debugging discipline they will need once hardware is involved.

For this specific lesson, students should first restate the goal in robot terms, then identify the value or behavior they expect to observe, then run the smallest test that proves the idea. The lesson should feel like a guided lab: predict, run, observe, explain, and only then extend.

DriveHelpers.java · Java

private void setTankPower(double left, double right) {
    left = Math.max(-1.0, Math.min(1.0, left));
    right = Math.max(-1.0, Math.min(1.0, right));

    frontLeft.setPower(left);
    backLeft.setPower(left);
    frontRight.setPower(right);
    backRight.setPower(right);
}

private double deadband(double value) {
    return Math.abs(value) < 0.05 ? 0.0 : value;
}

Debugging and failure modes

Most failures at this level come from hidden assumptions: a value has the wrong sign, a method runs at the wrong time, a variable is scoped where later code cannot see it, or a class is named differently than its file. The lesson should train students to check the smallest claim first instead of rewriting the whole OpMode.

Checks

The main loop reads like a short sequence of decisions.
All drivetrain motor powers pass through one method.
Deadband removes tiny joystick drift near zero.

Check your understanding

Module check

What is the main benefit of extracting drivetrain writes into a method?

0 of 1 answered

References

FIRST FTC DocsOfficial FTC SDK and robot programming documentation.Game Manual 0Community FTC programming, control, and robot design reference.Learn Java for FTCFTC-focused Java fundamentals by Alan G. Smith.