VEXcode V5 Setup Guide

flowchart TD
    Start([New laptop or new student]) --> Dl[Download VEXcode V5
code.vex.com/v5]
    Dl --> Install[Install the app
verify: opens and shows splash]
    Install --> Connect[Connect V5 Brain via USB
verify: VEXcode detects it]
    Connect --> Project[File → New Project
pick template:
Path B Spartan template]
    Project --> Build[Build button
verify: green check appears]
    Build --> Upload[Upload to Brain
verify: progress bar completes]
    Upload --> Q1{Runs on Brain?}
    Q1 -->|"Yes"| Done([VEXcode ready])
    Q1 -->|"No"| Debug[Diagnose:
cable? Brain firmware up to date?
VEXcode app up to date?]
    Debug --> Build

    style Start fill:#1e293b,stroke:#22d3ee,stroke-width:2px,color:#e2e8f0
    style Done fill:#1e293b,stroke:#22c55e,stroke-width:2px,color:#e2e8f0
    style Q1 fill:#fbbf24,color:#0f172a,stroke:#fbbf24

WHICH ONEWhich version do I download?

This guide covers the single-file workflow. Multi-file via VS Code Extension is covered in the appendix at the bottom of the page.

PRE-FLIGHTWhat you need

• VEXcode V5 installed — free from vexrobotics.com
• A single-file zip downloaded: clawbot-vexcode-single.zip, flex-vexcode-single.zip, or skimmer-vexcode-single.zip
• The zip contains one file: main.cpp, plus a README
• A text editor — Notepad, TextEdit, or any plain-text editor
• (Optional) A V5 brain for testing

STEP 1Create a fresh C++ project

1. Open VEXcode V5
2. File → New Text Project
3. Choose C++ when prompted
4. Use the Empty Project template (NOT "Clawbot Drivetrain" or any template that pre-configures devices)
5. File → Save As, give it a name (e.g., Clawbot-2822)

STEP 2Configure devices in the wizard

The reference code is Path A — hardware comes from the Devices wizard, not from code declarations. Before you paste the reference, configure all required devices in the Devices panel (left sidebar of VEXcode V5).

1. Open the Devices panel (left sidebar)
2. Click Add a Device for each device needed by your reference project
3. Use the exact device names listed in the reference's pragma region (top of main.cpp)

STEP 3Open the reference main.cpp

Unzip the downloaded reference (e.g., clawbot-vexcode-single.zip). Inside you'll find one file: main.cpp (plus a README). Open main.cpp in any plain-text editor — Notepad on Windows, TextEdit on Mac, or anything similar.

STEP 3.5Replace VEXcode's default main.cpp

1. In VEXcode, click into the main.cpp file
2. Select all (Ctrl+A / Cmd+A)
3. Delete (so the file is empty)
4. Switch back to the reference main.cpp in your text editor
5. Select all → copy (Ctrl+C / Cmd+C)
6. Switch to VEXcode → paste → save (Ctrl+S / Cmd+S)

STEP 4Build

Click the Build button (hammer icon or Ctrl+F5 / Cmd+B). Watch the output panel. If the build succeeds → skip to Step 5. If it fails → the first error in the output is the real problem.

Troubleshooting

STEP 5Download to the robot

1. Connect V5 brain via USB cable (or controller-to-brain VEXnet)
2. Brain icon at the top of VEXcode turns green
3. Pick a slot from the dropdown (default: slot 1)
4. Click Download (arrow icon)
5. Press Run on the brain to start

UNDERSTANDINGThe single-file structure

The reference main.cpp isn't a 600-line mess — it's organized into clearly-named SECTIONS separated by big banner comments. Each section is what would be a separate file in a multi-file project. Use Find (Ctrl+F) to jump to a section by its banner.

TUNINGWhat to edit after a successful build

1. Port assignments. Section 1 of main.cpp. The port numbers in motor constructors must match your wiring. This is the only section you need to edit for port changes.
2. Mechanism constants. Each subsystem section has tunable values at the top (ARM_POWER = 80, CLAW_OPEN_DEG = 200, etc.). Find the section banner, the constants are right below.
3. Autons. The drive_for_ms(power, ms) helper needs calibration for your wheel size and gearing. Run auton_drive_test and measure actual distance.
4. Read the architecture page. Full reference at spartandesignrobotics.org/code-architecture-vexcode.

APPENDIXMulti-file via VS Code Extension

When students outgrow the single-file edition and want the full multi-file architecture — one .cpp per mechanism, compiler-enforced encapsulation — the path is the VEX VS Code Extension. This is NOT the same as the PROS + EZ-Template setup students struggled with.

RESOURCESCompanion references