Everything new V5RC students need to learn about drivetrain, gear ratios, RPM, motors, and weight. Curated path through Spartan Design's existing guides + 5 vetted video tutorials. Built for Override 2026-27 build season.
If you can answer these questions out loud (without looking), you've got the basics. If not, work through the learning path in Section 1.
| Range | Linear Speed | Use Case | Trade-off |
|---|---|---|---|
| Slow | 3.5 β 4.5 ft/s | Push-heavy strategy, defensive blocking, very heavy robots | Can't cycle as many cup/pin trips in 1:45 |
| Sweet spot | 5.0 β 5.5 ft/s | Override default. Cycle scoring + toggle contests | Best balance for most teams |
| Fast | 5.5 β 6.5 ft/s | Speed-cycling strategies, lightweight robots, experienced drivers | Less precision; harder for new drivers; less push force |
| Too fast | 6.5+ ft/s | Skills runs only | Drivers lose control; overshooting goals; battery drain |
V5RC robots have no weight rule β the limit is the 18β³ Γ 18β³ Γ 18β³ starting envelope (R3) and the motor power caps (R10a/R11a). But weight directly affects how hard your motors work.
| Weight Range | Impact | Recommendation |
|---|---|---|
| Under 12 lb | Lightweight; motors push easily; quick acceleration | Often too light to push opponents; OK for speed strategy |
| 12 β 16 lb | Typical V5RC competition robot range | Most builds land here naturally with metal chassis + 6+ motors |
| 16 β 20 lb | Override sweet spot for push-heavy + manipulator builds | Heavier-on-purpose for toggle contests + endgame king-of-hill |
| Over 22 lb | Motor strain risk; brownout risk under load; slow acceleration | If you're here, audit the chassis for redundant metal; consider polycarb |
The relationship between speed, weight, motor count, and cartridge isn't a single formula β but here are the patterns most V5RC builds settle into:
If your students prefer reading to watching, these official articles cover the same material:
These map to actual build decisions your team will make in Phase A:
Use these to verify each team member understands the basics:
Document your team's drivetrain decision discussion on these notebook slides:
If your team gets stuck on a specific topic during discussion: