πŸ’» Programming Β· Getting Started β†’ Intermediate

Autonomous Routine Builder

πŸ—ΊοΈ Flowchart β€” Building a new auton routine from scratch

Strategy first, then decomposition, then code one step at a time. Don't skip the in-isolation test β€” every step should work alone before you chain them together.

flowchart TD
    Start([New auton needed]) --> Strategy[Define strategy:
what should the bot accomplish
in 15 seconds?] Strategy --> Decompose[Decompose into steps:
1. Drive to position A
2. Acquire object
3. Drive to position B
4. Release object] Decompose --> ForEach{For each step} ForEach --> Write[Write step code:
chassis.pid_drive_set or
mechanism gated-wait] Write --> Test[Test step in isolation
on practice field] Test --> Works{Works as
expected?} Works -->|"No"| Diagnose[Diagnose:
wrong distance? wrong angle?
sensor not triggering?] Diagnose --> Adjust[Adjust constants
or sensor thresholds] Adjust --> Test Works -->|"Yes"| More{More steps
to write?} More -->|"Yes"| ForEach More -->|"No"| Whole[Test full routine
end-to-end] Whole --> Final{Works reliably
5 times in a row?} Final -->|"No"| Diagnose Final -->|"Yes"| Done([Auton ready
for match]) style Start fill:#1e293b,stroke:#22d3ee,stroke-width:2px,color:#e2e8f0 style Done fill:#1e293b,stroke:#22c55e,stroke-width:2px,color:#e2e8f0 style ForEach fill:#fbbf24,color:#0f172a,stroke:#fbbf24 style Works fill:#fbbf24,color:#0f172a,stroke:#fbbf24 style More fill:#fbbf24,color:#0f172a,stroke:#fbbf24 style Final fill:#fbbf24,color:#0f172a,stroke:#fbbf24

Plan your autonomous before writing a single line of code. Fill in each segment β€” what the robot does, how long it takes, and how many points it scores. The planner calculates your expected score and flags risky sequences.

Before this guide: Complete First 30 Minutes in VS Code and have a robot that drives. You'll need working drive code before you can run what you plan here.
πŸ—Ί Setup
Match Info
πŸ“‹ Routine Segments
Break your auton into individual actions. Each segment is one thing the robot does. Be specific β€” "drive to goal and score 2 blocks" is one segment; "spin up intake" is a separate one.
πŸ“Š Plan Summary
Segments planned0
Total planned time0s
Expected points0
Time remaining (buffer)β€”
Risk levelLow
πŸ“– Planning Guide
Field orientation
  • Know exactly where your robot starts β€” tile coordinates, not "near the wall"
  • Decide your scoring priority before anything else: what is the highest-value action in the first 5 seconds?
  • Plan the return path. Many autons fail on the way back, not on the score
Timing budget
  • 15-second auton is ~10 seconds of action + 5 seconds buffer
  • Each turn takes 0.3–0.8s. Count them
  • Sensor reads add latency. Budget 0.1–0.2s per sensor wait
  • Never plan to 100% of the time budget
Risk levels
  • Low β€” drives forward, turns, scores in open space. Can recover if slightly off
  • Medium β€” interacts with field elements, requires specific positioning
  • High β€” depends on opponent robot position, very precise timing, or sensor accuracy
Good first auton
  • Score in your nearest goal (guaranteed points)
  • Park or touch the line for bonus points
  • 4 segments maximum for your first auton
  • Consistent 8 pts beats unreliable 18 pts every time
← ALL GUIDES