Step 2: Set Up Your Environment¶
02
Set Up Your Environment
Step 2 of 4
Set up your programming environment and the Driver Station software for your robot.
Before You Start
Keep the language and programming environment you selected in Zero to Robot. Complete the setup for that environment, then set up your program’s driver software. The programming environment is where you write code; the Driver Station is where you control the robot during a test.
The computer you plan to use for programming
Administrator access if you selected desktop development
Internet access, or offline packages downloaded in advance
FRC teams also need a Windows 11 computer for the competition Driver Station. It may be the same computer used for programming.
Choose how you’ll write code. OnBot runs in the browser with nothing to install; desktop development uses tools installed on your computer, including WPILib VS Code or LabVIEW. These paths support FRC and FTC with Systemcore. Keep using the environment and language you selected on the Zero to Robot page.
Important
Some 2027 instructions are still being completed. The FRC VS Code path is documented end to end. Detailed Systemcore OnBot and FTC walkthroughs will be added as their software is finalized. If you are using a REV Control Hub today, use the linked current FTC documentation instead.
Part 1: Set Up Your Programming Environment
OnBot runs directly in the browser, hosted on the Systemcore itself. There’s nothing to download or install.
Languages: Java, Blocks, Python, and LabVIEW.
Note
Systemcore-specific OnBot setup steps are still being written. In the meantime, do not substitute current REV Control Hub connection addresses or deployment steps. See the current FTC programming-tool guide when using current FTC hardware.
Tip
FRC teams: OnBot provides the programming environment, not the Driver Station. You’ll still need the FRC Driver Station installed locally for competition. See Set Up Driver Software below.
The WPILib installer and VS Code setup below are the same install for FRC and FTC. Where a tool or step is program-specific (like the FRC Driver Station or simulation), it’s labeled.
Languages: Java, Blocks, C++, and Python.
System Requirements
FRC + FTC: macOS / Linux
macOS 12+ or modern Linux distro
WPILib + VS Code for writing code
Can run Driver Station for testing only, cannot image Systemcore
Deploy code over USB or Wi-Fi (needs network access)
Robot simulation is currently FRC only
FRC + FTC: Windows
Windows 11
WPILib + VS Code for writing code
Robot simulation is currently FRC only
Installation Steps
FRC + FTC
Installs Visual Studio Code, WPILib extensions, and all desktop tools (Glass, Elastic, OutlineViewer). Required for Java, C++, and Python teams.
FRC + FTC, Python teams only
Install RobotPy and the required Python packages. Java and C++ teams can skip this part.
Optional: FRC + FTC
Preparing to install without internet access? Download the offline installer packages in advance.
Verify Your Installation
Install WPILib first. Python teams should then complete RobotPy setup; Java and C++ teams can skip it. The offline preparation guide is only needed when installing without internet access.
Confirm the installation is working:
FRC + FTC
Launch the WPILib VS Code shortcut (not the system VS Code). You should see the WPILib icon (W) in the activity bar.
FRC + FTC
Press Ctrl+Shift+P (or Cmd+Shift+P on Mac) and type WPILib. You should see WPILib commands in the palette.
Tip
Vendor libraries are not installed here. Libraries like REVLib and Phoenix 6 are added per-project in Step 4 using the WPILib Dependency Manager. You do not need them yet.
Desktop LabVIEW
LabVIEW is also available for desktop development. Its Systemcore installation and project-creation walkthroughs are still being completed. The VS Code installation steps above apply to Java, Blocks, C++, and Python.
Part 2: Set Up Driver Software
Your programming environment and your competition driver software are separate choices. Set up the driver software required by your program, regardless of whether you selected OnBot, VS Code, or desktop LabVIEW.
FRC only: Windows 11
Install this on the Windows laptop that will drive the robot at competition. The 2027 production release supports the official FMS. During pre-season testing, match alpha Driver Station builds with a compatible Systemcore release.
FTC with Systemcore
Systemcore and Motioncore use FTC-specific driver software. See the FTC overview for Systemcore resources. Teams using a REV Control Hub or Expansion Hub should use the FTC Docs.
Warning
Windows 10 is not supported by the FRC Driver Station beginning in 2027. Upgrade the FRC driver-station computer to Windows 11 before installing it.
Part 3: Check That You Can Continue
Your selected programming environment opens and its setup instructions are complete.
For VS Code, WPILib commands appear in the command palette.
The driver software for your program is installed and opens.
You do not need to create a project or install vendor libraries yet. Those belong to Step 4, after the control system is configured.
✓ Your programming environment is ready.
Continue when your selected programming environment opens successfully. FRC teams should also confirm that the FRC Driver Station opens; “No Robot Communication” is expected until the robot is configured in Step 3.