WestlakeLEARN
FTC / Java

First Tech Challenge

FTC / Java

01 · Java for FTC
  • OpMode Anatomy and Hello Robot
  • Variables, Math, and Decisions
  • Methods, Classes, and Robot Helpers
02 · FTC Hardware Essentials
  • Hardware Map and RobotHardware
  • Motors, Servos, and Sensors
  • IMU, Encoders, and Bulk Caching
03 · TeleOp and Mecanum
  • Robot-Centric Mecanum Drive
  • Field-Centric Driving
  • Driver Ergonomics and Safe TeleOp
04 · Subsystems and Commands
  • Subsystem Lifecycle
  • Enums and Finite State Machines
  • Command-Based OpModes
05 · From Timed Steps to Actions
  • Timed and Encoder Autonomous
  • Autonomous State Machines
  • Actions and Sequencing
06 · PID and Feedforward
  • PID Basics
  • Feedforward and PIDF
  • Dashboard Tuning Workflow
07 · Motion Profiling
  • Motion Profile Concepts
  • Implementing a Profiled Mechanism
  • Testing Profiles and Failure Modes
08 · OpenCV and AprilTags
  • VisionPortal Camera Setup
  • OpenCV Color and Region Processors
  • AprilTags and Field Pose
09 · Setup and Tuning2/3
  • Road Runner 1.0 Install and Drive Class
  • Feedforward Tuning
  • Localization and Validation
10 · Trajectories, Actions, and MeepMeep
  • Action Builder and Trajectories
  • MeepMeep Preview
  • Full Road Runner Autonomous
11 · Git, Debugging, and Competition Readiness
  • Git Workflow for FTC Teams
  • Telemetry-First Debugging
  • Competition Readiness Checklist
12 · Driver Control
  • Driver Control
13 · Autonomous Build
  • Simple Autonomous
14 · Debugging
  • Debugging with Telemetry

09 / Setup and Tuning

Feedforward Tuning

Tune kS, kV, and kA and understand how each affects path following.

90 minRoad RunnerSetup and Tuning

You will

  1. 01Explain static, velocity, and acceleration feedforward.
  2. 02Run tuning routines after major robot changes.
  3. 03Record tuned constants and test conditions.

Why Feedforward Tuning matters

This lesson is about planned robot motion using Road Runner 1.0. Students should understand that trajectories depend on tuning, localization, starting pose, and action composition. Road Runner is powerful, but it only works as well as the robot model underneath it.

Starting point

Tuning is robot-specific

As the slide deck notes, Road Runner tuning should be repeated after substantial robot changes. Weight, wheels, gearing, battery, and friction all influence the constants.

Constants map to behavior

kS starts motion, kV maintains velocity, and kA handles acceleration. Students should watch for symptoms: failing to start, wrong steady velocity, or lag during speed changes.

Build path

Use small validation steps: create the drive, set the start pose, run a short action, validate localization, then add more complex paths. Mechanisms and vision should be composed as actions only after the drive path works alone.

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.

TuningNotebook.md · Markdown

## Road Runner Tuning Log

- Robot configuration:
- Battery voltage:
- Wheel type:
- kS:
- kV:
- kA:
- Track width:

Observations:
- Starts smoothly:
- Holds velocity:
- Accelerates without lag:
- Re-test needed after mechanical changes:

Debugging and failure modes

Road Runner failures should be separated into layers. If pose is wrong, fix localization. If straight motion is wrong, revisit tuning. If the path is risky, simplify or preview it. If the full auto fails, inspect the selected branch, active action, pose, mechanism state, and finish condition.

Practice

Run the feedforward tuning workflow from Road Runner 1.0 docs and complete a tuning log entry for the robot.

Checks

  • Tuning is done on the current robot configuration.
  • Constants are recorded with context.
  • A straight-line validation test follows tuning.

Check your understanding

Module check

When should Road Runner tuning be revisited?

0 of 1 answered

References

Road Runner 1.0 DocsRoad Runner 1.0 installation, tuning, actions, and trajectory reference.FTC DashboardTelemetry, config variables, and tuning support.

Finished reading?

Mark this lesson complete.

You'll move on to “Localization and Validation” next.

Road Runner 1.0 Install and Drive ClassLocalization and Validation