Install the VESC Tool and connect your controller, either via USB or Bluetooth

VESC Tool is the software that allows you to configure, monitor, and update a VESC controller. It's through this software that everything happens: motor detection, current limits, throttle control, diagnostics. This guide covers the very first step: installing the software, connecting to the controller, and taking the two precautions that prevent most unexpected issues.

If you are new to the VESC, start with our guide "VESC Explained Simply".

Download VESC Tool

The VESC Tool can be downloaded from the official project website, vesc-project.com, and is also available in the Android and iOS app stores. Be wary of copies offered on third-party websites; always use the official version.

On a computer, the application either installs or launches directly, depending on the operating system. On a phone, it installs like any other application. For initial setup, a computer is more convenient: it offers a larger screen, a USB cable, and reduces the risk of losing the connection at a critical moment.

Connect via USB

1. Turn on the controller using its battery, with the wheel raised for safety. The USB connection is not sufficient to power the motor control circuitry.
2. Connect the USB cable between the computer and the controller's port. Use a cable that transmits data, not just a charging cable.
3. Launch VESC Tool and use the automatic connection button. The software searches for the controller on the USB ports and connects to it.
4. `Check the connection: The status bar displays the connected controller and the version of its firmware.`

If nothing happens under Windows, try a different cable or a different USB port; this is the most common cause. Under Linux, the user must have the necessary permissions to access the serial ports.

Connect via Bluetooth

A VESC controller doesn't always have Bluetooth built-in. In such cases, you'll need a compatible Bluetooth module connected to the controller's communication port, or a controller that already integrates Bluetooth. The connection is then established using the VESC Tool on your phone by searching for Bluetooth devices within the software (and not through the Bluetooth settings on your phone).

Bluetooth is convenient for monitoring data while riding or adjusting a setting near the track. However, for firmware updates or an initial, comprehensive setup, USB remains a more reliable option.

First precaution: back up the configuration

Before making any changes, save the current motor configuration and the settings for the inputs (throttle, brake) to separate files, using the dedicated menu in the VESC Tool. If a setting goes wrong, you can easily revert to the original state. This is especially important on a machine that has been configured by someone else.

Second precaution: the firmware

The firmware is the software that runs on the controller. The VESC Tool and the firmware evolve together: a recent version of the software may require a controller update to access all of the settings.

• The VESC Tool indicates when the controller's firmware is outdated and suggests the appropriate versions for the recognized hardware.
• The update is performed via USB, with the battery fully charged, and without disconnecting it during the process.
• On a dual-motor controller or when using two controllers connected together, each controller must have the same version.
• After the update, the configuration may be reset to its default settings. That's why we always back up the settings beforehand.

Navigating the VESC Tool

Once connected, the VESC Tool displays several main sections:

• The assistants guide the configuration of the motor and step inputs: this is where you begin
• Motor settings: currents, voltages, temperatures, control mode;
• Input settings (often called "App"): accelerator type, brake, communication;
• Real-time data: Current curves, voltage, temperature – useful for understanding what the machine is doing;
• The terminal, designed for advanced users, displays information such as the most recent recorded errors.

The next step is motor detection.