Build a Full Road Runner Autonomous

Complete vision-selected Road Runner autonomous.

Road Runner 1.0 Actions and AutonomousCapstone

In this lesson, you will:

Combine vision, drive, and mechanisms.
Add fallback behavior.
Document validation.

Concept narrative

The full autonomous capstone proves the curriculum has connected: hardware setup, vision, localization, actions, tuning, mechanisms, and debugging all meet in one routine.

Robot mental model

The robot is now a coordinated system. Each layer should be testable alone and visible in telemetry when combined.

Implementation walkthrough

Test vision selector, each path, each mechanism action, then full sequence. Add a pre-match checklist for start pose, camera result, and selected branch.

FullAuto.javaJava

try {
    Actions.runBlocking(new SequentialAction(
        closeClaw(),
        selectedBranchPath,
        new ParallelAction(scorePath, armToScore()),
        releaseAndPark()
    ));
} finally {
    robot.safeState();
}

Common mistakes and debugging

Full auto failures must be isolated by layer. Print vision result, selected action, pose, mechanism state, and stop reason.

Practice

Build and document a full autonomous routine with three branches and a fallback.

Checkpoint

The SDK, Road Runner artifact versions, drive class, localizer, configuration, and start pose are recorded.
Vision selection is proven with LEFT, CENTER, RIGHT, and UNKNOWN inputs before motion is connected.
Each path and mechanism action passes alone, including timeout and zero-output cleanup.
Every branch completes three cold-init runs within the team's declared endpoint tolerance.
UNKNOWN selects the conservative fallback without unintended motion.
Saved logs identify selection, pose, mechanism state, stop reason, and any failed acceptance limit.

Reflection check

Check your understanding before moving on.

What validation order best limits risk in a full Road Runner autonomous handoff?

Run the full routine first to save time.

Tune the arm only after a match failure.

Validate vision selection, each path, and each mechanism action before the full sequence.

Which handoff record makes a full autonomous reproducible for the next driver-station test?

Start pose, selected branch rule, validated commit, test conditions, and observed result.

Only the final field score.

A screenshot of the code editor without robot configuration.

0 of 2 answered

References

Road Runner autonomous organization guideCommunity-contributed Road Runner 1.0 example used for action and branch organization, not season-specific field geometry.Road Runner 1.0 ActionsAction composition, custom actions, and autonomous structure.FTC VisionPortal DocsOfficial FTC camera and processor lifecycle documentation.

Build a Full Road Runner Autonomous

Complete vision-selected Road Runner autonomous.

Road Runner 1.0 Actions and AutonomousCapstone

In this lesson, you will:

Combine vision, drive, and mechanisms.
Add fallback behavior.
Document validation.

Concept narrative

The full autonomous capstone proves the curriculum has connected: hardware setup, vision, localization, actions, tuning, mechanisms, and debugging all meet in one routine.

Robot mental model

The robot is now a coordinated system. Each layer should be testable alone and visible in telemetry when combined.

Implementation walkthrough

Test vision selector, each path, each mechanism action, then full sequence. Add a pre-match checklist for start pose, camera result, and selected branch.

FullAuto.javaJava

try {
    Actions.runBlocking(new SequentialAction(
        closeClaw(),
        selectedBranchPath,
        new ParallelAction(scorePath, armToScore()),
        releaseAndPark()
    ));
} finally {
    robot.safeState();
}

Common mistakes and debugging

Full auto failures must be isolated by layer. Print vision result, selected action, pose, mechanism state, and stop reason.

Practice

Build and document a full autonomous routine with three branches and a fallback.

Checkpoint

The SDK, Road Runner artifact versions, drive class, localizer, configuration, and start pose are recorded.
Vision selection is proven with LEFT, CENTER, RIGHT, and UNKNOWN inputs before motion is connected.
Each path and mechanism action passes alone, including timeout and zero-output cleanup.
Every branch completes three cold-init runs within the team's declared endpoint tolerance.
UNKNOWN selects the conservative fallback without unintended motion.
Saved logs identify selection, pose, mechanism state, stop reason, and any failed acceptance limit.

Reflection check

Check your understanding before moving on.

What validation order best limits risk in a full Road Runner autonomous handoff?

Run the full routine first to save time.

Tune the arm only after a match failure.

Validate vision selection, each path, and each mechanism action before the full sequence.

Which handoff record makes a full autonomous reproducible for the next driver-station test?

Start pose, selected branch rule, validated commit, test conditions, and observed result.

Only the final field score.

A screenshot of the code editor without robot configuration.

0 of 2 answered