🏎 Driver Playbook

You are the Driver

Your job is not to move the robot — it is to score points under pressure, adapt in real time, and execute the plan your team built together.

Driver Control Period
1:45
Ready — press Start to begin
:45 :30 :15 End
📈 Today's Session
Today's Driver Workflow
  1. 01Warm-up · 2 min
  2. 02Run 3 drills
  3. 03Run 2 matches
  4. 04Review mistakes
  5. 05Log session
⚡ Match Day Match Mode
Pre-match checklist
  • Fresh battery installed (≥ 80%)
  • Auton selector confirmed out loud
  • Robot starting position verified on tile
  • Mechanisms tested: intake, scoring, endgame
Communication reminders
  • Caller watches timer and score, not the robot
  • Call opponent position before every cycle
  • Short commands only — no full sentences
  • Confirm endgame at 0:20 remaining
Opening move reminder
  • Know exactly where auton ends
  • First driver action is rehearsed, not improvised
  • If auton fails, switch to backup plan immediately
If something goes wrong
  • Stay calm — panic costs more time than any mistake
  • Keep scoring — the match isn't over until time is
  • Listen to the caller — they see the whole field, you don't
// Section 01
The Role 🏎
Who you are on this team, how the drive team works, and the mindset it takes to win.

The driver is the interface between the robot and the game. Your job is not just to move the robot — it is to score points under pressure, adapt in real time, and execute a plan that your engineer built and your strategist designed. All three roles have to work for you to win.

You Own
  • ✓ Controller config & tuning
  • ✓ Auton calibration pre-match
  • ✓ All practice hours
  • ✓ Match execution
  • ✓ Endgame timing
  • ✓ Recovery when plans break
You Train
  • ● Smooth, consistent cycles
  • ● Precise positioning
  • ● Field awareness
  • ● Endgame execution
  • ● Alliance communication
  • ● Pressure composure
You Decide
  • ▶ Abort cycle or push through?
  • ▶ Score or play defense?
  • ▶ Endgame now or one more cycle?
  • ▶ Stay in zone or switch?
  • ▶ Call for help or handle it?
💡
The rule top drivers follow: Think one move ahead, not one move behind. While you are scoring the current piece, your eyes should already be reading where the next piece is and what the opponent is doing.

RECF Drive Team Certification

The REC Foundation publishes an official Drive Team Training Course every season. It covers the game rules every drive team member must know — including what referees watch for, how to handle disputes, and alliance station conduct rules.

🎓 Required — RECF Official

Every drive team member should complete this before their first competition. It takes about 90 minutes. Covers game rules, safety, alliance station conduct, and how to advocate for your team with referees.

🔗 RECF Drive Team Training Course →

Alliance Station Rules

These are not suggestions — they are game manual rules. Violations result in warnings or disqualification.

⚠️
All drive team members must stay in the alliance station for the entire match. No stepping onto the field.
⚠️
No communication devices during the match. Phones must be in airplane mode or left in the pit.
⚠️
Controller cable must stay plugged in. Do not unplug until the all-clear is given.
Max 3 drive team members per alliance station. Roles: main driver, operator (partner controller), and a spotter/caller.
DRIVE TEAM

VRC allows three drive team members per alliance station. Most teams use only one or two — that is a mistake. Each person should have a defined job before the match starts. Ambiguity in the alliance station creates hesitation, and hesitation loses matches.

1
Main Driver

Controls driving and scoring. Eyes on the game piece and field position. Does not watch the timer — that is the caller's job. Does not think about the score — that is also the caller's job. Full attention on executing cycles.

Focus: execution · Controls: drive + primary mechanisms
2
Operator (Partner Controller)

Controls secondary mechanisms — intake toggle, endgame deployment, PTO shift. Frees the main driver to focus purely on movement and positioning. Only used when your robot has enough complexity to justify splitting. Not every robot needs this.

Focus: mechanism control · Controls: secondary functions
3
Caller / Spotter

Watches the whole field. Calls the timer at :45, :30, and :15. Tracks the score. Communicates with the alliance partner. Spots opponent positioning and calls defensive moves. The driver should never have to check the timer — the caller tells them.

Focus: awareness · Controls: nothing — just talks

Communication Protocol

Decide your communication protocol before queue. During the match there is no time to figure it out.

Caller calls
  • "45 seconds"
  • "30 — endgame ready"
  • "Opponent on your right"
  • "Abort — go to endgame"
  • "One more cycle"
Driver never
  • Checks the timer mid-drive
  • Asks "how much time?"
  • Looks at the scoreboard
  • Argues a call during the match
  • Reacts to opponent trash talk
💡
Practice your communication out loud. It sounds obvious but most teams never do it. Run full 1:45 practice matches where the caller narrates everything they see. The first few sessions will feel clunky. By competition it will be automatic.
// Section 02
Training 💪
How to structure practice, what to drill, and how to track your progress over time.
How to Structure a Practice Session
A 45-minute practice session with clear phases returns more improvement than two hours of unstructured driving.
🎮 Pre-Practice Checklist
Battery charged and installed
Don't start a session with a low battery — results will be inconsistent
Control map confirmed — no recent changes
Practice with the competition layout, always
Field elements or targets set up for the drill
Match the actual competition field as closely as possible
Session goal defined before driving starts
Cycle time? Accuracy? Match sim? Pick one focus.
Session log open and ready
Record attempt count, times, and observations every session
Timer available for cycle time tracking
Phone stopwatch works — be consistent in when you start/stop
0:00
Warm-Up — Four Corners or Tile Stop
5 min
Start with a foundation drill every session. This establishes spatial awareness, gives the driver a feel for the field and controller, and provides a consistent baseline measurement. Do not skip this even if the driver feels ready — it takes 5 minutes and the data is valuable over time.
5:00
Targeted Drill — One Specific Weakness
15 min
Pick one drill that addresses the team's current biggest weakness. Run it repeatedly, measure it, and debrief afterward. What improved? What did not? Why? Focused improvement on one thing beats scattered practice on everything. Example: if last event's match simulations showed the end-game was failing, spend the targeted drill block exclusively on end-game execution.
20:00
Match Simulation — Full 105 Seconds
20 min
Run 2–3 full match simulations using the Match Timer at the top of the page (click the 1:45 Match preset in section 6 to load it). Log the score of each. The coach tracks score while the timer handles the :45, :30, and :15 alerts. After each simulation, spend 2 minutes discussing what happened — not what to do differently in theory, but what specifically caused cycles to fail or succeed. Keep it factual and brief.
40:00
Debrief — 5 Minutes Maximum
5 min
Answer three questions: (1) What was today's target metric? (2) Did we hit it? (3) What is the target for next session? Log this in the practice log. If you do not track metrics, you cannot tell if practice is working. Over-long debriefs eat into the next session — keep them tight.

Roles During Practice

⚠️
The week before competition: no new drills, no new routes, no risky changes. Consistency-only practice — repeat what you already know until execution is automatic. Trying new things the week before an event is how teams arrive at a competition and discover they have forgotten their reliable strategies.
📝 Post-Session Debrief — 5 Minutes
Write today's session result in the practice log
Time, cycle count, or drill scores — whatever you tracked
Identify one specific thing the driver improved
Be precise: "turn accuracy at south goal" not "driving got better"
Identify one thing to fix before next session
One actionable target is better than a vague list
Check robot for damage or wear from practice
Look for loose screws, worn cables, or mechanism issues before they become match failures
Confirm controller charged and returned to storage
Don't leave practice with a partially charged controller
PRACTICE LOG
// Practice Log
Practice Session Log
Log every session. Progress saves automatically. Without data, you cannot tell whether practice is working or which drills are producing results.
Session Log
Date Drills Run Sim Score 1 Sim Score 2 Target Metric Hit Target? Next Focus Feel
Best Sim Score:
📝
Notebook entry tip: your practice log is direct evidence of systematic driver improvement — exactly what judges want to see in the engineering notebook. Export or photograph this log for your notebook documentation at least once before each competition. Include graphs of your sim score over time if possible.
The driver practice curriculum applies deliberate practice principles from sports science. Research by Anders Ericsson shows that improvement requires practicing just beyond your current ability level — not repetition of what you can already do. In VRC, this means structured drills with measurable targets (cycle time, accuracy percentage) rather than casual driving. Spaced repetition — practicing consistently across weeks — produces better motor learning than cramming. The session log in this guide exists because tracking progress is the only way to know if deliberate practice is working.
🎤 Interview line: “Our driver practice curriculum applies deliberate practice principles from motor learning research. We set specific, measurable targets for each session and track performance across time. Consistent data collection lets us know if our practice is producing improvement — or if we need to change our approach.”
Your driver has practiced for 10 hours total but all in two long weekend sessions. A teammate practiced 2 hours per week for 5 weeks. Who is likely more consistent at competition?
The driver with 10 hours — more total practice time always wins
They are equal — total hours is the only metric that matters
The driver with spaced weekly practice — spaced repetition produces better long-term motor learning than massed practice
Cannot determine without measuring their cycle times
🏎 Driver Control Tuning →🏎 Curvature Drive →🎮 Partner Controller →🔍 Robot Pre-Check →
▶ Next Step

Practice structured. Now make sure your controller mapping is locked and competition-ready.

🎮 V5 Controller Guide →
DRILL LIBRARY
Drill Library ⏱
Focused drills that target specific driver weaknesses. Each has a target metric — click Load Timer on any drill to send it to the Match Timer at the top of the page, then log results below.

Foundation Drills

🕐 5 min Beginner Spatial Awareness
Four Corners
Drive the robot to each corner of the field and stop with the robot fully inside the corner tile. No scoring — pure navigation. Rotate 180 degrees at each corner before leaving. This builds spatial awareness and motor memory for the field dimensions.
Use this whenyou misjudge field position or lose track of robot rotation.
Metric: time to complete one full circuit of all four corners. Target: under 15 seconds by week 3.
🕐 8 min Beginner Precision Stopping
Tile Stop
Place a cone or marker on a random field tile. Drive to it and stop with the robot's center over the marker. Repeat from different starting positions. This teaches the driver to judge stopping distance — critical for game element pickup where being 4 inches off means a missed cycle.
Use this whenyou overshoot pickups or stop too short.
Metric: distance from center of robot to marker after stop. Target: within 3 inches from any starting position.

Mechanism Drills

🕐 10 min Intermediate Cycle Time
Single Cycle Timer
Set up one game element and one scoring location. Time the driver from "element neutral" (not holding anything, positioned at start) to "element scored." Reset and repeat 10 times. This isolates the exact time cost of one scoring cycle and makes improvement measurable.
Use this whencycles feel slow but you can't point to what's costing time.
Metric: average cycle time and standard deviation across 10 attempts. Target: reduce average by 15% over two weeks. Low standard deviation = consistent.
🕐 8 min Intermediate Mechanism Speed
Mechanism Isolation
Park the robot against a wall so it cannot move. Run the primary scoring mechanism 20 times — pickup, score position, stow — without driving. This builds muscle memory for mechanism controls so the driver can operate them without looking at the robot and without conscious thought during a match.
Use this whenyou have to look at the robot to run mechanisms.
Metric: number of successful mechanism cycles in 60 seconds. Track weekly improvement.

Competition Preparation Drills

🕐 12 min Advanced Pressure Execution
Match Simulation
Load the 1:45 Match timer below. Start from the autonomous end position. Drive your planned match route as if it is a real match — call out each completed element. The coach tracks score; timer alerts fire at :45, :30, and :15. No pausing, no restarts. Log the score after every simulation run.
Use this whenpractice scores don't match what you post at real competitions.
Metric: simulated match score. Track across sessions. If score is not improving week over week, identify the specific phase where cycles are being lost.
🕐 10 min Advanced Recovery
Disruption Recovery
During a normal practice drive, the coach randomly calls "disruption" — at which point they move one game element from its expected position. The driver must adapt and continue the cycle without starting over. This simulates opponent interaction and game element variability during a real match.
Use this whenone bad cycle or bumped element throws off your whole match.
Metric: time from disruption call to resuming normal cycling. Target: under 4 seconds before competition.
🕐 6 min All levels End-Game
End-Game Under Pressure
Load the 0:12 timer below. From a random position on the field, the driver must execute the complete end-game sequence (climb, park, or whatever the current game requires) and have it fully completed before the timer expires. Repeat from 5 different starting positions. This is the most time-critical skill in any match.
Use this whenyou run out of time during the final 12 seconds of a match.
Metric: success rate across 10 attempts from random positions. Target: 90% by competition week.

Spatial Awareness Drills

The #1 beginner failure mode is losing track of which way the robot is facing when it is far from you. These drills fix that.

Far Corner Orientation Beginner · 8 min

Drive the robot to the far corner of the field. Without moving, identify which side is the robot's front. Call it out loud. Turn 90°. Call front again. Repeat. Do this until you can identify robot orientation instantly at any distance.

Target: 0 wrong calls in 20 reps
Blindspot Return Intermediate · 10 min

Drive robot behind an obstacle or to the far end. Close your eyes for 3 seconds. Open and immediately drive back to start tile in minimum moves. Trains muscle memory for robot orientation without visual confirmation.

Target: return in under 4 seconds
Mirror Drive Advanced · 12 min

Have a partner stand on the opposite side of the field — their perspective is your robot's "red alliance" view. They call out "left" or "right" commands. You must execute them correctly from your perspective. This forces you to translate robot-relative directions in real time, exactly like a real match when the robot faces you vs faces away.

Target: 90% accuracy at full speed
Field Position Call-Out Intermediate · 8 min

Drive a cycle. Mid-cycle, your partner says "freeze." You must immediately call the robot's position on the field (e.g., "near post, facing alliance wall"). Builds active field awareness — you should always know where the robot is without looking directly at it.

Target: correct call within 1 second
💡
VEX Forum consensus: Practice with the robot in positions where it is not right in front of you. The field is 12×12 feet. Knowing which way is robot-front should be second nature — not something you think about.
// Section 03
Match Play 🎯
Reading the field, when to defend, and how to run skills routes.
Match Awareness 🔬
Reading the field while driving. When to score, when to defend, when to abort a cycle.

A driver who can only run their practiced route will max out at a ceiling score. A driver who reads the field in real time adjusts to what the game is giving them and consistently outperforms their practice scores in real matches.

What to Track While Driving

Game piece availability

Where are pieces clustered? Which zones are depleted? Are there pieces your opponent has set up that you can intercept? Eyes on the field, not on your robot.

Opponent position

Where is the opponent robot? Are they setting up for endgame early? Are they playing defense on your partner? You do not need to stare at them — a glance every 5 seconds is enough.

Score differential

Your caller handles the scoreboard. Listen to them. If they say "we are down by 8" you need to know whether to take more risks or protect what you have. This is a conversation, not a decision you make alone.

Time remaining

At :45 you should know whether you have time for one more full cycle or should start working toward endgame. At :25 if endgame is not started you are probably starting it right now. Your caller calls these — but you should already feel the rhythm.

Decision Framework — Score vs Defend vs Endgame

Situation Default action Override if
Up by 10+ with :30 left Protect — endgame Endgame already done
Down by 5–10 with :45 left Score aggressively Robot is damaged
Down by 15+ with :30 left Defense + endgame High-value play available
Tied at :25 Endgame first Endgame risky/unreliable
Opponent playing defense on you Switch zones Your zone has more pieces

Match Simulation Scenarios

Run these with your drive team. Nothing should surprise you in a real match.

Robot jams at :45

Call it to your engineer. Pivot to defense or alternate scoring. Keep moving — a stopped robot scores zero.

Autonomous fails

Know where you need to be at 0:00. Driver control starts wherever you land. Have a recovery plan for every auton scenario.

Alliance partner blocks your zone

Agree on zones before the match. If they are in your zone, switch — do not fight. Communicate, pivot, keep scoring.

30 seconds left, endgame not started

Decide before the match, not at :30. Your caller tells you the time. You already know the plan. Execute it.

DEFENSIVE DRIVING
Defensive Driving 🛡️
Defense is a match decision, not a fallback. When to play it, how to do it legally, and how to avoid fouls.
⚠️
Prerequisite: You should have solid offensive driving — consistent cycles, reliable endgame. Defense is an add-on to a strong offense, not a substitute for one. A weak offensive driver who plays defense is just a driver who is not scoring.

When Defense Is the Right Call

Defense is correct when the math supports it. Ask yourself: will blocking their next cycle change the match outcome more than scoring my own?

Play defense when
  • ✓ You are down and their next score ends the match
  • ✓ Your robot cannot score faster than they can
  • ✓ Their endgame hang is worth more than your cycle
  • ✓ Alliance partner is already scoring — you are redundant
  • ✓ Eliminations — every point is amplified
Never play defense when
  • ✗ You are winning comfortably
  • ✗ Your scoring rate exceeds theirs
  • ✗ It will take you away from your endgame
  • ✗ Your alliance partner has not agreed to it
  • ✗ You have not practiced it

Legal Defense — The RECF Rules

Defensive play is legal but referees will not give you the benefit of the doubt. Know these rules before you play defense.

Blocking movement — positioning your robot to impede their path is legal. Stay between them and the game piece.
Field perimeter contact — using the field wall to box in an opponent is generally allowed.
Pinning — trapping an opponent robot against the field wall for more than 5 seconds is a violation. Count in your head and release.
Entanglement — getting your robot tangled with an opponent's mechanism leads to disablement. Keep your chassis clear of their mechanisms.
Tipping — intentionally tipping an opponent robot is a DQ. Never drive under or lift an opponent.

Defensive Techniques

Zone Denial

Position your robot in the most valuable zone before the opponent gets there. You are not chasing them — you are making their best move unavailable. Requires reading the field 2–3 seconds ahead.

Shadow Defense

Follow the opponent robot without contact, staying between them and their scoring target. Slow them down without risking a foul. Works best when you are faster than them.

Endgame Denial

Position near their endgame target in the last 20 seconds to block their hang or climb attempt. High risk — only do this if you have already completed your own endgame and the point differential justifies it.

Defensive Drills

Shadow Drill

One robot drives offensive cycles. Your job is to stay within 12 inches of them at all times without contact. 90 seconds. If they score, they win. Forces you to read their movement, not react to it.

Pin Clock Drill

Pin an opponent against the wall. Count 4 seconds in your head. Release. Repeat. This trains the 5-second pin rule into muscle memory before a match where you will not be counting consciously.

🔬 Full Defensive Driving Guide →
SKILLS STRATEGY
Skills Strategy 🏆
Driver skills is a different discipline from match play. Route design, consistency targets, and how to improve your skills ranking.

Driver skills is a solo run — no alliance, no opponent interference, no communication pressure. It is a timed test of your route efficiency and consistency. Most drivers treat it like a fast match. Top teams treat it like a discipline of its own.

Skills vs Match Play — Key Differences

Driver Skills
  • 60 seconds, not 1:45
  • Full field, no alliance
  • Planned route, repeated exactly
  • Consistency over speed
  • Score every run, not just best run
  • Counts toward season ranking
Match Play
  • 1:45 with auton, full match
  • Alliance + opponents present
  • Adaptable — read the field
  • Speed matters but so does awareness
  • Win the match, not the score
  • One bad match recovers in next

Building Your Skills Route

1
Paper plan first

Draw the field. Mark every game piece. Draw your path with a pencil. Calculate approximate time per cycle. Check total estimated score before you drive it once.

2
Slow first, fast later

Drive the route at 60% speed first. Get the path right before you add speed. A fast wrong route scores less than a slow correct route.

3
Log every run

Score and time each run. Note where you lost time or missed pieces. After 10 runs you will see the pattern — fix the worst point in the route, then repeat.

4
Consistency first, score second

A route you score 80% consistently beats a route you score 100% on 1 in 5 runs. VEX Forum consensus: repetition is what separates elite skills drivers. Run it hundreds of times.

Virtual Driving Skills

✅ Official VEX Tool — Free

VEX now has official Virtual Driving Skills — connect your real V5 controller to Chrome and practice on the Hero Bot field. Same controller, different environment. Great for practicing the route when the physical field is not available.

🔗 VEX Virtual Driving Skills →
// Section 04
Competition Day 🏆
Morning checklist, queue protocol, and post-match debrief.
Competition Day 🏆
Morning through final match. Pre-match checklist, queue protocol, and post-match debrief.

Morning Checklist

Robot

Auton Calibration Checklist

The driver owns auton calibration — not the engineer. The engineer writes the code. The driver confirms it works on this specific field, at this battery level, today.

Pre-Match Auton Protocol
Fresh battery installed — auton drifts on low charge. Never run auton on a battery below 80%.
IMU calibrated — check the Brain screen. If the IMU shows "calibrating" you cannot run. Allow 2 seconds minimum after power-on.
Auton selector confirmed — cycle through all options and confirm the correct routine is selected. Call out the selection to your caller so they hear it too.
Robot starting position verified — your robot must start in the correct tile orientation. 1-inch offset at start = 6-inch offset at scoring target.
Have a backup plan — if auton fails, know where you will be at 0:00 and what your first driver control action is. Decide before queue, not after the failure.
  • ✓ Battery charged to 100%
  • ✓ All ports respond on Brain screen
  • ✓ Auton selector cycles all options
  • ✓ Drive test — all 4 directions
  • ✓ Mechanisms test — intake, scoring, endgame
  • ✓ Spare battery ready and charged
Driver
  • ✓ Controller firmware updated
  • ✓ Control scheme confirmed
  • ✓ 10-minute warm-up drive completed
  • ✓ Match plan discussed with strategist
  • ✓ Drive team roles confirmed
  • ✓ Pre-match routine rehearsed

Queue Protocol

Q
Queue at least 2 matches early. Late queue = automatic DQ risk. Your strategist watches the match schedule and tells you when to leave the pit.
In queue: confirm auton selection, discuss match plan with alliance partner, run pre-match mental routine.
On the field: robot in starting position, controller plugged in, phone in airplane mode or left in pit. Refs are watching.

Post-Match Debrief

Every match is data. Run a 2-minute debrief with your drive team after each match before returning to the pit.

Ask these three questions
1. What worked? — Which cycles were clean? What decisions paid off? Reinforce good habits explicitly.
2. What cost us points? — One specific thing. Not everything — one thing. That becomes the drill focus for next practice.
3. What do we change for the next match? — Adjust the plan, the zone split, the endgame timing. Specific and actionable.
🔧 Full Robot Pre-Check Guide →
// Section 05
Mental Game 🧠
Pre-match routine, resetting after mistakes, and managing nerves.
Mental Game 🧠
Composure under pressure. Pre-match routine. How to reset after a mistake mid-match.

VEX Forum veterans have said this for years: the gap between good and great drivers is rarely mechanical skill. It is mental composure. A driver who executes at 80% of their practice speed consistently will beat a driver who peaks at 100% but shakes in elimination matches.

The Pre-Match Routine

Elite drivers in motorsport, esports, and traditional sports all use pre-performance routines to get to the same mental state every time. Build yours and do it exactly the same before every match — qualifier, elimination, and skills.

1
Confirm the plan

Before queue, agree with your strategist on the match plan. One sentence: "We score left side, they score right, endgame at :25." Everyone on your drive team repeats it back.

2
Physical reset

Shake out your hands, take two slow breaths, loosen your grip on the controller. Tension in your hands telegraphs to the joysticks. Smooth hands, smooth robot.

3
Eyes on the field, not the crowd

During disabled, study the field. Where are the game pieces? Where is the opponent robot positioned? What does their setup tell you about their auton? Use every second of disabled time.

4
First move decided

Know exactly what your first action is when driver control starts. No hesitation at the whistle. The first 5 seconds set the rhythm for the whole match.

Resetting After a Mistake

Every driver makes mistakes in a match. The best ones recover in under 3 seconds. The worst ones are still thinking about the mistake 20 seconds later while the opponent scores.

The 3-Second Reset Protocol
1 second: Acknowledge it internally. "That was bad. Moving on."
2 seconds: Eyes back to field. Find next game piece or best position.
3 seconds: You are back in the match. The mistake is over.

Do not replay the mistake. Do not apologize to your teammate mid-match. Process it after, not during. Your team needs you present right now.

Managing Match Nerves

Signs you are over-anxious
  • Gripping the controller too hard
  • Driving faster than in practice
  • Skipping your pre-match checks
  • Not hearing your caller
  • Tunnel vision — missing the field
What actually helps
  • The pre-match routine (above)
  • Breathing — slow down, not up
  • Focus on first move only
  • Remind yourself: this is practice with stakes
  • Log practice hours — confidence comes from reps
SigBots insight: Thousands of hours of practice runs is what makes top skills drivers consistent — not natural talent. The mental calm comes from repetition, not from trying to calm down.
// Section 06
Setup & Film 🎮
Controller tuning, button mapping, macro philosophy, and film study.
Controller Tuning 🎮
Expo curves, deadband, slew rate, and control scheme. How to configure the robot around your driver.

In Formula One the car is configured around the driver — not the other way around. EZ Template and PROS give you the same tools. Every setting here directly changes how the robot feels in your hands. Tuning is not a programmer task — it is a driver task that requires a programmer to implement.

Tank vs Arcade — Choose First

Tank Drive

Left stick = left side. Right stick = right side. More precise turning — you control each side independently. Higher skill ceiling. Most top competitive drivers use tank.

Better for: precise positioning, tight turns, experienced drivers
Arcade / Curvature

Left stick = forward/back. Right stick = turn. More intuitive for new drivers. Curvature drive adds speed-proportional turning for smoother arcs at competition speed.

Better for: new drivers, smooth arcing paths, simpler setups

Joystick Curves (Expo Drive)

A linear joystick maps 50% stick deflection to 50% motor speed. An exponential curve maps 50% stick to ~25% speed — giving you finer control at low speeds while still reaching 100% at full deflection.

LemLib Expo Drive — Community Standard
chassis.arcade(controller.get_analog(pros::E_CONTROLLER_ANALOG_LEFT_Y),
                controller.get_analog(pros::E_CONTROLLER_ANALOG_RIGHT_X),
                true); // true = expo curve enabled

The third parameter enables exponential scaling. Start with the LemLib default curve value and adjust based on driver feedback. The driver must drive with it — not just code it.

Too aggressive

Robot jerks at slow speeds. Overshoots targets. Driver fighting the robot constantly.

Dialed in

Fine control near targets. Full speed feels natural. Driver is not correcting constantly.

Too flat

Robot feels sluggish to respond. Hard to reach max speed quickly. Driver pushes stick further than needed.

Deadband

Joysticks do not perfectly return to zero. Without a deadband, your robot drifts slowly when no one is touching the controller. The LemLib expo drive implementation includes joystick and drivetrain deadbands — make sure both are set.

// Joystick deadband — ignore inputs below 5%
if(abs(stick_value) < 5) stick_value = 0;

// Drivetrain deadband — minimum power to actually move
// LemLib handles this automatically in expo drive

Slew Rate (Acceleration Limiting)

A slew rate limiter caps how fast the motor speed can change per loop cycle. Prevents wheel spin on fast starts, reduces stress on gears, and makes the robot feel smoother. Most important for heavy robots or aggressive drivers.

Use slew when
  • Robot spins wheels on hard starts
  • Driver is "gunning" the joystick 0-100
  • Gears wear out early in season
  • Robot tips forward on hard braking
Avoid when
  • Robot feels sluggish to respond
  • Driver needs instant direction change
  • Playing defense requires quick pivots
🔗 Full Controller Tuning Guide →
MACROS & FILM STUDY
Macros & Film Study 🎥
When to automate vs keep manual. How to study match recordings and turn observations into drills.

Macro Philosophy — Automate the Routine, Keep the Control

A macro is a button that executes a sequence of actions — intake toggle, endgame deployment, arm position preset. The goal is to reduce the driver's mental load so they can focus on field awareness, not mechanism management.

💡
The rule: Automate actions that are always the same. Keep manual control over actions that depend on context. A macro that fires in the wrong situation is worse than no macro at all.
✓ Good candidates to automate
● Intake on/off toggle
● Endgame deployment sequence
● Arm move to preset height
● Auton selector increment
● PTO shift (drive ↔ hang)
● Pneumatic fire with hold
✗ Keep manual — context dependent
● Scoring action (game-specific)
● Defense pivots
● Fine positioning
● Anything needing partial activation

Button Mapping Principles

1
Most-used action gets the best button

The action you fire 20+ times per match goes on R2 or L2 — your index fingers. Actions used once per match go on face buttons. Map by frequency, not by what feels logical.

2
Endgame needs a dedicated button, never a combo

Under pressure at :25, you will not hit a two-button combo reliably. Endgame deployment is a single button. If your engineer says "we need a safety," add a hold requirement, not a combo.

3
The driver decides the layout — not the programmer

Ask the driver which hand position feels natural for each action, then code it. A programmer who maps controls without asking the driver is building a robot that fights its operator.

Skill Score Targets by Level

Use these benchmarks to set practice goals. If you do not know what score to aim for, you will not know when you are ready to compete.

Level Driver Skills Target Consistency Bar Notes
First competition Any complete run Finish without stopping Route completion is the goal
Regional competitive Top 20% regional 7/10 runs hit target Consistent route, known weakpoints
State qualifier Top 10% state 8/10 runs hit target Route optimized, no wasted seconds
State championship Top 5% state 9/10 runs hit target Near-max route, sub-second timing
Worlds caliber Top 50 global 10/10 near-max 100s of hours — SigBots level

Film Study — Watching Your Own Matches

The best drivers in any sport watch film. VRC matches are short — a 2-minute match can be reviewed in 6 minutes if you know what to look for.

1
Watch for dead time

Any second where the robot is not moving toward a game piece or scoring position is dead time. Timestamp every pause. These become your drill targets — what caused the hesitation?

2
Watch missed pickups

Count every game piece the robot drove over or past without picking up. Note the angle of approach. Most missed pickups happen at the same approach angle — that is a drill.

3
Watch the endgame clock

When did endgame start? When did it finish? How many seconds were left when it completed? If endgame completed with 8+ seconds to spare you started too early. If it was close, you started too late.

4
Watch the opponent

Where was the opponent scoring from? What zones did they own? If you face them again at eliminations you need to know their route. 10 seconds of study per match is enough.

Physical Preparation

A long competition day is 8–12 matches over 6–8 hours. Hand fatigue, grip tension, and focus degradation are real and rarely discussed.

Between matches
  • ● Shake out hands — release tension
  • ● Eat and hydrate — skipping lunch is a mistake
  • ● Do not practice drive between matches — rest
  • ● Review debrief — 2 minutes, then let it go
  • ● Avoid spectating other matches if it adds pressure
Grip technique
  • ● Light grip — thumbs only on sticks
  • ● Do not white-knuckle the controller body
  • ● Resting fingers on triggers, not pressing
  • ● Wrists relaxed, not locked
  • ● Consistent grip across all matches
🎮 Full Driver Tuning Guide →
// Drills
Drills & Presets ⏱
The Match Timer itself sits at the top of the page — always visible while you browse drills or match play. Use the presets and chip grid below to load a duration into it.
⏰ Custom time:

Quick Load

Click a drill to load its target time into the countdown above. Press Start to begin.

Full drill descriptions — when to use each, metrics, targets — live in the Drill Library.

← ALL GUIDES