AlphaBit - OpenML

Getting Started - Decode Setup for FTC Teams

Decode Documentation Path

Beginner-friendly setup checklist for teams that want to reproduce the Decode stack safely. Follow this page in order, then move to Resources and the feature-specific pages.

Step 1

Confirm Hardware Configuration Names

Your Robot Controller configuration names must match your code exactly. Start with this baseline map:

// Drive + localization
"Front_Right", "Back_Right", "Back_Left", "Front_Left"
"imu", "Back_Left", "Back_Right"

// Vision
"AlphaBit_Webcam"

// Mechanisms
"Intake_LeftMotor", "Intake_RightMotor"
"Outtake_LeftMotor", "Outtake_RightMotor"
"LeftTurret", "RightTurret", "AngleTurret"
"BlockArtifact", "PushLastArtifact"
"leftDistanceSensor", "rightDistanceSensor", "colorSensor"

If one name is wrong, your OpMode can fail before match start.

Step 2

Run the Basic Smoke Tests

Run ChasisEngineering to validate drive motors and encoder telemetry.

Run TeleOp_Decode to validate intake, turret, flywheel, and sensor updates.

Only after TeleOp is stable, run autonomous tests.

Step 3

Validate Localization Baseline

Road Runner two-wheel localizer: RoadRunner/drive/opmode/TwoWheelTrackingLocalizer.java.

IMU heading source: drive/Skeletal_Structures/GyroscopeBHIMU.java.

Run straight-line and square-repeatability tests before tuning scoring logic.

Step 4

Validate Vision Baseline

Pattern IDs: 21 / 22 / 23.

Localization IDs: 20 / 24.

Check webcam image quality before trusting pose correction in motion.

Step 5

First Autonomous Acceptance Check

Robot completes one safe cycle: intake -> align -> score -> reset.

No uncontrolled drift across repeated runs.

Driver can always override/stop mechanism behavior.

Open Resources for file-by-file mapping, then continue through AprilTag and Autonomous pages in order.

Support -> Discord

Choose Language / Alege Limba

AlphaBit AI Assistant