Tools overview

Blocks

Blocks is the tool where you write a robot program by arranging blocks. It turns the blocks into ready-made code: Arduino code (.ino) for the Probot kit, and a .blk file and OnBot Java for an FTC robot. The tool runs in the browser and needs no account and no installation.

Address: probotstudio.com/blocks

Warning

Blocks has no account and no cloud save. Your work is stored only in this browser. To keep a lasting copy, save it to a file with Download blocks (Probot) or Download .blk (FTC).

Who it is for

What it does and does not do

Blocks does Blocks does not
Generates Arduino code (.ino) from Probot blocks and shows it in Code Preview. It does not compile the code or send it to the board. You compile and upload in Arduino IDE: Upload the code to the Probot board.
Generates a .blk file and OnBot Java (.java) from FTC blocks. It does not send the program to the Control Hub by itself: Upload the program to the Control Hub.
Hands the FTC program to Sim when Sim is open in the same browser. It does not run the program by itself. A Probot Blocks program does not run in Sim either. To try an FTC program on a virtual field: Try the program in Sim.
Downloads a Probot project as a .probot.json file and an FTC program as a .blk file. It does not save to an account or to the cloud. A Probot project is autosaved only in this browser: How autosave works.
Defines the device names of an FTC program in Robot configuration. It does not design robots. You build the robot in Builder: probotstudio.com/builder.

Two modes

You work in one of the two tabs in the toolbar.

Tab What it is for What it generates
Probot Blocks Probot kit (ESP32 board) .ino code, .probot.json project file
FTC Blocks FTC robot (REV Control Hub) .blk file, OnBot Java (.java)

The first time you open the tool, it opens on the FTC Blocks tab. The tab you select is remembered on your next visit.

Get started

Select the starting page that fits your robot.

Your robot Start here
Probot kit First 10 minutes: get your first Probot code from a ready-made example. Then Set up the robot WiFi, Copy or download the code, Upload the code to the Probot board.
FTC robot Start with an FTC example: open a ready-made FTC program. Then Set up the robot configuration, Write a new FTC program, Save the program, open it and get the Java code, Upload the program to the Control Hub.

Probot Blocks tasks

FTC Blocks tasks

Both modes

Glossary

Term Meaning
Toolbar The top strip with the mode tabs, the project name and the file buttons.
Block list The list of categories next to the workspace (Gamepad, Motor & Drive...).
Block panel The panel that opens when you press a category and shows the blocks of that category.
Workspace The large area where you arrange blocks. Its background is dotted in Probot mode and plain white in FTC mode.
Side panel The settings and code panel next to the workspace.
Lifecycle blocks The six blocks that are already there in Probot mode and cannot be deleted (robotInit, teleopLoop...). They set what the robot does at each moment.
Variable A name that stores a value. Motor, servo and gamepad names are variables too.
OpMode In FTC, the one program the robot runs. You select it by name on the Driver Station.
Robot configuration The names of the motors, servos and sensors connected to the Control Hub.
.ino The code file that Arduino IDE opens.
.probot.json The Probot Blocks project file: blocks, project name, WiFi settings.
.blk The FTC Blocks program file. The Blocks editor on the Control Hub uses the same format.
OnBot Java The Java editor on the Control Hub. Blocks generates Java code to paste into this editor.
Next →First 10 minutes
On this page
Who it is forWhat it does and does not doTwo modesGet startedProbot Blocks tasksFTC Blocks tasksBoth modesGlossary