Lesson 8.2: Configure Mecanum Motor Direction and Wheel Mixing

---

Technical Context

Most FTC teams use a four-motor mecanum drivetrain because it can drive forward, strafe sideways, and rotate without changing wheel modules. Mecanum is not a differential or tank drive: each wheel needs its own power calculated from forward, strafe, and rotate commands.

The motors are still mounted in mirror-image orientations. Before applying mecanum math, use setDirection(REVERSE) in init() on the side that is physically opposed. The team CAD and simulator configuration in this lesson use reversed left-side motors. After that correction, positive power has one consistent physical meaning on all four wheels.

---

When setDirection() Fixes the Real Problem

The setDirection() method flips the logical orientation of a DcMotor object. By passing DcMotorSimple.Direction.REVERSE, all subsequent positive power commands and encoder tick counts are inverted by the SDK before the signal reaches the Control Hub port.

This is technically superior to negating joystick values manually in loop() because:

• It applies universally. Every setPower() call everywhere in the codebase behaves correctly without needing manual adjustment.
• It also inverts the encoder direction, so getCurrentPosition() increments in the expected direction.
• It documents intent. A teammate reading the code immediately understands the motor is physically reversed.

The default direction for all motors is DcMotorSimple.Direction.FORWARD.

Once motor direction is consistent, standard robot-centric mecanum mixing is:

leftFront  = forward + strafe + rotate
rightFront = forward - strafe - rotate
leftBack   = forward - strafe + rotate
rightBack  = forward + strafe - rotate

Dividing all four values by the largest magnitude, or by 1.0 when none exceeds it, preserves their ratio while keeping every command inside the legal motor range.

---

Annotated Code

package org.firstinspires.ftc.teamcode;

import com.qualcomm.robotcore.eventloop.opmode.OpMode;
import com.qualcomm.robotcore.eventloop.opmode.TeleOp;
import com.qualcomm.robotcore.hardware.DcMotor;
import com.qualcomm.robotcore.hardware.DcMotorSimple;

@TeleOp(name="Direction_Demo")
public class DirectionDemo extends OpMode {

    private DcMotor leftFront, rightFront, leftBack, rightBack;

    @Override
    public void init() {
        leftFront  = hardwareMap.get(DcMotor.class, "leftFront");
        rightFront = hardwareMap.get(DcMotor.class, "rightFront");
        leftBack   = hardwareMap.get(DcMotor.class, "leftBack");
        rightBack  = hardwareMap.get(DcMotor.class, "rightBack");

        // Match the physical mounting used by this robot and its CAD model.
        leftFront.setDirection(DcMotorSimple.Direction.REVERSE);
        leftBack.setDirection(DcMotorSimple.Direction.REVERSE);

        telemetry.addData("Status", "Mecanum drivetrain ready");
    }

    @Override
    public void loop() {
        double forward = -gamepad1.left_stick_y;
        double strafe = gamepad1.left_stick_x;
        double rotate = gamepad1.right_stick_x;

        double fl = forward + strafe + rotate;
        double fr = forward - strafe - rotate;
        double bl = forward - strafe + rotate;
        double br = forward + strafe - rotate;

        double denominator = Math.max(
            1.0,
            Math.max(Math.abs(fl), Math.max(Math.abs(fr),
                Math.max(Math.abs(bl), Math.abs(br))))
        );

        leftFront.setPower(fl / denominator);
        rightFront.setPower(fr / denominator);
        leftBack.setPower(bl / denominator);
        rightBack.setPower(br / denominator);

        telemetry.addData("Forward / Strafe / Rotate", "%.2f / %.2f / %.2f",
            forward, strafe, rotate);
        telemetry.update();
    }
}

---

Fill-in-the-Blank Practice

1. Mecanum mixing calculates four separate wheel powers from forward, __________, and rotate commands.
2. The setDirection() method is typically called during the __________ phase of the OpMode lifecycle.
3. Dividing all four powers by their largest magnitude preserves their __________ while keeping every value within range.

Show answers

1. strafe
2. init()
3. ratio (relative magnitude)

---

Simulator Challenge

Use the simulator below to practice fixing left-side motor direction on a mecanum drivetrain with lesson-specific starter code.

1.Complete the codeWork in fullscreen when you need more room for the editor and visualizer. Where file tabs are available, hover over the tab strip and choose + to create a file or reuse saved code.

2.Run the lifecyclePress Init, then Start. Use the available gamepad or scene controls.

3.Debug the behaviorCheck telemetry, motion, requirements, and hints before opening the answer.

Telemark Unit 8.2 Simulator

Loads the lesson-specific Telemark motor challenge with starter code instead of a completed solution.

Includes live hardware feedback, telemetry checks, and gamepad input for each motor-control concept.

Best for practicing power, direction, braking, stopping behavior, and limit-switch safety in context.

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.