Road Runner Localization

Validate x, y, and heading before trusting paths.

Module 12: Road Runner 1.0 Setup and TuningRoad Runner

In this lesson, you will:

01Read pose.
02Push-test axes.
03Diagnose sign errors.

Concept narrative

Localization is the robot’s estimate of where it is. Trajectories depend on this estimate; if pose is wrong, path following will look wrong even with perfect path code.

Robot mental model

Pose has x, y, and heading. Students should physically move the robot and predict which value should change.

Implementation walkthrough

Print pose, push forward, strafe, and rotate. Confirm signs and units. Then test under low power before running long paths.

PoseTelemetry.javaJava

drive.updatePoseEstimate();
Pose2d pose = drive.pose;
telemetry.addData("x", pose.position.x);
telemetry.addData("y", pose.position.y);
telemetry.addData("heading deg", Math.toDegrees(pose.heading.toDouble()));

Common mistakes and debugging

Swapped encoders, reversed signs, wrong track width, or drifting heading all show up as pose errors. Solve those before tuning complex auto.

Checkpoint

Pose changes match physical movement.
Units are understood.
Signs are correct.
The test record includes the setup, prediction, and observed result.
A teammate can repeat the check from the saved evidence without guessing.

Reflection check

Check your understanding before moving on.

Which result best demonstrates completion of “Road Runner Localization”?

Why record the test setup, prediction, and observed result?

0 of 2 answered

References

Road Runner 1.0 ActionsAction composition, custom actions, and autonomous structure.Road Runner 1.0 TuningDrive class setup, tuning op modes, feedforward, feedback, and validation.Road Runner 1.0 Builder ReferenceTrajectory/action builder method reference.