Lesson 4.2: Turning Joystick X and Y into Smooth Drive Control

Technical Context

The gamepad joysticks provide a range of motion used for proportional speed control. However, by default, the Y-axis on the gamepad is negative when pushed up and positive when pushed down. If a programmer fails to negate this value in the Java code, the robot will drive backward when the driver intends to move forward, leading to high-speed collisions and potential drivetrain failure.

How Joystick Values Become Drive Commands

Joysticks are members of the gamepad object and are stored as double precision variables with a range of -1.0 to 1.0. The center position of the joystick is exactly 0.0. In a Differential Drive (or Tank Drive) configuration, the Y-axis input is typically used to command the voltage of the DC Motors. To correct the hardware's inverted logical bias, the programmer must perform a simple math operation: double forwardPower = -gamepad1.left_stick_y;.

Annotated Code

@TeleOp(name="Joystick_Scaling", group="Unit4")
public class JoystickScaling extends OpMode {

    @Override
    public void init() {
        telemetry.addData("Status", "Drive Initialized");
    }

    @Override
    public void loop() {
        // Correcting the negative 'up' bias of the Y-axis
        double drivePower = -gamepad1.left_stick_y;

        // Streaming the raw and scaled data back to the Driver Station
        telemetry.addData("Raw Stick Y",       gamepad1.left_stick_y);
        telemetry.addData("Scaled Drive Power", drivePower);
    }
}

Scaling in a Competition Drive Loop

Titan Robotics Club passes its driver inputs through separate translation and turn scales before selecting the appropriate drive method:

double[] inputs = driverGamepad.getDriveInputs(
    Dashboard.Subsystem_Drivebase.driveMode,
    true,
    drivePowerScale,
    turnPowerScale
);

if (robot.robotBase.driveBase.supportsHolonomicDrive()) {
    robot.robotBase.driveBase.holonomicDrive(
        null, inputs[0], inputs[1], inputs[2],
        robot.robotBase.driveBase.getDriveGyroAngle()
    );
} else {
    robot.robotBase.driveBase.arcadeDrive(inputs[1], inputs[2]);
}

Their framework centralizes scaling inside getDriveInputs(...); the simpler multiplication in this lesson is the same idea without that abstraction. Excerpted from Team 3543 Titan Robotics Club's FtcTeleOp.java at a pinned commit under the MIT License.

Fill-in-the-Blank Practice

A gamepad joystick returns values as a/an __________ datatype.
When a joystick is pushed fully toward the top of the controller, its Y-value is __________.
The X-axis of a joystick is __________ when pushed to the left and positive to the right.

Show answers

double
-1.0 (negative: this is the hardware bias that must be corrected)
negative

Simulator Challenge

Robot Scenario: Your robot's drivetrain is too fast for a rookie driver. Create a program that scales the joystick's Y-axis input to 50% of its maximum value and negates it so the robot moves forward when the stick is pushed up.

Telemark Unit 4 Simulator

Supports buttons, joysticks, triggers, bumpers, and D-pad input.

Shows live input values, basic telemetry, deadzones, and curve visualization when relevant.

Lesson 4.5 also compiles mapped motors and shows the power produced by the arcade-drive mix.

Show answer

@Override
public void loop() {
    double safePower = -gamepad1.left_stick_y / 2.0;
    telemetry.addData("Safe Power", safePower);
}

Ready to move on?

Only mark complete if you genuinely understand the material. Your progress will be saved in this browser.

Stuck on this lesson?

Ask about anything on this page. It can see which lesson you have open and which part you are reading.

Technical Context​

How Joystick Values Become Drive Commands​

Annotated Code​

Scaling in a Competition Drive Loop​

Fill-in-the-Blank Practice​

Simulator Challenge​