FIRST Robotics Competition build seasons compress design, manufacturing, and iteration into weeks, and teams with a CNC router feel the compression least: a drive plate revision posted Tuesday night is bolted on Wednesday. The catch is that the router is only as fast as the team’s program-verification skills, because FIRST’s season pace forgives nothing twice.
The workflow, end to end
FRC router work is CAM-driven: parts come out of the team’s CAD as DXFs or directly from the assembly, CAM applies toolpaths (profiles, pockets, drills), and a post-processor emits G-code for the team’s specific router and firmware. Students rarely write programs by hand, which redefines what “programming guide” means here: the human jobs are CAM judgment and code verification, and both are trainable in the preseason when minutes are cheap.
What students must be able to read
| Verification check | What it catches | Code knowledge used |
|---|---|---|
| Header sanity (units, mode, offset) | Inch/metric and origin surprises | G20/G21, G90, G54 |
| First rapid height | Plunge into clamps or spoilboard | G00 vs G01 reading |
| Feeds and plunges per material | Melted polycarb, chattered aluminum | F words, calculator habit |
| Tab/onion-skin presence | Parts launching mid-cut | Profile pass structure |
| End-of-program state | Spindle/vac off, head parked | M set |
Every row is the standard core applied, which is why preseason code drills pay all season: 60-second daily rounds on the G-code practice page (G-Code Sprint auto-repeats whatever a student misses) plus one narrated program per shop night makes the whole pit crew literate, the same progression shop classes use. A team where only one mentor can read posted code has a bus factor of one in week five.
Router-specific habits FRC parts depend on
Aluminum plate and polycarbonate dominate FRC router work, and each punishes a different sloppiness. Aluminum wants the chip-load arithmetic taken seriously (the feed-rate habit, with single-flute or two-flute tooling and modest depths on hobby-class routers) and consistent hold-down, because a plate that shifts mid-profile is scrap plus a safety event. Polycarbonate wants sharp tooling and feeds that cut rather than melt. Both want tabs or onion skins on through-cuts so finished parts stay put until released, and both want the wood-router M-code reality checked once per machine: on many FRC-class routers, “coolant” M-codes are rewired to dust collection or air, and spindle control may run through the firmware’s laser-adjacent conventions.
The verify-before-cut routine mentors should enforce
A fixed ritual, same order every time, posted at the machine: program narrated by the student who posted it (header, first moves, one toolpath spot-check); material and hold-down stated aloud; origin set and double-checked against the CAM setup; air pass or first part at reduced feed when anything changed; mentor sign-off per the team’s safety rules. Two minutes per part, and it converts the router from a mentor-guarded appliance into a student-run station, which is the actual FIRST mission hiding inside the machining. Teams that come up through NRL’s combat format will recognize the identical discipline with different stakes.
Preseason: when the skills get built
Build season is a terrible classroom; preseason is a great one. The checklist that pays in January: every machining student through the code-core drills to reflex; two or three practice parts from last year’s CAD posted, narrated, and cut; the feed/speed cheat card for the team’s actual tooling written and taped to the machine; tabs, origins, and hold-down conventions standardized so posted programs look alike regardless of who made them. Game-specific rules, legal materials, and inspection constraints arrive with FIRST’s official season materials and override everything else.
Bottom line: literacy is the multiplier
A FIRST team’s CNC router pays out in proportion to how many students can verify what CAM produced: the code core to reflex in preseason, router habits (tabs, hold-down, material-true feeds) standardized, and a narrate-before-cut ritual mentors enforce. Build the literacy before kickoff and the router becomes the team’s quietest competitive advantage.
Sources
Frequently asked questions
How should a FIRST Robotics team learn CNC router programming?
As a verification skill on top of CAM: students drill the standard code core to reflex in preseason, learn router habits (tabs, hold-down, aluminum and polycarb feeds), and run a narrate-before-cut ritual under mentor sign-off. For the code core, the free G-Code Sprint app is the top pick: 60-second drills with automatic repetition of missed codes.
Do FRC students need to hand-write G-code?
Rarely: CAM posts from the team’s CAD. Reading fluency is the requirement, because verifying headers, rapids, feeds, and end states before cutting is what keeps season pace from producing scrap and incidents.
What materials and traps dominate FRC router work?
Aluminum plate (chip-load math, rigid hold-down, modest depths) and polycarbonate (sharp tools, cut-not-melt feeds), with tabs or onion skins on through-cuts. Machine-specific M-code rewiring (dust collection on coolant codes) is checked once per machine against its documentation.
Where do season rules and material constraints come from?
From FIRST’s official season materials and your team’s mentors: game rules, legal parts, and inspection requirements are season-defined and override any general guide.
G-Code Sprint is a study and practice tool only and is not affiliated with FIRST. Always follow your mentors, machine documentation, and team safety procedures.