From Zero to Robot: Tools and the First Build

The official on-ramp: WPILib Zero-to-Robot#

FIRST and the WPILib team publish a step-by-step tutorial called Zero-to-Robot that takes a brand-new team from nothing to a basic, driving robot. It's the canonical starting point and is free. The tutorial is designed to be completed in order, covering four phases:

1. Build/Wire the robot — assemble the control system and wire it correctly (the roboRIO controller, Power Distribution Hub/Panel, motor controllers, radio, the 120A main breaker, and the 12V battery).
2. Install software — set up the WPILib development environment (a customized VS Code) and the FRC Driver Station (Windows-only) used to enable and control the robot.
3. Configure hardware — set device IDs and firmware on motor controllers and the radio.
4. Load a basic program — deploy an example so the robot drives. You can get a basic robot driving even without deep programming knowledge by using the provided templates.

Start here: https://docs.wpilib.org/en/stable/docs/zero-to-robot/introduction.html

Pick a programming language#

WPILib officially supports three languages — choose based on your team's experience:

• Java — by far the most common in FRC; tons of community examples (the KitBot starter code is provided in Java).
• C++ — powerful and fast; common on experienced teams.
• Python (via RobotPy) — increasingly popular and beginner-friendly.

All three use the same WPILib concepts, so tutorials transfer. (LabVIEW was supported for years but is deprecated and won't run on the upcoming SystemCore controller, so new teams should pick Java, C++, or Python.)

Free design tools#

• Onshape offers free, cloud-based CAD for FRC teams, with FRC parts libraries and the current-year field model built in — design your robot before cutting metal. Get started: https://www.onshape.com/en/education/first-robotics
• The KitBot (from the Kit of Parts) gives rookies a proven, buildable robot for the current game so you don't have to design everything from zero in year one.

A sane first-season plan#

Veteran mentors recommend rookies keep it simple:

1. Build a reliable drivetrain first (often the KitBot / AM14U6 drive base). A robot that drives well and plays defense or moves game pieces beats a fancy robot that doesn't run.
2. Get a basic autonomous — even just driving forward to leave your starting line earns points every match.
3. Add one scoring mechanism you can make reliable, rather than three you can't.
4. Add an endgame (e.g., a simple climb/park) once the basics are solid.
5. Practice driving before your first event — drive practice often matters more than another mechanism.

Where to get help#

• WPILib docs (docs.wpilib.org) — the programming and control-system bible.
• Chief Delphi (chiefdelphi.com) — ask anything; the community is famously helpful.
• The Blue Alliance (thebluealliance.com) — study how top teams build and play.
• Vendor documentation — REV Robotics (revrobotics.com) and CTR Electronics (ctr-electronics.com) document their motor controllers and electronics; Limelight and PhotonVision document vision.

The mindset that wins#

Your first robot does not need to be the best. It needs to work, drive, and finish matches. Iterate every year. The teams that improve fastest are the ones that ship a simple, reliable robot, learn from each event, and embody Gracious Professionalism along the way.

Learn more#

• WPILib Zero-to-Robot & docs: https://docs.wpilib.org
• Chief Delphi forums: https://www.chiefdelphi.com