FTC Training Program | Cool Name Found

Achievement	Event	Standing
Inspire Award	NJ State Qualifier	1st Place
Inspire Award	NJ State Championship	1st Place
Connect Award	World Championship — Houston 2026	1st Place
World Championship	Houston, TX — 2026	Qualified

Role	Responsibility
Head Referee	Enforces game rules on the competition field
Judge Advisor	Leads the judging panel for all award decisions
Lead Mentor / Coach	Guides the team throughout the full season
Team Captain	Student leader and primary team representative
Drive Team	Up to 4 students who operate the robot at competitions
Pit Crew	Repairs and prepares the robot between matches
Engineering Notebook Lead	Owns the documentation and portfolio submissions

Overview & the org chart

How an FTC team is structured — the full organisational picture from mentor to match-day crew.

An FTC team is not just a group of students who build a robot. It is a fully functioning organisation — with leadership, engineering sub-teams, documentation, outreach, strategy, and competition-day operations. The most successful teams treat every seat as a real job with real accountability. Understanding the structure before the season starts is what separates champion teams from teams that scramble.

◆ The team organisational chart

Lead Mentor / Coach

Adult — guides strategy, culture & compliance

Team Captain

Student — primary decision-maker & ambassador

Co-Captain

Operations & scheduler

Design Lead

Mechanical & CAD

Software Lead

Programming & autonomous

Outreach Lead

Community & awards

Business & Finance Lead

Sponsors, budget & notebook

Drive Team

Driver 1 · Driver 2 · Coach

Design Members

CAD · Fabrication · Assembly

Software Members

TeleOp · Sensors · Vision

Outreach Members

Events · Social · Docs

Finance Members

Grants · Budgeting · Portfolio

◆ Three pillars of an FTC team

Engineering: Designing, building, programming, and iterating on the robot — the hardware and software that plays the game.
Documentation & Outreach: The engineering portfolio, engineering notebook, outreach records, and community engagement that judges evaluate for awards.
Operations & Finance: Team organisation, scheduling, budgeting, sponsor acquisition, grant writing, and competition logistics.

◆ The five lead roles at a glance

Co-Captain: Operations, scheduling, logistics — keeps the team machine running on time
Design Lead: Robot design, CAD, mechanical build and pit crew leadership
Software Lead: All code — autonomous routines, TeleOp, sensors, and vision systems
Outreach Lead: Community events, STEM engagement, social media, and Connect Award documentation
Business & Finance Lead: Sponsors, budget, grants, and engineering notebook / portfolio ownership

★

Cool Name Found principle: Every member of this team owns something. Owning means you know it deeply, you can explain it to anyone, and you are accountable if it is not done. No one is just a "helper." From day one, you have a role title, a responsibility set, and a deliverable. That is how championship teams operate.

Ideal team size

FIRST rules, practical considerations, and the sweet spot for a competitive FTC team.

2–5

members

Too small for a full season without burnout. Each member carries multiple critical roles simultaneously.

Challenging

8–12

members ← sweet spot

Full role coverage without overlap or idle members. Strong enough for robot build, docs, AND outreach simultaneously.

Recommended

13–15

members (FIRST max)

FIRST maximum is 15. Larger teams can dilute ownership. Every member must have a defined role or engagement drops.

Manageable

◆ FIRST official rules on team size

FTC teams may have a maximum of 15 student members
There is no official minimum — but 2 students can register and compete
Adult mentors do not count toward the student member limit
Drive team at competition is capped at 4 members (typically 2 drivers + 1 coach + 1 human player if applicable)
All registered members must be listed on the team roster submitted to FIRST

◆ Why 8–12 is optimal

Enough people to cover all 7+ core roles without doubling up on everything
Small enough that every person knows what everyone else is doing
Redundancy on critical roles (e.g. two people can do CAD if one is absent)
Competition day: full drive team + pit crew + scouting team possible
Award judging: diverse student voices presenting different areas of work

◆ Risks to manage at any size

Too small: Single points of failure — one sick student can derail a critical deliverable
Too large: Passive members who attend but don't contribute — visibly noted by judges
Any size: Undefined roles lead to "someone else will do it" culture
Any size: Without sub-team structure, the captain becomes a bottleneck

◆ Recommended role coverage at team size 10

Role	Primary	Backup	Min Headcount
Team Captain	1	Co-Captain	2
Lead Mentor	1 adult	—	1
Build / Mechanical	2	+1 shared	2–3
Software / Programming	2	+1 shared	2
Electronics / Wiring	1	+1 shared	1–2
Engineering Notebook	1	+1 shared	1–2
Outreach & Connect	1	+1 shared	1–2
Drive Team	2 drivers	1 coach	3

Note: Members can hold multiple roles. "Shared" means a team member carries a secondary responsibility alongside their primary role.

For Cool Name Found in 2026–2027: As a rookie team, starting at 8–10 members gives you full operational coverage while keeping communication tight. Every season, evaluate whether to add members — but always define a role before inviting someone new onto the roster.

Leadership roles

The captain, co-captain, and mentor — the three people who set the culture and direction of the entire team.

🌟

Team Captain

Primary student leader · Team ambassador · Decision-maker

Core Role

The Team Captain is the central figure of the team — the student who owns the team's direction, culture, and performance holistically. In judging rooms, the Captain speaks first and sets the tone. On build days, the Captain makes decisions when the team is stuck. In competition, the Captain is the bridge between the mentor and the students. This is not a popularity title — it is a job that demands preparation, communication, and sacrifice.

Core responsibilities

Run weekly team meetings — set agenda, track action items
Be the primary voice in all judging interviews and presentations
Maintain awareness of all sub-teams' progress and blockers
Represent the team at alliance selection and competition events
Approve major engineering and strategic decisions with the mentor
Draft and review the team's seasonal goals and milestones
Coordinate with outreach lead on STEM ambassador activities

What judges expect from the captain

Can articulate the team's mission, values, and season goals fluently
Knows every sub-team's work — not just their own area
Can explain engineering decisions without being an engineer themselves
Demonstrates Gracious Professionalism in every interaction
Shows evidence of leadership through team documentation
Handles follow-up questions calmly and accurately

📊

Co-Captain / Operations Lead

Backup leader · Scheduler · Internal coordinator

Core Role

The Co-Captain ensures the team machine runs on time and on schedule. While the Captain focuses externally (judging, alliances, presentations), the Co-Captain manages internally — tracking deliverables, running logistics, managing the team calendar, and covering for the Captain when needed. In a 10-person team, this role prevents the Captain from becoming overwhelmed and provides genuine redundancy at the leadership layer.

Core responsibilities

Maintain the team's master calendar — meetings, build days, deadlines, competitions
Track task completion across sub-teams and escalate blockers
Coordinate travel, logistics, and competition registrations
Facilitate team retrospectives and post-competition debriefs
Step into the Captain role seamlessly if the Captain is absent
Manage team communications (internal group chats, meeting notes)

What makes a great Co-Captain

Organisationally rigorous — nothing falls through the cracks on their watch
Strong communicator across sub-teams — bridges silos
Comfortable giving and receiving feedback constructively
Knows when to escalate to the mentor vs. handle independently
Contributes to the portfolio with meeting minutes and planning docs

🌟

Lead Mentor / Coach

Adult guide · Strategic advisor · Gracious Professionalism model

Adult Role

The Lead Mentor is the most important adult on the team. FIRST's philosophy is clear: mentors guide, students do. A great mentor does not build the robot, write the code, or fill in the notebook — they ask the right questions, push the team to think deeper, and create the conditions where students can succeed independently. At competitions, the mentor is in the pit but not on the field. They advise strategy; students execute it.

Core responsibilities

Ensure the team follows FIRST rules, FTC game manual, and safety guidelines
Guide the team's engineering process — question assumptions, not dictate answers
Review and advise on the engineering portfolio — not write it
Mentor students in specific technical domains (programming, CAD, etc.)
Facilitate conflict resolution and team culture challenges
Manage relationships with school/org administration, sponsors, parents
Eligible for the Compass Award — nominated by the team's students

What Gracious Professionalism looks like from a mentor

Celebrates other teams' innovations genuinely
Allows students to make (and learn from) mistakes
Models respectful disagreement and collaborative problem-solving
Never coaches from the sidelines during matches — that is the drive team's job
Treats referees, judges, and volunteers with visible respect at all times
Frames every failure as engineering data, not personal shortcoming

A common rookie mistake: Letting the mentor do too much. Judges know immediately when they are looking at adult-produced work. The engineering portfolio, robot design decisions, and judging presentations must be genuinely student-owned. A mentor who builds the robot for the team is not helping — they are disqualifying the team's award chances and violating FIRST's core mission.

Build & hardware roles

The people who design, fabricate, assemble, and iterate on the physical robot.

🛠

Mechanical / Build Lead

Hardware sub-team lead · CAD owner · Fabrication supervisor

Core Role

The Mechanical Lead owns everything that is physically part of the robot — from the chassis geometry to the end-effector tolerances. They coordinate CAD design (typically in Onshape or SolidWorks), oversee fabrication and assembly, and manage the iterative build process. At competition, they lead the pit crew and make real-time repair decisions. This role requires the most technical depth in hardware and the most organised thinking about physical systems.

Core responsibilities

Lead the robot design process from concept to CAD to physical prototype
Own the CAD model — keep it updated as the robot evolves
Manage the build schedule and assign fabrication tasks to team members
Maintain the parts inventory and identify procurement needs early
Coordinate with software lead on motor placement, sensor mounts, and cable routing
Lead competition pit crew — triage issues, prioritise fixes between matches
Document design iterations in the engineering notebook

Skills expected & to be developed

CAD — Onshape (preferred for FTC) or SolidWorks fundamentals
Metric and imperial measurement, tolerancing, and fit/clearance
FTC legal materials — REV, goBILDA, Tetrix, custom aluminium
Power transmission — chain/belt/gear ratios and their trade-offs
Structural analysis — moment loads on arms, joint stress, deflection
Safe use of hand tools, drill press, band saw, and 3D printer

🔧

Build Member (×1–2)

Fabricator · Assembler · Iteration support

Core Role

Build members execute the physical construction of the robot under the direction of the Mechanical Lead. In a 10-person team, 2–3 students total (including the lead) should be consistently engaged in the build sub-team. Build members are not passive assistants — they are expected to understand the design intent, propose improvements, and execute with precision. Every build member should be developing toward being capable of designing independently by mid-season.

Expected contributions

Fabricate components to spec — cut, drill, tap, assemble accurately
Follow CAD models and engineering sketches during build
Identify and flag tolerance/fit issues before they become match-day problems
Participate in design reviews — build members who have cut metal know where designs fail
Maintain the build workspace — cleanliness prevents part loss and injury
Document build sessions in the engineering notebook with photos

Growth path for build members

Semester 1: Learn tools, follow drawings, ask questions about every design decision
Semester 2: Begin generating design alternatives and presenting them to the lead
Year 2: Take on sub-assembly ownership (e.g. "you own the intake mechanism")
Year 3+: Ready to step into the Mechanical Lead role

⚡

Electronics / Wiring Lead

Electrical systems · Control Hub · Power distribution

Core Role

The Electronics Lead owns the robot's electrical architecture — from the battery and main power switch to the REV Control Hub, motor controllers, servo controllers, sensors, and all wiring. In FTC, electronics failures are the most common cause of match losses. A well-wired robot with properly crimped connectors, colour-coded cables, and strain-relieved joints is a robot that competes reliably. This role demands both technical knowledge and obsessive attention to detail.

Core responsibilities

Design and implement the robot's wiring diagram before building begins
Install and configure REV Control Hub, Expansion Hub, and all peripherals
Crimp, label, and route all cables — Anderson Powerpole, JST, XT30, servo connectors
Configure motor ports, servo ports, and I2C device addresses in the Control Hub
Troubleshoot electrical faults — voltage drops, disconnections, EMI issues
Maintain a spare parts kit for competition (connectors, fuses, zip ties)

Technical knowledge areas

REV Robotics ecosystem — Control Hub, Expansion Hub, Driver Hub
FTC legal motors: REV HD Hex, Core Hex, goBILDA Yellow Jacket series
FTC legal servos: REV Smart Robot Servo, Axon MAX, goBILDA servos
Sensor types — encoders (quadrature), IMU (BHI260AP), colour, distance (TOF), webcam
Power budget — total current draw vs. 12V battery output
Limelight 3A integration — PoE, Ethernet to Control Hub via USB adapter

★

Competition-day reality: The pit is where hardware roles earn their reputation. Between matches you may have as little as 8 minutes to diagnose a problem, fix it, and be re-inspected. The Mechanical Lead and Electronics Lead must be able to execute a pre-match inspection checklist from memory, identify the 5 most likely failure points on their robot, and communicate fixes to the drive team and coach clearly under pressure. Practice this. Do not improvise it at your first qualifier.

Software & electronics roles

Programming, autonomous control, sensor integration, and the software that wins matches.

💻

Software Lead / Programmer

Java · FTC SDK · Autonomous · Control loops

Core Role

The Software Lead writes, reviews, tests, and iterates on all code that runs on the robot. In FTC, code runs on the REV Control Hub via the FTC Robot Controller app, written in Java using the FTC SDK. The quality of the autonomous program — how reliably, how accurately, and how quickly the robot scores in the 30-second autonomous period — is the single biggest software-driven competitive differentiator. Strong autonomous routines are worth 20–40+ points that are simply unavailable to teams with weak software.

Core responsibilities

Develop and maintain all OpModes — TeleOp and Autonomous
Implement and tune PID control loops for motors and servos
Integrate all sensors into the codebase — IMU, encoders, webcam, TOF
Implement and tune odometry for autonomous positioning accuracy
Develop path-following for autonomous navigation (RoadRunner, Pedro Pathing, or custom)
Integrate Limelight 3A vision processing for AprilTag or TFOD detection
Write unit-testable, documented, version-controlled code (Git/GitHub)
Document all software architecture in the engineering portfolio

Technical knowledge areas

Java fundamentals — OOP, inheritance, interfaces, generics
FTC SDK — HardwareMap, LinearOpMode, iterative OpMode patterns
Finite State Machines (FSMs) for autonomous and TeleOp coordination
PID tuning — Kp, Ki, Kd and their effects on motor response
Dead-reckoning odometry — 2-wheel + IMU, 3-wheel passive configurations
SE(2) pose math — translation and rotation in 2D for localisation
Computer vision — Limelight 3A, AprilTags, TensorFlow Object Detection
Git workflows — branching, pull requests, version control hygiene

🔓

Software Member (×1)

Driver assist · TeleOp tuning · Code testing partner

Support Role

A second software team member is invaluable for code review, testing, and debugging. While the Software Lead handles core autonomous development, the second programmer focuses on TeleOp enhancement, driver feedback integration, and test harnesses. On competition day, having a second programmer means there is someone who can pull up code, read through it, and push a fix without a single point of failure on the software sub-team.

Expected contributions

Build and maintain TeleOp enhancements — macros, pre-set arm positions, state toggles
Write test routines to validate hardware changes without full match simulation
Perform code reviews — catch logic errors, redundant code, naming inconsistencies
Document software decisions in the engineering notebook with pseudocode and flowcharts
Act as the driver during software testing — report feel and behaviour accurately

Path to becoming Software Lead

Understand and be able to explain every OpMode in the repository
Independently implement a new sensor integration from scratch
Successfully tune a PID loop on a mechanism from zero
Complete at least one autonomous path contribution before state championship

◆ Workload distribution across the season

Software Lead

95%

Mechanical Lead

90%

Electronics Lead

80%

Team Captain

85%

Notebook Lead

85%

Build Member (×2)

75%

Outreach Lead

70%

Co-Captain

80%

Workload intensity is highest Sept–Feb (build and competition season). All roles spike at qualifiers and state. Software and Mechanical leads carry the heaviest sustained loads of any student role.

Software is the multiplier for hardware. A robot with an 80% build quality and excellent software will beat a robot with 100% build quality and poor software in almost every match. Every hour spent tuning autonomous is an hour that pays dividends for the entire season — including in award judging, where the Control Award evaluates software excellence directly.

Outreach, documentation & strategy roles

The roles that win awards, document the season, and shape competition strategy.

📖

Engineering Notebook Lead

Portfolio owner · Documentation architect · Award anchor

Core Role

The Engineering Notebook Lead is responsible for the single most important document a team produces — the engineering portfolio that judges use to evaluate the Think Award, the Innovate Award, the Connect Award, and ultimately the Inspire Award. This is not a secretary role. The Notebook Lead is an active engineering thinker who understands the design process deeply enough to document it accurately, compellingly, and in the format judges expect. Teams that win at Worlds typically have a notebook lead who treats this role as their primary engineering contribution to the season.

Core responsibilities

Establish and maintain the engineering portfolio structure from day one of the season
Document every design decision with problem → analysis → solution → test format
Capture photos, data tables, and diagrams from build and test sessions
Write team meeting minutes and embed them in the portfolio
Ensure all outreach events are documented with dates, photos, and impact data
Submit all required documentation to FIRST before competition deadlines
Prepare the 5-minute engineering portfolio pitch for judge presentations
Track judge feedback from each event and improve the portfolio in response

What a world-class portfolio looks like

Clear table of contents with numbered pages and dated entries
Every mechanism has: original problem statement, sketches/CAD, alternatives considered, final choice rationale, and test results
Software architecture section — flowcharts, pseudocode, autonomous path diagrams
Outreach section — events list, people reached, photos, testimonials, sponsor letters
Team structure section — roles, bios, contributions per member
Business plan / sustainability section
Professional layout — consistent font, colour scheme, logo, page headers

🌐

Outreach & Connect Lead

Community builder · Sponsor manager · STEM ambassador

Core Role

The Outreach Lead owns the team's relationship with the world beyond the competition field. They plan and execute STEM outreach events, manage sponsor relationships, maintain social media presence, and create the documentation that supports the Connect Award. Cool Name Found's 2026 World Championship Connect Award win is direct evidence that this role, done excellently, produces top-tier recognition at the highest level of the sport.

Core responsibilities

Plan a minimum of 4–6 community outreach events per season
Recruit and manage relationships with STEM professionals and sponsors
Run the team's social media accounts (Instagram, website, etc.)
Maintain the outreach tracker — dates, attendees, hours, impact metrics
Develop the Connect Award portfolio section with the Notebook Lead
Coordinate the Forge Ally / inclusive STEM initiative documentation for the team
Prepare talking points for outreach questions in judging sessions

What excellent outreach looks like

Consistent year-round engagement — not a last-minute pre-competition flurry
Events that target under-served or underrepresented STEM communities
Real relationships with professionals who can speak to the team's impact
Quantified impact — how many students did you introduce to STEM this season?
A documented "sustainability plan" — what happens to this outreach without us?

🎯

Scouting & Strategy Lead

Match analyst · Alliance selection advisor · Competitive intelligence

Optional but Impactful

At larger competitions and at state level, the difference between winning and losing alliances is often determined by the quality of alliance selection decisions. The Scouting Lead watches opposing teams' matches, records performance data, and prepares recommendations for the Team Captain ahead of alliance selection. On a rookie team, this role can be combined with the Co-Captain role in the early season, but as the team grows toward state-level competition, dedicated scouting becomes important.

Core responsibilities

Design a scouting form — scoring categories, reliability ratings, autonomous notes
Watch and record data on all other teams during qualification matches
Summarise findings for the Captain before alliance selection
Identify teams with complementary strengths to your own robot
Advise on match strategy when playing as an alliance

Drive Team roles (match day)

Driver 1: Primary robot operator — typically controls drivetrain and main scoring mechanism
Driver 2: Secondary operator — controls ancillary mechanisms, end game, and assists
Coach: Observes field and communicates strategy to drivers; cannot touch controller
Maximum 4 members on field — 3 drive team + 1 human player (game-dependent)

◆ Full season contribution matrix — who owns what

Area of work	Captain	Co-Capt	Mech Lead	Software Lead	Electronics	Notebook Lead	Outreach Lead
Robot design decisions
CAD modelling
Programming / autonomous
Wiring & electronics
Engineering portfolio
Outreach events & docs
Judging presentation
Alliance selection / strategy
Pit crew / match repairs
Sponsor relationships

Primary owner

Active contributor

Minimal / none

◆ What is expected from every team member — by season phase

Phase 1 — Kickoff & Build (Sept–Nov)

Attend every build session unless formally excused
Complete assigned tasks before the next meeting
Document your work in the notebook within 48 hours of doing it
Ask questions — but research first, then ask
Actively participate in design reviews and strategy sessions

Phase 2 — Qualifier season (Nov–Dec)

Know your role at competition day and execute it without reminders
Support other sub-teams in the pit between matches
Be ready to speak about your contribution to any judge at any time
Analyse match video and propose specific improvements
Treat every alliance partner and opponent with Gracious Professionalism

Phase 3 — State Championship (Jan–Feb)

Portfolio is polished and practised — every member knows the pitch
Robot is in its most reliable, tested state of the season
Drive team has completed ≥20 full practice runs on autonomous
Every member can answer judge questions about the full team's work
Arrive ready to compete for every award, not just field performance

Year-round responsibilities

Represent the team professionally at all public and outreach events
Use social media to amplify team activities — no private venting
Support recruitment of new members for next season
Maintain your role documentation in the engineering portfolio
Show up, communicate, and follow through every single time

★

The outreach win at Worlds 2026 was not an accident. Cool Name Found won the Connect Award at the World Championship because the team had spent the entire season building genuine relationships, documenting real impact, and preparing a compelling story that judges from around the world found credible and inspiring. That is the product of a dedicated Outreach Lead, a meticulous Notebook Lead, and a Captain who understood that the award season is never separate from the build season — they run in parallel from day one.

What is COTS? — Commercial Off-The-Shelf

Understanding the vendor ecosystem, procurement strategy, and how COTS parts define the modern FTC robot.

Primary COTS vendors

M3–M5

Core fastener sizes

12V

FTC max battery voltage

Total motor ports (dual hub)

◆ What does COTS mean?

COTS stands for Commercial Off-The-Shelf — pre-manufactured components purchased from vendors and used directly on the robot, as opposed to custom-fabricated or machined parts. In FTC, the vast majority of a competitive robot is built from COTS parts: aluminium extrusion channel, gearbox motors, high-torque servos, control electronics, and standardised fasteners. Understanding which vendor sells what — and which parts are the best choice for a given task — is one of the most critical skills a build student can develop.

◆ Why COTS over custom fabrication?

Speed — order today, build tomorrow; no machine shop time
Reliability — vendor-tested tolerances and known failure modes
Interoperability — standardised hole patterns and shaft sizes across vendors
Cost — amortised tooling over thousands of units keeps per-part cost low
Documentation — datasheets, CAD files, and community support exist
Replaceability — if a part breaks at competition, another team may have a spare

◆ FTC COTS Vendor Map

goBILDA — Structure, motors, servos, hardware, batteries
REV Robotics — Control Hub, Expansion Hub, Driver Hub, electronics, batteries
Axon Robotics — High-precision smart servos with AUX position feedback
Swyft Robotics — Compact, competition-optimised performance servos
McMaster-Carr — All fasteners: bolts, nuts, standoffs, bearings, shafting
Home Depot — General supplies, tools, consumables, shop materials

◆ FTC Legal COTS Rules (at a glance)

The FTC Game Manual Part 1 governs what COTS parts are legal. Key rules: all motors must appear on the FTC legal motors list (goBILDA Yellow Jacket motors are legal); servos must be standard RC-type or meet specific FTC servo rules; the control system must use REV Control Hub or Expansion Hub; batteries must be within the approved list; and all electronics must be properly fused and protected. Always cross-reference your parts against the current season's legal parts list before ordering.

Procurement Strategy: Build your robot's Bill of Materials (BOM) before ordering. Group parts by vendor to minimise shipping costs. Order critical mechanical parts — channels, motors, hubs — at least 2–3 weeks before you need them. For servos and electronics, keep spares; they fail at the worst moments. McMaster-Carr ships same-day for most in-stock fasteners — use them as your fastener backbone.

★

Mentor insight: Build a shared Google Sheet BOM with columns: Part Name · Vendor · Part Number · Qty · Unit Price · Total · Status · Link. Update it every time something is ordered. By competition season you will have spent hundreds of dollars — the BOM tells you exactly what is on the robot and what it cost. Judges often ask about cost-awareness in engineering interviews.

goBILDA — Structure, Motors, Servos & Hardware

The primary structural and mechanical vendor for FTC. Aluminium channel, Yellow Jacket motors, servos, and a complete hardware ecosystem.

■

Structural Channel & Extrusion

The backbone of every goBILDA robot — 6061-T6 anodised aluminium

Structure

goBILDA's 1120 Series U-Channel is the gold standard for FTC robot structure. It uses a metric M4 hole pattern on 8mm centres, providing dense, predictable mounting points along its entire length. All channels are anodised 6061-T6 aluminium — lightweight (2.70 g/cm³), rigid, and easy to cut to length with a hacksaw or band saw. The consistent hole pattern means any bracket, motor mount, or accessory designed for goBILDA channel will fit anywhere on the frame.

Key Channel Series

1120 Series U-Channel — most common; 48mm wide, lengths 48–720mm; primary frame members, arms, slide carriages
1121 Series Low-Side U-Channel — shallow variant; fits tight spaces; secondary supports
1122 Series Flat Beam — single-face flat plate; brackets, gussets, custom mounting plates
1150 Series Square Tube — smooth interior for linear slide rails; glide carriages
1152 Series C-Channel — very rigid; ideal for cantilevered horizontal members
GoRAIL T-Slot Extrusion — T-slot aluminium; compatible with standard T-nut accessories and adjustable mounting

Pattern, Compatibility & CAD

All 1120 series: M4 × 0.7mm threaded holes on 8mm grid
Compatible with all goBILDA M4 standoffs, brackets, and hardware out of the box
Interoperable with REV 15mm extrusion via goBILDA-to-REV pattern adapters
Linear slides: 1150 square tube as outer rail with delrin HDPE sliders inside
CAD: downloadable from gobilda.com in STEP/STP and native Onshape format for every part
Material: 6061-T6 aluminium; density 2.70 g/cm³; yield strength 276 MPa

Brackets, Mounts & Accessories

goBILDA sells an extensive line of right-angle brackets, face-mount brackets, clamping hubs, pattern adapters, and shaft mounts — all in the M4 system. Key items: 1120 Series Flat Beam brackets for perpendicular channel connections; 1502 Series Clamping Hubs for attaching wheels and sprockets to 6mm D-shafts; 1200 Series Spacers and Standoffs in M4 for panel separation; and pattern plates for custom geometry transitions. Before fabricating anything custom, check if goBILDA sells it — they usually do.

⚡

Yellow Jacket Planetary Gear Motors

FTC-legal 12V DC gearmotors — the industry standard for FTC drive and mechanism motors

Motors

The goBILDA Yellow Jacket Planetary Gear Motor series is the most widely used motor in FTC. These are 12V brushed DC motors with integrated planetary gearboxes, available in a wide range of gear ratios. They feature a 6mm D-shaft output and a standardised 16mm × 16mm face mount, making them interchangeable across gear ratios with zero mechanical redesign. All Yellow Jacket motors are on the FTC legal motors list. Each motor includes an integrated quadrature encoder for closed-loop speed and position control.

Gear Ratio Options & Output Speed

3.7:1 → 1620 RPM — max speed; flywheels, fast rollers; minimal torque
5.2:1 → 1150 RPM — high speed; fast intake rollers
13.7:1 → 435 RPM — balanced; very popular all-purpose motor; mecanum drive
19.2:1 → 312 RPM — moderate torque; mecanum drive, extension slides
26.9:1 → 223 RPM — higher torque; intake, lift mechanisms
50.9:1 → 117 RPM — high torque; heavy lifts, viperslides, climbing systems
99.5:1 → 60 RPM — very high torque; winches, balancing arms
188:1 → 30 RPM — maximum torque; extremely heavy loads only

Technical Specifications

Nominal voltage: 12V DC
No-load current: ~0.2A; stall current: ~9.2A
Integrated encoder: 28 counts/rev at motor shaft (pre-gearbox)
Effective CPR at output: 28 × gear ratio (e.g. 435 CPR for 19.2:1 after 4× quadrature)
Output shaft: 6mm D-shaft — pairs with 1310 series clamping hubs
Face mount: 16mm × 16mm M3 bolt pattern
Connector: JST-VH 2-pin motor power + 4-pin JST-PH encoder
Operating temperature: −20°C to +50°C
Weight: ~90g depending on ratio

Choosing the Right Gear Ratio

Rule of thumb: higher ratio = more torque, less speed. For a 4-motor mecanum drivetrain: 312–435 RPM (13.7:1 or 19.2:1). For linear slide intake: 117 RPM (50.9:1). For viperslide extension: 223–312 RPM. For high-speed intake roller: 1620 RPM (3.7:1). Always calculate your theoretical free speed and stall torque requirements before selecting. goBILDA provides torque curves and stall torque data on every motor's product page.

⚙

goBILDA Servos

Torque servos, speed servos, and 5-turn multi-rotation variants

Servos

goBILDA sells a range of standard-size and micro servos for FTC use. While Axon and Swyft are often preferred for precision mechanisms, goBILDA servos offer a reliable, cost-effective option particularly for claws, intake flaps, latching mechanisms, and low-torque deployments. All use standard 3-pin PWM interface and 25-tooth spline horns.

Key goBILDA Servo Models

2000 Series (Speed Servo) — 0.09 sec/60° · 2.5 kg·cm · lightweight intake hinges
2100 Series (Torque Servo) — 0.18 sec/60° · 13.5 kg·cm · arms and grabbers
2200 Series (Super Torque) — 0.23 sec/60° · 25.0 kg·cm · heavy-load mechanisms
5-Turn Servo (2401) — 1800° rotation range · use as continuous rotation servo for linear actuators
Dual-Mode Servo — switchable between standard and continuous rotation via programming

Servo Interface & Wiring

Signal: standard 50Hz PWM, 500–2500µs pulse width
Connector: JR/Futaba-compatible 3-pin (signal, power, ground)
Operating voltage: 4.8–6.0V (powered by REV servo port or Servo Power Module)
Spline: 25-tooth — compatible with all goBILDA and REV servo horns
All servos include multiple horn styles and mounting hardware in the box

🔋

goBILDA Batteries & Power Hardware

FTC-legal 12V NiMH match batteries and XT30 power connectors

Power

goBILDA supplies FTC-legal 12V NiMH batteries for robot power. These connect to the REV Control Hub via XT30 connector. Having at least two batteries is required at competition — one on the robot, one on the charger in the pit.

Battery Specifications

Chemistry: Nickel Metal Hydride (NiMH)
Nominal voltage: 12V (10 cells × 1.2V per cell)
Capacity: 3000 mAh
Peak current: 20A continuous; 40A brief surge
Connector: XT30 plug
Dimensions: 136 × 46 × 24mm; Weight: ~465g
Charge time: ~90 min at 2A on a NiMH smart charger

Battery Best Practices

Charge the night before; top up morning of competition
Never deep-discharge NiMH — stop use when voltage drops below 10V under load
Rotate and label batteries: track charge cycles per unit
Storage: 40–60% charge in a cool, dry location
Inspect XT30 connector before each match — loose connectors cause voltage brownouts
Always carry a spare charged battery to competition — battery failure ends the match

★

Ordering tip: goBILDA offers a FTC Team Discount — register with your team number on their website. Always order channel in at least 2× your needed length to allow for mis-cuts. Add 10% margin on all fastener quantities. Download the goBILDA Onshape library to your team's workspace — it has CAD for every part and saves hours of modelling time. Keep the goBILDA Mechanical Design Guide bookmarked; it is one of the best practical FTC build references available for free.

REV Robotics — Control System, Electronics & Batteries

The mandated FTC control system supplier. Every legally operated FTC robot uses REV electronics at its core.

💻

REV Control Hub (REV-31-1595)

The brain of the FTC robot — Android-based autonomous and TeleOp controller

Control System

The REV Control Hub is a combined Android computer and motor/servo controller in a single enclosure. It runs the FTC Robot Controller application and communicates wirelessly with the Driver Hub via Wi-Fi Direct. It is the central node of every FTC robot's electronics system — all motors, servos, sensors, and I²C devices connect to it or the paired Expansion Hub.

Hardware Specifications

Processor: Qualcomm Snapdragon 210, quad-core 1.1GHz
RAM: 1GB; Storage: 8GB eMMC
OS: Android 8.1 (Oreo)
Motor ports: 4 × DC motor ports (Anderson Powerpole connectors)
Servo ports: 6 × servo/PWM ports
I²C buses: 4 × I²C ports
Digital I/O: 8 × digital pins (limit switches, magnetic encoders)
Analog input: 4 × analog ports (0–3.3V)
USB: 1 × USB 2.0 Type-A (webcam or USB devices)
IMU: BNO055 9-axis IMU + BHI260AP secondary IMU (newer revisions)

Power & Connectivity

Input power: 12V NiMH battery via XT30
5V regulated: available on servo bus
12V pass-through: to REV Expansion Hub via RS485 + power cable
Wi-Fi Direct: 2.4GHz / 5GHz; robot creates its own Wi-Fi network
Ethernet: RJ45 port for wired configuration and updates
Status LEDs: indicate power state, connectivity, and fault conditions
Mounting: 32mm × 32mm M3 hole pattern (standard FTC mount)
Dimensions: ~190 × 95 × 50mm; Weight: ~325g

Programming Interface

The Control Hub runs the FTC SDK, available on GitHub (github.com/FIRST-Tech-Challenge/FtcRobotController). Code is written in Java via Android Studio or the OnBot Java browser IDE. The SDK provides classes for all hardware: DcMotor, Servo, IMU, I2cDevice. Configuration is done in the Robot Controller app — every hardware device must be named and mapped in a hardware config file before it can be used in code.

➕

REV Expansion Hub (REV-31-1153)

Additional motor, servo, and sensor ports via RS485 daisy-chain

Control System

The REV Expansion Hub adds 4 more motor ports + 6 more servo ports + full sensor capability to the system. It connects to the Control Hub via a 2-wire RS485 serial cable. Most competitive robots use both a Control Hub and an Expansion Hub — providing 8 total motor ports and 12 total servo ports.

Expansion Hub Specifications

Motor ports: 4 × DC motor ports (Anderson Powerpole)
Servo ports: 6 × servo/PWM outputs
I²C: 4 × I²C buses
Digital I/O: 8 × digital pins
Analog: 4 × analog inputs (0–3.3V)
RS485 connection: 2-wire serial to Control Hub (included cable)
Address: configurable 0 or 1 — must be unique on the RS485 bus
Power input: separate 12V XT30 — can run from dedicated battery

Why you need an Expansion Hub

4 drive motors + 1–2 slide motors + 1–2 intake motors = 7–8 total motors needed
6 servo channels on Control Hub + 6 on Expansion Hub = 12 total
Separate power input allows load splitting across two batteries
SDK treats all motor ports identically regardless of which hub they're on
REV recommends keeping drivetrain motors on Control Hub for minimal network latency
RS485 cable should be kept under 1m for maximum reliability

🎮

REV Driver Hub (REV-31-1596)

The operator-side Android device — Driver Station for TeleOp and Autonomous

Control System

The REV Driver Hub is the Driver Station device carried by the drive team during a match. It connects to the Robot Controller (Control Hub) over Wi-Fi Direct and runs the FTC Driver Station application. Two gamepads plug into its USB ports to control the robot during TeleOp.

Hardware Specifications

Processor: MediaTek Helio A22, quad-core 2.0GHz
RAM: 3GB; Storage: 32GB
OS: Android 11
Display: 7" HD touchscreen, 1280×800
USB: 2 × USB 2.0 Type-A for gamepads
Wi-Fi: 2.4GHz / 5GHz — connects to Control Hub's Wi-Fi Direct network
Battery: 3500mAh Li-ion internal; charges via USB-C
Compatible gamepads: Logitech F310, PS4 DualShock, Xbox controllers (all FTC legal)

Driver Hub Best Practices

Charge fully overnight; charge via USB-C before every event
Use airplane mode with Wi-Fi manually enabled — eliminates cellular interference
Pair gamepads before entering the driver station queue at events
Set a fixed RC Wi-Fi channel in DS settings — prevents channel hopping interference
Keep Driver Station app version in sync with Robot Controller app — mismatch causes connection failure
Carry a USB-C cable to competition — emergency charges save matches

🔋

REV Slim Battery (REV-31-1302) & Power Accessories

High-capacity 12V NiMH and essential power distribution modules

Power

REV's REV Slim Battery has a higher capacity (5000mAh vs 3000mAh) than most alternatives and mounts flush against the robot frame using the 15mm extrusion system's mounting slots. It is the preferred battery for teams wanting maximum match endurance.

REV Slim Battery Specs

Chemistry: NiMH (Nickel-Metal Hydride)
Nominal voltage: 12V (10 cells)
Capacity: 5000 mAh
Peak discharge: 20A continuous
Connector: XT30
Dimensions: 183 × 46 × 25mm; Weight: ~700g
Flat form factor — mounts along robot frame edge

REV Power Accessories

REV Servo Power Module — boosts servo bus to 6V; eliminates brownouts on high-torque servos
REV Servo Hub — 6-channel servo expander with dedicated 6V regulated rail
REV Ultra Planetary Gearbox — modular planetary gearbox for custom motor setups
REV 15mm Aluminium Extrusion — structural channel for REV-compatible builds with HDPE sliders
RS485 Cable — daisy-chain from Control Hub to Expansion Hub; keep under 1m

★

Critical setup: Before every competition, update both Control Hub and Driver Hub firmware and FTC app to the same SDK version. Mismatched versions are the #1 cause of communication failures at events. REV provides an update guide on docs.revrobotics.com. Name your robot's Wi-Fi network something unique — at a competition with 40+ robots, connecting to the wrong Control Hub is a real risk. Use your team number in the SSID.

Axon Robotics — Precision Smart Servos

The premier choice for high-precision, feedback-enabled servos in FTC. Used in intake wrists, turret systems, and any mechanism requiring exact positioning with closed-loop verification.

⚙

Axon MAX+ & Axon MINI+

Smart servos with 12-bit magnetic absolute position feedback

Servos — Smart

Axon servos are "smart servos" — they include an onboard magnetic encoder that reports real-time absolute position back to the Control Hub via an auxiliary analog feedback wire. This allows software to read the servo's actual position rather than trusting the commanded position, enabling closed-loop servo control that is significantly more robust than standard servos — especially for autonomous routines.

Axon MAX+ Specifications

Torque: 35 kg·cm @ 6V
Speed: 0.13 sec/60° @ 6V
Operating voltage: 4.8–8.4V (use REV Servo Power Module for 6V)
Feedback: 12-bit magnetic encoder AUX analog line (~0.088° resolution)
Rotation range: 270° configurable
Gear material: all-metal steel + aluminium; competition-grade durability
Case: CNC aluminium housing
Spline: 25-tooth Futaba-compatible
Weight: ~68g

Axon MINI+ Specifications

Torque: 14 kg·cm @ 6V — compact form factor
Speed: 0.09 sec/60° @ 6V — very fast for its torque rating
Operating voltage: 4.8–6.0V
Feedback: same 12-bit magnetic AUX line as MAX+
Form factor: standard mini-servo envelope — fits tight spaces
Use cases: wrist joints, intake fingers, light-duty pivots
Gear material: titanium gears — exceptional strength-to-weight ratio
Weight: ~38g

AUX Feedback — How It Works in Code

AUX wire connects to an analog input port on the Control Hub
Output: 0–3.3V proportional to servo angle (0V = 0°, 3.3V = 270°)
Read via analogInput.getVoltage() in FTC SDK
Convert to degrees: angle = (voltage / 3.3) * 270
Enables position verification, closed-loop feedback, and stall detection
Critical for autonomous: verify wrist is in correct state before next action

When to Use Axon vs Standard Servos

Use Axon: intake wrists, scoring arms, turret rotation — anywhere exact position matters
Use Axon: autonomous routines needing position confirmation
Use standard servo: simple claws, one-position latches, flag/panel deployments
Axon servos cost ~$60–90 each; budget accordingly and prioritise critical joints
Requires REV Servo Power Module for 6V operation — budget ~$30 per robot
Free Axon Servo Programmer tool (USB device) for configuring travel limits

★

Build tip: goBILDA sells Axon-compatible servo brackets — pattern plates designed specifically for the MINI+ and MAX+ case geometry. Use these instead of custom brackets. Always read the AUX feedback in your OpMode's init() loop to confirm the servo is in its expected starting position before autonomous begins. A wrist that is 10° off at match start will be 10° off on every scoring attempt.

Swyft Robotics — Competition Performance Servos

Compact, high-performance servos engineered for the demands of competitive FTC seasons — speed-optimised with robust metal gearing.

⚡

Swyft Servo Series

High torque density, speed-optimised servos for FTC TeleOp mechanisms

Servos — Performance

Swyft servos are designed by FTC competitors for FTC competitors. They focus on delivering maximum torque per gram in a compact, reliable package. Swyft's design philosophy prioritises field reliability — the servos are built to survive repeated impact and shock loading typical of a full FTC competition season without gear failure. All-metal gear trains throughout.

Swyft Servo Key Characteristics

High torque output optimised for FTC operating voltages (4.8–6.0V)
Full metal gear train — no plastic gear failure under impact or shock loading
Compact form factor within standard servo envelope
Standard 25-tooth spline — compatible with goBILDA and REV servo horns
Standard 3-pin PWM signal — plug-and-play with Control Hub servo ports
Configurable in standard range (180°) and extended range (270°+) modes
Designed for high-cycle-count applications — thousands of actuations per season

Typical Use Cases

Intake wrist mechanisms requiring fast, repeatable motion cycles
Claw open/close where speed of cycle directly impacts TeleOp efficiency
Deployment mechanisms — field elements, arm initial deploy sequences
Linkage-driven mechanisms undergoing oscillating load profiles
Applications where Axon's AUX feedback is not required
Budget-conscious builds prioritising reliability over precision feedback

Swyft vs Axon — Complete Comparison

Both Swyft and Axon produce high-quality FTC competition servos. The key differentiator: Axon servos offer 12-bit absolute position feedback (AUX line) for closed-loop control; Swyft servos are open-loop but often faster to integrate and optimised for cycle speed. For mechanisms requiring precise autonomous positioning with real-time verification, Axon is the clear choice. For high-speed TeleOp mechanisms where cycle time is the priority, Swyft is excellent. Many top teams run both: Axon on precision joints (wrist, arm), Swyft on high-cycle actuators (claw, intake).

◆ Full Servo Comparison Matrix

goBILDA 2000 (Speed): 2.5 kg·cm · fast · budget · no feedback
goBILDA 2200 (Super Torque): 25 kg·cm · reliable · no feedback
Axon MINI+: 14 kg·cm · compact · 12-bit AUX feedback
Axon MAX+: 35 kg·cm · high torque · 12-bit AUX feedback
Swyft Series: high torque density · speed-optimised · metal gears · no feedback
Rule of thumb: Axon for precision/autonomous, Swyft for speed/reliability

◆ Servo Wiring Best Practices

Connect signal (white/yellow) to pin 1 on REV servo port — correct polarity matters
Use 6V via REV Servo Power Module for maximum torque from all high-performance servos
Secure cables with zip ties every 50mm — servo cables snag in mechanisms
Strain-relieve the connector at the servo body — plug movement causes intermittent signal loss
Label servo ports in hardware config to match physical robot locations
Keep servo cable runs short — long cables pick up motor PWM electrical noise

★

Competition-day insight: Carry 2× spare servos of each type used on your robot to every event. Servo failures — from impact, over-torque, or connector fatigue — are among the most common hardware issues at competition. A spare servo swapped in 5 minutes during a pit stop can save your match schedule. Pre-label spare servos with their configured PWM range so you don't have to re-tune under pressure in the pit.

McMaster-Carr — Fasteners, Precision Hardware & Bearings

The world's most comprehensive industrial hardware catalogue. Every nut, bolt, standoff, bearing, and shaft your robot needs — with same-day shipping from New Jersey.

🔧

Metric Fasteners — The FTC Standard

M3, M4, M5 — the three thread sizes every FTC builder must know cold

Fasteners

goBILDA's channel system uses M4 × 0.7mm pitch. REV's extrusion system uses M3 × 0.5mm pitch. Yellow Jacket motor face mounts use M3. Understanding which size goes where — and ordering in bulk before season — eliminates the single most common build delay: running out of the right bolt in the middle of an assembly session.

Critical Metric Fastener Sizes for FTC

M3 × 0.5mm: REV 15mm extrusion, Yellow Jacket motor face, servo mounts — stock: M3×8, M3×12, M3×16 button-head
M4 × 0.7mm: goBILDA 1120 channel — primary structural fastener — stock: M4×8, M4×10, M4×14, M4×20 socket-head
M5 × 0.8mm: shaft couplers, bearing blocks, drivetrain axle retention hardware
Hex Nuts: M3, M4 in standard hex and nylon-insert (nylock) for vibration-prone joints
Flat Washers: M3, M4 — use under bolt heads on aluminium to distribute load and prevent pull-through
M4 T-Nuts: for inserting into goBILDA channel end — enables post-assembly attachments

McMaster Key Part Numbers (save these)

M4×8 Button Head 18-8 SS: 92095A192
M4×10 Button Head 18-8 SS: 92095A193
M4×16 Socket Head 18-8 SS: 92095A204
M4×25 Socket Head 18-8 SS: 92095A208
M3×8 Socket Head 18-8 SS: 92095A182
M3×12 Socket Head 18-8 SS: 92095A185
M4 Hex Nut 18-8 SS: 90592A008
M4 Nylon Lock Nut: 90576A102
M3 Hex Nut 18-8 SS: 90592A003
M4 Flat Washer 18-8 SS: 93475A230

▷

Standoffs, Shafting, Bearings & Shoulder Bolts

Precision hardware for drivetrain, live axles, and smooth-running mechanisms

Precision Hardware

Beyond basic fasteners, McMaster-Carr is the go-to source for hex standoffs, precision ground shafting, radial ball bearings, set screws, and shoulder bolts — the hardware that makes mechanisms run smoothly and survive load under competition conditions.

Key Precision Hardware Categories

Hex Standoffs (M3 F-F): PCB and electronics spacing; 5mm, 10mm, 15mm heights — 95947A005 and variants
Precision Ground Shafts (6mm OD): 304 SS smooth rod for custom axles; pairs with goBILDA 6mm ID bearings
Radial Ball Bearings 6×13×5mm: press-fit into goBILDA bearing blocks — McMaster 5972K59
Shoulder Bolts (M4): precision shoulder acts as axle for pivot joints without a separate shaft — 90278A029
Set Screws M3×3mm: securing hubs to D-shafts; always use with Loctite 243 — 92311A105
M4 Thumbscrews: for hand-tool-accessible covers and access panels

Ordering Strategy

Search by thread size + length + head type — "M4 × 12 socket head 18-8 stainless"
Filter "18-8 Stainless Steel" for most FTC applications — corrosion resistant, moderate strength
Use "Alloy Steel Class 12.9" for high-stress joints (drivetrain pivots, lift axles)
Create a McMaster saved list — reorder the whole BOM fastener kit in one click
Ships from Elmhurst, NJ warehouse — NJ teams receive most orders next day
No minimum order — order a single shoulder bolt if that's all you need
Download STEP CAD files from McMaster for accurate clearance modelling in CAD

◆ Essential Fastener Starter Kit — Order Before Build Season

M3×8 Socket Head Button × 100 — REV mounts, goBILDA motor faces
M3×12 Socket Head × 50 — motor-to-bracket with clearance
M4×8 Button Head × 100 — general goBILDA channel
M4×12 Button Head × 100 — channel-to-channel connections
M4×16 Socket Head × 50 — bracket-to-channel with nut clearance behind
M4×25 Socket Head × 25 — spacer-plus-fastener assemblies
M3 Nylock Nuts × 100; M4 Nylock Nuts × 100
M3 Hex Nuts × 50; M4 Hex Nuts × 50
M3 Flat Washers × 50; M4 Flat Washers × 50
Loctite 243 (blue, medium) × 1 bottle — set screws and critical joints only

CAD tip: McMaster's website has a CAD Download button (STEP format) on every product page. Download bolt CAD files and include them in your SolidWorks or Onshape assemblies for accurate clearance modelling. This prevents interference issues between fastener heads and adjacent mechanisms — problems that only reveal themselves when you try to physically assemble the robot at 11pm the night before competition.

Home Depot — Tools, Materials & General Supplies

Your local hardware store is an essential complement to specialty robotics vendors — fast, accessible, and stocked with consumables and tools that keep the build shop running day to day.

🔨

Tools & Shop Equipment

Build shop essentials — stock before Season Kickoff

Cordless Drill/Driver 18V (DeWalt or Milwaukee): driving M4 screws and drilling pilot holes in aluminium channel
Drill Bit Set (Metric): 3.2mm, 4.2mm, 5.0mm pilot/clearance bits for M3, M4, M5 thread sizes
Hacksaw + 24-tooth Blades: cutting goBILDA channel to length; 24-tooth is ideal for aluminium
File Set (flat and half-round): deburring cut aluminium edges — sharp edges cut wires and fingers
Combination Square: checking 90° perpendicularity of channel frame assemblies
M3/M4 Tap and Die Set: threading holes in flat aluminium plate for custom mounts
Allen Key / Hex Key Set (Metric): 2mm, 2.5mm, 3mm sizes for socket-head screws on robot
Torque Wrench (1/4" drive): tightening to spec without stripping M3/M4 aluminium threads

🛒

Materials & Consumables

Stock before Season Kickoff — running out costs build days

Zip Ties (4", 8", 12" assorted 100-pack): cable management and temporary fixturing
3M VHB Double-Sided Foam Tape: mounting electronics to robot frame without drilling
Electrical Tape: wire insulation and colour-coding motor leads by direction
Velcro Cable Ties: securing battery and encoder cable bundles cleanly
Sandpaper 220-grit: final deburring and surface prep on aluminium cuts
Safety Glasses (bulk pack): one per team member — FIRST requires eye protection during build
Nitrile Gloves: handling batteries and electronics soldering work
Permanent Markers (Sharpie): labelling parts, battery cycle counts, cable runs
Blue Painter's Tape: masking during paint, temporary joint alignment
1"×1" Aluminium Angle Stock: quick custom gussets when no goBILDA bracket fits

◆ Electronics Supplies from Home Depot

Home Depot's electrical aisle carries several items useful for FTC electronics work: 18 AWG and 22 AWG wire in short spool lengths for custom cable runs; wire stripper/crimper combo tools for making JST and XT30 cable extensions; heat shrink tubing assortment packs for cable splices; multimeters for continuity testing and voltage measurement; and cable staples for routing wires neatly along robot frame members. None of these are robotics-specific — Home Depot is simply faster and cheaper than online ordering for these commodity items when you need them today.

◆ Competition Pit Kit — Home Depot Contributions

Folding table and plastic storage bins — pit organisation and parts sorting
LED work light or clip lamp — bright pit illumination for electronics work under field tents
Power strip with surge protection — simultaneously charging Driver Hub and two batteries
Small plastic parts organiser (fishing tackle box style) — sorting M3/M4 bolts at competition
Blue painter's tape roll — last-minute cable management and labelling at events
Small first aid kit — FIRST events require a team first aid kit in the pit area
Whiteboard or foam board + markers — displaying team info, alliance strategy diagrams
Bungee cords — securing robot in transport tote during transit to events

★

Budget tip: Home Depot is significantly cheaper than Amazon for most consumables when purchased in-store. Buying 2× what you think you need of zip ties, tape, and sandpaper at the start of season costs maybe $30 extra and eliminates half-a-dozen mid-build interruptions to run to the store. Keep a "running low" list on the build room whiteboard; restock before build sessions, not during them. Total Home Depot budget for a full season should be approximately $150–200.

Introduction to FIRST Tech Challenge

FTC Awards & Their Significance

Team Roles & Structure

COTS Vendors & Procurement Guide