2026 FIRST^® Robotics Competition

Game Manual

REBUILT^TM presented by Haas

 

Contents

1     Introduction. 4

1.1       About FIRST^®. 4

1.2       In Memoriam... 4

1.3       FIRST^® Robotics Competition. 5

1.4       FIRST Ethos and Core Values. 5

1.5       Spirit of Volunteering. 7

1.6       This Document & Its Conventions. 9

1.7       Translations & Other Versions. 10

1.8       Team Updates. 11

1.9       Question and Answer System... 11

2     FIRST Season Overview.. 13

3     Game Sponsor Recognition. 14

4     Game Overview.. 15

5     ARENA.. 17

5.1       Dimensions and Accuracy. 17

5.2       FIELD.. 18

5.3       Areas, Zones, & Markings. 20

5.4       HUB.. 22

5.5       BUMP.. 24

5.6       TRENCH.. 25

5.7       DEPOT.. 25

5.8       TOWER.. 26

5.9       ALLIANCE WALL. 27

5.10     SCORING ELEMENTS.. 32

5.11     AprilTags. 33

5.12     The FIELD Management System... 36

5.13     FIELD STAFF. 37

6     Game Details. 39

6.1       MATCH Overview.. 39

6.2       DRIVE TEAM... 39

6.3       Setup. 41

6.4       MATCH Periods. 44

6.5       Scoring. 45

6.6       Violations. 48

6.7       Head REFEREE and FTA Interaction. 51

6.8       Other Logistics. 52

7     Game Rules (G) 53

7.1       Personal Safety. 53

7.2       Conduct 54

7.3       Pre-MATCH.. 59

7.4       In-MATCH.. 62

7.5       Post-MATCH.. 70

8     ROBOT Construction Rules (R) 71

8.1       General ROBOT Design. 74

8.2       ROBOT Safety & Damage Prevention. 78

8.3       Budget Constraints & Fabrication Schedule. 79

8.4       BUMPER Rules. 82

8.5       Motors & Actuators. 89

8.6       Power Distribution. 93

8.7       Control, Command & Signals System... 101

8.8       Pneumatic System... 106

8.9       OPERATOR CONSOLE. 110

9     Inspection & Eligibility (I) 113

9.1       Rules. 113

10       Tournaments (T) 117

10.1     MATCH Schedules. 117

10.2     MATCH Replays. 117

10.3     Measurement 119

10.4     Practice MATCHES.. 119

10.5     Qualification MATCHES.. 120

10.6     Playoff MATCHES.. 121

11       District Tournaments. 131

11.1     District Events. 131

11.2     District Championship Eligibility. 134

11.3     District Championships with Multiple Divisions. 136

11.4     District Championship Playoffs. 136

11.5     FIRST Championship Eligibility. 138

12       Regional Tournaments. 141

12.1     Regional Events. 141

12.2     FIRST Championship Eligibility. 143

13       FIRST Championship Tournament (C) 145

13.1     Advancement to the FIRST Championship. 145

13.2     4-ROBOT ALLIANCES.. 145

13.3     FIRST Championship Pit Crews. 146

13.4     FIRST Championship Playoffs. 146

14       Event Rules (E) 147

14.1     General Rules. 147

14.2     Machine Shops. 151

14.3     Wireless Rules. 151

14.4     Load-In. 152

14.5     Pits. 153

14.6     TEST AREAS and PRACTICE AREAS.. 154

14.7     ROBOT Carts. 156

14.8     Ceremonies. 156

14.9     In the Stands. 157

15       Glossary. 159

 

1.1       About FIRST^®

FIRST^® (For Inspiration and Recognition of Science and Technology) was founded by inventor Dean Kamen to inspire young people’s interest in science and technology. As a robotics community that prepares young people for the future, FIRST is the world’s leading youth-serving nonprofit advancing STEM education. For 30 years, FIRST has combined the rigor of STEM learning with the fun and excitement of traditional sports and the inspiration that comes from community through programs that have a proven impact on learning, interest, and skill-building inside and outside of the classroom. FIRST provides programs that span a variety of age groups:

-        FIRST^® Robotics Competition for grades 9-12, suggested ages 14-18

-        FIRST^® Tech Challenge for grades 7-12, ages 12-18

-        FIRST^® LEGO^® League for grades Pre-K-8, ages 4-16

o   FIRST^® LEGO^® League Challenge for grades 4-8 (ages 9-16, ages vary by country)

o   FIRST^® LEGO^® League Explore for grades 2-4 (ages 6-10)

o   FIRST^® LEGO^® League Discover for grades Pre-K-1 (ages 4-6)

Please visit the FIRST website for more information about FIRST and its programs.

 

Purpose	Vision	Mission
FIRST exists to prepare the young people of today for the world of tomorrow.	To transform our culture by creating a world where science and technology are celebrated and where young people dream of becoming science and technology leaders.	The mission of FIRST is to provide life-changing robotics programs that give young people the skills, confidence, and resilience to build a better world.

1.2       In Memoriam

In October 2019, Dr. Woodie Flowers, an innovator in design and engineering education and a Distinguished Advisor to FIRST and supporter of our mission, passed away. As thousands of heartfelt tributes to Woodie have poured in from around the world, it is clear his legacy will live on indefinitely through the gracious nature of our community and our ongoing commitment to empowering educators and building global citizens.

Figure 1‑1 Dr. Woodie Flowers, 1943-2019

1.3       FIRST^® Robotics Competition

FIRST^® Robotics Competition combines the excitement of sport with the rigors of science and technology. Teams of students are challenged to design, build, and program industrial-size robots and compete for awards, while they also create a team identity, raise funds, hone teamwork skills, and advance respect and appreciation for STEM within the local community.

Volunteer professional mentors lend their time and talents to guide each team. It’s as close to real-world engineering as a student can get. Plus, high school students gain access to exclusive scholarship opportunities from colleges, universities, and technical programs.

Each January at an event known as “Kickoff,” a new, challenging game is introduced. These exciting competitions combine the practical application of science and technology with the fun, intense energy, and excitement of a championship-style sporting event. Teams are encouraged to display Gracious Professionalism^®, help other teams, and cooperate while competing. This is known as Coopertition^®.

In 2026, FIRST Robotics Competition is projected to reach approximately 90,000 high-school students representing more than 3,700 teams. Teams represent more than 30 countries and come from nearly every state in the United States.

FIRST Robotics Competition teams will participate in 56 Regional Competitions, 125 District Competitions, and 15 District Championships. In addition, approximately 600 teams will qualify to attend the FIRST Championship in April 2026.

This year’s game, and this manual, were presented at the 2026 FIRST Robotics Competition Kickoff on Saturday, January 10, 2026. At the Kickoff, all teams:

-        saw the 2026 game, REBUILT^TM presented by Haas, for the first time,

-        learned about the 2026 game rules and regulations, and

-        received a set of game specific materials.

1.4       FIRST Ethos and Core Values

1.4.1       Core Values

The FIRST Core Values are fundamental to FIRST and unique to its programs. They emphasize friendly sportsmanship, respect for the contributions of others, teamwork, learning, and community involvement and are part of our commitment to fostering, cultivating, and preserving a culture of unity.

Our community expresses the FIRST philosophies of Gracious Professionalism^® and Coopertition^® through the FIRST Core Values.

Discovery: We explore new skills and ideas.

Innovation: We use creativity and persistence to solve problems.

Impact: We apply what we learn to improve our world.

Inclusion: We respect each other and embrace our differences.

Teamwork: We are stronger when we work together.

Fun: We enjoy and celebrate what we do!

1.4.2       Gracious Professionalism^®, a FIRST Credo

Gracious Professionalism is part of the ethos of FIRST. It’s a way of doing things that encourages high quality work, emphasizes the value of others, and respects individuals and the community. Gracious Professionalism is not clearly defined for a reason. It is an aspirational ideal to always strive towards, not a goal to be achieved or a method of measuring someone, and for this reason, you can never say someone “is” or “is not” being Graciously Professional. We should each work to better embody Gracious Professionalism in all our actions. How we pursue this can and should mean different things to everyone.

Some possible meanings of Gracious Professionalism include:

-        gracious attitudes and behaviors are win-win,

-        gracious folks respect others and let that respect show in their actions,

-        professionals possess special knowledge and are trusted by society to use that knowledge responsibly, and

-        gracious professionals make a valued contribution in a manner pleasing to others and to themselves.

In the context of FIRST, this means that all teams and participants should:

-        learn to be strong competitors, but also treat one another with respect and kindness in the process and

-        avoid leaving anyone feeling as if they are excluded or unappreciated.

Knowledge, pride, and empathy should be comfortably and genuinely blended.

In the end, Gracious Professionalism is part of pursuing a meaningful life. When professionals use knowledge in a gracious manner and individuals act with integrity and sensitivity, everyone wins and society benefits.

Figure 1‑2 Dr. Woodie Flowers, Gracious Professionalism advocate and exemplar

“The FIRST spirit encourages doing high-quality, well-informed work in a manner that leaves everyone feeling valued. Gracious Professionalism seems to be a good descriptor for part of the ethos of FIRST. It is part of what makes FIRST different and wonderful.”

- Dr. Woodie Flowers, (1943 – 2019)

Distinguished Advisor to FIRST

It is a good idea to spend time going over this concept with your team and reinforcing it regularly. We recommend providing your team with real-life examples of Gracious Professionalism in practice, such as when a team loans valuable materials or expertise to another team that they will later face as an opponent in competition. Routinely highlight opportunities to display Gracious Professionalism at events and encourage team members to suggest ways in which they can demonstrate this quality themselves and through outreach activities.

1.4.3       Coopertition^®

At FIRST, Coopertition is displaying unqualified kindness and respect in the face of fierce competition. Coopertition is founded on the concept and philosophy that teams can and should help and cooperate with one another even as they compete. Coopertition involves learning from teammates and mentors. Coopertition means competing always but assisting and enabling others when you can.

Message from Woodie Flowers Award Recipients

The Woodie Flowers Award is the most prestigious mentoring award in FIRST. The award recipients created an important message for all FIRST Robotics Competition teams to consider as we tackle each season.

Performing at your best is important. Winning is important. This is a competition.

However, winning with Gracious Professionalism and being proud of what you have accomplished and how you have accomplished it is more important. FIRST could create rules and penalties to cover almost any scenario or situation, but we prefer an understandable game with simpler rules that allow us to think and be creative in our designs.

We want to know that our partners and opponents are playing at their best in every MATCH. We want to know they are playing with integrity and not using strategies based on questionable behaviors.

As you create your ROBOTS and award presentations, prepare for competition and MATCH play, create and implement game strategies, and live your daily lives, remember what Woodie said time and time again, and let’s ‘Make your Grandmother proud.’

Woodie Flowers Liz Calef (88) Mike Bastoni (23) Ken Patton (51, 65) Kyle Hughes (27) Bill Beatty (71) Dave Verbrugge (5110, 67) Andy Baker (3940, 45) Dave Kelso (131) Paul Copioli (3310, 217)

Rob Mainieri (812, 64, 498, 991, & 2375) Dan Green (111) Mark Breadner (188) John Novak (16, 323) Chris Fultz (234) John Larock (365) Earl Scime (2614) Fredi Lajvardi (842) Lane Matheson (932) Mark Lawrence (1816)

Eric Stokely (258, 360, 2557, & 5295) Glenn Lee (359) Gail Drake (1885) Allen Gregory (3847) Lucien Junkin (118) Matt Fagen (4253) Christine Sapio (2486) Mark Buckner (4265) Norman Morgan (2468) Francisco Guerra (4635)

1.5       Spirit of Volunteering

Message from the Global Volunteers

Welcome– we're excited for you to discover this season. We’re even more excited to see what you and your team can achieve this season and at the almost 200 events worldwide this season.

FIRST is made possible by our volunteers

Volunteers are the driving force behind the delivery of all FIRST programs including the FIRST Robotics Competition. Each year it takes thousands of volunteers donating their time, energy, and enthusiasm to ensure that every FIRST Robotics Competition team has the opportunity to achieve its goals. FIRST volunteers come from a diverse set of backgrounds and are united by the same goal: to provide the best possible FIRST experience for all participating teams.

We encourage everyone in the FIRST community to join in the fun and excitement of events by participating as a volunteer.

Why Volunteer?

·         Witness capable students learning and growing

·         Forge meaningful friendships with other awesome volunteers

·         Be part of the magic that brings events to life

·         Share the wonders of FIRST with those who are yet to discover it

·         Bring invaluable event experiences back to your team

·         Learn and grow beyond your usual circles

FIRST Alumni and Graduating Students:

You’ve experienced firsthand the impact of FIRST in your life, the opportunities it has provided, and the excitement of participating. Your FIRST experience does not have to end after you graduate – being a volunteer or mentor gives you the opportunity to continue learning, growing, building a community, and having fun at FIRST events. Your experience as a student in a FIRST program is invaluable to helping ensure future students have an amazing experience. There are volunteer roles for every skill level, background, and level of commitment – everyone is welcome!

Learn more and sign up as a FIRST volunteer on the FIRST website.

FIRST is about you

Volunteers eagerly donate their time and efforts to make it possible for you to participate and have fun! We strive to demonstrate the FIRST philosophies of Gracious Professionalism and Coopertition in every interaction – in return, we ask the same of you. If for any reason you feel like our volunteers could have done a better job, we want to know about it – talk to a mentor, trusted adult, other event volunteer or staff member, or report it to FIRST via customerservice@firstinspires.org.

Join us for the 2026 season and be a part of the incredible journey that is FIRST Robotics Competition! Your involvement is key to our collective success. We look forward to welcoming you!

 

With gratitude and excitement for what lies ahead, your 2026 Global Volunteers:

Global Field Supervisors – Ayla DeLaat & Bryan Herbst
Global FIRST Technical Advisors (FTAs) – James Cerar & Mark McLeod
Global Head Referees – Aidan Browne & Jon Zawislak
Global Judge Advisors – Cindy Stong & Allen Bancroft
Global Lead Robot Inspectors – Chuck Dickerson & Alida Mendes-MacCracken
Global Lead Scorekeepers – Alex Herreid & Andrea “Duckie” Tribo
Global Volunteer Coordinators – Laurie Shimizu & Sarah Plemmons

1.6       This Document & Its Conventions

The 2026 Game Manual is a resource for all FIRST Robotics Competition teams for information specific to the 2026 season and the REBUILT game. Its audience will find the following detail:

-        a general overview of the REBUILT game,

-        detail about the REBUILT playing FIELD,

-        a description of how to play the REBUILT game,

-        rules (related to safety, conduct, game play, inspection, event, etc.), and

-        a description of how teams advance at 2026 tournaments and throughout the season.

The intent of this manual is that the text means exactly, and only, what it says. Please avoid interpreting the text based on assumptions about intent, implementation of past rules, or how a situation might be in “real life.” There are no hidden requirements or restrictions. If you’ve read everything, you know everything.

Specific methods are used throughout this manual to highlight warnings, cautions, key words, and phrases. These conventions are used to alert the reader to important information and are intended help teams in constructing a ROBOT that complies with the rules in a safe manner.

Links to other section headings in this manual, external articles, and rule references appear in blue underlined text.

Key words that have a particular meaning within the context of the FIRST Robotics Competition and REBUILT are defined in the Glossary and indicated in ALL CAPS throughout this document.

The rule numbering method indicates the section, subsection, and position of the rule within that subsection. The letter indicates the section in which the rule is published.

-        Q for 6.7.1 Question Box (Q)

-        G for 7 Game Rules (G)

-        R for 8 ROBOT Construction Rules (R)

-        I for 9 Inspection & Eligibility (I)

-        T for 10 Tournaments (T)

-        C for 13 FIRST Championship Tournament (C)

-        E for 14 Event Rules (E)

The following digit(s) represents the subsection in which the rule can be found. The final digits indicate the rule’s position within that subsection.

Figure 1‑3 Rule numbering method

Imperial dimensions are followed by comparable metric dimensions in parentheses to provide metric users with the approximate size, mass, etc. Decimal values are rounded in order to limit the number of decimal places shown and the number of significant figures. Metric conversions in rules round such that the metric dimension is compliant with the rule (i.e. maximums round down, minimums round up). The metric conversions are offered for convenient reference only and do not overrule or take the place of the imperial dimensions presented in this manual and the official drawings (i.e. dimensions and rules will always defer to measurements using imperial units).

Rules include colloquial language, also called headlines, in an effort to convey an abbreviated version of the rule or rule set. There are two versions of headline formatting.

Evergreen rules, or rules which are expected to go relatively unchanged from season to season, are indicated with a leading asterisk and their rule number and headline are presented in bold green text. “Relatively unchanged” means that the overall intent and presence of the rule from season to season is constant, but game specific terms may be updated as needed (e.g.  changing Power Cells to FUEL in a rule about what COACHES may not contact during a MATCH). These rules also start their respective section, so their rule number is not expected to change from season to season.

All other rule headlines use bold blue text. Any disagreement between the specific language used in the rules and the colloquial language is an error, and the specific rule language is the ultimate authority. If you discover a disparity, please let us know at customerservice@firstinspires.org and we will correct it.

Team resources that aren’t generally season specific (e.g., what to expect at an event, communication resources, team organization recommendations, ROBOT transportation procedures, and award descriptions) can be found on the FIRST Robotics Competition website.

1.7       Translations & Other Versions

The REBUILT manual is originally and officially written in English and is occasionally translated into other languages for the benefit of FIRST Robotics Competition teams whose native language may not be English. These assets are posted on the Translated Manuals section.

A text-based English version is provided only for use with assistive devices on the Translated Manuals section. This document is locked for editing and has a watermark applied to indicate that it should not be copied. If you have any questions on the document, please contact the FIRST Robotics Competition Team Advocate at frcteamadvocate@firstinspires.org.

In the event that a rule or description is modified in an alternate version of this manual, the English pdf version as published on the Season Materials webpage is the commanding version.

1.8       Team Updates

Team Updates are used to notify the FIRST Robotics Competition community of revisions to the official season documentation (e.g. the manual, drawings, etc.) or important season news. Team Update posts are scheduled as follows:

-        each Tuesday and Friday, starting on the first Tuesday after Kickoff and ending on the Tuesday prior to Week 1 events

-        each Tuesday, starting Week 1 and ending the week after the final District Championship events.

Team Updates are posted on the Season Materials webpage and are generally posted before 5 pm, Eastern.

Generally, Team Updates follow the following convention:

-        Additions are highlighted in yellow. This is an example.

-        Deletions are indicated with a strikethrough. This is an example.

1.9       Question and Answer System

The Question and Answer System (Q&A) is a resource for clarifying the 2026 REBUILT Game Manual, Awards webpages, official FIELD drawings, and/or District and Regional Events webpage content. Teams can search for previously asked questions and responses or pose new questions. Questions can include examples for clarity or reference multiple rules to understand the relationships and differences between them.

The Q&A opens on January 14, 2026, 12:00 PM Eastern. Details on the Q&A can be found on the Season Materials webpage. The Q&A may result in revisions to the text in the official manuals (which are communicated using the process described in Team Updates).

The responses in the Q&A do not supersede the text in the manual, although every effort will be made to eliminate inconsistencies between the two. While responses provided in the Q&A may be used to aid discussion at each event, per section 9 Inspection & Eligibility and section 6.7 Head REFEREE and FTA Interaction, REFEREES and INSPECTORS are the ultimate authority on rules. If you have concerns about enforcement trends by volunteer authorities, please notify FIRST at customerservice@firstinspires.org. 

The Q&A is not a resource for firm predictions on how a situation will play out an event. Questions about the following will not be addressed:

-        rulings on vague situations,

-        challenging decisions made at past events, or

-        design reviews of a ROBOT system for legality.

Weak questions are overly broad, vague, and/or include no rule references. Some examples of questions that will not be answered in the Q&A are:

-        Is this part/design legal?

-        How should the REFEREE have ruled when this specific game play happened?

-        Duplicate questions

-        Nonsense questions

Good questions ask generically about features of parts or designs, gameplay scenarios, or rules, and often reference one or more relevant rules within the question. Some examples of questions that will likely be answered in the Q&A are:

-        A device we are considering using on the ROBOT comes with purple AWG 40 wire, does this comply with R?? and R??

-        We’re not sure how to interpret how Rule G?? applies if blue ROBOT A does X and red ROBOT B does Y, can you please clarify?

-        If a ROBOT does this specific action, is it doing what this defined term is describing?

Questions from “FRC 99999” represent content asked by key volunteers (e.g., REFEREES, INSPECTORS, etc.), answered by FIRST, and are considered relevant to teams.

 

Uncover the Future

Thank you to the 2026 FIRST^® Robotics Competition season presenting sponsor, the Gene Haas Foundation.

 

 

 

  

In REBUILT^TM presented by Haas, two competing alliances are invited to score fuel, cross obstacles, and climb the tower before time runs out. Alliances earn additional rewards for meeting specific scoring thresholds.

During the first 20 seconds of the match, robots are autonomous. Without guidance from their drivers, robots score fuel into their hub. Fuel can be pre-loaded into a robot, obtained from the human player, collected at the depot, or picked up throughout the center of the field. Some robots may also climb the tower to obtain additional points.

During the remaining 2 minutes and 20 seconds, drivers control their robots. Based on the result of autonomous play, alliance hubs will alternate between active and inactive, shifting gameplay between both sides of the field. Robots can collect fuel at any point in the match and may control any amount of fuel at a time. Drivers control their robots to score fuel into their hub while it is active and may perform defensive strategies or collect more fuel while their hub is inactive.

As time runs out, all hubs become active, allowing all robots to score. Robots can climb to the tower’s highest heights to score additional points and claim match bonuses to increase their position in the rankings.

The alliance that earns the most points wins the match!

The ARENA includes all elements of the game infrastructure that are required to play REBUILT^TM presented by Haas: the FIELD, SCORING ELEMENTS, queue area, team media area (when available), designated TECHNICIAN area, and all equipment needed for FIELD control, ROBOT control, and scorekeeping.

Figure 5‑1 REBUILT ARENA (queue area, TECHNICIAN area, and media area not pictured)

5.1       Dimensions and Accuracy

All official models for the REBUILT FIELD were created in Onshape.

The specification for the REBUILT FIELD can be retrieved from a few locations:

-        The 3D CAD model is the official representation of the REBUILT FIELD and how it is constructed.

-        Illustrations included in this section are for a general visual understanding of the REBUILT ARENA, and dimensions included in the manual are nominal and no tolerances are implied. Please refer to the official drawings for exact dimensions, tolerances, and construction details.

-        The Field Dimension Drawings package has critical dimensions for each FIELD element.

-        The FIELD Manual (coming soon) includes instructions on how to build the FIELD along with showing the ways construction type will influence the field tolerances. It also includes many of the key dimensions which are listed in the Official FIELD Drawings.

-        The FIELD Acceptance Checklist (coming soon) includes the controlled dimensions (with relevant tolerances) which will be checked by event staff a few times throughout the event. The FIELD is expected to change during MATCH play. Teams can ask the FTA to re-check specific measurements if they believe something is out of spec prior to a MATCH beginning.

The official drawings, CAD models, and drawings for low-cost versions of important elements of the REBUILT FIELD are posted on the Playing FIELD webpage.

5.2       FIELD

Each FIELD for REBUILT is an approximately 317.7in (~8.07m) by 651.2in (~16.54m) carpeted area bounded by inward facing surfaces of the ALLIANCE WALLS, OUTPOSTS, TOWER WALLS, and guardrails.

Figure 5‑2 FIELD boundary in pink

The FIELD is populated with and surrounded by the following elements:

-        1 OUTPOST per ALLIANCE,

-        1 HUB per ALLIANCE,

-        1 TOWER per ALLIANCE,

-        2 DEPOTS,

-        4 BUMPS, and

-        4 TRENCHES.

The surface of the FIELD is low pile carpet, Shaw Floors, Philadelphia Commercial, Neyland II 20, “66561 Medallion.” Neyland II carpet is not available for purchase at this time, and the closest equivalent is Shaw, Philadelphia Brand, Profusion 20, Style 54933; see results from evaluation in this blog post.

Carpet edges and seams are secured with 3M^TM Premium Matte Cloth (Gaffers) Tape GT2, GT3 or comparable Gaffer’s Tape. Tears, rips, and damage to the carpet may be repaired with the same styles of tape and ROBOTS must be prepared to operate on surfaces made of carpet, tape, or combinations of both materials as repairs are made through the course of competition.

Guardrails form the long edges of the FIELD. Guardrails are a 20.0in (50.8cm) tall system of transparent polycarbonate supported on the top and bottom by aluminum extrusion. There are 4 gates in the guardrail that allow access to the FIELD for placement and removal of ROBOTS. The gate passthrough, when open, is 38.0in (96.5cm) wide. Gates are closed and shielded during the MATCH.

Figure 5‑3 Gate locations

There are 2 versions of guardrails and DRIVER STATIONS used for competitions. 1 design is the Welded FIELD which is reflected in the 2026 Official FIRST FIELD Drawings & Models. The other is designed and sold by AndyMark. Table 5‑1 and

Table 5‑2 illustrate which areas have each kind of FIELD. While the designs are slightly different, the critical dimensions, performance, and expected user experience between them are the same unless otherwise noted. Detailed drawings for the AndyMark design are posted on the AndyMark website. All illustrations in this manual show the traditional Welded FIELD design.

Table 5‑1: District Field Types

District	Field Type
FIRST Chesapeake	AndyMark
FIRST California	Welded
FIRST in Michigan	Welded
FIRST in Texas	AndyMark
FIRST Indiana Robotics	AndyMark
FIRST Israel	Welded
FIRST Mid-Atlantic	Welded
FIRST North Carolina	AndyMark
FIRST South Carolina	Welded
FIRST Wisconsin	AndyMark
NE FIRST	AndyMark
Ontario	Welded
Pacific Northwest	Welded
Peachtree	Welded

Table 5‑2 Regional Field Types

5.3       Areas, Zones, & Markings

FIELD areas, zones, and markings of consequence are described below. Unless otherwise specified, the tape used to mark lines and zones throughout the FIELD is 2.0in (5.1cm) 3M™ Premium Matte Cloth (Gaffers) Tape (GT2), ProGaff^® Premium Professional Grade Gaffer Tape, or comparable gaffers tape.     

Figure 5‑4 Areas, markings, and zones

-        ALLIANCE AREA: an approximately 360in wide by 134in deep (~9.14m by 3.4m) infinitely tall volume formed by, and including the ALLIANCE WALL, OUTPOST, TOWER WALL, the edge of the carpet, and ALLIANCE colored tape perpendicular to the DRIVER STATIONS.

-        ALLIANCE ZONE: A 158.6in deep by 317.7in long (~4.03m by 8.07m), infinitely tall volume formed by an ALLIANCE WALL, TOWER WALL, and guardrails. It surrounds an ALLIANCE TOWER and a DEPOT. It is bounded by and includes the ROBOT STARTING LINE.

-        CENTER LINE: a white line that spans the width of the FIELD that bisects the NEUTRAL ZONE in half.

-        NEUTRAL ZONE: A 283in deep by 317.7in long (7.19m by 8.07m), infinitely tall volume formed by the BUMPS, TRENCHES, HUBS, and guardrails. It surrounds and includes the CENTER LINE.

-        HUMAN STARTING LINE: a white line spanning the ALLIANCE AREA up to the OUTPOST AREA that is parallel to and located 24.0in (61.0cm) from the bottom square tube of the ALLIANCE WALL to the near edge of the tape.

-        OUTPOST AREA: a 71.0in wide by 134in deep (1.8m by 3.4m) infinitely tall volume bounded by the OUTPOST, edge of carpet, and ALLIANCE and white colored tape.

-        ROBOT STARTING LINE: an ALLIANCE colored line that spans the width of the FIELD at the edge of an ALLIANCE ZONE in front of two BUMPS and an ALLIANCE HUB.

5.4       HUB

Figure 5‑5 HUB

A HUB is one of two 47in by 47in (~1.19m by 1.19m) rectangular prism structures with an extended opening at the top surface. Each ALLIANCE has a dedicated HUB centered between two BUMPS located 158.6in (~4.03m) away from their ALLIANCE WALL. Each HUB has a set of exits that randomly distributes FUEL into the NEUTRAL ZONE. A net structure located in the back of the HUB prevents FUEL launched from most prohibited areas from entering the opening.

Figure 5‑6: HUB distance to the ALLIANCE WALL

The top of each HUB has a 41.7in (~1.06m) hexagonal opening into which ROBOTS can deliver FUEL. The front edge of the opening is 72in (~1.83m) off the carpet.

Figure 5‑7: HUB Dimensions

 

HUBS have a series of exits at the base of the HUB facing towards the NEUTRAL ZONE. FUEL processed through the HUB are distributed into the NEUTRAL ZONE via one of four exits as shown in Figure 5‑8. Examples of FUEL distribution from the HUB can be found on the Playing FIELD webpage.

Figure 5‑8: HUB exits (approximation)

 

The top angles of the HUB are lit by DMX light bars that indicate if the HUB is active. See Table 5‑3 for more details about the various light states in the HUB.

Table 5‑3: HUB Lighting

Color	Pre-MATCH	MATCH	Post-Match
ALLIANCE color at 100% brightness	N/A	HUB active	N/A
ALLIANCE color pulsing		HUB deactivation warning. Starts 3 seconds before and continues until deactivation.
Purple		N/A	FIELD is safe for FIELD STAFF.
Green			FIELD is safe for all.
Off	MATCH ready to start.	HUB is not active.	N/A

 

5.5       BUMP

Figure 5‑9 BUMP

BUMPS are 73.0in (1.854m) wide, 44.4in (1.128m) deep, and 6.513in (16.54cm) tall structures on either side of the HUB that ROBOTS drive over. The top surface of each BUMP is made up of 0.5in (1.27cm) thick, ALLIANCE colored, Orange Peel textured, HDPE ramps at a 15-degree angle with one ramp sloping down towards the NEUTRAL ZONE and the other ramp sloping down towards the ALLIANCE ZONE.

5.6       TRENCH

Figure 5‑10: TRENCH

TRENCHES are a 65.65in (1.668m) wide, 47.0in (1.194m) deep, and 40.25in (1.022m) tall structure that ROBOTS drive underneath. The TRENCH extends from the guardrail to the BUMP on both sides of the FIELD. The space underneath each TRENCH arm is 50.34in (1.279m) wide, 22.25in (56.52cm) tall.

TRENCHES along the guardrail closest to the scoring table contain additional electronics to reach the HUB. The TRENCHES along the guardrail furthest from the scoring table have a pivot arm that allows the horizontal portion of the TRENCH to rotate into a vertical position for post-MATCH ROBOT retrieval and to let FIELD staff reset the field between matches. The pivot arm will be locked in the horizontal position during the MATCH.

5.7       DEPOT

Figure 5‑11: DEPOT

A DEPOT is a 42.0in (1.07m) wide, 27.0in (68.6cm) deep structure located along the ALLIANCE WALL. There is 1 DEPOT per ALLIANCE. DEPOTS are made up of 3.0in (7.62cm) wide, 1.0in (2.54) tall steel barriers. The DEPOT is secured to the carpet using hook fastener which increases the height to approximately 1.125in (2.86cm).

5.8       TOWER

Figure 5‑12: TOWER

A TOWER is a 49.25in (1.251m) wide, 45.0in (1.143m) deep, and 78.25in (1.988m) tall structure made up of the TOWER WALL, TOWER BASE, UPRIGHTS, RUNGS and supporting structures. There is 1 TOWER per ALLIANCE. A TOWER is integrated into each ALLIANCE WALL between DRIVER STATION 2 and DRIVER STATION 3.

The TOWER BASE is a 39.0in (99.06cm) wide by 45.18in (1.148m) deep plate that sits on the floor and extends from the TOWER WALL. The TOWER BASE is powder-coated steel with hook fastener underneath. The edges of the TOWER BASE are approximately 0.2in (0.5cm) to 0.3in (0.8cm) tall.

The UPRIGHTS are two 72.1in (1.831m) tall, 1.5in (3.81cm) thick, 3.5in (8.89cm) deep sheet metal box frames that extend vertically up from the TOWER BASE. The distance between each UPRIGHT is 32.25in (81.92cm).

The UPRIGHTS hold three horizontal RUNGS made up of 1-1/4in Sch 40 (1.66in (4.216cm) OD) pipe. Each RUNG is centered between the UPRIGHT and extend 5.875in (14.92cm) from the outer face of the UPRIGHT on either side. The center of the LOW RUNG is located 27.0in (68.58cm) from the floor. The center of the MID RUNG is located 45.0in (114.3cm) from the floor. The center of the HIGH RUNG is 63.0in (1.6m) from the floor. The RUNGS are 18.0in (45.72cm) apart center to center.

The UPRIGHTS and RUNGS are powder-coated red or blue.

Each TOWER has additional supporting structures extending from the UPRIGHT to the TOWER WALL between approximately 28.40in (72.14cm) and 43.38in (1.102m) off the floor.

Figure 5‑13: TOWER Dimensions

5.9       ALLIANCE WALL

The ALLIANCE WALL separates ROBOTS from DRIVE TEAM members in the ALLIANCE AREA. It consists of 3 DRIVER STATIONS, an OUTPOST, and a TOWER WALL.

Figure 5‑14: ALLIANCE WALL

5.9.1       DRIVER STATIONS

Figure 5‑15: DRIVER STATION (ALLIANCE AREA perspective and FIELD perspective)

A DRIVER STATION is 1 of 3 assemblies within an ALLIANCE WALL behind which a DRIVE TEAM operates their ROBOT. Each DRIVER STATION is made from a 36.8in (93.5cm) tall diamond plate base topped with a 42in (1.07m) tall transparent plastic sheet and a top rail.

An aluminum shelf is attached to each DRIVER STATION to support an OPERATOR CONSOLE. The shelf is 69in (1.75m) wide and 12.25in (31.1cm) deep. There is a 54.0in (1.372m) long by 2.0in (nominal) wide strip of hook-and-loop tape (“loop” side) along the center of the support shelf that may be used to secure the OPERATOR CONSOLE to the shelf. The shelf also includes two clips to hold the shelf in place with a 1.0in (2.5cm) wide by 2.0in (5.1cm) deep tab that sits on the top surface of the shelf.

There is a 6.0in (15.2cm) tall sponsor panel in each DRIVER STATION. The top of this panel is 42.9in (1.09m) from the carpet.

Each DRIVER STATION contains the following elements for DRIVE TEAMS:

-        1 Ethernet cable: attaches to the Ethernet port of the OPERATOR CONSOLE and provides connectivity to the FIELD Management System (FMS).

-        1 120VAC NEMA 5-15R power outlet (i.e. standard US outlet): located on each DRIVER STATION shelf and protected by its own 2-Amp circuit breaker. It can be used to power the OPERATOR CONSOLE. DRIVE TEAMS are responsible for monitoring their power consumption as a tripped breaker in the outlet does not constitute an ARENA FAULT. For some events in regions that don’t use NEMA 5-15 shaped outlets, event organizers may install appropriate plug adapters to be used throughout the event.

-        1 Emergency Stop (E-Stop) button: located on the left side of the DRIVER STATION shelf and is used to deactivate a ROBOT in an emergency.

-        1 Autonomous Stop (A-Stop) button: located on the right side of the DRIVER STATION shelf and is used to DISABLE a ROBOT during AUTO.

-        1 team sign: located at the top of each DRIVER STATION. The FIELD facing side of the sign displays the team number in the ALLIANCE color. The ALLIANCE AREA side of the sign displays the following information in red: 

o   Pre-MATCH: team number and ROBOT connection state

o   During Qualification MATCHES:

§  Current SHIFT and time remaining in that period,

·         A shows for AUTO when both ALLIANCE’s HUBS are active

·         T shows for the TRANSITION SHIFT when both ALLIANCE’s HUBS are active

·         R shows when the Red ALLIANCE’S HUB is active

·         B shows when the Blue ALLIANCE’S HUB is active

·         E shows for END GAME when both ALLIANCE’s HUBS are active

§  Progress towards the FUEL Ranking Points. This shows total scored out of the ENERGIZED RP and once that threshold passes it shows out of the SUPERCHARGED RP

§  AUTO TOWER points, and

§  remaining MATCH period time.

Figure 5‑16 Back of team sign (during Qualification MATCH)

o   During the MATCH during Playoff MATCHES:

§  Which MATCH period is active and time remaining in that period,

§  MATCH scores, and

§  remaining MATCH period time.

Figure 5‑17 Back of team sign (during Playoff MATCH)

-        1 timer (in DRIVER STATION 2 only): displays the official time remaining in the MATCH period on the FIELD-facing side (in white) and on the team facing side the following information in red:

o   remaining MATCH period time, and

o   MATCH scores.

Figure 5‑18 Back of timer

-        1 team LED stack: indicates ALLIANCE color, ROBOT status, E-Stop and A-Stop status, and is centered at the top of each DRIVER STATION.

The stack includes 2 identical ALLIANCE-colored ROBOT status LEDs above a third amber A-stop/E-stop LED. LED states are as follows:

o   ROBOT status LEDs

§  Solid: indicates that the ROBOT is connected and enabled. This only happens during a MATCH.

§  Blinking: indicates that either the FMS is preset for the MATCH and the ROBOT is not connected yet, or it’s during a MATCH and the corresponding ROBOT has lost connectivity, or the E-stop was pressed.

§  Off: indicates that the ROBOT is linked and DISABLED prior to the start of the MATCH, or the ROBOT is BYPASSED. This light is also off, regardless of ROBOT connection status, after the MATCH has concluded.

o   A-Stop/E-stop LED

§  Solid: the ROBOT is DISABLED due to a press of the team E-stop button, the FIELD E-stop button, or by the scorekeeper via the FMS.

§  Blinking: the ROBOT is DISABLED for the remainder of AUTO due to a press of the team A-Stop button.

§  Off: the ROBOT is not DISABLED by the FIELD.

-        FMS hardware and wiring: mostly located below shelves in the 2 DRIVER STATIONS closer to the scoring table.

5.9.2       OUTPOST

Figure 5‑19 OUTPOST

An OUTPOST is an assembly through which HUMAN PLAYERS feed FUEL into the FIELD and ROBOTS can deliver FUEL to their HUMAN PLAYERS. There are 2 OUTPOSTS, 1 on either end of the FIELD connecting the guardrail to the ALLIANCE WALL. Each OUTPOST has a 31.8in (80.8cm) wide by 7.0in (17.8cm) tall opening through which FUEL passes to the FIELD. The bottom of the opening is 28.1in (71.4cm) off the floor.

A 15.0° sloped tunnel, called the CHUTE, leads to the upper opening in the OUTPOST. The CHUTE can hold approximately 25 FUEL at a time retained by the CHUTE DOOR. The CHUTE DOOR is an HDPE arm on a pivot that can be rotated approximately 90 degrees by the HUMAN PLAYER to open or close the CHUTE.

At the base of the OUTPOST is an opening 32.0in (81.3cm) wide by 7.0in (17.8cm) tall where ROBOTS can push FUEL into the CORRAL. The bottom of the opening is 1.88in (4.77cm) off the ground. The opening is divided in the center by a vertical 1-1/4in Sch 40 (1.66in (4.216cm) OD) pipe. The CORRAL is made up of 8.13in (20.6cm) tall polycarbonate panels that create a 35.8in (90.8cm) wide, 37.6in (95.5cm) deep area on the floor in which FUEL can be stored.

The CHUTE and CORRAL each feature an ALLIANCE-colored tape line that indicates where DRIVE TEAMS may be restricted from reaching. The near edge of the CORRAL tape is 12.7in (32.3cm) from the FIELD-facing wall of the OUTPOST. The near edge of the CHUTE tape line is 12.9in (32.8cm) from the FIELD-facing wall of the OUTPOST.

5.10  SCORING ELEMENTS

SCORING ELEMENTS are items that teams use to score points. There is one type of SCORING ELEMENT used in REBUILT: FUEL.

5.10.1   FUEL

Figure 5‑20 FUEL

A FUEL is a 5.91in (15.0cm) diameter, high density foam ball. FUEL is a custom made SCORING ELEMENT available for purchase on the AndyMark website, am-5801.

FUEL has a weight of between 0.448-0.500lb (~0.203-0.227kg).

FUEL undergoes wear and tear during a competition. Generally, a FUEL that still appears to look approximately like a FUEL is considered a FUEL for the purposes of rule evaluation and scoring, whether damaged or not. Small chunks of a FUEL are not considered a FUEL.

5.11  AprilTags

AprilTags are 8.125in (20.64cm) square targets located on the HUB, TOWER WALL, OUTPOST, and TRENCHES. There are 32 unique markers on the FIELD positioned as shown in Figure 5‑21.

Figure 5‑21 AprilTag Locations

All markers are from the 36h11 tag family, IDs 1-32. All AprilTags are mounted to and centered on a 10.5in (26.67cm) square polycarbonate panel. Each marker has an identifying text label. If AprilTags experience wear and marking during MATCHES they are repaired with gaffers tape.

Figure 5‑22 AprilTag sizing

HUB AprilTags (IDs 2, 3, 4, 5, 8, 9, 10, 11, 18, 19, 20, 21, 24, 25, 26, 27) are located on all four faces of the HUB. Each face has two AprilTags with centers located 44.25in (1.124m) off the floor as shown in Figure 5‑23. One AprilTag per face is centered and the other AprilTag is horizontally offset.

Figure 5‑23 HUB AprilTags

Two AprilTags (IDs 15, 16, 31, 32) are located on each TOWER WALL with centers 21.75in (55.25cm) off the floor as shown in Figure 5‑24. One AprilTag per TOWER is centered and the other AprilTag is horizontally offset.

Figure 5‑24 TOWER WALL AprilTags

Two AprilTags (IDs 13, 14, 29, 30) are located on each OUTPOST with centers 21.75in (55.25cm) off the floor as shown in Figure 5‑25. One AprilTag per OUTPOST is centered with the CHUTE and CORRAL openings and the other AprilTag is horizontally offset.

Figure 5‑25 OUTPOST AprilTags

TRENCH AprilTags (IDs 1, 6, 7, 12, 17, 22, 23, 28) are attached to mounting brackets located on the top surface of the horizontal arm of the TRENCH. Each TRENCH has two AprilTags, one facing the ALLIANCE ZONE and one facing the NEUTRAL ZONE. TRENCH AprilTags are approximately centered on the opening under the TRENCH arm and their centers are located 35in (88.9cm) off the floor as shown in Figure 5‑26.

Figure 5‑26 TRENCH AprilTags

For further marker locating information please refer to the 2026 Field Dimension Drawings. Printable copies of the field AprilTags can be found on the Playing FIELD webpage.

5.12  The FIELD Management System

The FIELD Management System (FMS) is all the electronics responsible for sensing and controlling the FIRST Robotics Competition FIELD. The FMS encompasses all FIELD electronics, including computers, REFEREE touchscreens, the wireless access point, sensors, stack lights, A-Stops and E-Stops, etc.

When a DRIVE TEAM connects the Ethernet cable from their assigned DRIVER STATION to their OPERATOR CONSOLE, the Driver Station Software on the OPERATOR CONSOLE computer communicates with FMS. Once connected, the open ports available are described in Table 8‑5.

Note that ROBOT code cannot be deployed while connected to the FMS. Additional information about the FMS may be found in the FMS Whitepaper.

The FMS alerts participants to milestones in the MATCH using audio cues detailed in Table 5‑4. Please note that audio cues are intended as a courtesy to participants and not intended as official MATCH markers. If there is a discrepancy between an audio cue and the FIELD timers, the FIELD timers are the authority.

Table 5‑4: Audio Cues

5.13  FIELD STAFF

FIELD STAFF are responsible for making sure the MATCHES are cycled through efficiently, fairly, safely, and with a spirit of cooperation, Gracious Professionalism, and generosity of spirit. FIELD STAFF roles are filled by volunteers from the community who prepare for the event with thorough training and certification. There are 3 FIELD-side key volunteer roles with whom teams should be familiar and are encouraged to use as resources to make their event experience valuable (in whatever way the team defines “valuable”).

-        Head REFEREE – trains, directs, and supervises REFEREES. They oversee all scoring processes and procedures in collaboration with the FIRST Technical Advisor (FTA). They interact with STUDENTS, volunteers, and contracted/FIRST staff. The Head REFEREE is positioned between the FIELD and the scoring table and wears a yellow shirt. The Head REFEREE has final authority for decisions regarding MATCH scores, penalties, and YELLOW and RED CARD assignments. For additional details, please refer to the Head REFEREE role description.

-        FIRST Technical Advisor (FTA) - ensures events run smoothly, safely, and in accordance with FIRST requirements. The FTA collaborates with FIRST staff, event staff, and other event volunteers in many different areas at events. The FTA is the liaison between FIRST HQ and the event for all things related to the FIELD, ROBOTS, and game, acts as a team advocate for all teams competing at the event and is a major point of escalation and conflict resolution for the event. For additional details, please refer to the FTA role description.

-        FIELD Supervisor - directs activity on the FIELD to ensure efficient execution of the MATCHES, pacing of the event, and smooth flow of MATCH play. FIELD Supervisors are responsible for ensuring the FIELD is intact and lead FIELD Reset teams, who are responsible for resetting the FIELD after each MATCH in preparation for the subsequent MATCH. For additional details, please refer to the FIELD Supervisor role description.

Figure 6‑1 REBUILT

In REBUILT, 2 ALLIANCES (an ALLIANCE is a cooperative of up to 4 FIRST Robotics Competition teams) play MATCHES, set up and implemented per the details described below.

6.1       MATCH Overview

MATCHES run on 7–10-minute cycles, which consist of pre-MATCH setup, the 2-minute and 40-second MATCH, and the post-MATCH reset.

During the MATCH, ROBOTS collect FUEL and score in their HUB. HUMAN PLAYERS can deliver FUEL to ROBOTS or score them in their HUB.

ROBOTS conclude the MATCH climbing on their TOWER.

6.2       DRIVE TEAM

A DRIVE TEAM is a set of up to 5 people from the same FIRST Robotics Competition team responsible for team performance for a specific MATCH. There are 4 specific roles on a DRIVE TEAM which ALLIANCES can use to assist ROBOTS, and no more than 1 member of the DRIVE TEAM may be a non-STUDENT.

Table 6‑1 DRIVE TEAM roles

Role	Description	Max./ DRIVE TEAM	Criteria
DRIVE COACH	a guide or advisor	1	any team member, must wear “DRIVE COACH” button
TECHNICIAN	a resource for ROBOT troubleshooting, setup, and removal from the FIELD	1	any team member, must wear “TECHNICIAN” button
DRIVER	an operator and controller of the ROBOT	3	STUDENT, must wear a “DRIVE TEAM” button
HUMAN PLAYER	a SCORING ELEMENT manager

A STUDENT is a person who has not completed high-school, secondary school, or the comparable level as of September 1 prior to Kickoff.

The TECHNICIAN provides teams with a technical resource for pre-MATCH setup, ROBOT connectivity, OPERATOR CONSOLE troubleshooting, and post-MATCH removal of the ROBOT. Some pre-MATCH responsibilities for the TECHNICIAN may include, but are not limited to:

-        location of the ROBOT radio, its power connection, and understanding of its indicator lights

-        location of the roboRIO and understanding of its indicator lights

-        username and password for the OPERATOR CONSOLE

-        restarting the Driver Station and Dashboard software on the OPERATOR CONSOLE

-        changing the bandwidth utilization (e.g. camera resolution, frame rate, etc.)

-        changing a battery

-        charging pneumatics

Per Table 6‑1, each team is allotted up to 3 STUDENTS who may be assigned as DRIVERS or HUMAN PLAYERS. If multiple teams on an ALLIANCE do not have 3 STUDENTS at the event to act in these roles, 1 of the ALLIANCE’S teams may substitute a STUDENT TECHNICIAN as a HUMAN PLAYER for that MATCH only. In this case,

-        the Head REFEREE must be notified,

-        all HUMAN PLAYER rules now apply to this DRIVE TEAM member, and

-        this DRIVE TEAM member is no longer considered a TECHNICIAN for that MATCH.

6.3       Setup

Before each MATCH begins, FIELD STAFF stage SCORING ELEMENTS as described in section 6.3.4 SCORING ELEMENTS. DRIVE TEAMS stage their ROBOTS (as described in section 6.3.3 ROBOTS) and OPERATOR CONSOLES (as described in section 6.3.2 OPERATOR CONSOLES). Then, DRIVE TEAMS take their places as described in section 6.3.1 DRIVE TEAMS.

6.3.1       DRIVE TEAMS

DRIVE TEAMS prepare for a MATCH by staging in the appropriate areas, according to their role on the DRIVE TEAM, and by identifying themselves accordingly. DRIVE TEAM starting conditions are listed below, and a DRIVE TEAM obstructing or delaying any of the conditions is at risk of violating G301.

A.      only DRIVE TEAM members assigned to the upcoming MATCH are present,

B.      for Qualification MATCHES only DRIVE TEAM members whose ROBOTS have passed initial, complete Inspection are present,

C.      any number of HUMAN PLAYERS are staged in their OUTPOST AREAS,

D.      HUMAN PLAYERS not included in C, DRIVERS, and DRIVE COACHES are in their ALLIANCE AREA and behind the HUMAN STARTING LINE,

E.      TECHNICIANS are in the event-designated area near the FIELD,

F.      DRIVE TEAM members clearly display their designated buttons above their waists (DRIVE COACH - “Drive Coach”, DRIVERS and HUMAN PLAYERS - “Drive Team”, and TECHNICIAN - “Technician”), and

G.     if a Playoff MATCH, the ALLIANCE CAPTAIN clearly displays their designated ALLIANCE CAPTAIN identifier (e.g. hat or armband).

6.3.2       OPERATOR CONSOLES

DRIVE TEAMS set up their OPERATOR CONSOLE as soon as the DRIVE TEAM from the previous MATCH has cleared the area. OPERATOR CONSOLES must be compliant with all relevant rules, specifically those in section 8.9 OPERATOR CONSOLE. The OPERATOR CONSOLE is plugged into the team’s assigned DRIVER STATION, as indicated on the team sign. Any control devices worn or held by their HUMAN PLAYERS and/or DRIVERS during the MATCH must be disconnected from or set on or beside the OPERATOR CONSOLE before the MATCH can begin. A DRIVE TEAM obstructing or delaying OPERATOR CONSOLE setup is at risk of violating G301.

 

6.3.3       ROBOTS

DRIVE TEAMS stage their ROBOT in accordance with G303. A DRIVE TEAM obstructing or delaying ROBOT setup requirements is at risk of violating G301.

If order of placement matters to either or both ALLIANCES, the ALLIANCE notifies the Head REFEREE during setup for that MATCH, and the Head REFEREE instructs ALLIANCES to alternate placement of ROBOTS. In a Qualification MATCH, REFEREE instructions are that ROBOTS are placed in the following order:

1.      red DRIVER STATION 1 ROBOT

2.      blue DRIVER STATION 1 ROBOT

3.      red DRIVER STATION 2 ROBOT

4.      blue DRIVER STATION 2 ROBOT

5.      red DRIVER STATION 3 ROBOT

6.      blue DRIVER STATION 3 ROBOT

In an intra-Division Playoff MATCH, the same pattern is applied, but instead of blue ALLIANCE placing last, the higher seeded ALLIANCE (regardless of color) places last. For inter-Division Playoff MATCHES, the ALLIANCE that places last is determined by a (real or virtual) coin flip facilitated by the Head REFEREE where a “heads” result invites the red ALLIANCE to place last.

6.3.4       SCORING ELEMENTS

Before each MATCH begins, FIELD STAFF stage SCORING ELEMENTS.

Figure 6‑2 SCORING ELEMENT staging positions

 

 

504 FUEL are staged for each MATCH as follows (reference Figure 6‑2):

A.      24 FUEL are staged in each DEPOT (FUEL may not be in a uniform layout),

B.      24 FUEL are staged in each OUTPOST CHUTE,

C.      8 FUEL may be preloaded in each ROBOT by the ROBOT’S DRIVE TEAM, such that each FUEL is fully supported by the ROBOT (up to 48 total; a FUEL not pre-loaded in a ROBOT is staged in the NEUTRAL ZONE), and

D.      remaining FUEL are arranged in the NEUTRAL ZONE through a process listed in Section 6.3.4.1 (360 to 408, depending on how many are preloaded in ROBOTS).

For District Championship and/or FIRST Championship events, the quantity of FUEL staged in a MATCH may increase up to 600. If this happens, the additional FUEL will be included as part of an updated FUEL arrangement in the NEUTRAL ZONE.

The NEUTRAL ZONE is staged by the FIELD crew by corralling all FUEL within a bounding box that is approximately 206.0in (5.23m) wide and 72.0in (1.83m) deep. The bounding box has a solid divider in the middle that is 2.0in (5.08cm) wide that will result in a small gap in FUEL. The dividers will be removed prior to the start of the MATCH.

 Figure 6‑3 NEUTRAL ZONE FUEL setup

The expected result of the dispersal is a roughly equal split of FUEL on both sides of the CENTER LINE. The dispersal between the scoring table side and non-scoring table side of the field is expected to vary match to match.

6.4       MATCH Periods

The first period of each MATCH is 20 seconds long and called the Autonomous Period (AUTO). During AUTO, ROBOTS operate without any DRIVE TEAM control or input. ROBOTS score SCORING ELEMENTS, may leave their ROBOT STARTING LINE and retrieve additional SCORING ELEMENTS, and may climb their TOWER. There is a 3-second delay between AUTO and TELEOP for scoring purposes as described in section 6.5 Scoring.

The second period of each MATCH is the remaining 2 minutes and 20 seconds (2:20) and called the Teleoperated Period (TELEOP). During TELEOP, DRIVERS remotely operate ROBOTS to retrieve and score SCORING ELEMENTS and climb their TOWER. TELEOP is split into further segments: the TRANSITION SHIFT, the ALLIANCE SHIFTS, and END GAME. There are four ALLIANCE SHIFTS named SHIFT 1, SHIFT 2, SHIFT 3, and SHIFT 4. The duration of each timeframe is shown in Table 6‑2.

Table 6‑2: MATCH SHIFTS

6.4.1       HUB Status

During the MATCH, the status of a HUB can be either active or inactive. FUEL scored in an active HUB is worth MATCH points but FUEL scored in an inactive HUB will not earn any points as shown in Table 6‑3. Both ALLIANCE HUBS are active during AUTO, the TRANSITION SHIFT, and END GAME. During the ALLIANCE SHIFTS, only one ALLIANCE HUB will be active while the other ALLIANCE’S HUB becomes inactive.

The status of both HUBS during the ALLIANCE SHIFTS is based on the results of AUTO. The ALLIANCE that scores the most FUEL during AUTO will have their HUB set to inactive for SHIFT 1 while their opponent’s HUB will be active, as shown in Table 6‑3. HUB statuses will then alternate at the start of each following ALLIANCE SHIFT, until the start of END GAME where both HUBS return to active. If both ALLIANCES score the same number of FUEL during AUTO, the FMS will randomly select an ALLIANCE and use its HUB status order for the ALLIANCE SHIFTS during the MATCH.

Table 6‑3: Hub Status during MATCH Timeframes

AUTO Result:	RED ALLIANCE scores more FUEL during AUTO or is selected by the FMS		BLUE ALLIANCE scores more FUEL during AUTO or is selected by the FMS
MATCH Timeframe (timer values)	RED ALLIANCE HUB status	BLUE ALLIANCE HUB status	RED ALLIANCE HUB status	BLUE ALLIANCE HUB status
AUTO (0:20 – 0:00)	Active	Active	Active	Active
TRANSITION SHIFT (2:20 – 2:10)	Active	Active	Active	Active
SHIFT 1 (2:10 – 1:45)	Inactive	Active	Active	Inactive
SHIFT 2 (1:45 – 1:20)	Active	Inactive	Inactive	Active
SHIFT 3 (1:20 – 0:55)	Inactive	Active	Active	Inactive
SHIFT 4 (0:55 – 0:30)	Active	Inactive	Inactive	Active
END GAME (0:30 – 0:00)	Active	Active	Active	Active

6.5       Scoring

ALLIANCES are rewarded for accomplishing various actions throughout a MATCH, including scoring FUEL, climbing their TOWER, and winning or tying MATCHES.

Rewards are granted either via MATCH points or Ranking Points (often abbreviated to RP, which increase the measure used to rank teams in the Qualification Tournament).

All scores are assessed and updated throughout the MATCH, except as follows:

A.      assessment of FUEL scored in the HUB continues for up to 3 seconds after the ARENA timer displays 0:00 following AUTO.

B.      assessment of FUEL scored in the HUB continues for up to 3 seconds after the ARENA timer displays 0:00 following TELEOP.

C.      assessment of AUTO TOWER points is made after the ARENA timer displays 0:00 following AUTO.

D.      assessment of TELEOP TOWER points is made 3 seconds after the ARENA timer displays 0:00 following TELEOP, or when all ROBOTS have come to rest following the conclusion of the MATCH, whichever happens first.

Assessment of FUEL scored in the HUB continues for 3 seconds after the HUB deactivates to account for FUEL processing time.

6.5.1       SCORING ELEMENT Scoring Criteria

A FUEL is scored in the HUB once it passes through the top opening of the HUB and through the sensor array.

6.5.2       ROBOT Scoring Criteria

To qualify for TOWER points for a given LEVEL, a ROBOT must meet the following conditions:

-        For LEVEL 1 – a ROBOT must no longer be touching the CARPET or the TOWER BASE, or

-        For LEVEL 2 – a ROBOT must be positioned such that its BUMPER covers are completely above the LOW RUNG, or

-        For LEVEL 3 – a ROBOT must be positioned such that its BUMPER covers are completely above the MID RUNG.

Additionally, a ROBOT must be contacting at least one RUNG and/or UPRIGHT and may additionally only contact the following elements:

A.      the TOWER WALL,

B.      support structure,

C.      FUEL, and/or.

D.      another ROBOT.

A ROBOT may only earn TOWER points for LEVEL 1 during AUTO. A ROBOT may only earn TOWER points for a single LEVEL during TELEOP. A ROBOT that earns TOWER points in AUTO is eligible to earn additional TOWER points during TELEOP.

Figure 6‑4: TOWER contact limitation for ROBOT Scoring Criteria

6.5.3       Point Values

Point values for tasks in REBUILT are detailed in Table 6‑4.

Table 6‑4 REBUILT point values

 

Table 6‑5: REBUILT BONUS RP thresholds

 

6.6       Violations

Unless otherwise noted, all violations are assigned for each instance of a rule violation. A description of the penalties is listed in Table 6‑6. All rules throughout the Game Rules section are called as perceived by a REFEREE.

Table 6‑6 Rule violations

6.6.1       YELLOW and RED CARDS

In addition to rule violations explicitly listed throughout this document, YELLOW CARDS and RED CARDS are used in FIRST Robotics Competition to address team and ROBOT behavior that does not align with the mission, values, and culture of FIRST.

The Head REFEREE may assign a YELLOW CARD as a warning, or a RED CARD for egregious behavior inappropriate at a FIRST Robotics Competition event.

If an action resulting in the assignment of a YELLOW or RED CARD is determined to be the result of an ARENA FAULT, per section 10.2, the CARD will be rescinded.

A YELLOW or RED CARD is indicated on the audience display MATCH results screen. During Qualification MATCHES, A YELLOW or RED CARD is indicated next to the team who received the CARD and the Game Announcer describes the violation. During Playoff MATCHES, the card is applied to the whole ALLIANCE and as such “RED CARD" or "YELLOW CARD" appears above the ALLIANCE number.

YELLOW CARDS are additive, meaning that a second YELLOW CARD is automatically converted to a RED CARD. A team is issued a RED CARD for any subsequent incident in which they receive an additional YELLOW CARD, including earning a second YELLOW CARD during a single MATCH. A second YELLOW CARD is indicated by the Head REFEREE holding a YELLOW CARD and RED CARD in the air simultaneously after the completion of the MATCH. A team that has received either a YELLOW CARD or a RED CARD carries a YELLOW CARD into subsequent MATCHES, except as noted below.

Once a team receives a YELLOW or RED CARD, a yellow rectangle will show next to the team number on the audience display during subsequent MATCHES, including any replays.

Figure 6‑5 Example audience screen graphic showing YELLOW CARD indicators

All YELLOW CARDS are cleared in FMS at the conclusion of Practice, Qualification, and division Playoff MATCHES. VERBAL WARNINGS issued by the head REFEREE are cleared after Practice MATCHES and persist from Qualification MATCHES through subsequent tournament phases.

6.6.2       YELLOW and RED CARD application

YELLOW and RED CARDS are applied based on the following:

Table 6‑7: YELLOW and RED CARD application

6.6.3       YELLOW and RED CARDS during Playoff MATCHES

During Playoff MATCHES, YELLOW and RED CARDS are assigned to the violating team’s entire ALLIANCE instead of to only the violating team. If an ALLIANCE receives 2 YELLOW CARDS, the entire ALLIANCE is issued a RED CARD which results in DISQUALIFICATION for the associated MATCH. If both ALLIANCES receive a RED CARD, the ALLIANCE assessed the first RED CARD, chronologically, is DISQUALIFIED and loses the MATCH.

6.6.4       Violation Details

There are several styles of violation wording used in this manual. Below are some example violations and a clarification of the way the violation would be assessed. The examples shown do not represent all possible violations, but rather a representative set of combinations.

Table 6‑8 Violation examples

6.7       Head REFEREE and FTA Interaction

The Head REFEREE has the ultimate authority in the ARENA during the event, but may receive input from additional sources, e.g. Game Designers, FIRST personnel, FTA, and other event staff. The Head REFEREE rulings are final. No event staff, including the Head REFEREE, will review video, photos, artistic renderings, etc. of any MATCH, from any source, under any circumstances.

6.7.1       Question Box (Q)

Each ALLIANCE has a designated Question Box near the scoring table. If a DRIVE TEAM has a question about a MATCH, the FIELD, etc., they may send up to 2 DRIVE TEAM members to their corresponding Question Box. Depending on timing, the Head REFEREE or FTA may postpone any requested discussion until the end of the subsequent MATCH.

Technical questions regarding FIELD or ROBOT operation are addressed by the FTA, and additional team members are invited to participate in these conversations if necessary. If a DRIVE TEAM needs clarification on a ruling or score, per Q101, up to 2 DRIVE TEAM members should address the Head REFEREE after the ARENA Reset Signal (e.g. FIELD lights turn green).

While FMS tracks quantities of MINOR and MAJOR FOULS, FIRST instructs REFEREES to not self-track details about MINOR FOULS and MAJOR FOULS; as a result, REFEREES are not expected to recall details about what MINOR FOULS and MAJOR FOULS were made, when they occurred, and against whom.

Q101       *Head REFEREE Interactions. A team may only address the Head REFEREE with maximum of 2 people, 1 of which must be a STUDENT.

Violation: The Head REFEREE will not address non-compliant team members or peripheral conversations.

Q102       Conversations must be civil. Any team interaction with the Head REFEREE must be appropriate.

Violation: The Head REFEREE may terminate the conversation to allow time for parties to cool down. A person with subsequent violations will not be allowed to interact with the Head REFEREE.

6.8       Other Logistics

SCORING ELEMENTS that leave the FIELD (other than through the opening at the base of the OUTPOST) are placed back into the FIELD approximately at the point of exit by FIELD STAFF (REFEREES, FTAs, or other staff working around the FIELD) at the earliest safe opportunity.

An ARENA FAULT (an error in ARENA operation described in section 10.2 MATCH Replays) is not called for MATCHES that accidentally begin with damaged SCORING ELEMENTS. Damaged SCORING ELEMENTS are not replaced until the next ARENA reset period. DRIVE TEAMS should alert the FIELD STAFF to any missing or damaged SCORING ELEMENTS prior to the start of the MATCH but as noted in 6.3.4, the exact number of FUEL in the NEUTRAL ZONE may vary.

Once the MATCH is over and the Head REFEREE determines that the FIELD is safe for FIELD STAFF and DRIVE TEAMS, they or their designee change the FIELD lights to green and DRIVE TEAMS may retrieve their ROBOT. Some MATCHES may include a short period afterward to allow FIELD staff to begin to clean the field to make it easier and safer for teams to collect their robot. This period is indicated with purple lights on the team signs and the word “clean” displayed. TEAMS are not allowed on the field during this time.

During ARENA reset, the ARENA is cleared of ROBOTS and OPERATOR CONSOLES from the MATCH that just ended, ROBOTS and OPERATOR CONSOLES for the subsequent MATCH are loaded into the ARENA by DRIVE TEAMS, and FIELD STAFF reset ARENA elements.

FIRST Robotics Competition uses 3 words in the context of how durations and actions are assessed with regards to evaluation of rules and assignment of violations. These words provide general guidance to describe benchmarks to be used across the program. It is not the intent for REFEREES to provide a count during the time periods.

-        MOMENTARY describes durations that are fewer than approximately 3 seconds.

-        CONTINUOUS describes durations that are more than approximately 10 seconds.

-        REPEATED describes actions that happen more than once within a MATCH.

7.1       Personal Safety

G101       *Humans, remain outside the FIELD. A team member may not reach into the FIELD with any part of their body during a MATCH .

Violation: VERBAL WARNING. YELLOW CARD if subsequent violations during the event.

G102       *Never step over the guardrail. A team member may only enter or exit the FIELD through open gates and only enter if FIELD lighting (FIELD facing side of the team signs and timers) is green, unless explicitly instructed by a REFEREE or an FTA.

Violation: VERBAL WARNING. YELLOW CARD if subsequent violations during the event.

G103       *Be careful what you interact with. A team member is prohibited from the following actions with regards to interaction with ARENA elements.

A.      climbing on or inside,

B.      hanging from,

C.      manipulating such that it doesn’t return to its original shape without human intervention, and

D.      damaging.

Violation: VERBAL WARNING. YELLOW CARD if subsequent violations during the event.

G104       *Teams may not enable their ROBOTS on the FIELD. Teams may not tether to the ROBOT while on the FIELD except in special circumstances (e.g. after Opening Ceremonies, before an immediate MATCH replay, etc.) and with the express permission from the FTA or a REFEREE.

Violation: VERBAL WARNING. YELLOW CARD if subsequent violations during the event.

7.2       Conduct

G201       *Be a good person. All teams must be civil toward everyone and respectful of team and event equipment while at a FIRST Robotics Competition event.

Violation: VERBAL WARNING. YELLOW CARD if subsequent violations during the event.

G202       *Don’t bang on the glass. A team member may never strike or hit the DRIVER STATION plastic windows.

Violation: VERBAL WARNING. YELLOW CARD if subsequent violations during the event.

G203       *Asking other teams to throw a MATCH – not cool. A team may not encourage an ALLIANCE of which it is not a member to play beneath its ability.

Note: This rule is not intended to prevent an ALLIANCE from planning and/or executing its own strategy in a specific MATCH in which all the teams are members of the ALLIANCE.

Violation: VERBAL WARNING. RED CARD if subsequent violations during the event.

G204       *Letting someone coerce you into throwing a MATCH – also not cool. A team, as the result of encouragement by a team not on their ALLIANCE, may not play beneath its ability.

Note: This rule is not intended to prevent an ALLIANCE from planning and/or executing its own strategy in a specific MATCH in which all the ALLIANCE members are participants.

Violation: VERBAL WARNING. RED CARD if subsequent violations during the event.

 

G205       *Throwing your own MATCH is bad. A team may not intentionally lose a MATCH or sacrifice Ranking Points in an effort to lower their own ranking or manipulate the rankings of other teams.

Violation: VERBAL WARNING. RED CARD if subsequent violations during the event.

G206       *Don't violate rules for RPs. A team or ALLIANCE may not collude with another team to each purposefully violate a rule in an attempt to influence Ranking Points.

Violation: YELLOW CARD and the ALLIANCE is ineligible for the BONUS RPs.

G207       *Don’t abuse ARENA access. A team member (except DRIVERS, HUMAN PLAYERS, and DRIVE COACHES) granted access to restricted areas in and around the ARENA (e.g. via TECHNICIAN button, event issued Media badges, etc.) may not assist or use signaling devices during the MATCH. Exceptions will be granted for inconsequential infractions and in cases concerning safety.

Violation: VERBAL WARNING. YELLOW CARD if subsequent violations during the event.

G208       *Show up to your Qualification MATCHES. If a ROBOT has passed initial, complete inspection, at least 1 member of its DRIVE TEAM must report to the ARENA and participate in each of their assigned Qualification MATCHES.

Violation: DISQUALIFIED from the current MATCH.

G209       *Keep your ROBOT together. A ROBOT may not intentionally detach or leave a part on the FIELD.

Violation: RED CARD.

G210       *Don’t expect to gain by doing others harm. A strategy not consistent with standard gameplay and clearly aimed at forcing the opponent ALLIANCE to violate a rule is not in the spirit of FIRST Robotics Competition and not allowed. Rule violations forced in this manner will not result in an assignment of a penalty to the targeted ALLIANCE.

Violation: MAJOR FOUL. YELLOW CARD if REPEATED.

G211       *Egregious or exceptional violations. Egregious behavior beyond what is listed in the rules or subsequent violations of any rule or procedure during the event is prohibited.

In addition to rule violations explicitly listed in this manual and witnessed by a REFEREE, the Head REFEREE may assign a YELLOW or RED CARD for egregious ROBOT actions or team member behavior at any time during the event.

Please see section 6.6.1 YELLOW and RED CARDS for additional detail.

Violation: YELLOW or RED CARD.

G212       *All teams can play. A team may not encourage another team to exclude their ROBOT or be BYPASSED from a qualification MATCH for any reason.

Violation: YELLOW CARD. RED CARD if the ROBOT does not participate in the MATCH.

7.3       Pre-MATCH

G301       *Be prompt. A DRIVE TEAM member may not cause significant delays to the start of their MATCH. Causing a significant delay requires both of the following to be true:

A.      The expected MATCH start time has passed, and

B.      The DRIVE TEAM has access to the FIELD and is neither MATCH ready nor making a good faith effort, to quickly become MATCH ready.

Violation: If a Qualification MATCH, VERBAL WARNING. MAJOR FOUL for the upcoming MATCH if a subsequent violation occurs within the tournament phase. If the DRIVE TEAM is not MATCH ready within 2 minutes of the VERBAL WARNING/MAJOR FOUL and the Head REFEREE perceives no good faith effort by the DRIVE TEAM to quickly become MATCH ready, DISABLED.

If a Playoff MATCH, VERBAL WARNING issued to the ALLIANCE. MAJOR FOUL for the ALLIANCE’S upcoming MATCH if a subsequent violation occurs within the tournament phase. If the ALLIANCE is not MATCH ready within 2 minutes of the VERBAL WARNING/MAJOR FOUL having been issued to all 3 teams and the Head REFEREE perceives no good faith effort by the DRIVE TEAM(s) to quickly become MATCH ready, the offending team’s ROBOT is DISABLED.

G302       *Limit what you use during a MATCH. Items used during a match must fit on your team’s DRIVER STATION shelf, be worn or held by members from your DRIVE TEAM, or be an item used as an accommodation (e.g. stools, crutches, etc.). Regardless of if the equipment fits the criteria above, it may not:

A.      be employed in a way that introduces a safety hazard,

B.      extend more than 78.0in (1.981m) above the floor,

C.      communicate with anything or anyone outside of the ARENA with the exception of medically required equipment,

D.      block visibility for FIELD STAFF or audience members, or

E.      jam or interfere with the remote sensing capabilities of another team or the FIELD.

Exceptions to part B are granted for momentary extensions above 78.0in (1.91m) and for individuals above 78.0in (1.91m) wearing PPE or reasonable decorative apparel such as hats, headbands, etc.

Violation: MATCH will not start until the situation is remedied. If discovered or used inappropriately during a MATCH, YELLOW CARD.

G303       *Start your ROBOTS. A ROBOT must meet all following MATCH-start requirements:

A.      it does not pose a hazard to humans, FIELD elements, or other ROBOTS,

B.      has passed initial, complete inspection, i.e. it’s compliant with all ROBOT rules (for exceptions regarding Practice MATCHES, see section 9 Inspection & Eligibility (I),

C.      if modified after initial Inspection, it’s compliant with I104,

D.      its BUMPERS overlap their ROBOT STARTING LINE,

E.      it’s not contacting the BUMP,

F.      it’s the only team-provided item left on the FIELD,

G.     it’s not attached to, entangled with, or suspended from any FIELD element,

H.     it’s confined to its STARTING CONFIGURATION (reference R102 and R104), and

I.        it fully and solely supports not more than 8 FUEL (as described in section 6.3.4 SCORING ELEMENTS).

Violation: If fix is a quick remedy, the MATCH won’t start until all requirements are met. If it is not a quick remedy, DISABLED and, at the discretion of the Head REFEREE, must be re-inspected. If a ROBOT not compliant with part B or C participates, its team receives a RED CARD.

 

 

 

7.4       In-MATCH

Rules in this section pertain to game play once a MATCH begins.

7.4.1       AUTO

The AUTO period is the first 20 seconds of the MATCH, and the FMS blocks any DRIVER control, so ROBOTS operate with only their pre-programmed instructions. Rules in this section apply only during the AUTO period.

G401       *Behind the lines. In AUTO, each DRIVE TEAM member must remain in their staged areas. A DRIVE TEAM member staged behind a HUMAN STARTING LINE may not contact anything in front of that HUMAN STARTING LINE, unless for personal or equipment safety, to press the E-Stop or A-Stop, or granted permission by a Head REFEREE or FTA.

Violation: MINOR FOUL regardless of the number of items contacted.

G402       *Let the ROBOT do its thing. In AUTO, a DRIVE TEAM member may not directly or indirectly interact with a ROBOT or an OPERATOR CONSOLE unless for personal safety, OPERATOR CONSOLE safety, or pressing an E-Stop or A-Stop. A HUMAN PLAYER entering FUEL onto the FIELD is an exception to this rule.

Violation: MINOR FOUL and YELLOW CARD.

G403       Limited AUTO opponent interaction. In AUTO, a ROBOT whose BUMPERS are completely across the CENTER LINE (i.e. to the opposite side of the CENTER LINE from its ROBOT STARTING LINE) may not contact an opponent ROBOT.

Violation: MAJOR FOUL.

7.4.2       SCORING ELEMENTS

G404       *ROBOTS: use SCORING ELEMENTS as directed. A ROBOT may not deliberately use a SCORING ELEMENT in an attempt to ease or amplify a challenge associated with a FIELD element.

Violation: MAJOR FOUL.

G405       *Keep SCORING ELEMENTS in bounds. A ROBOT may not intentionally eject SCORING ELEMENTS from the FIELD (either directly or by bouncing off a FIELD element or other ROBOT) with an exception of through the opening at the base of the OUTPOST.

Violation: MINOR FOUL. If REPEATED, MAJOR FOUL.

G406       *Don’t abuse SCORING ELEMENTS. Neither a ROBOT nor a HUMAN PLAYER may damage a SCORING ELEMENT.

Violation: VERBAL WARNING. MAJOR FOUL if REPEATED in any subsequent MATCHES during the event. If via a ROBOT and the Head REFEREE determines that further damage is likely to occur, DISABLED. Corrective action (such as eliminating sharp edges, removing the damaging MECHANISM, and/or re-inspection) may be required before the ROBOT may compete in subsequent MATCHES.

G407       Only score while in your ALLIANCE ZONE. A ROBOT may not launch a SCORING ELEMENT into their HUB unless their BUMPERS are partially or fully within their ALLIANCE ZONE.

Violation: MAJOR FOUL

G408       Don’t catch FUEL. A ROBOT may not do either of the following with FUEL released by the HUB unless and until that FUEL contacts anything else besides that ROBOT or FUEL CONTROLLED by that ROBOT:

A.      gain greater than MOMENTARY CONTROL of FUEL, or

B.      push or redirect FUEL to a desired location or in a preferred direction.

A ROBOT is in CONTROL of a SCORING ELEMENT if the SCORING ELEMENT is fully supported by or stuck in, on, or under the ROBOT.

Violation: MINOR FOUL. If strategic, MAJOR FOUL and YELLOW CARD.

7.4.3       ROBOT

G409       *ROBOTS must be safe. A ROBOT may not pose an undue hazard to a human, an ARENA element, or another ROBOT in the following ways:

A.      the ROBOT or anything it CONTROLS, e.g. FUEL, contacts anything outside the FIELD except for MOMENTARY contact inside the CHUTE and/or the CORRAL,

B.      its BUMPERS fail such that a segment completely detaches,

C.      a corner of its ROBOT PERIMETER is exposed,

D.      its team number or ALLIANCE color are indeterminate,

E.      its BUMPERS leave the BUMPER ZONE (see R405) REPEATEDLY or for more than a MOMENTARY amount of time, or

F.      its operation or design is dangerous or unsafe.

Violation: DISABLED. Corrective action (such as repair of BUMPERS, removing the unsafe MECHANISM, and/or re-inspection) may be required before the ROBOT will be allowed to compete in subsequent MATCHES.

G410       *Keep your BUMPERS low. ROBOT extensions may not interact with the carpet, BUMPS, or TOWER BASE such that the BUMPERS are lifted out of the BUMPER ZONE (see R405).

Violation: MINOR FOUL. Corrective action (such as removing the offending MECHANISM, and/or re-inspection) may be required before the ROBOT will be allowed to compete in subsequent MATCHES.

G411       Don’t damage the FIELD. A ROBOT may not damage FIELD elements.

Violation: VERBAL WARNING. If the Head REFEREE infers that additional damage is likely, DISABLED. YELLOW CARD for any subsequent damage during the event.

Corrective action (such as eliminating sharp edges, removing the damaging MECHANISM, and/or re-inspection) may be required before the ROBOT will be allowed to compete in subsequent MATCHES.

G412       Watch your FIELD interaction. A ROBOT is prohibited from the following interactions with FIELD elements (with the exception of the RUNGS and UPRIGHTS):

A.      grabbing,

B.      grasping,

C.      attaching to (including the use of a vacuum or hook fastener to anchor to the FIELD carpet),

D.      becoming entangled with, and

E.      suspending from.

Violation: MAJOR FOUL, plus YELLOW CARD if REPEATED, or longer than MOMENTARY. If the Head REFEREE infers that damage is likely, DISABLED. Corrective action (such as removing the offending MECHANISM, and/or re-inspection) may be required before the ROBOT will be allowed to compete in subsequent MATCHES.

G413       Expansion limits. A ROBOT may not extend beyond any of the horizontal or vertical expansion limits described in R105, R106, and R107.

If the over-expansion is due to damage and not used for strategic benefit, it is an exception to this rule, and no penalty is imposed.

Violation: MINOR FOUL, or MAJOR FOUL if the over-expansion is used for strategic benefit, including if it impedes or enables a scoring action. Corrective action (such as removing the offending MECHANISM, and/or re-inspection) may be required before the ROBOT will be allowed to compete in subsequent MATCHES.

G414       Don’t Climb on each other. ROBOTS may not fully support the weight of other ROBOTS on their ALLIANCE to climb the TOWER.

Violation: Supported ROBOTS become ineligible for TOWER points for the remainder of the MATCH.

7.4.4       Opponent Interaction

Note, G415, G416, G417 are mutually exclusive. A single ROBOT to ROBOT interaction which violates more than 1 of these rules results in the most punitive penalty, and only the most punitive penalty, being assessed.

G415       *Stay out of other ROBOTS. A ROBOT may not use a COMPONENT outside its ROBOT PERIMETER (except its BUMPERS) to initiate contact with an opponent ROBOT inside the vertical projection of the opponent’s ROBOT PERIMETER. Contact with an opponent in an opening of their BUMPERS or in the space above the BUMPER opening are exceptions to this rule.

Violation: MINOR FOUL.

G416       *This isn’t combat robotics. A ROBOT may not damage or functionally impair an opponent ROBOT in either of the following ways:

A.      deliberately.

B.      regardless of intent, by initiating contact, either directly or transitively via a SCORING ELEMENT CONTROLLED by the ROBOT, inside the vertical projection of an opponent’s ROBOT PERIMETER. Contact between the ROBOT’S BUMPERS or COMPONENTS inside the ROBOT PERIMETER and COMPONENTS inside an opening of an opponent’s BUMPERS or in the space above the BUMPER opening are exceptions to this rule.

Damage or functional impairment because of contact with a tipped-over opponent ROBOT, which is not perceived by a REFEREE to be deliberate, is not a violation of this rule.

Violation: MAJOR FOUL and YELLOW CARD, or if opponent ROBOT is unable to drive, then MAJOR FOUL and RED CARD.

G417       *Don’t tip or entangle. A ROBOT may not deliberately, attach to, tip, or entangle with an opponent ROBOT.

Violation: MAJOR FOUL and YELLOW CARD, or if CONTINUOUS or opponent ROBOT is unable to drive, then MAJOR FOUL and RED CARD.

G418       *There’s a 3-count on PINS. A ROBOT may not PIN an opponent’s ROBOT for more than 3 seconds. A ROBOT is PINNING if it is preventing the movement of an opponent ROBOT by contact, either direct or transitive (such as against a FIELD element). A PIN count ends once any of the following criteria below are met:

A.      the ROBOTS have separated by at least 72.0in (1.83m) from each other for more than 3 seconds,

B.      either ROBOT has moved 72.0in (1.83m) from where the PIN initiated for more than 3 seconds, or

C.      the PINNING ROBOT gets PINNED.

For criteria A, the PIN count pauses once ROBOTS are separated by 72.0in (1.83m) until either the PIN ends or the PINNING ROBOT moves back within 72.0in (1.83m), at which point the PIN count is resumed.

For criteria B, the PIN count pauses once either ROBOT has moved 72.0in (1.83m) from where the PIN initiated until the PIN ends or until both ROBOTS move back within 72.0in (1.83m), at which point the PIN count is resumed.

Violation: MINOR FOUL, and for every 3 seconds in which the situation is not corrected, a MAJOR FOUL is assessed.

G419       *Don’t collude with your partners to shut down major parts of game play. 2 or more ROBOTS that appear to a REFEREE to be working together may not isolate or close off any major element of MATCH play.

Violation: MAJOR FOUL, and for every 3 seconds in which the situation is not corrected, a MAJOR FOUL is assessed.

G420       TOWER protection. A ROBOT may not contact, directly or transitively through a SCORING ELEMENT, an opponent ROBOT in contact with an opponent TOWER during the last 30 seconds of the MATCH regardless of who initiates contact.

Violation: MAJOR FOUL and if the opponent ROBOT is off the ground the opponent ROBOT is awarded LEVEL 3 TOWER points.

7.4.5       Human

G421       *No wandering. A DRIVE TEAM member must remain in their designated area as follows:

A.      DRIVERS and DRIVE COACHES may not contact anything outside their ALLIANCE AREA,

B.      a DRIVER must use the OPERATOR CONSOLE in the DRIVER STATION to which they are assigned, as indicated on the team sign,

C.      a HUMAN PLAYER may not contact anything outside their ALLIANCE AREA, and

D.      a TECHNICIAN may not contact anything outside their designated area.

Exceptions are granted as follows:

E.      for a HUMAN PLAYER partially outside the ALLIANCE AREA,

F.      in cases concerning safety, and

G.     for actions that are inadvertent, MOMENTARY, and inconsequential.

Violation: MINOR FOUL.

G422       *DRIVE COACHES and other teams: hands off the controls. A ROBOT shall be operated only by the DRIVERS and/or HUMAN PLAYERS of that team. A DRIVE COACH activating their E-Stop or A-Stop is the exception to this rule.

Violation: MAJOR FOUL. RED CARD if greater-than-MOMENTARY.

G423       *DRIVE TEAMS, watch your reach. A DRIVE TEAM member may not extend:

A.      into the CHUTE beyond the ALLIANCE-colored tape line while the CHUTE DOOR is open, or

B.      into the CORRAL beyond the ALLIANCE-colored tape line. 

Violation: MINOR FOUL.

G424       *Humans: use SCORING ELEMENTS as directed. A DRIVE TEAM member may not deliberately use a SCORING ELEMENT in an attempt to ease or amplify a challenge associated with a FIELD element. 

Violation: MAJOR FOUL.

G425       *SCORING ELEMENT delivery. FUEL may only be introduced to the FIELD by a HUMAN PLAYER or DRIVER in the following ways:

A.      through the CHUTE,

B.      through the bottom opening in the OUTPOST, or

C.      thrown from the OUTPOST AREA.

Violation: MAJOR FOUL.

G426       *DRIVE COACHES, SCORING ELEMENTS are off limits. DRIVE COACHES may not touch SCORING ELEMENTS, unless for safety purposes.

Violation: MINOR FOUL.

G427       The OUTPOST has a storage limit. Off-FIELD FUEL may only be stored in the CHUTE and the CORRAL. Excess FUEL, defined as the CHUTE & CORRAL being full, must immediately be entered onto the FIELD.

HUMAN PLAYERS making a good-faith effort to immediately move or enter additional FUEL is an exception to this rule.

Violation: MINOR FOUL, and if CONTINUOUS, a MAJOR FOUL is assessed.

7.5       Post-MATCH

G501       *Leave promptly. A DRIVE TEAM member may not cause significant or multiple delays to the start of a subsequent MATCH, scheduled break content, or other FIELD activities.

Violation: VERBAL WARNING. YELLOW CARD if subsequent violations at any point during the event.

 

The rules listed below explicitly address legal parts and materials and how those parts and materials may be used on a REBUILT ROBOT. A ROBOT is an electromechanical assembly built by the FIRST Robotics Competition team to play the current season’s game and includes all the basic systems required to be an active participant in the game –power, communications, control, BUMPERS, and movement about the FIELD. A BUMPER is a protective assembly designed to attach to the exterior of the ROBOT and constructed as specified in section 8.4 BUMPER Rules.

There are many reasons for the structure of the rules, including safety, reliability, parity, creation of a reasonable design challenge, adherence to professional standards, impact on the competition, and compatibility with the Kit of Parts (KOP). The KOP is the collection of items listed on the current season’s Kickoff Kit Checklists, distributed to the team via FIRST Choice in the current season, or paid for completely (except shipping) with a Product Donation Voucher (PDV) from the current season.

Another intent of these rules is to have all energy sources and active actuation systems on the ROBOT (e.g. batteries, compressors, motors, servos, cylinders, and their controllers) drawn from a well-defined set of options. This is to ensure that all teams have access to the same actuation resources and that the INSPECTORS are able to accurately and efficiently assess the legality of a given part.

ROBOTS are made up of COMPONENTS and MECHANISMS. A COMPONENT is any part in its most basic configuration, which cannot be disassembled without damaging or destroying the part or altering its fundamental function. A MECHANISM is an assembly of COMPONENTS that provide specific functionality on the ROBOT. A MECHANISM can be disassembled (and then reassembled) into individual COMPONENTS without damage to the parts.

Many rules in this section reference Commercial-Off-The-Shelf (COTS) items. A COTS item must be a standard (i.e. not custom order) part commonly available from a VENDOR for all teams for purchase. To be a COTS item, the COMPONENT or MECHANISM must be in an unaltered, unmodified state (with the exception of installation or modification of any software). Items that are no longer commercially available but are functionally equivalent to the original condition as delivered from the VENDOR are considered COTS and may be used.

A VENDOR is a legitimate business source for COTS items that satisfies all the following criteria:

A.      has a Federal Tax Identification number. In cases where the VENDOR is outside of the United States, they must possess an equivalent form of registration or license with the government of their home nation that establishes and validates their status as a legitimate business licensed to operate within that country.

B.      is not a “wholly owned subsidiary” of a FIRST Robotics Competition team or collection of teams. While there may be some individuals affiliated with both a team and the VENDOR, the business and activities of the team and VENDOR must be completely separable.

C.      should maintain sufficient stock or production capability so they are able to ship any general (i.e., non-FIRST unique) product within 5 business days of receiving a valid purchase request. It is recognized that certain unusual circumstances (such as such as a global supply chain disruption and/or 1,000 FIRST teams all ordering the same part at once from the same VENDOR) may cause atypical delays in shipping due to backorders for even the largest VENDORS. Such delays due to higher-than-normal order rates are excused. This criterion may not apply to custom-built items from a source that is both a VENDOR and a fabricator.

D.      makes their products available to all FIRST Robotics Competition teams. A VENDOR must not limit supply or make a product available to just a limited number of FIRST Robotics Competition teams.

A FABRICATED ITEM is any COMPONENT or MECHANISM that has been altered, built, cast, constructed, concocted, created, cut, heat treated, machined, manufactured, modified, painted, produced, surface coated, or conjured partially or completely into the final form in which it will be used on the ROBOT.

Teams may be asked to provide documentation proving the legality of non-REBUILT KOP items during inspection where a rule specifies limits for a legal part (e.g. pneumatic items, current limits, COTS electronics, etc.).

Some of these rules make use of English unit requirements for parts. If your team has a question about a metric-equivalent part’s legality, please e-mail your question to the FIRST Robotics Competition Kit of Parts team at frcparts@firstinspires.org for an official ruling. To seek approval for alternate devices for inclusion in future FIRST Robotics Competition seasons, please contact the Kit of Parts team at frcparts@firstinspires.org with item specifications.

Teams should acknowledge the support provided by the corporate sponsors and mentors with an appropriate display of their school and sponsors names and/or logos (or the name of the supporting youth organization, if appropriate).

FIRST Robotics Competition can be a full-contact competition and may include rigorous game play. While the rules aim to limit severe damage to ROBOTS, teams should design their ROBOTS to be robust.

 

8.1       General ROBOT Design

R101       *ROBOT PERIMETER must be fixed. The ROBOT (excluding BUMPERS) must have a ROBOT PERIMETER, contained within the BUMPER ZONE and established while in the ROBOT’S STARTING CONFIGURATION, that is comprised of fixed, non-articulated structural elements of the ROBOT. Minor protrusions no greater than 0.25in (0.64cm) such as bolt heads, fastener ends, weld beads, and rivets are not considered part of the ROBOT PERIMETER.

R102       *STARTING CONFIGURATION – no overhang. In the STARTING CONFIGURATION (the physical configuration in which a ROBOT starts a MATCH), no part of the ROBOT shall extend outside the vertical projection of the ROBOT PERIMETER, with the exception of its BUMPERS and minor protrusions such as bolt heads, fastener ends, rivets, cable ties, etc.

R103       *ROBOT weight limit. The ROBOT weight must not exceed 115.0lb (52.16kg). When determining weight, the basic ROBOT structure and all elements of all additional MECHANISMS that might be used in a single configuration of the ROBOT shall be weighed together (see I103).
For the purposes of determining compliance with the weight limitations, the following items are excluded:

A.      ROBOT BUMPERS,

B.      ROBOT battery and its associated half of the Anderson cable quick connect/disconnect pair (including wire, the associated cable lugs, connecting bolts, and insulation), and

C.      tags used for location detection systems if provided by the event.

R104       STARTING CONFIGURATION – max size. A ROBOT’S STARTING CONFIGURATION may not have a ROBOT PERIMETER greater than 110.0in (2.794m) and may not be more than 30in (76.2cm) tall.

R105       ROBOT horizontal extension limit. ROBOTS may not extend more than 12in (30.48cm) beyond the vertical projection of their ROBOT PERIMETER.

Figure 8‑2 ROBOT PERIMETER extension

R106       Horizontal extension – one direction at a time. ROBOTS may not extend beyond their ROBOT PERIMETER in more than one direction (i.e. over more than 1 side of the ROBOT) at a time. The extension may not reach outside the projection of that side of the ROBOT PERIMETER.
For the purposes of this rule, a round or circular section of ROBOT PERIMETER is considered to have an infinite number of sides. Exceptions include:

A.      BUMPERS

B.      Minor protrusions excluded from the ROBOT PERIMETER per R101

C.      MOMENTARY and inconsequential extensions in multiple directions

 

 

 

R107       ROBOT vertical extension limit. ROBOTS may not extend such that their total height exceeds 30.0in (76.2cm).

R108       ROBOT extension floor interaction ROBOT extensions may not interact with the carpet, BUMPS, or TOWER BASE such that the BUMPERS are lifted out of the BUMPER ZONE (see R405).

8.2       ROBOT Safety & Damage Prevention

R201       *No digging into carpet. Traction devices must not have surface features that could damage the ARENA (e.g. metal, sandpaper, inflexible studs, cleats, hook-loop fasteners or similar attachments). Traction devices include all parts of the ROBOT that are designed to transmit any propulsive and/or braking forces between the ROBOT and FIELD carpet.

R202       *No exposed sharp edges. Protrusions from the ROBOT and exposed surfaces on the ROBOT shall not pose hazards to the ARENA elements (including SCORING ELEMENTS) or people.

R203       *General safety. ROBOT parts shall not be made from hazardous materials, be unsafe, cause an unsafe condition, or interfere with the operation of other ROBOTS.

R204       *Leave SCORING ELEMENTS at the FIELD. ROBOTS must allow removal of SCORING ELEMENTS from the ROBOT and the ROBOT from FIELD elements while DISABLED and powered off.

R205       *Don’t contaminate the FIELD. Liquids, gels, greases and fine particles must not contaminate the FIELD or other ROBOTS.

R206       *Don’t damage SCORING ELEMENTS. ROBOT elements likely to come in contact with a SCORING ELEMENT shall not pose a significant hazard to the SCORING ELEMENT.

8.3       Budget Constraints & Fabrication Schedule

R301       *Individual item cost limit. No individual, non-KOP item or software shall have a Fair Market Value (FMV) that exceeds $600 USD. The total cost of COMPONENTS purchased in bulk may exceed $600 USD as long as the cost of an individual COMPONENT does not exceed $600 USD.

R302       *MAJOR MECHANISM, from this year only. MAJOR MECHANISMS, as defined in I101, created before Kickoff are not permitted.

R303       *Create new designs and software, unless they’re public. ROBOT software and designs created before Kickoff are only permitted if the source files (complete information sufficient to produce the design) are available publicly prior to Kickoff.

8.4       BUMPER Rules

A BUMPER is a required assembly which attaches to the ROBOT frame. BUMPERS protect ROBOTS from damaging/being damaged by other ROBOTS and FIELD elements.

A BUMPER guide providing additional information on materials and design based on historical best practices may be found under the Mechanical Resources section of the Technical Resources page. Teams may also reference the KitBot Instructions for a detailed step-by-step on how to build bumpers for the KitBot.

All dimensions specified in this section are nominal and will be measured during inspection with a tolerance of 0.25in (0.63cm) unless otherwise specified. This means that maximums specified have a tolerance of +0.25in (0.63cm) and minimums specified have a tolerance of –0.25in (0.63cm). Teams are encouraged to design to the nominal dimension and reserve the tolerance for unexpected deviation such as manufacturing error or tolerance stack-up.

R401       *BUMPERS almost all around. ROBOTS are required to use BUMPERS to protect the entire ROBOT PERIMETER. Gaps of less than 1.25in (3.17cm) between adjacent segments are permitted as long as all corners are filled per R406. A single gap larger than 1.25in (3.17cm) is permitted, as long as at least 5.0in (12.7cm) of ROBOT PERIMETER on each side of each corner is protected by BUMPER.

Figure 8‑4 BUMPER coverage requirements

R402       *BUMPER construction. BUMPERS must consist of the following:

A.      Padding – A minimum of 2.25in (5.72cm) depth of foam padding, at least 4.5in (11.43cm) tall consisting of solid blocks, sheets, or stacked rods of one or more of the following materials:

                                                         i.      Solid pool noodles or backer rod

                                                       ii.      Solid polyethylene closed cell foam (including crosslinked) with density between 1.5 and 3.0lb/ft³ (24.03 to 48.05kg/m³)

                                                     iii.      Solid EVA closed cell foam with density between 2.0 and 6.0lb/ft³ (32.04 to 96.11kg/m³)

                                                     iv.      Foam floor tiles

Multiple types, shapes, and/or layers of foam may be used within a single BUMPER.

B.      Backing – A backer at least 4.5in (11.43cm) tall which supports the padding (i.e. padding is not cantilevered other than in corners) and facilitates installation and removal of the BUMPER from the ROBOT (as noted in R410). Additional elements may be added to strengthen the backing, fill space between the BUMPER and ROBOT frame, serve as part of the attachment system, or for any other purpose.

Figure 8‑5 BUMPER backing supporting padding (cross section)

C.      Cover – Cloth (as noted in R411) which covers all outward, upward and downward facing surfaces of padding such that no padding is exposed to interaction with the FIELD or other ROBOTs.

D.      Fastening System – BUMPERS must attach to the ROBOT PERIMETER with a rigid fastening system to form a tight, robust connection to the main structure/frame (e.g. not attached with hook-and-loop tape, tape, or cable ties). The fastening system must be designed to withstand vigorous game play. All removable fasteners (e.g. bolts, locking pins, quick release pins, etc.) may be considered part of either the BUMPERS or ROBOT for determination of weight per R103 and R408.

Figure 8‑6 BUMPER Cross Section Example

-       

R403       *BUMPER extension limit. BUMPERS must not extend more than 4.0in (10.16cm) from the ROBOT PERIMETER.

Figure 8‑7 BUMPER Extension Limit

R404       *BUMPERS must be soft. Hard parts of BUMPERS must not extend more than 1.25in (3.17cm) out from the ROBOT PERIMETER. Only padding (per R402-A), cover (per R402-C, including any coatings or markings), and soft fasteners used to secure padding or cover are permitted beyond this limit. Padding must extend at least 2.0in (5.08cm) beyond any hard parts of the BUMPER. There is no limit on how far BUMPER hard parts may extend inside the ROBOT PERIMETER.

Figure 8‑8 BUMPER Hard Parts Limit

R405       *BUMPERS interact with BUMPERS. While navigating the FIELD normally, all BUMPERS must have padding (per R402-A) supported by backing (per R402-B) entirely filling the BUMPER ZONE, a space between 2.5in (6.35cm) and 5.75in (14.61cm) from the floor.

Figure 8‑9 BUMPER ZONE examples

 

R406       *Fill BUMPER corners. Corner joints between BUMPERS must be filled with uncompressed padding material extending at least 2.25in (5.72cm) from the corner with no gaps or voids. Examples of implementation are shown in Figure 8‑10.

Figure 8‑10 Uncompressed corner padding

  

R407       *BUMPERS shouldn’t be wedges. BUMPERS must not act as wedges when interacting with other BUMPERS.

R408       *Weight limit with BUMPERS. The total weight of the ROBOT (as described in R103) with BUMPERS must not exceed 135.0lb (61.23kg)

 

 

R409       *BUMPERS should be passive. BUMPERS must be fixed relative to the ROBOT PERIMETER. BUMPERS may not contain any elements which move during the MATCH or electrical elements.

R410       *BUMPERS must come off. BUMPERS must be designed for installation and removal to facilitate inspection and weighing.

R411       *BUMPERS indicate your ALLIANCE. Each ROBOT must be able to display red or blue BUMPER covers to reflect their ALLIANCE color, as assigned in the MATCH schedule distributed at the event (as described in section 10.1 MATCH Schedules). Contrasting markings on outward, upward, or downward facing surfaces of the BUMPER cover, other than the following, are prohibited:

A.      those required per R412,

B.      hook-and-loop tape, snap fasteners, or functional equivalents backed by the hard parts of the BUMPER,

C.      solid white FIRST logos between 4.75in (12.06cm) and 5.25in (13.33cm) wide (i.e. comparable to those available in the REBUILT Virtual Kit), and

D.      narrow areas of underlying cloth exposed at seams, corners, or folds.

R412       *Team number on BUMPERS. Team numbers must be displayed and positioned on the BUMPER cover in at least 3 locations approximately 90 degrees apart such that an observer walking around the perimeter of the ROBOT can unambiguously tell the team’s number from most points of view, from as far as approximately 720.0in (18.29m). Team numbers must meet the following additional criteria:

A.      consist of only white Arabic numerals at least 3.75in (9.53cm) high, at least 0.5in (1.27cm) in stroke width,

B.      must not wrap around sharp corners (less than 135.0°) of the ROBOT PERIMETER,

C.      must not split individual digits such that the team number is ambiguous, and

D.      may not substitute logos or icons for numerals.

 

8.5       Motors & Actuators

R501       *Allowable motors. The only motors and actuators permitted include the following (in any quantity):

Table 8‑1 Motor allowances

R502       *Only 4 propulsion motors. A ROBOT may not have more than 4 propulsion motors. A propulsion motor is a motor that enables the ROBOT to move around the FIELD surface (i.e., carpet). Motors that generate small amounts of thrust as a secondary or incidental feature are not considered propulsion motors.

R503       *Don’t modify motors (mostly). The integral mechanical and electrical system of any motor must not be modified. Motors, servos, and electric solenoids used on the ROBOT shall not be modified in any way, except as follows:

A.      The mounting brackets and/or output shaft/interface may be modified to facilitate the physical connection of the motor to the ROBOT and actuated part.

B.      The electrical leads may be trimmed to length as necessary and connectors or splices to additional wiring may be added.

C.      The locking pins on the window motors (P/N 262100-3030 and 262100-3040) may be removed.

D.      The connector housings on KOP automotive motors listed in Table 8‑1 may be modified to facilitate lead connections.

E.      Servos may be modified as specified by the manufacturer (e.g. re-programming or modification for continuous rotation).

F.      Minimal labeling may be applied to indicate device purpose, connectivity, functional performance, etc.

G.     Any number of #10-32 plug screws may be removed from the Falcon 500 and the Kraken X60.

H.     Insulation may be applied to electrical terminals.

I.        Repairs, provided the original performance and specifications are unchanged.

J.      Maintenance recommended by the manufacturer.

R504       *Power (most) actuators off of approved devices. With the exception of servos, fans, or motors integral to sensors of COTS computing devices permitted in R501, each actuator must be controlled by a power regulating device. The only power regulating devices for actuators permitted on the ROBOT include:

A.      motor controllers:

a.      Koors40 Motor Controller (P/N am-5600),

b.      Spark Flex Motor Controller (P/N REV-11-2159, am-5276)

c.      Spark Motor Controller (P/N REV-11-1200, am-4260),

d.      Spark MAX Motor Controller (P/N REV-11-2158, am-4261),

e.      Talon FX Motor Controller (P/N 217-6515, 19-708850, am-6515, am-6515_Short, WCP-0940, WCP-0941) for controlling integral Falcon 500, Kraken X60, Kraken X44 only,

f.        Talon FXS Motor Controller (P/N 24-708883, WCP-1692)

g.      Talon Motor Controller (P/N CTRE_Talon, CTRE_Talon_SR, and am-2195),

h.      Talon SRX Motor Controller (P/N 217-8080, am-2854, 14-838288),

i.         Thrifty Nova (P/N TTB-0100),

j.         Venom Motor with Controller (P/N BDC-10001) for controlling integral motor only,

k.       Victor SP Motor Controller (P/N 217-9090, am-2855, 14-868380), and

l.         Victor SPX Motor Controller (P/N 217-9191, 17-868388, am-3748).

B.      relay modules:

a.      Spike H-Bridge Relay (P/N 217-0220 and SPIKE-RELAY-H),

b.      Automation Direct Relay (P/N AD-SSR6M12-DC-200D, AD-SSRM6M25-DC-200D, AD-SSR6M40-DC-200D), and

c.      Power Distribution Hub (PDH) switched channel (P/N REV-11-1850) for controlling non-actuator CUSTOM CIRCUITS only.

C.      pneumatics controllers:

a.      Pneumatics Control Module (P/N am-2858, 217-4243) and

b.      Pneumatic Hub (P/N REV-11-1852).

D.      servo controllers:

a.      Servo Hub (P/N REV-11-1855)

R505       *Don’t overload controllers. Each power regulating device may control electrical loads per Table 8‑2. Unless otherwise noted, each power regulating device shall control 1 and only 1 electrical load.

Table 8‑2 Power regulating device allotments

R506       *Control servos safely. Servos must be connected to, and only to, 1 of the following:

A.      PWM ports on the roboRIO,

B.      PWM ports on a WCP Spartan Sensor Board (P/N WCP-0045),

C.      REV Robotics Servo Power Module (P/N REV-11-1144), or

D.      REV Robotics Servo Hub (P/N REV-11-1855).

8.6       Power Distribution

In order to maintain safety, the rules in this section apply at all times while at the event, not just while the ROBOT is on the FIELD for MATCHES.

R601       *Battery limit – everyone has the same power. The only legal source of electrical energy for the ROBOT during the competition, the ROBOT battery, must be 1 and only 1 non-spillable sealed lead acid (SLA) battery with the following specifications:

A.      Nominal voltage: 12V

B.      Nominal capacity at 20-hour discharge rate: minimum 17Ah, maximum 18.2Ah

C.      Shape: Rectangular

D.      Nominal Dimensions: 7.1in x 3.0in x 6.6in, +/- 0.1in for each dimension (18.03cm x 7.62cm x 16.76cm, +/-0.25cm for each dimension)

E.      Nominal weight: 11.0lb to 14.5lb (4.99kg to 6.57kg)

F.      Terminals: Nut and bolt style

G.     Battery vents must not be obstructed.

R602       *Other batteries for cameras or computers only. COTS USB battery packs with a capacity of 100Wh or less (27000mAh at 3.7V) with 5V/5A max output or 12V/5A max output using USB-PD per port, batteries integral to and part of a COTS computing device or self-contained camera (e.g. laptop batteries, GoPro style camera, etc.), or batteries used to power CMOS/RTC features may be used to power COTS computing devices and any peripheral COTS input or output devices connected to the COTS computing device provided they are:

A.      securely fastened to the ROBOT,

B.      connected only using unmodified COTS cables, and

C.      charged according to manufacturer recommendations.

R603       *Charge batteries with safe connectors. Any battery charger used to charge a ROBOT battery must have the corresponding Anderson SB connector installed.

R604       *Charge batteries at a safe rate. Any battery charger used to charge a ROBOT battery may not be used such that it exceeds 6-Amp average charge current.

R605       *Batteries are not ballast. No batteries other than those allowed per R601 and R602 are allowed on the ROBOT, whether or not they are being used to supply power.

R606       *Secure the battery. The ROBOT battery must be secured such that it will not dislodge during vigorous ROBOT interaction including if the ROBOT is turned over or placed in any arbitrary orientation.

R607       *Insulate battery connections. Each electrical terminal on the ROBOT battery, main breaker, and their connections (lugs, stripped wire ends, etc.) to the wire must be fully insulated at all times.

R608       *Limit non-battery energy. Non-electrical sources of energy used by the ROBOT (i.e., stored at the start of a MATCH) shall come only from the following sources:

A.      compressed air stored in the pneumatic system that has been charged in compliance with R806 and R807,

B.      a change in the altitude of the ROBOT center of gravity,

C.      storage achieved by deformation of ROBOT parts,

D.      closed-loop COTS pneumatic (gas) shocks, or

E.      air-filled (pneumatic) wheels.

R609       *Connect main power safely. The following devices shall be connected with 6 AWG (7 SWG or 16 mm2) copper wire or larger as shown in Figure 8‑11:

A.      1 ROBOT battery

B.      a single pair of Anderson Power Products (or APP) 2-pole SB type connectors

C.      a single main 120-Amp (120A) surface mount circuit breaker (Cooper Bussman P/N CB185-120, CB185F-120, CB285-120 CB285F-120, CB285120F or Optifuse P/N 153120, 253120)

D.      a single main power distribution device (PD):

a.      CTR Electronics Power Distribution Panel (PDP) P/N am-2856, 217-4244, 14-806880,

b.      CTR Electronics Power Distribution Panel 2.0 (PDP 2.0) P/N 24-806880, WCP-1690

c.      REV Robotics Power Distribution Hub (PDH) P/N REV-11-1850

d.      AndyMark Power Distribution (AMPD) P/N am-5754

No additional devices or modifications shall be permitted with the following exceptions:

E.      Monitoring circuitry permitted by R625

F.      SB-50 to SB-120 adapters, provided they have been presented for Inspection

G.     Termination of wires with appropriate cable lugs

Figure 8‑11 Electrical connection diagram

R610       *1 breaker/fuse per circuit. All circuits, with the exceptions of those listed in R615 and R617, must connect to, and have power sourced solely by, a single protected connector pair of the PD. Circuits must not connect to the main power input of the PD.

R611       *The ROBOT frame is not a wire. All wiring and electrical devices shall be electrically isolated from the ROBOT frame. The ROBOT frame must not be used to carry electrical current.

R612       *Must be able to turn ROBOT on and off safely. The 120A circuit breaker must be quickly and safely accessible from the exterior of the ROBOT. This is the only 120A circuit breaker allowed on the ROBOT.

R613       *Electrical system must be inspectable. The PD, associated wiring, and all circuit breakers must be visible for inspection.

R614       *No high voltage allowed. Any active electrical item that is not an actuator (specified in R501) or core control system item (specified in R710) is considered a CUSTOM CIRCUIT. CUSTOM CIRCUITS shall not produce measurable voltages exceeding 24V with the exception of COTS Power-over-Ethernet (PoE) injector devices used with COTS Ethernet cables and COTS receiving devices (i.e. not a breakout or adapter).

R615       *Power roboRIO as specified. The roboRIO power input must be connected directly to a non-switched pair of protected output terminals of a PD with a 10A fuse or circuit breaker installed.

R616       *Power radio as specified – Part 1. The wireless bridge (radio) power must be connected based on the radio type:

A.      For VH-109 radios, radio power must be sourced from one or both of:

a.      Injected into the “RIO” port of the radio using a passive injector or modified Ethernet cable connected directly to a PD, and/or

b.      Wired directly to the 12V power input of the radio from a PD.

B.      For OM5P radios (China events only), radio power must be sourced from only one of:

a.      the 12V/2A output of a CTR Electronics Voltage Regulator Module (VRM) (P/N am-2857, 217-4245), as shown in Figure 8‑12, and must be the only load connected to any of the 12V/2A terminals or

Figure 8‑12 Radio power source from a VRM

b.      using an Ethernet cable between a REV Radio Power Module (RPM) (P/N REV-11-1856) and the “18-24v PoE” port. 

R617       *Power radio as specified – Part 2. The device supplying power to the wireless bridge per R616 must be connected directly to a non-switched pair of protected output terminals of a PD with a 10A fuse or circuit breaker installed with the exception of the PDP 1.0 shared VRM/PCM pairs which may be protected with a 20A fuse or circuit breaker.

R618       *Use PD terminals as designed. Only 1 wire shall be connected to each terminal on the PD.

R619       *Only use specified circuit breakers in a PD. The only circuit breakers permitted for use in the PD are:

A.      Snap Action VB3-A Series or AT2-A, terminal style F57, 40A rating or lower,

B.      Snap Action MX5-A or MX5-L Series, 40A rating or lower,

C.      REV Robotics ATO auto-resetting breakers 40A rating or lower,

D.      CTR Electronics ATO auto-resetting breakers 40A rating or lower, and

E.      Any ATM circuit breaker with value less than or equal to the fuses permitted per R620.

R620       *Only use specified fuses in PD. The only fuses permitted for use in the PD are automotive blade fuses with the following values:

A.      for the PDP, ATM style fuses with values matching the value printed on the device’s corresponding fuse holder,

B.      for all PDs ATC/ATO style fuses with values 10A or lower, and

C.      for the PDH, ATM style fuses with values 15A or lower with the exception of a single 20A fuse for powering a PCM or PH.

R621       *Protect circuits with appropriate circuit breakers. Each branch circuit must be protected by 1 and only 1 circuit breaker or fuse on the PD per Table 8‑3. No other electrical load can be connected to the breaker or fuse supplying this circuit with the exception of devices downstream of a permitted motor power adapter board placed between the PD and a motor controller (WCP-1380, WCP-1903, WCP-1904, RF-4003, RF-4004, RF-4005).

Table 8‑3 Branch circuit protection requirements

R622       *Use appropriately sized wire. All circuits shall be wired with appropriately sized insulated copper wire (SIGNAL LEVEL cables don’t have to be copper):

Table 8‑4 Breaker and wire sizing

Wires that are recommended by the device manufacturer or originally attached to legal devices are considered part of the device and by default legal. Such wires are exempt from this rule, provided they are powered by the smallest value fuse or breaker which permits proper device operation.

R623       *Use only appropriate connectors. Branch circuits may include intermediate elements such as COTS connectors, splices, COTS flexible/rolling/sliding contacts, and COTS slip rings, as long as the entire electrical pathway is via appropriately gauged/rated elements.

R624       *Use specified wire colors (mostly). All non-SIGNAL LEVEL wiring with a constant polarity (i.e., except for outputs of relay modules, motor controllers, or sensors) shall be color-coded along their entire length from the manufacturer as follows:

A.      red, yellow, white, brown, or black-with-stripe on the positive (e.g. +24VDC, +12VDC, +5VDC, etc.) connections,

B.      black or blue for the common or negative side (-) of the connections

Exceptions to this rule include:

C.      wires that are originally attached to legal devices and any extensions to these wires using the same color as the manufacturer,

D.      Ethernet cable used in PoE cables.

R625       *Don’t modify critical power paths. CUSTOM CIRCUITS shall not directly alter the power pathways between the ROBOT battery, PD, motor controllers, relays (per R504-B), motors and actuators (per R501), pneumatic solenoid valves, or other elements of the ROBOT control system (items explicitly mentioned in R710). Custom high impedance voltage monitoring or low impedance current monitoring circuitry connected to the ROBOT’S electrical system is acceptable, if the effect on the ROBOT outputs is inconsequential.

R626       *VH-109 PoE passthrough. The VH-109 PoE output may be used only under the following conditions:

A.      The device being powered is a COTS device or COTS adapter connected to a single COTS device with current draw ≤ 2A at 12V.

B.      The connection is made using standard Cat5e/6/7/8 cable.

C.      The VH-109 is powered using the 12V input terminals with 18AWG wire or larger (it may additionally be powered using the PoE input if desired).

8.7       Control, Command & Signals System

R701       *Control the ROBOT with a roboRIO. ROBOTS must be controlled via 1 programmable NI roboRIO or roboRIO 2.0 (P/N am3000 or am3000a, both versions referred to throughout this manual as “roboRIO”), with image version 2026_v1.2 or later.

R702       *Communicate with the ROBOT with the specified radio. 1 Vivid Hosting wireless bridge (P/N: VH-109, WCP-1538), that has been configured with the appropriate encryption key for your team number at each event, is the only permitted device for communicating to and from the ROBOT during the MATCH. Events held in China are the exceptions to this rule and must use an OpenMesh (P/N: OM5P-AN or OM5P-AC) radio.

R703       *Use specific Ethernet port for roboRIO. The roboRIO Ethernet port must be connected as specified:

A.      For VH-109 v1.5 radios: to the port labeled “RIO” either directly, via a Cat5 Ethernet pigtail, or via a passive PoE injector cable or adapter.

B.      For VH-109 v1.0 radios (either directly or via Cat5 Ethernet pigtail):

a.      to the radio port labeled “RIO” via a passive PoE injector cable or adapter (whether or not it is used to power the radio), or an Ethernet cable with the appropriate wires removed on the roboRIO end. All wires or adapters used must be fully insulated, or

b.      to the radio port labeled “AUX 1” or “AUX 2” with the corresponding DIP switch in the off (default) position.

C.      For OM5P radios (China events only): to the wireless bridge port labeled “18-24v PoE” (either directly, via a network switch, via an RPM, or via a Cat5 Ethernet pigtail).

R704       *Only use allowed ports and bandwidth to communicate with the ROBOT. Communication between the ROBOT and the OPERATOR CONSOLE may not exceed the following and is restricted to network ports listed in Table 8‑5:

A.      7.0Mbits/second for Vivid Hosting wireless bridge radios

B.      4.0Mbits/second for OpenMesh radios

Table 8‑5 Open FMS ports

Teams may use these ports as they wish if they do not employ them as outlined above (i.e. TCP 1180 can be used to pass data back and forth between the ROBOT and the Driver Station Software if the team chooses not to use the camera on USB).

R705       *Configure devices for your team number. The roboRIO, Driver Station Software, and wireless bridge must be configured to correspond to the correct team number, per the procedures defined in the FIRST Robotics Competition Control System documentation.

R706       *Don’t bypass the ARENA network. All signals must originate from the OPERATOR CONSOLE and be transmitted to the ROBOT via the ARENA Ethernet network.

R707       *Limited wireless allowed. The only forms of wireless communication that may be used to communicate to, from, or within the ROBOT, include:

A.      those required per R702 and R706,

B.      tags used for location detection systems if provided by the event, and

C.      RFID or NFC systems used exclusively within the ROBOT.

R708       *Wireless bridge must be visible. The wireless bridge must be mounted on the ROBOT such that the diagnostic lights are visible to FIELD STAFF.

R709       *ROBOTS must have a signal light. ROBOTS must use at least 1, but no more than 2, diagnostic ROBOT Signal Light (RSL) (P/N 855PB-B12ME522 and/or am-3583).

Any RSL must be:

A.      mounted on the ROBOT such that it is easily visible while standing 36.0in (91.44cm) away from at least one side of the ROBOT,

B.      connected to the “RSL” supply terminals on the roboRIO, and

C.      if using the 855PB-B12ME522, wired for solid light operation, by placing a jumper between the “La” and “Lb” terminals on the light per Figure 8‑13.

Figure 8‑13 855PB-B12ME522 jumper wiring

R710       *Only specified modifications to control system devices permitted. The Driver Station Software, roboRIO, PD, PCM(s)/PH(s), VRM(s)/RPM(s), RSL, 120A breaker, motor controllers, MXP devices used to control actuators per R713-C, relay modules (per R504-B), wireless bridge, PD breakers and fuses, Servo Power Module, Servo Hub, motor power adapter boards, and batteries shall not be tampered with, modified, or adjusted in any way (tampering includes drilling, cutting, machining, rewiring, disassembling, painting, etc.), with the following exceptions:

A.      User programmable code in the roboRIO may be customized.

B.      Motor controllers may be calibrated as described in owner's manuals.

C.      Fans may be attached to motor controllers and may be powered from the power input terminals.

D.      If powering the compressor, the fuse on a Spike H-Bridge Relay may be replaced with a VB3A-20A Snap-Action circuit breaker.

E.      Wires, cables, and signal lines may be connected via the standard connection points provided on the devices.

F.      Fasteners (including adhesives) may be used to attach the device to the OPERATOR CONSOLE or ROBOT or to secure cables to the device.

G.     Thermal interface material may be used to improve heat conduction.

H.     Labeling may be applied to indicate device purpose, connectivity, functional performance, etc.

I.        Jumpers may be changed from their default location.

J.      Limit switch jumpers may be removed from a Jaguar motor controller and a custom limit switch circuit may be substituted.

K.      Device firmware may be updated with manufacturer supplied firmware.

L.      Integral wires on motor controllers may be cut, stripped, and/or connectorized.

M.    Devices may be repaired, provided the performance and specifications of the device after the repair are identical to those before the repair.

N.     The cover may be removed from the Talon SRX or Talon FX data port.

O.     Electrical tape may be applied to the aluminum plate inside the wireless bridge.

P.      The input terminal cover from the PDP may be omitted (no other element may be installed using the threaded holes to install something in place of the PDP terminal cover).

Q.     The roboRIO 2.0 SD card may be replaced with an SD card of any capacity.

R.      adding insulating material to exposed conductors.

S.      replacing control system power terminal blocks (e.g. RSL power connector) with functional equivalents.

T.      tape may be applied for debris protection.

U.      VH-109 v1.0 may be upgraded to VH-109 v1.5 using manufacturer materials and instructions.

R711       *Don’t connect motor outputs to roboRIO. Neither 12VDC power nor relay module or motor controller outputs shall be directly connected to the roboRIO, with the exception of the designated 12VDC input.

R712       *Control PWM controllers from the roboRIO. Every relay module (per R504-B), servo, Servo Power Module, and PWM motor controller shall be connected to a corresponding port (relays to Relay ports, servos, and PWM controllers to PWM ports) on the roboRIO (either directly or through a WCP Spartan Sensor Board) or via a legal MXP connection (per R713). They shall not be controlled by signals from any other source.

R713       *Only approved MXP devices can control actuators. If a motor is controlled via the MXP, its power regulating device must be connected by 1 of the following methods:

A.      directly to any PWM pins,

B.      via a network of PASSIVE CONDUCTORS used to extend the PWM pins, or

C.      via 1 approved ACTIVE DEVICE:

a.      Kauai Labs navX MXP

b.      Kauai Labs navX2 MXP

c.      RCAL MXP Daughterboard

d.      REV Robotics RIOduino

e.      REV Robotics Digit Board

f.        West Coast Products Spartan Sensor Board

g.      Huskie Robotics HUSKIE 2.0 Board

R714       *Control CAN motor controllers from the roboRIO. Each CAN motor controller must be controlled with enable/disable inputs sourced from the roboRIO and passed via either a PWM (wired per R713) or CAN bus (either directly or daisy-chained via another CAN bus device) signal, but both shall not be wired simultaneously on the same device.

R715       *Control PCM, PH, and Servo Hub from roboRIO. Each Pneumatic Control Module (PCM), Pneumatic Hub (PH), and Servo Hub must be controlled with signal inputs sourced from the roboRIO and passed via a CAN bus connection from the built-in CAN on the roboRIO (either directly or daisy-chained via another CAN bus device).

R716       *Don’t alter the CAN bus. No device that interferes with, alters, or blocks communications among the roboRIO and the PCMs/PHs, and/or CAN motor controllers on the bus will be permitted.

R717       *USB to CAN adapter permitted. Additional CAN bus connections may be added to the roboRIO using the CTR Electronics CANivore^TM (P/N 21-678682, WCP-1522) USB-to-CAN adapter.

8.8       Pneumatic System

In order to maintain safety, the rules in this section apply at all times while at the event, not just while the ROBOT is on the FIELD for MATCHES.

R801       *Only use explicitly permitted pneumatic parts. To satisfy multiple constraints associated with safety, consistency, inspection, and constructive innovation, no pneumatic parts other than those explicitly permitted in this section shall be used on the ROBOT.

R802       *No custom pneumatics and meet minimum pressure ratings. All pneumatic items must be COTS pneumatic devices and either:

A.      rated by their manufacturers for pressure of at least 125.0psi (861.8kPa, 8.618Bar), or

B.      installed downstream of the primary relieving regulator (see R809), and rated for pressure of at least 70.0psi (482.6kPa, 4.826Bar).

R803       *Don’t modify pneumatics. All pneumatic COMPONENTS must be used in their original, unaltered condition. Exceptions are as follows:

A.      tubing may be cut,

B.      wiring for pneumatic devices may be modified to interface with the control system,

C.      assembling and connecting pneumatic COMPONENTS using the pre-existing threads, mounting brackets, quick-connect fittings, etc.,

D.      removing the mounting pin from a pneumatic cylinder, provided the cylinder itself is not modified, and

E.      labeling applied to indicate device purpose, connectivity, functional performance, etc.

R804       *Only use specific pneumatic devices. The only pneumatic system items permitted on ROBOTS include the following items:

A.      pneumatic pressure vent plug valves functionally equivalent to those provided in the KOP,

B.      pressure relief valves functionally equivalent to those provided in the KOP,

C.      solenoid valves with a maximum ⅛in (nominal, 0.31cm) NPT, BSPP, or BSPT port diameter or integrated quick connect ¼in (nominal, 0.64cm) outside diameter tubing connection,

D.      additional pneumatic tubing, with a maximum ¼in (nominal, 0.64cm) outside diameter,

E.      pressure transducers, pressure gauges, passive flow control valves (specifically “needle valve”), manifolds, and connecting fittings (including COTS pneumatic U-tubes),

F.      check and quick exhaust valves, provided that the requirements of R813 are still met,

G.     shutoff valves which relieve downstream pressure to atmosphere when closed (may also be known as 3-way or 3-way exhausting valves),

H.     pressure regulators with the maximum outlet pressure adjusted to no more than 60.0psi (413.7kPa, 4.137Bar),

I.        pneumatic cylinders, pneumatic linear actuators, and rotary actuators,

J.      pneumatic storage tanks (with the exception of white Clippard tanks P/N AVT-PP-41),

K.      1 compressor that is compliant with R806,

L.      debris or coalescing (water) filters, and

M.    Venturi valves (note: the high-pressure side of a Venturi valve is considered a pneumatic device and must follow all pneumatic rules. The vacuum side of a Venturi valve is exempt from the pneumatic rules per “a” in the blue box below).

R805       *If using pneumatics, these parts are required. If pneumatic COMPONENTS are used, the following items are required as part of the pneumatic circuit and must be used in accordance with this section, as illustrated in Figure 8‑14.

A.      1 FIRST Robotics Competition legal compressor (per R806),

B.      a pressure relief valve (per R804-B) connected and calibrated (per R811),

C.      a Nason pressure switch (P/N SM-2B-115R/443) and/or REV Robotics Analog Pressure Sensor (P/N REV-11-1107) connected and wired per R812,

D.      at least 1 pressure vent plug plumbed (per R813),

E.      stored pressure gauge and working pressure gauge (per R810), and

F.      1 primary working pressure regulator (per R808).

Figure 8‑14 Pneumatic circuitry

R806       *Compressed air from ROBOT compressor only. Throughout an event, compressed air on the ROBOT must be provided by its 1 onboard compressor only. Compressor specifications must not exceed nominal 1.1cfm (519.1cm³/s) flow rate @ 12VDC at any pressure.

R807       *Air storage pressure limit. Stored air pressure on the ROBOT must be no greater than 120.0psi (~827 kPa, 8.2 Bar). No stored air pressure intended for the ROBOT may be located off-board the ROBOT.

R808       *Working air pressure limit. Working air pressure (air pressure used to actuate devices) on the ROBOT must be no greater than 60.0psi (413.7kPa, 4.137Bar) and must be provided through a single primary adjustable, relieving, pressure regulator. Additional regulators may be located downstream of the single primary regulator.

R809       *Limited devices at high pressure. Only the compressor, relief valve, pressure switch, pressure vent plug, pressure gauge, storage tanks, tubing, pressure transducers, filters, and connecting fittings may be in the high-pressure pneumatic circuit upstream from the regulator.

R810       *Pressure gauges must be visible. Pressure gauges must be placed in easily visible locations upstream and downstream of the regulator to display the stored and working pressures, respectively. Pressure gauges must show pressure in psi, kPa, or Bar.

R811       *Relief valve requirements. The relief valve must be attached directly to the compressor or attached by legal hard fittings (e.g. brass, nylon, etc.) connected to the compressor output port.

Teams are required to check and/or adjust the relief valve to release air at 125.0psi (861.8kPa, 8.618Bar). The valve may or may not have been calibrated prior to being supplied to teams.

R812       *Pressure switch requirements. The pressure switch must be connected to the high-pressure side of the pneumatic circuit (i.e. prior to the pressure regulator) to sense the stored pressure of the circuit.

It must be either:

A.      Nason P/N SM-2B-115R/443 (wired as described) and/or

The 2 wires from the pressure switch must be connected directly to the pressure switch input of the PCM/PH controlling the compressor or, if controlled using the roboRIO and a relay, to the roboRIO. If connected to the roboRIO, the roboRIO must be programmed to sense the state of the switch and operate the relay module that powers the compressor to prevent over-pressuring the system.

B.      REV Robotics P/N REV-11-1107 (wired as described)

The analog output of the sensor must be connected directly to analog input 0 of the PH (with firmware version 22.0.2 or newer) controlling the compressor.

R813       *Vent plug requirements. Any pressure vent plug must be:

A.      connected to the pneumatic circuit such that, when manually operated, it will vent to the atmosphere to relieve all stored pressure in a reasonable amount of time and

B.      placed on the ROBOT so that it is visible and easily accessible.

R814       *Don’t connect solenoid outputs together. The output air from multiple solenoid valves must not be combined.

8.9       OPERATOR CONSOLE

R901       *Use the specified Driver Station Software. The Driver Station Software provided by National Instruments (install instructions found here) is the only application permitted to specify and communicate the operating mode (i.e. AUTO/TELEOP) and operating state (Enable/Disable) to the ROBOT. The Driver Station Software must be version 26.0 or newer.

R902       *The OPERATOR CONSOLE must have a visible display. The OPERATOR CONSOLE, the set of COMPONENTS and MECHANISMS used by the DRIVERS and/or HUMAN PLAYERS to relay commands to the ROBOT, must include a graphic display to present the Driver Station Software diagnostic information. It must be positioned within the OPERATOR CONSOLE so that the screen display can be clearly seen during inspection and in a MATCH.

R903       *Connect FMS Ethernet directly to the OPERATOR CONSOLE. Devices hosting the Driver Station Software must only interface with the FMS via the Ethernet cable provided at the DRIVER STATION (e.g. not through a switch). Teams may connect the FMS Ethernet cable to the device running the Driver Station Software directly via an Ethernet pigtail, or with a single-port Ethernet converter (e.g. docking station, USB-Ethernet converter, Thunderbolt-Ethernet converter, etc.). The Ethernet port on the OPERATOR CONSOLE must be easily and quickly accessible.

R904       *OPERATOR CONSOLE physical requirements. The OPERATOR CONSOLE must not

A.      be longer than 60.0in (1.524m),

B.      be deeper than 16.0in (40.64cm) (excluding any items that are held or worn by the DRIVERS during the MATCH),

C.      extend more than 78.0in (1.981m) above the floor, or

D.      attach to the FIELD, except via the loop tape as described in section 5.9.1 DRIVER STATIONS or clamping to the DRIVER STATION support shelf (as long as the shelf is not damaged).

R905       *FIELD wireless only. Other than the system provided by the FIELD, no other form of wireless communications shall be used to communicate to, from, or within the OPERATOR CONSOLE.

R906       *No unsafe OPERATOR CONSOLES. OPERATOR CONSOLES shall not be made using hazardous materials, be unsafe, cause an unsafe condition, or interfere with other DRIVE TEAMS or the operation of other ROBOTS.

R907       *No AC inverters. OPERATOR CONSOLES must not contain AC inverters.

 

This section describes the rules governing MATCH participation. A team has participated in a MATCH if any member of their DRIVE TEAM is in the ALLIANCE AREA, with or without the ROBOT on the FIELD, at the start of the MATCH.

At each event, the Lead ROBOT INSPECTOR (LRI) has final authority on the legality of any COMPONENT, MECHANISM, or ROBOT. The LRI may consult with additional sources including the Global LRIs and/or FIRST personnel before making their final decision. INSPECTORS may re-inspect ROBOTS at any time to ensure compliance with the rules. Teams are encouraged to consult with INSPECTORS or the LRI if they have any questions regarding the legality of a ROBOT or about how to make a ROBOT legal.

The inspection process may progress in blocks, i.e. it may pause for a team’s Practice MATCH, lunch break, etc. The process may employ various INSPECTORS throughout the process based on availability. At the team’s discretion, they may request a different INSPECTOR or invite the Lead ROBOT INSPECTOR to participate in their ROBOT’S inspection.

ROBOTS may be modified after completing initial inspection; however, note that, per I104, any modifications not specifically exempt must be re-inspected. Prior to the beginning of Playoff MATCHES, all ROBOTS wishing to participate will be re-weighed to help identify any modifications that should be re-inspected per I104.

ROBOTS are permitted to participate in scheduled Practice MATCHES prior to passing inspection. However, the FTA, LRI, or Head REFEREE may determine at any time that the ROBOT is unsafe and may prohibit further participation in Practice MATCHES until the condition is corrected and/or the ROBOT passes inspection. A safe ROBOT has functional BUMPERS that approximately meet the required coverage (R401), height (R402), and cross section (R408) requirements.

Prior to the start of a MATCH, any ROBOT which is unable or ineligible to participate in that MATCH, as determined by the FTA, LRI, or Head REFEREE, is declared to be BYPASSED and is DISABLED. A team whose ROBOT is BYPASSED remains eligible to receive Qualification Ranking Points or Playoff MATCH points provided that its ROBOT has passed inspection, per I102.

9.1       Rules

I101          *It’s your team’s ROBOT. The ROBOT and its MAJOR MECHANISMS must be built by the FIRST Robotics Competition team.

A MAJOR MECHANISM is a group of COMPONENTS and/or MECHANISMS assembled together to address at least 1 game challenge: ROBOT movement, SCORING ELEMENT manipulation, FIELD element manipulation, or performance of a scorable task without the assistance of another ROBOT.

I102          *Get inspected before playing a Qualification MATCH. A team is only permitted to participate in a Qualification or Playoff MATCH and receive Ranking or MATCH Points if their ROBOT has passed an initial, complete inspection.

Violation: If prior to the start of the MATCH, the team is DISQUALIFIED and not eligible to participate in the MATCH. If after the MATCH, the team receives a RED CARD and the MATCH may be replayed per T201.

I103          *Bring it all to inspection. At the time of inspection, the OPERATOR CONSOLE and the ROBOT must be presented with all MECHANISMS (including all COMPONENTS of each MECHANISM), configurations, and decorations that will be used on the ROBOT in MATCHES without re-inspection (per I104) and may not exceed 150.0lb (68.04kg) (note that while up to 150.0lb (68.04kg) of ROBOT MECHANISMS may be inspected together, the ROBOT configuration used in a MATCH may not violate R103). The OPERATOR CONSOLE and exceptions listed in R103 are not included in this weight.

I104          *Unless the change is listed below, any change to a ROBOT must get re-inspected. A ROBOT may play MATCHES with a subset of the MECHANISMS that were present during inspection provided the reconfigured ROBOT still complies with all ROBOT Construction Rules. Only MECHANISMS that were present during the inspection may be added, removed, or reconfigured between MATCHES without re-inspection per this rule. If a ROBOT is modified after its most recent passed inspection, it must be re-inspected before it is eligible to participate in a MATCH.

Exceptions are listed in A through F (unless they result in a significant change to the ROBOT’S size, weight, legality, or safety).

A.      addition, relocation, or removal of fasteners (e.g. cable ties, tape, and rivets),

B.      addition, relocation, or removal of labeling or marking,

C.      revision of ROBOT code,

D.      replacement of a COTS COMPONENT with an identical COTS COMPONENT,

E.      replacement of a MECHANISM with an identical MECHANISM (size, weight, material), and

F.      additions, removals, or reconfiguration of ROBOT with a subset of MECHANISMS already inspected per I103.

I105          *Don’t exploit re-inspection. Teams may not use the re-inspection process in I104 to circumvent the weight limit in I103.

I106          *ROBOTS are off for inspection (mostly). For the safety of all those involved, ROBOTS must be presented for inspection with the ROBOT powered off, pneumatics unpressurized, and springs or other stored energy devices in their lowest potential energy states (e.g. battery removed).

Power and air pressure should only be enabled on the ROBOT during those portions of the inspection process where it is absolutely required to validate certain system functionality and compliance with specific rules (firmware check, etc.). INSPECTORS may allow the ROBOT to be powered beyond the parameters above if both criteria below are met:

A.      the ROBOT design requires power or a charged stored energy device in order to confirm that the ROBOT meets volume requirements and

B.      the team has included safety interlocks that mitigate unexpected release of such stored energy.

 

 

I107          *No STUDENT, no inspection. At least 1 STUDENT team member must accompany the ROBOT for any inspection efforts.

 

Each 2026 FIRST Robotics Competition event is played in a tournament format. Each tournament consists of 3 types of MATCHES: Practice MATCHES (not necessarily played at all District Events), Qualification MATCHES, and Playoff MATCHES.

Practice MATCHES provide each team with an opportunity to operate its ROBOT on the FIELD prior to the start of the Qualification MATCHES.

Qualification MATCHES allow each team to earn Ranking Points which determine their seeding position and may qualify them for participation in the Playoff MATCHES.

Playoff MATCHES determine the event Champions.

10.1  MATCH Schedules

A MATCH schedule is used to coordinate MATCHES at an Event. Figure 10‑1 details information shown on each schedule. SURROGATE MATCHES are described in section 10.5.2 MATCH Assignment.

Figure 10‑1 Sample MATCH schedule

10.2  MATCH Replays

Over the course of the tournament, it may be necessary for a MATCH to be replayed. Typical causes for replays are MATCHES that end in a tie during the Playoffs (due to criteria listed in Table 10‑3. or any Finals MATCH), MATCHES that are stopped because FIELD STAFF anticipated FIELD damage or personal injury, or if there is an ARENA FAULT.

An ARENA FAULT is an error in ARENA operation that includes, but is not limited to:

A.      broken FIELD elements due to

a.      normal, expected game play or

b.      ROBOT abuse of FIELD elements that affects the outcome of the MATCH for their opponents.

B.      power failure to a portion of the FIELD (tripping the circuit breaker in the DRIVER STATION is not considered a power failure),

C.      improper activation by the FMS,

D.      errors by FIELD STAFF (except those listed in section 6.8 Other Logistics), and

E.      a ROBOT radio disconnect that impairs operation of other ROBOTS on the FIELD for more than 8 seconds.

If, in the judgment of the Head REFEREE, an ARENA FAULT occurs that affects the outcome of the MATCH and any team on the affected ALLIANCE desires a replay, the MATCH will be replayed. FIRST Headquarters reserves the right to, with consultation of the Head REFEREE and the FTA, replay a MATCH in which an ARENA FAULT impacts the outcome of an event. Once a MATCH replay is granted, a team may not withdraw the request for the replay.

T201       *Replays will be the same. All reasonable effort is made to create the same conditions when replaying a MATCH caused by an ARENA FAULT or FIELD damage. This means, for example, that a team that was BYPASSED prior to the start of the MATCH which is to be replayed is BYPASSED for the replay MATCH. ROBOT and DRIVE TEAM starting locations do not need to be replicated when replaying a MATCH.

Violation: MATCH with not start until the situation is corrected

10.3  Measurement

At each event, the ARENA will be open for at least 30 minutes prior to the start of Qualification MATCHES, during which time teams may survey and/or measure the ARENA and bring ROBOTS on the FIELD to perform sensor calibration. Events may schedule additional measurement and calibration times. The specific time(s) that the FIELD is open will be communicated to teams at the event. Teams may bring specific questions or comments to the FTA.

 

T301       *Measurement, not practice. During the period when the ARENA is open for measurement:

A.      ROBOTS can be enabled, but may neither drive, extend outside their ROBOT PERIMETER, nor interact with (e.g. score, push, pickup, etc.) SCORING ELEMENTS (or anything resembling SCORING ELEMENTS), a HUB, BUMP, TRENCH, OUTPOST, or other FIELD elements.

B.      Humans may touch a SCORING ELEMENT but may not practice with it (e.g. throw FUEL, or anything resembling FUEL, or use the OUTPOST).

Violation: VERBAL WARNING, plus YELLOW CARD if subsequent violations at any point during the event or egregious.

10.4  Practice MATCHES

Practice MATCHES are played before Qualification MATCHES. The Practice MATCH schedule is available as soon as possible, but no later than the start of Practice MATCHES. For Regional events, it will also be published and available online on the FRC-Events website, except during exceptional circumstances. Practice MATCHES are randomly assigned, and teams may not switch scheduled Practice MATCHES. Each team is assigned an equal number of Practice MATCHES unless the number of teams multiplied by number of Practice MATCHES is not divisible by 6. In this case, the FMS randomly selects some teams to play an extra Practice MATCH.

Practice MATCHES are not guaranteed at District Events due to event schedule constraints.

10.4.1   Filler Line

A Filler Line is used to fill open slots at events that employ scheduled Practice MATCHES or all slots at events with an open Practice MATCH schedule. Teams from the Filler Line are used on a first come, first served basis to fill empty spots in Practice MATCHES left by other teams that do not report to Queueing. The number of teams in the Filler Line is dependent upon space at venues.

Only teams that meet all criteria below qualify for the Filler Line:

A.      ROBOTS in the Filler Line must have passed inspection (this requirement may be waived for events with open Practice MATCH schedules),

B.      DRIVE TEAMS must join the Filler Line with their ROBOT,

C.      teams may not work on their ROBOT while in the Filler Line,

D.      teams may not occupy more than 1 spot in the Filler Line, and

E.      if a team is queued for their Practice MATCH, they may not also join the Filler Line.

10.5  Qualification MATCHES

10.5.1   Schedule

The Qualification MATCH schedule is made available as soon as possible, but no later than 30 minutes before Qualification MATCHES are scheduled to begin. Teams receive 1 hard copy and it is also available on the FRC-Events website, except during exceptional circumstances. Each Qualification schedule consists of a series of rounds in which each team plays 1 MATCH per round.

 

10.5.2   MATCH Assignment

FMS assigns each team 2 ALLIANCE partners for each Qualification MATCH using a predefined algorithm, and teams may not switch Qualification MATCH assignments. The algorithm employs the following criteria, listed in order of priority:

1.      ensure each team has at least the minimum required time between MATCHES (varies by event size)

2.      minimize the number of times a team is allied with any team

3.      minimize the number of times a team plays opposite any team

4.      minimize the use of SURROGATES (teams randomly assigned by the FMS to play an extra Qualification MATCH)

5.      provide even distribution of MATCHES played on blue and red ALLIANCE

6.      provide even distribution of MATCHES played in each DRIVER STATION number

At events with fewer than 24 participating teams, the criteria are similar, except #5 is changed to minimize the number of times a team swaps between the blue and red ALLIANCE rather than an even distribution.

All teams are assigned the same number of Qualification MATCHES, equal to the number of rounds, unless the number of teams multiplied by number of MATCHES is not divisible by 6. In this case, the FMS randomly selects some teams to play an extra MATCH. For the purpose of seeding calculations, those teams are designated as SURROGATES for the extra MATCH. If a team plays a MATCH as a SURROGATE, it is indicated on the MATCH schedule, it is always their third Qualification MATCH, and the outcome of the MATCH has no effect on the team’s ranking. YELLOW and RED CARDS assigned to SURROGATES, however, do carry forward to subsequent MATCHES.

10.5.3   Qualification Ranking

Ranking Points are units credited to a team based on their ALLIANCE’S performance in Qualification MATCHES. Ranking Points are awarded to each eligible team at the completion of each Qualification MATCH per Table 6‑4.

Exceptions to Ranking Point assignment are as follows:

A.      A SURROGATE receives 0 Ranking Points.

B.      A DISQUALIFIED team, as determined by the Head REFEREE, receives 0 Ranking Points.

C.      A “no-show” team is either DISQUALIFIED from or issued a RED CARD for that MATCH (see G208). A team is declared a no-show if no member of the DRIVE TEAM is in the ALLIANCE AREA at the start of the MATCH.

The total number of Ranking Points earned by a team throughout their Qualification MATCHES divided by the number of MATCHES they’ve been scheduled to play (minus any SURROGATE MATCH), then rounded to 2 decimal places, is their Ranking Score (RS).

All teams participating in Qualification MATCHES are ranked by Ranking Score. If the number of teams in attendance is ‘n’, they are ranked ‘1’ through ‘n’, with ‘1’ being the team with the highest-Ranking Score and ‘n’ being the team with the lowest Ranking Score.

Teams are ranked in order, using the sorting criteria defined in Table 10‑1.

Table 10‑1 Qualification MATCH ranking criteria

10.6  Playoff MATCHES

Playoff MATCHES follow the qualification MATCHES. In the Playoffs, teams play on set ALLIANCES, chosen during ALLIANCE selection, and advance through a double elimination bracket. Teams do not earn Ranking Points; they advance based on winning, losing, or tying a MATCH.

A DISQUALIFIED team, as determined by the Head REFEREE, causes their ALLIANCE to receive 0 MATCH points in a Playoff MATCH.

10.6.1   ALLIANCE Selection Process

At the end of the Qualification MATCHES, the top 8 ranked teams become the ALLIANCE Leads. The ranked ALLIANCES are designated, in order, ALLIANCE 1, ALLIANCE 2, etc., down to ALLIANCE 8. Using the ALLIANCE selection process described in this section, each ALLIANCE Lead chooses 2 other teams to join their ALLIANCE.

A break of 8 minutes (8:00) occurs between the posting of scores from the last qualification match (scheduled or replay, whichever comes later) and the start of the ALLIANCE Selection process for events that host Alliance Selection shortly after QUALIFICATION MATCHES. At the end of this break, ALLIANCE 1 is “on the clock” as defined below in T605.

T601       *Send your STUDENT representatives. Each team must choose and send a minimum of one and a maximum of three STUDENT team representatives. Representative(s) must report to the ARENA before the start of ALLIANCE Selection.

Violation: Team is ineligible for the Playoff Tournament if they are not represented by the time they are announced.

The designated STUDENT representative from each ALLIANCE Lead is called the ALLIANCE CAPTAIN (if the ALLIANCE has sent multiple STUDENT representatives, they must designate only one as the ALLIANCE CAPTAIN). This representative may change between ALLIANCE selection and Playoff MATCHES.

T602       *STUDENTS must outnumber adults. A non-STUDENT may additionally be a representative from a team if the team has exactly two STUDENT representatives.

Violation: Non-STUDENT must leave the ARENA

The ALLIANCE selection process consists of rounds during which each ALLIANCE CAPTAIN invites a team ranked below them in the standings to join their ALLIANCE. The invited team’s representative must either accept or decline the invitation immediately. If the team accepts, it becomes a member of that ALLIANCE. This process results in 8 ALLIANCES of 3 teams.

Each round is complete when all ALLIANCES have added one additional team, and each round must be complete before the next round can begin. In round 1 selections are made in descending order (ALLIANCE 1 to ALLIANCE 8), whereas in round 2 selections are made in ascending order (ALLIANCE 8 to ALLIANCE 1).

T603       * Only STUDENTS may use the mic. Only a single STUDENT from the invited team is allowed to accept/decline.

Violation: The team is assumed to have declined.

T604       * Only the ALLIANCE CAPTAIN may invite an ALLIANCE. The ALLIANCE CAPTAIN is the only representative of the ALLIANCE who may approach the emcee and make a valid pick via the microphone.

Violation: Pick does not count, and pick timer continues to count down.

T605       * Picks are time limited. Once the emcee requests an ALLIANCE’S selection, the ALLIANCE is considered “on the clock” and the pick timer begins to countdown. In round 1, the timer begins at 45 seconds (0:45), in round 2 the timer begins at 1 minute and 30 seconds (1:30). A sound will play to indicate that there are 5 seconds left on the timer and a buzzer will go off to indicate the end of the time. The ALLIANCE CAPTAIN must make a good faith effort, as determined by the FTA or their designee, to state a valid team selection before the expiration of the pick timer.

Violation: The ALLIANCE is skipped, and the emcee moves to the next ALLIANCE, unless the selection is the last of a round in which case the ALLIANCE receives the next highest-ranked unselected team to the ALLIANCE.

If an ALLIANCE CAPTAIN extends a valid invitation and the invited team declines, the pick clock resets to the time for the designated round and restarts immediately.

After each accepted ALLIANCE invitation or T605 violation, the emcee invites any ALLIANCE CAPTAINS that received a T605 violation in that round to make their selections. Each ALLIANCE CAPTAIN may either indicate that they are ready to make their selection (and immediately do so as determined by the FTA or their designee) or indicate that they are not yet ready, and they will be revisited after the next accepted invitation or T605 violation. If a team with a T605 violation extends a valid invitation and the invited team declines, they are allowed to make another selection immediately or else they are skipped and will be revisited as described above. If there are multiple ALLIANCE CAPTAINS that have received T605 violations, they are revisited in the same order in which they received their violations. If all remaining teams in a round have received a T605 violation, each team is revisited to either make a pick immediately or receive the next highest-ranked unselected team.

A break of 2 minutes (2:00) occurs between each round of selections. At the conclusion of the break, the ALLIANCE scheduled to make the next selection goes “on the clock” and their timer begins per T605.

T606       *Declining teams can’t be picked. An ALLIANCE CAPTAIN may not invite a team that has declined another ALLIANCE’S invitation to participate in the Playoff tournament. Declining teams are ineligible to be a BACKUP TEAM.

Violation: The ALLIANCE CAPTAIN must make another selection and pick timer continues to count down.

An ALLIANCE Lead that declines an invitation from another ALLIANCE is able to invite teams to join their ALLIANCE but may not be invited to join another ALLIANCE.

At the conclusion of ALLIANCE selection, the highest ranked unselected teams are eligible to become a BACKUP TEAM, as defined in section 10.6.3 BACKUP TEAMS.

10.6.2   Playoff MATCH Bracket

The double elimination tournament consists of an Upper and Lower bracket as shown in Figure 10‑2. Each ALLIANCE begins with a slot in the Upper bracket. If an ALLIANCE wins a MATCH in the Upper bracket, they remain in the Upper bracket. If an ALLIANCE loses a MATCH in the Upper bracket, they transition to the Lower bracket. ALLIANCES in the Lower bracket must win any subsequent MATCHES (except for finals) to remain in the tournament, i.e. once they lose a MATCH, they’re out of the tournament.

In Round 1, the higher ranked ALLIANCE is assigned to the red ALLIANCE. For subsequent rounds, ALLIANCE color is assigned as shown in Figure 10‑2. regardless of ALLIANCE rank at the start of the Playoff tournament.

Figure 10‑2 Playoff MATCH bracket (Red ALLIANCE tops each pairing)

As shown in Figure 10‑2 and Table 10‑2, Playoff MATCHES consist of 6 rounds with breaks between later rounds and between Finals MATCHES. Breaks begin after the FIELD has been cleared from the previous MATCH. The Blue and Red Gap columns indicate the approximate time between each ALLIANCE’S MATCHES. The expected start time of the scheduled MATCH is the time indicated on the MATCH schedule or 15 minutes from the end of either ALLIANCE’S previous MATCH, whichever is later. Occasionally, replayed MATCHES within a round may be played out of order; if MATCHES are played out of order, teams are informed by the emcee, FIELD STAFF, and/or queueing staff.

If a Playoff MATCH needs to be replayed as described in section 10.2 MATCH Replays, teams are notified of when the replay will occur. A minimum 10-minute delay is provided for teams to reset their ROBOTS prior to the replay unless all teams are ready sooner. The affected MATCH must be replayed before the next round begins.

Table 10‑2 Typical Playoff MATCH schedule

* if required

** Program Delivery Partners may choose to hold these awards until after all MATCHES are complete.

If final MATCH scores for both ALLIANCES are equal, the win is awarded to the ALLIANCE per criteria listed in Table 10‑3.

Table 10‑3 Playoff MATCH Tiebreaker Criteria

Once a single ALLIANCE remains in each Upper and Lower bracket, those ALLIANCES proceed to the Finals round. The first ALLIANCE to win 2 MATCHES in the Finals becomes the event’s Champions.

If a Finals MATCH ends in a tie score, the tie is not broken using the criteria in Table 10‑3, the MATCH remains a tie. In the case where an ALLIANCE hasn’t won 2 MATCHES after 3 MATCHES have been played (because of tied MATCHES), the Playoffs proceed with up to 3 additional Finals MATCHES, called Overtime MATCHES, until an ALLIANCE has won 2 Finals MATCHES. In the case where the Overtime MATCH scores for both ALLIANCES are equal, the win for that Overtime MATCH is awarded based on the criteria listed in Table 10‑3.

10.6.3   BACKUP TEAMS

During the Playoff MATCHES an ALLIANCE CAPTAIN may elect to replace one of its ROBOTS. The team whose ROBOT and DRIVE TEAM replaces another ROBOT and DRIVE TEAM on an ALLIANCE during the Playoff MATCHES is called the BACKUP TEAM.

In this situation, the ALLIANCE CAPTAIN has the option to bring in the highest ranked team from the pool of available teams to join its ALLIANCE for the following MATCH. The resulting ALLIANCE is then composed of 4 teams.

Each ALLIANCE is allotted 1 BACKUP TEAM coupon during the Playoff MATCHES. If two or more ROBOTS from the ALLIANCE become inoperable, then the ALLIANCE must play the following MATCHES with only 2 (or even 1) ROBOTS.

The Head REFEREE will not accept the BACKUP TEAM coupon unless it lists the number of the team whose ROBOT is being replaced and is initialed by the ALLIANCE CAPTAIN. Once a BACKUP TEAM coupon is submitted and accepted by the Head REFEREE, the BACKUP TEAM coupon may not be withdrawn by the ALLIANCE.

T607          *No BACKUP TEAM for replayed MATCHES. An ALLIANCE may not request a BACKUP TEAM for a replayed MATCH. The sole exception is if, in the judgment of the Head REFEREE, the replay is due to an ARENA FAULT that rendered an ALLIANCE’S ROBOT inoperable.

Violation: The request is denied.

T608          *No BACKUP TEAMS for 1st MATCH. An ALLIANCE may not request a BACKUP TEAM until after their first Playoff MATCH.

Violation: The request is denied.

T609          *BACKUP TEAMS play when called. A BACKUP TEAM must be included in the LINEUP for the ALLIANCE’S next MATCH following their recruitment.

Violation: The LINEUP is denied.

T610       *BACKUP TEAMS due 2 minutes before the MATCH start time. The BACKUP TEAM Coupon must be submitted to the Head REFEREE (or their designee) by the ALLIANCE CAPTIAN not later than 2 minutes before the expected MATCH start time in which the BACKUP TEAM is to play.

Violation: The request is denied

After the top ranked ALLIANCE has made their final pick during ALLIANCE Selection, the lead queuer (or their designee) polls the remaining eligible teams. In rank order, the lead queuer (or their designee) will invite remaining teams to accept or decline a position in the BACKUP POOL, i.e. the group of teams willing and able to join an ALLIANCE during the Playoff MATCHES, if needed, until up to 8 teams accept.

T611       *Be there to be a BACKUP TEAM. A team must be present after ALLIANCE Selection to accept the lead queuer’s (or their designee) invitation to join the BACKUP POOL.

Violation: Team is ineligible to be a BACKUP TEAM.

T612       *Send a BACKUP TEAM Representative. The top 2 ranked BACKUP TEAMS must send at least 1 STUDENT representative (and optionally 1 additional STUDENT or mentor) to a designated area near the FIELD for the duration of the Playoff MATCHES.

These 2 representatives are available to answer questions and accept invitations to be a BACKUP TEAM from ALLIANCE CAPTAINS. If 1 of these 2 teams joins an ALLIANCE or excuses themselves from the BACKUP POOL, the next highest ranked team in the BACKUP POOL must provide their representative. Once a BACKUP TEAM has declined an invitation to join an ALLIANCE, it is no longer a member of the BACKUP POOL and ineligible to join another ALLIANCE.

Violation: VERBAL WARNING, plus the team is removed from BACKUP POOL if the situation cannot be corrected within a reasonable amount of time.

10.6.4   LINEUPS

Each ALLIANCE competing in a Playoff MATCH has the option to submit a LINEUP, which lists the 3 teams participating in the MATCH and their selected DRIVER STATIONS.

The LINEUP is kept confidential until the FIELD is set for the MATCH at which point each ALLIANCE’S LINEUP appears on the Team Signs.

If an ALLIANCE has 4 members (either because a 3-team ALLIANCE has called a BACKUP TEAM or the event is the FIRST Championship), a single representative from the team not on the LINEUP is allowed as a sixteenth ALLIANCE member but must be a member of that team’s DRIVE TEAM. This additional representative may only serve as a DRIVE COACH.

T613       *LINEUPS due 2 minutes before the MATCH. The ALLIANCE CAPTAIN must submit their LINEUP in writing to the Head REFEREE (or their designee) 2 minutes before their expected MATCH start time.

Violation: Late LINEUPS are denied, and the ALLIANCE’S most recent LINEUP is applied.

T614       *For replays, no changing LINEUPS (mostly). If a MATCH must be replayed due to an ARENA FAULT, the LINEUP for the replayed MATCH is the same as the original MATCH. The sole exception is if, in the opinion of the Head REFEREE, the ARENA FAULT rendered a ROBOT inoperable, in which case the LINEUP can be changed.

Violation: The new LINEUP is denied.

10.6.5   Pit Crews

During the Playoff MATCHES and because of the distance between the FIELD and the pit area, extra team members may be needed to maintain and otherwise assist with the ROBOT between MATCHES. Each team is permitted to have up to 3 additional pit crew members to help with needed ROBOT repairs/maintenance.

10.6.6   Small Event Exceptions

The scheduling algorithm described in section 10.5.2 MATCH Assignment works to minimize teams playing in back-to-back MATCHES. However, at events with fewer than 24 teams, back-to-back plays may occur.

Multi-day events with 24 teams or fewer employ a modified Playoff MATCH format. Instead of 8 ALLIANCES, these events proceed through ALLIANCE SELECTION and the Playoff Tournament with the maximum number of complete 3-team ALLIANCES that can be formed while leaving at least 1 BACKUP TEAM (e.g. a 24-team event creates 7 ALLIANCES, a 20-team event creates 6 ALLIANCES).

The Playoff Bracket remains as shown in Figure 10‑2 with any matchup against a non-existent ALLIANCE resulting in a bye (i.e. automatic advancement to the next round). An ALLIANCE assigned a bye-MATCH is invited, though not required, to practice together in a null MATCH (i.e. it has no bearing on the Playoff tournament) during the designated time in the Playoff schedule.

District points for Draft Order Acceptance (per section 11.1.2 ALLIANCE Selection Results) are awarded as if a full set of ALLIANCES was selected (i.e. the 2^nd selection of the 3-seed ALLIANCE still receive 3 points regardless of how many ALLIANCES are formed).