the video version
The same lesson as a narrated video. Watch it on YouTube
Two separate installers#
Getting fully set up requires two downloads:
- WPILib installer — installs a dedicated copy of Visual Studio Code, the WPILib extension, the JDK, the C++ toolchain, and the WPILib tools. This is required for Java and C++ teams (RobotPy has its own pip-based install via
robotpy). - FRC Game Tools from NI — installs the FRC Driver Station and the roboRIO Imaging Tool. Windows only.
Installing WPILib#
Download the WPILib release for the current season from the WPILib GitHub releases (linked from the install guide) and run it. Two important choices:
- Everything vs. Tools Only — pick Everything for a dev machine (this installs VS Code, the extension, the JDK, the C++ compiler, and the tools). "Tools Only" is for machines that just run dashboards.
- This User vs. All Users — "This User" needs no admin rights.
The installer creates an isolated VS Code so your FRC setup never conflicts with another VS Code. The bundled WPILib tools include Elastic, Shuffleboard, Glass, SysId, OutlineViewer, the Data Log Tool, AdvantageScope, WPIcal, and PathWeaver. (Heads-up: PathWeaver and Shuffleboard are slated for removal in 2027 — Elastic and AdvantageScope are the modern recommendations for dashboards and data review, and Choreo/PathPlanner for paths.)
Installing the FRC Game Tools#
Go to the NI FRC Game Tools download page, sign in with a free NI account, download, and run the installer. Note:
- It is recommended to remove old versions first; the new version is tested only against the current season.
- The Game Tools install the Driver Station and the roboRIO Imaging Tool (no LabVIEW required for the text languages).
- A reboot is usually required.
Imaging the roboRIO#
A new roboRIO must be imaged (have the correct firmware/OS for the season) before it can run your code:
- roboRIO 1.0 — connect over a USB Type-B cable and use the roboRIO Imaging Tool. Firmware must be at least v5.0 to accept a 2019-or-later image; only brand-new units typically need a firmware update. Set your team number and pick the latest image, then Reformat.
- roboRIO 2.0 — you flash the season image onto a microSD card using a separate SD-burner application (balenaEtcher or Raspberry Pi Imager); the roboRIO Imaging Tool just helps you locate the image file and set the team number. Then boot the roboRIO from the card.
Set your team number on the roboRIO during imaging — this configures its network identity so your laptop and Driver Station can find it.
Sanity check#
After installing, open VS Code and click the red WPILib "W" icon (top-right) to open the command palette. If you see commands like "Create a new project" and "Build Robot Code," the extension is working. Open the Driver Station; if it launches and shows your team number, you're ready to deploy.
the part worth keeping
Key takeaways
- You need two installs: the WPILib installer and the NI FRC Game Tools.
- Choose 'Everything' when setting up a development laptop.
- The Driver Station and roboRIO Imaging Tool are Windows-only and come from NI.
- roboRIO 1.0 needs firmware v5.0+; roboRIO 2.0 boots from a flashed microSD card.
- Set your team number during imaging before deploying code.
Programming, Controls & SensorsFoundations: Tools, Languages, and Your First Robot Programlesson 3 of 4
Keep going
Take the quiz+10 XP with an accountMore in Foundations: Tools, Languages, and Your First Robot Program
where this came from
Sources and corrections
This lesson is AI-assisted: drafted from primary sources, then reviewed and edited by hand. Errors still get through. When one is reported we fix it and write down what changed, in public, in the corrections log.
sources and further reading
- docs.wpilib.orgWPILib Installation Guide
- docs.wpilib.orgInstalling the FRC Game Tools
- docs.wpilib.orgImaging your roboRIO 2
clipped to this lesson
Articles that go further on this
The lesson gets you through the topic. These go wider on it, and they read in one sitting.
- 13 min readThe roboRIO 2.0: Imaging, Setup & Managing FRC's Robot BrainImage, set up, and wire the roboRIO 2.0 and 1.0: the roboRIO Imaging Tool workflow, microSD flashing, team number, I/O ports, power, and deploying code./blogread it
- 20 min readInstalling WPILib and VS Code for FRC (Step by Step)Learn how to install WPILib and VS Code for FRC step by step: download the installer, create a robot project, add vendordeps, and deploy to the roboRIO./blogread it
- 8 min readThe FRC Software Toolbox: Driver Station, Dashboards, AdvantageScope & SysIdA beginner-friendly tour of the FRC software ecosystem beyond robot code: Driver Station, dashboards (Glass, Elastic, AdvantageScope), SysId, and vendor tools./blogread it
answer sheet
Lesson quiz
All 3 right completes the lesson. Miss one and only that question comes back, anything you already answered correctly stays banked.
0 of 3 answered
01The roboRIO Imaging Tool and the FRC Driver Station are distributed as part of which package?
02What does the WPILib installation primarily set up for Java and C++ teams?
03How is a roboRIO 2.0 imaged for the season?
Answer every question to submit.
All 51 lessons in Programming, Controls & Sensorsopenclose
01 / prerequisites
02 / foundations-tools-and-first-program
03 / robot-program-and-command-based
04 / motors-and-control
05 / autonomous-trajectories-simulation
06 / sensing-fundamentals
07 / encoders
08 / gyros-imus-orientation
09 / closed-loop-control
10 / vision-pose-estimation
11 / worked-examples-mini-projects
- Not read yet:Mini-Project: A Closed-Loop Elevator with Motion Magic
- Not read yet:Mini-Project: A Velocity-Controlled Shooter on REVLib
- Not read yet:Mini-Project: A Teleop Swerve Drive Subsystem
- Not read yet:Mini-Project: An Autonomous Routine with PathPlanner
- Not read yet:Mini-Project: Vision-Aligned Scoring with Limelight
12 / common-mistakes-troubleshooting
13 / advanced-techniques-case-studies
- Not read yet:State-Space Control and Kalman Filtering
- Not read yet:Log Replay Architecture with AdvantageKit
- Not read yet:Advanced Pose Estimation: Multi-Tag Fusion and Standard Deviations
- Not read yet:Robot Coordination, Alerts, and Operator Feedback
- Not read yet:Case Study: Hardening Software Before an Event