Contents
1.3 FIRST® Robotics Competition
1.4 Gracious Professionalism®, a FIRST Credo
1.7 This Document & Its Conventions
1.8 Translations & Other Versions
1.10 Question and Answer System
5.9 The Field Management System
7.2 Robot to Robot Interaction
9.2 Robot Safety & Damage Prevention
9.3 Budget Constraints & Fabrication Schedule. 72
9.7 Control, Command & Signals System
10 Inspection & Eligibility Rules
11.7.1 Alliance Selection Process
11.7.7 Single-Day Event Exceptions
11.8 Advancement Through the District Model
11.8.2 District Championship Eligibility
11.8.3 District Championships with Multiple Divisions 126
11.9 FIRST Championship: Additions and Exceptions. 127
11.9.1 Advancement to the FIRST Championship
11.9.3 FIRST Championship Pit Crews
11.9.4 FIRST Championship Playoffs
11.9.5 FIRST Championship Timeouts
1
Introduction
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, 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.
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
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 2022, FIRST Robotics Competition is projected to reach between 55,000 and 81,000 high-school students representing approximately 3,200 teams. Teams come from nearly every state in the United States, as well as many other countries.
FIRST Robotics Competition teams will participate in 59 Regional Competitions, 106 District Competitions, and 11 District Championships. In addition, approximately 450 teams will qualify to attend the FIRST Championship in April 2022.
This year’s game, and this manual, were presented at the 2022 FIRST Robotics Competition Kickoff on Saturday, January 8, 2022.
At the Kickoff, all teams:
• saw the 2022 game, RAPID REACTSM presented by The Boeing Company, for the first time,
• learned about the 2022 game rules and regulations, and
Safety is always paramount, and many rules are intended to establish norms at each event that will mitigate injury risk to all participants.
Event staff have the final decision authority for all safety-related issues within a venue.
Please refer to FIRST Robotics Competition District and Regional Event web page for safety, conduct, etc. rules not specific to RAPID REACT or limited to Match play. As with all violations in this document, any event rules also carry the potential consequence of a yellow or Red Card.
• received a Kickoff Kit that provides a starting point for robot build.
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 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.
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.
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, 2735, 6833)
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)
2022 Season Spirit of Volunteering: A Message from the Chief Volunteers to the FIRST Community
We know 2020 didn’t go as planned and 2021 was a year unlike any other for the FIRST Community. The 2022 season is shaping up to be another non-traditional year. With that in mind, we think it’s more important than ever to recognize the two phrases which drive and motivate the individuals that volunteer their time for FIRST: “Giving Back” and “Pay It Forward”. This year will be a year where you can help create the best-ever experience for our mentors, coaches, students, and fellow volunteers.
Volunteering has enormous, lifelong impacts for everyone involved. Every student, teacher, event volunteer, mentor, coach, and family member learns and grows throughout the season as they interact with each other – via both in-person as well as virtual interactions. There are tremendous growth opportunities for all!
To our team members and mentors: Whether you are attending events remotely or hopefully in-person, remember that the volunteers you interact with are giving up their most precious asset - their time - to ensure that all teams have a fulfilling, fun, and memorable competition. Volunteers are the lifeblood of FIRST and without them, FIRST would not be where it is today. We encourage you to remember that 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.
To our loyal volunteers – and everyone else that is considering volunteering - we want to encourage you to join us in whatever capacity that you can for the 2022 season. There’s a lot to gain from volunteering and part of what makes it so much fun is:
• Seeing capable students learning and growing
• Making new friends with other awesome volunteers
• Being a part of the magic that makes an event happen
• Sharing FIRST with folks who didn’t know about it
• Taking event experiences back to your team
• Learning how to communicate with people outside of your normal circle
Just as with so many other circumstances and situations in our lives these last couple of years, volunteering for FIRST Robotics Competition in 2022 will probably look a little different. We know a day will come when we will put this virus behind us. And we know that together, we will adapt, stay connected, engage our teams, and continue to move #FIRSTFORWARD.
To our FIRST alumni – We need you! You know the impact of FIRST in your life and the opportunity you’ve been given. We’re asking you to pay it forward and help the next generation have the same opportunity. The FIRST website has great resources for finding out how you can get involved by giving a few hours or more!
We look forward to welcoming you!
Chief Referees – Aidan Browne & Jon Zawislak
Chief Judge Advisors – Cindy Stong & Allen Bancroft
Chief Volunteer Coordinators – Laurie Shimizu & Sarah Plemmons
Chief Robot Inspectors - Al Skierkiewicz & Chuck Dickerson
Chief Field Supervisors – Scott Goering & Ayla DeLaat
The 2022 Game Manual is a resource for all FIRST Robotics Competition teams for information specific to the 2022 season and the RAPID REACT game. Its audience will find the following detail:
• a general overview of the RAPID REACT game,
• detail about the RAPID REACT playing Field,
• a description of how to play the RAPID REACT game,
• game rules (related to safety, conduct, game play, inspection, etc.), and
• a description of how teams advance at 2022 tournaments and throughout the season
All participants should also study the Event Rules Manual as it details event rules and expectations that perpetuate from season to season. That content complements, and carries the same weight as, this document.
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 and external articles appear in blue underlined text. All rule references are also hyperlinks to the rule even though they do not appear as blue underlined text.
Key words that have a particular meaning within the context of the FIRST Robotics Competition and RAPID REACT are defined in the Section 12 Glossary section 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.
• G for Section 7 Game Rules: Robots
• H for Section 8 Game Rules: Humans
• R for Section 9 Robot Construction Rules
• I for Section 10 Inspection and Eligibility Rules
• T for Section 11 Tournaments
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‑2 Rule numbering method
Warnings, cautions, and notes appear in blue boxes. Pay close attention to their contents as they’re intended to provide insight into the reasoning behind a rule, helpful information on understanding or interpreting a rule, and/or possible “best practices” for use when implementing systems affected by a rule.
While blue boxes are part of the manual, they do not carry the weight of the actual rule (if there is an inadvertent conflict between a rule and its blue box, the rule supersedes the language in the blue box).
Imperial dimensions are followed by comparable metric dimensions in parentheses to provide metric users with the approximate size, weight, etc. Metric conversions for non-rules (e.g. dimensions) round to the nearest whole unit, e.g. "17 in. (~43 cm)” and “6 ft. 4 in. (~193 cm).” 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 intent 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 Cargo 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 firstroboticscompetition@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.
The RAPID REACT 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.
A text-based English version can be provided only for use with assistive devices and not for redistribution. For more information, please contact the FIRST Robotics Competition Team Experience Specialist 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 RAPID REACT - Season Materials web page is the commanding version.
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 of the final District Championship events.
Team Updates are posted on the RAPID REACT - Season Materials web page 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.
The Question and Answer System (Q&A) is a resource for clarifying the 2022 RAPID REACT Game Manual, Awards webpages, official field drawings, and/or FIRST Robotics Competition District and Regional Events web page 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 12, 2022, 12:00 PM Eastern. Details on the Q&A can be found on the RAPID REACT - Season Materials web page. The Q&A may result in revisions to the text in the official manuals (which are communicated using the process described in Section 1.9 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 10 Inspection & Eligibility Rules and Section 11.2 Referee Interaction, Referees and inspectors are the ultimate authority on rules. If you have concerns about enforcement trends by volunteer authorities, please notify FIRST at firstroboticscompetition@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 9999” represent content asked by key volunteers (e.g., Referees, Inspectors, etc.), answered by FIRST, and are considered relevant to teams.
2
FIRST
Season Overview
In the 2022 season, FIRST® FORWARDSM presented by Qualcomm, FIRST teams will explore the future of transportation. From the shipment of packages in rural and urban areas, to disaster relief delivery and high-tech air transit, teams will re-imagine faster, more reliable, inclusive, and sustainable transportation innovations that better connect and grow communities and economies around the world.
This year, FIRST teams will address today’s global challenges related to United Nations Sustainable Development Goal #9, focused on building resilient infrastructure, promoting inclusive and sustainable industrialization, and fostering innovation. By encouraging FIRST participants to think about future transportation sustainability, we’re also empowering them to be the next generation of leaders and innovators, tackling the world’s toughest challenges.
3
Game Sponsor Recognition
4
Game Overview
Figure 4‑1 RAPID REACT field and key elements
In RAPID REACTSM presented by The Boeing Company, two competing alliances are invited to process cargo for transportation. Each alliance is assigned a cargo color (red or blue, based on alliance affiliation) to process by retrieving their assigned cargo and scoring it into the hub. Human players assist the cargo retrieval and scoring efforts from within their terminals. In the final moments of each match, alliance robots race to engage with their hangar to prepare for transport!
Each match begins with a 15-second autonomous period, during which time alliance robots operate only on pre-programmed instructions to score points by:
· taxiing from their tarmac and
· retrieving and scoring their assigned cargo into the hub.
In the final 2 minutes and 15 seconds of the match, drivers take control of the robots and score points by:
· continuing to retrieve and score their assigned cargo into the hub and
· engaging with their hangar.
The alliance with the highest score at the end of the match wins!
5 ARENA
The Arena is modular and assembled, used, disassembled, and shipped many times during the competition season. It will undergo wear and tear. The Arena is designed to withstand rigorous play and frequent shipping. Every effort is made to ensure that Arenas are consistent from event to event. However, Arenas are assembled in different venues by different event staff and some small variations occur. For details regarding assembly tolerances, please refer to the 2022 Arena Layout and Marking Diagram. Successful teams will design Robots that are insensitive to these variations.
Illustrations included in this section are for a general visual understanding of the RAPID REACT Arena, and dimensions included in the manual are nominal. Please refer to the official drawings for exact dimensions, tolerances, and construction details. The official drawings, CAD models, and drawings for low-cost versions of important elements of the RAPID REACT Field are posted on the RAPID REACT - Season Materials web page on the FIRST website.
Figure 5‑1: RAPID REACT
Each Field for RAPID REACT is a 27 ft. (~823 cm) by 54 ft. (~1646 cm) carpeted area bound by and including the inward- and upward-facing surfaces of the guardrails, inward-facing surfaces of the Alliance Walls, and the front vertical faces of the Terminals.
Figure 5‑2 RAPID REACT Field boundary
The FIELD is populated with the following elements:
• 1 Hub (including 1 Upper Hub and 1 lower Hub),
• 2 Hangars (a red Hangar and a blue Hangar),
• 2 Terminals, and
• 14 Cargo RINGS.
The surface of the Field is low pile carpet, Shaw Floors, Philadelphia Commercial, Neyland II 20, “66561 Medallion” (please note that Neyland II carpet is not available for team purchase and the closest equivalent is Neyland III). The edge of the carpet is secured to the venue floor using 3M™ Premium Matte Cloth (Gaffers) Tape GT2 or comparable gaffers tape.
Guardrails form the long edges of the Field. Guardrails are a 1 ft. 8 in. (~51 cm) 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 3 ft. 2 in. (~97 cm) 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 reflected in the 2022 Official FIRST Field Drawings & Models. The other is designed and sold by AndyMark. While the designs are slightly different, the critical dimensions, performance, and expected user experience between them are the same. Detailed drawings for the AndyMark design are posted on the AndyMark website. All illustrations in this manual show the traditional Field design.
A run of black HDPE cable protectors extends from the guardrail on the scoring table side of the Field to the nearest Lower Exit of the HUB, straddling the Center Line. A cable protector run is made up of multiple floor segments and an exit segment. The total length of the cable protector run is 10 ft. 10⅝ in. (~332 cm). The floor segments are ¾ in. (~2 cm) tall, 7 in. (~18 cm) wide, with ~45° lead in ramps on each leading edge. It is secured to the carpet using hook fastener which increases the height to approximately ⅞ in. (~2 cm). Exit segments are attached to the guardrail with hook fastener and are 7 in. (~18 cm) tall, 6⅛ in. (~15 cm) wide and 1¾ in. (~4 cm) deep.
Figure 5‑4 Cable protector segment
Field zones and markings of consequence are described below. Unless otherwise specified, the tape used to mark lines and zones throughout the Field is 2-in. (~5 cm) 3M™ Premium Matte Cloth (Gaffers) Tape (GT2) or comparable gaffers tape.
Figure 5‑5 Zones and Markings
• Alliance Area: a 30 ft. (~914 cm) wide by 8 ft. 10 in. (~269 cm) deep infinitely tall volume formed by, and including the Alliance Wall, the edge of the carpet, and Alliance colored tape. It includes neither the Terminal AREA nor the terminal.
• Cargo Line: a 3 ft. (~91 cm) black line that starts 1 ft. (~30 cm) from the intersection of the Terminal and the ALLIANCE WALL and runs parallel to and 1 ft. (~30 cm) from the Alliance Wall.
• Cargo ring: 1 of 14 small rings used to keep the CARGO in place prior to the start of the MATCH. Rings are ⅛ in. (~3mm) thick, 1¾ in. (~4 cm) diameter O-rings (McMaster Item#: 9452K63). 12 rings are placed around the HUB, and 1 ring is in front of each terminal. They are secured to FIELD carpet with red or blue tape to indicate the color cargo to be placed on it.
• Center Line: a white line that bisects the length of the Field at a ~66° angle to the guardrail
• Hangar Zone: a 9 ft. 8 in. (~295 cm) wide, 10 ft. 8¾ in. (327 cm) deep, and infinitely tall volume defined by the Alliance Wall, guardrail, and Alliance colored tape. The Hangar Zone includes the tape.
Figure 5‑6 Hangar Zone
• Shadow Line: a black line that lies directly below the MID RUNG
Figure 5‑7 Shadow Line
• Terminal Area: 1 of 2 7 ft. 8½ in, (~235 cm) wide by 6 ft. 9 in. (~206 cm) deep and infinitely tall volumes bounded by and including purple tape.
Figure 5‑9 Terminal Area
• Terminal starting line: a white line spanning the width of the terminal area and located 2 ft. (~61 cm) from the back of the terminal area.
Figure 5‑10 Hub (click image to see field tour video)
The Hub is centered on the Field and shared between Alliances. It consists of 2 funnel-shaped goals (an Upper Hub and a lower Hub), upper and Lower Exits, and 4 fenders. The Hub is 8 ft. 11 in. (~272 cm) wide by 8 ft. 11 in. (~272 cm) deep by 8 ft. 8 in. (~264 cm) tall.
An agitator extends up the center of each Hub and rotates throughout the Match. The motors driving the agitator assemblies are supplied with (nominal) 12V each, and their direction may vary from MATCH to MATCH. Generally, the agitator causes a single Cargo dropped into the Upper Hub to reenter play in approximately 7 seconds and a cargo dropped in the lower Hub to reenter play in approximately 5 seconds.
An Upper Exit is 1 of the 4 extensions on which Cargo leaves the Upper Hub, and a Lower Exit is one of the 4 tunnels from which Cargo leaves the lower Hub.
4 legs, each centered under an UPPER EXIT, support the Upper Hub. The maximum Robot height defined in G106 is marked with black tape on each leg (i.e. the bottom edge of the tape is 4 ft. 4 in. (~132 cm) above FIELD carpet). A fender is located in between each of the Lower Exits.
Figure 5‑11 Hub with nominal dimensions
The opening of the lower Hub is 3 ft. 5 in. (~104 cm) above FIELD carpet, and the opening of the Upper Hub is 8 ft. 8 in. (~264 cm) above the field carpet. A web of #2 black plastic chain is hung 7½ in. (~19 cm) below the rim of the lower Hub opening.
Figure 5‑12 Hub with nominal dimensions
The Upper Hub opening has a 4-ft. (~122-cm) diameter, and the Lower Hub opening has a 5-ft. ⅛ in. (~153 cm) diameter.
Fenders are 3 ft. 10⅛ in. (~117 cm) wide by 1 ft. 10½ in. (~57 cm) tall, are positioned between each lower exit, and are perpendicular to the carpet. Fenders extend past the footprint of the lower Hub by 1 in. (~3 cm). The shortest horizontal distance between the outward face of a fender and the opening of the lower hub is 3⅞ in. (~10 cm). The shortest horizontal distance between the outward face of a fender and center of the lower hub is 2 ft. 9⅞ in. (~86 cm).
Figure 5‑13 Fender geometry
Figure 5‑14 Blue Hangar (click image to see field tour video)
A
HANGAR is located in front of each Hangar Wall
and DRIVER STATION 1. A Hangar assembly consists of truss structure, bases, 4 rungs,
RUNG mounting brackets, floor protection, and 2
Launch Pads. The maximum robot height limit described in G106 is marked on the
center of each horizontal truss assembly in black tape (i.e. the bottom edge of
the tape is 5 ft. 6 in. (~168 cm) above floor protection carpet).
Figure 5‑15 Hangar nominal dimension
Hangar truss is 1 ft. x 1 ft. (~30 cm x ~30 cm) square truss. The truss structure is 9 ft. ¼ in. (~275 cm) wide, 10 ft. ¾ in. (~307 cm) deep, and 6 ft. 2 in. (~188 cm) tall when measured from the field carpet. Each of the 4 legs is attached to a baseplate (baseplates are not part of the truss structure). Each baseplate extends 6 in. (~15 cm) out from each leg face and is ⅛ in. (~3 mm) thick.
Each Hangar has 4 rungs highlighted in Figure 5‑16: low, mid, high, and traversal. Rungs are 1¼ in. Schedule 40 steel pipes, with a 1.66 in. (~4 cm) outer diameter, and are powder coated to reflect the Alliance color. Rungs are 7 ft. (~213 cm) wide and bound by the truss and brackets (note that pipe that overlaps the truss structure and brackets is not considered part of the Rung).
Figure 5‑17 illustrates spacing between rungs. The top of the Low Rung is 4 ft. ¾ in. (~124 cm) above Field carpet. The top of the Mid Rung is 5 ft. ¼ in. (~153 cm) above floor protection carpet, and its center is 3 ft. 6 in. (~107 cm) from the center of the Low Rung. The top of the High Rung is 6 ft. 3⅝ in. (~192 cm) above floor protection carpet, and the top of the Traversal Rung is 7 ft. 7 in. (~231 cm) above floor protection carpet. Mid, high, and Traversal Rungs are spaced such that their centers are 2 ft. (~61 cm) apart. The horizontal distance between the center of the traversal rung and the alliance wall is 3 ft. 3 in. (~99 cm).
Figure 5‑17 Rung spacing
A layer of ⅛ in. (~3 mm) thick hardboard is installed on top of the FIELD carpet in the space bounded by the truss bases to protect venue flooring. The hardboard is covered with a layer of carpet and adds approximately ⅜ in. (~1 cm) of height to the area.
Figure 5‑18 Floor protection cross section
Figure 5‑19 Launch Pad locations
Launch Pads are mounted to the 2 truss legs closest to the Hub such that they are flush to the top of the truss base. Each Launch Pad is a piece of ¼ in. (~6 mm) thick, 1 ft. 5¼ in. (~44 cm) tall, and 10 in. (~25 cm) wide HDPE of the corresponding Alliance color.
Figure 5‑20 Terminal (click image to see field tour video)
One Terminal is in each of the 2 Field corners opposite the Hangars. Each TERMINAL is shared between Alliances. A Terminal consists of 1 ramp, 1 Guard, 1 PuRPle Plane, 1 Chute, and other structure elements shown in Figure 5‑20. Each Terminal has 5 Cargo delivery openings through which Robots may transfer Cargo to Human Players. The space between the PuRPle Plane and the retention chain can hold approximately 10 Cargo.
Figure 5‑21 Terminal details
Each Terminal is 4 ft. (~122 cm) deep, 8 ft. 1⅛ in. (~247 cm) wide (excluding the ends of the ramp) and is a maximum of 5 ft. 1¾ in. (~157 cm) tall.
A 2¾ in. (~7 cm) tall ramp leads to the 1 ft. 5¼ in. (~44 cm) wide, 1 ft. (~30 cm) tall openings.
The Chute is a plastic sheet with 1⅛ in. (~3 cm) tall aluminum angles spaced 6½ in. (~17 cm) from each other to form channels. The Chute is angled such that the top of the plastic is 3 ft. 7 in. (~109 cm) above carpet on the Field side and 4 ft. 2 in. (~127 cm) on the Human Player side. The high edge of the Chute is padded with black foam cushion.
Figure 5‑22 PuRPle Plane
The Terminal has exterior HPDE and interior polycarbonate ramps which each run the width of the Terminal and meet at a height of 2¾ in. (~7 cm). The exterior ramp is 10 in. (~25 cm) deep. Once pushed through any opening, a Cargo rolls down the interior ramp into the Terminal Area.
A PuRPle Plane is a virtual boundary which extends the width of the Terminal and is defined by the Field side edge of the Guard and the purple tape which runs parallel to the interior ramp. It is 1 ft. (~30 cm) from the Human Player side of the Terminal.
The Guard is the framing formed by all Terminal structure above the Chute, and it is used by Human Players to feed Cargo to the Field. The top of the Guard is above and parallel to the Chute. The Guard creates a 9¾ in. tall opening (~25 cm) which is 4 ft. 2 in. (~127 cm) above the carpet.
Figure 5‑23 Alliance Wall (click image to see field tour video)
An Alliance Wall consists of 3 Driver Stations and a Hangar Wall.
Figure 5‑24 Driver Station dimensions
A Driver Station is 1 of 3 assigned positions in an Alliance Wall from where a drive team operates their Robot. Each Driver Station is made from a 3 ft. ¾ in. (~93 cm) tall diamond plate base topped with a 3 ft. 6 in. (~107 cm) 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 5 ft. 9 in. (~175 cm) wide and 1 ft. ¼ in. (~31 cm) deep. There is a 4 ft. 6 in. (~137 cm) long by 2 in. (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.
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 team sign: displays
the team number and located at the top of each Driver
Station
- 1 team LED stack:
indicates Alliance color, Robot status, E-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 E-stop LED. LED states are as follows:
- 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 is Bypassed, 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. This light is also off, regardless of Robot connection status, after the Match has concluded.
- 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.
- Off: the robot is not disabled
by the field.
· 1 string of LED nodes described in Section 5.6.1.1 Driver Station LED Strings.
- 1 timer (in Driver Station 2 only): displays the official
time remaining in the Match and Timeouts. It is marked with white tape along the
bottom edge.
· FMS hardware and wiring: mostly located below the Driver Station 2 shelf
5.6.1.1
Driver
Station
LED Strings
A string of LED nodes is mounted to the bottom of each Driver Station window frame. The string is used to communicate field safety information, match state, and cargo bonus progress.
If the light string is all green, the field is safe for humans.
Figure 5‑25 FIELD is safe for humans
During a match, nodes 1 through 4 and 15-17 are yellow if the match is in auto (as shown in Figure 5‑26) and white if in teleop (as shown in Figure 5‑27 and Figure 5‑28). Additionally, the center 10 nodes of each string, 5 through 14, indicate the Alliance’s Cargo Bonus progress in the Alliance’s color. The first scored Cargo causes node 5 to turn on. The second Cargo causes node 5 to dim. The third Cargo causes the node 6 to turn on; the fourth Cargo causes node 6 to dim, and so on (see Figure 5‑26, Figure 5‑27, and Figure 5‑28).
If an alliance achieves a quintet (as described in Table 6‑1), node 14 turns on (see Figure 5‑27) indicating the lowered threshold to achieve the cargo bonus.
Figure 5‑26 Match is in Auto, red Alliance has scored 3 Cargo
Figure 5‑27 Match is in Teleop, red Alliance achieved a quintet
Figure 5‑28 Match is in Teleop, red Alliance has scored 7 Cargo, but without a quintet
If the Cargo Bonus is achieved, all 3 Driver Station strings display an animated light sequence, blink twice, and then all nodes remain dim in the Alliance color for the remainder of the Match.
Figure 5‑29 Red Alliance has earned the Cargo Bonus
Driver Station light strings remain active after Teleop ends for 5 seconds. The lights then pulse for an additional 5 seconds (to indicate that the time frame described in Section 6.4, item C is complete).
A Hangar Wall is a 2 ft. 9 ⅝ in. (~85 cm) wide by 6 ft. 5¾ in. (~197 cm) tall structure located between Driver Station 1 and the guardrail. The aluminum frame is covered with clear polycarbonate on the FIELD side.
Figure 5‑30 Hangar Wall frame
Figure 5‑31: Cargo
RAPID REACT is played with oversized tennis balls called Cargo, custom modified for FIRST by Flaghouse. Cargo is 9½ in. (~24 cm) in diameter, weighs 9½ oz. (~270 g), and has a fuzz surface. Cargo is inflated to 3½ psi. ±½ psi. (checked every morning and lunch break and as outliers are suspected using this gauge at official events). Typically, if a Cargo is dropped on field carpet from a height of 3 ft., it bounces back to a height between 2 ft. 1 in. (~64 cm) and 2 ft. 6 in. (~76 cm) (as measured from the bottom of the ball). Cargo is available for purchase at AndyMark, part numbers am-4600_blue and am-4600_red. The oversized tennis balls used as CARGO are not manufactured with any tight tolerance. Wall thickness, surface pilling, and shedding may vary. An off-the-shelf ball may perform differently from the official CARGO.
The Upper Hub is marked with a single 360° vision target consisting of 5 in. (~13 cm) long strips of 2 in. (~5 cm) wide 3M 8830 Scotchlite™ Reflective Material. A sample of the material is included in each Rookie Kickoff Kit and FIRST Choice. The target is a 4 ft. 5⅜ in. (~136 cm) diameter ring of plastic with 16 strips adhered to it with 5½ in. (~14 cm) gaps between them. The ring is aligned such that 1 of the gaps is centered over each UPPER EXIT. The distance from FIELD carpet to the top of the target assembly is 8 ft. 8 in. (~264 cm); the distance from field carpet to the bottom of the vision tape is 8 ft. 5⅝ in. (~258 cm).
Figure 5‑32: Vision target
The Field Management System (FMS) is the electronics core responsible for sensing and controlling the FIRST Robotics Competition Field. The FMS encompasses all Field electronics, including computers, Referee touchscreens, wireless access point, sensors, stack lights, 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 will communicate with FMS. Once connected, the open ports available are described in Table 9‑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‑1. 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.
|
Event |
Timer Value |
Audio Cue |
|
Match start |
0:15 (for Auto) |
“Cavalry Charge” |
|
Auto ends |
0:00 (for Auto) |
“Buzzer” |
|
Teleop begins |
2:15 |
“3 Bells” |
|
Hangar Zone protection engaged |
0:30 |
“Train Whistle” |
|
Match end |
0:00 |
“Buzzer” |
|
Match stopped |
n/a |
“Foghorn” |
|
Timeout warning |
1:00 |
“Trumpet Fanfare” |
|
Timeout end |
0:00 |
“Buzzer” |
6
MATCH Play
During RAPID REACT, 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.
Figure 6‑1 Match setup
22 Cargo, 11 red and 11 blue, are staged for each Match as follows:
A. Each DRIVE TEAM may pre-load 1 of their Cargo in their Robot such that the Cargo is fully supported by their Robot.
a. Any of the 3 Cargo not pre-loaded in the Alliance’s Robots are staged between the opponent’s Alliance Wall and the adjacent Cargo Line.
B. 1 Alliance colored Cargo is staged in the Terminal closest to its Alliance Area.
C. 1 alliance colored cargo is centered in front of the terminal closest to its alliance area and placed on a cargo ring whose center is 1½ in. (~4 cm) from the edge of the ramp.
D. 12 Cargo, 6 red and 6 blue, are staged on Cargo Rings beyond the Tarmacs as shown in Figure 6‑2. Cargo is placed as shown on a 25 ft. 6 in. (~777 cm) diameter circle centered around the Hub. Please refer to the 2022 Arena Layout and Marking Diagram for a fully dimensioned drawing of the placement locations. Cargo centers are 40⅜ in. from the outside edges of the tarmacs.
Figure 6‑2 Cargo staging just outside Tarmacs
Each DRIVE TEAM stages their Robot such that its bumpers are fully contained within 1 of its Tarmacs.
If order of placement matters to either or both Alliances, the Alliance must notify the Head Referee during setup for that Match. Upon notification, the Head Referee will require Alliances to alternate placement of all Robots. In a Qualification Match, 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 a Playoff Match, the same pattern is applied, but instead of blue Alliance placing last, the higher seeded Alliance (regardless of color) places last.
Humans stage for the match as follows:
A. exactly 1 Human Player per Alliance stages in each Terminal Area
a. the human player in the terminal area furthest from their alliance area stages behind the terminal starting line,
B. Drivers, Coaches, and any additional Human Players stage inside their Alliance Area and behind the Starting Line, and
C. Technicians stage in the event-designated area near the Field.
The first phase of each Match is called Autonomous (Auto) and consists of the first 15 seconds. During Auto, Robots operate without any drive team control or input. Robots attempt to taxi from the Tarmac, score Cargo in the Hub, and retrieve additional Cargo from around the Field. Human players attempt to score their cargo in the hub.
The second phase of each Match is called the Teleoperated Period (Teleop) and consists of the remaining 2 minutes and 15 seconds (2:15). During this phase, Drivers remotely operate Robots to retrieve and score their Cargo in the Hub and engage with their Hangar.
Alliances are rewarded for accomplishing various actions through the course of a Match, including taxiing, scoring Cargo in the Hub, engaging with their Hangar, and winning or tying Matches.
Rewards are granted either via Match points (which contribute to the Alliance’s Match score) or Ranking Points (sometimes abbreviated to RP, which increase the measure used to rank teams in the Qualification Tournament). Such actions, their criteria for completion, and their point values are listed throughout Section 6.4.
All scores are assessed and updated throughout the Match, except as follows:
A. assessment of Cargo scored in the Hub continues for up to 5 seconds after the Arena timer displays 0 following Auto.
B. assessment of Cargo scored in the Hub continues for up to 10 seconds after the Arena timer displays 0 following Teleop.
C. assessment of Hangar points is made 5 seconds after the Arena timer displays 0, or when all Robots have come to rest following the conclusion of the Match, whichever happens first.
Taxi and Hangar points are both evaluated and scored by human Referees. Teams are encouraged to make sure that it is obvious and unambiguous that a Robot has met the criteria.
Point values for tasks in RAPID REACT are detailed in Table 6‑1.
A cargo is scored in an upper or lower hub if it passes through the top horizontal opening of the upper or lower hub and passes through the sensor array, and the points awarded for that cargo are assigned based on when the cargo passed through the sensor array.
A ROBOT may only earn points for a single rung. To qualify for Hangar points from a given Rung, a Robot may only be contacting:
· Rung(s) at that level or higher (i.e. the level is determined by the lowest Rung with which a Robot is in contact),
· truss structure,
· Launch Pads,
· the Alliance Wall,
· Cargo,
· guardrails,
· an opponent Robot, and/or
· another Robot qualified for any Hangar points, including those awarded per violation of G208.
Table 6‑1: RAPID REACT point values
|
Award |
Awarded for… |
Match Points |
Ranking Points |
|
|
auto |
teleop |
|||
|
Taxi |
each Robot whose Bumpers have completely left the Tarmac from which it started at any point during Auto |
2 |
|
|
|
Cargo |
each Alliance color Cargo scored in the lower Hub |
2 |
1 |
|
|
each Alliance color Cargo scored in the Upper Hub |
4 |
2 |
|
|
|
Hangar (per Robot) |
Low Rung |
|
4 |
|
|
Mid Rung |
|
6 |
|
|
|
High Rung |
|
10 |
|
|
|
Traversal Rung |
|
15 |
|
|
|
Cargo Bonus |
20 or more Alliance colored Cargo scored in the Hub. If at least 5 Alliance colored Cargo are scored in Auto, called a Quintet, this threshold drops to 18. |
|
|
1 |
|
Hangar Bonus |
Alliance is credited with at least 16 Hangar points |
|
|
1 |
|
Tie |
completing a Match with the same number of Match points as your opponent |
|
|
1 |
|
Win |
completing a Match with more Match points than your opponent |
|
|
2 |
An Alliance can earn up to 4 Ranking Points per Qualification Match as described in Table 6‑1. There are no Ranking Points or comparable points for the Cargo Bonus or Hangar Bonus in Playoff Matches.
Upon a rule violation, 1 or more of the penalties listed in Table 6‑2 are assessed.
Table 6‑2 Rule violations
|
Penalty |
Description |
|
Foul |
|
|
Tech Foul |
a credit of 8 points toward the opponent’s Match score
|
|
Yellow Card |
|
|
Red Card |
|
|
Disabled |
the state in which a Robot is commanded to deactivate all outputs, rendering the Robot inoperable for the remainder of the Match. |
|
Disqualified |
FIRST Robotics Competition uses 3 words in the context of how rules and violations are assessed in deliberate ways. 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 rule violations that happen for fewer than approximately 3 seconds.
· Continuous describes rule violations that happen for more than approximately 10 seconds.
· Repeated describes rule violations that happen more than once within a Match.
See Section 11.2.1 Yellow and Red Cards for additional 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‑3 Violation examples
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 with RAPID REACT. Only 1 of the 5 drive team members is permitted to be a non-Student.
The intent of the definition of drive team and drive team related rules is that, barring extenuating circumstances, the drive team consists of people who arrived at the event affiliated with that team and are responsible for their team’s and Robot’s performance at the event (this means a person may be affiliated with more than 1 team). The intent is not to allow teams to “adopt” members of other teams for strategic advantage for the loaning team, borrowing team, and/or their Alliance (e.g. an Alliance Captain believes 1 of their Drivers has more experience than a Driver on their first pick, and the teams agree the first pick team will “adopt” that Driver and make them a member of their drive team for Playoffs).
The definition isn’t stricter for 2 main reasons. First, to avoid additional bureaucratic burden on teams and event volunteers (e.g. requiring that teams submit official rosters that Queuing must check before allowing a drive team into the Arena). Second, to provide space for exceptional circumstances that give teams the opportunity to display Gracious Professionalism (e.g. a bus is delayed, a Coach has no Drivers, and their pit neighbors agree to help by loaning Drivers as temporary members of the team until their bus arrives).
Table 6‑4 Drive team roles
|
Role |
Description |
Max./ DRIVE TEAM |
Criteria |
|
Coach |
1 |
any team member, must wear “Coach” button |
|
|
Driver |
an operator and controller of the Robot
|
3 |
Student, must wear a “drive team” button |
|
Human Player |
|
||
|
Technician |
a resource for Robot troubleshooting, setup, and removal from the Field |
1 |
any team member, must wear “Technician” button |
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
While the Technician may be the primary technical member of the drive team, all members of the drive team are encouraged to have knowledge of the basic functionality of the Robot, such as the location and operation of the main circuit breaker, connecting and resetting joysticks or gamepads from the Operator Console, and removing the Robot from the Field.
If an Alliance does not have at least 2 Human Players, 1 of the Alliance’s teams must substitute a student Technician as a Human Player to be compliant with H310 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.
Cargo that leaves the Field, other than via the Terminal, are placed back into the Field approximately at the point of exit by Field Staff (Referees, FIRST Technical Advisors (FTAs), or other staff working around the Field) at the earliest safe opportunity.
Note that, except via the Terminal, Robots may not deliberately cause opponent Cargo to leave the Field (see G401).
An Arena Fault is not called for Matches that accidentally begin with damaged Cargo. Damaged Cargo is not replaced until the next Arena reset period. Drive teams should alert the Field Staff to any missing or damaged Cargo prior to the start of the Match.
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 LED lights to green and drive teams may retrieve their Robot.
In addition to the 2 minutes and 30 seconds (2:30) of game play, each Match also has pre- and post-Match time to reset the Arena. 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.
7
Game Rules: ROBOTS
The 2022 FRC Game Manual implements updated methods for identifying rule numbers and recurring rules. See Section 1.7 This Document & Its Conventions for details.
G101 *Dangerous Robots: not allowed. Robots whose operation or design is dangerous or unsafe are not permitted.
Violation: If before the Match, the offending Robot will not be allowed to participate in the Match. If during the Match, the offending Robot will be Disabled.
Examples include, but are not limited to:
a. uncontrolled motion that cannot be stopped by the drive team,
b. Robot parts “flailing” outside of the Field,
c. Robots dragging their battery, and
d. Robots that consistently extend beyond the Field.
G102 *Robots, stay on the Field during the Match. Robots and anything they control, e.g. Cargo, may not contact anything outside the Field except for Momentary incursions into the Terminal and Momentary contact with the Chute.
Violation: Disabled.
Please be conscious of Referees and Field Staff working around the Arena who may be in close proximity to your Robot.
G103 *Keep your Bumpers low. Bumpers must be in the Bumper Zone (see R402) during the Match.
Violation: Foul. If Repeated or greater than Momentary, Disabled.
G104 *Keep your Bumpers together. Bumpers may not fail such that a segment completely detaches, any corner (as defined in R401) of a Robot’s Frame Perimeter is exposed, or the team number or Alliance color are indeterminate.
Violation: Disabled.
G105 *Keep it together. Robots may not intentionally detach or leave parts on the Field.
Violation: Red Card.
G106 Tall Robots in Hangar Zone only. Robot height, as measured when it’s resting normally on a flat floor, may not exceed the maximum Starting Configuration height (4 ft. 4 in. (~132 cm)) unless any part of the Robot’s Bumpers is in its Hangar Zone, in which case its height may not exceed 5 ft. 6 in. (~167 cm).
Violation: Foul. Tech Foul if the over-extension blocks an opponent’s shot, scores a Cargo, or is the first thing that contacts Cargo exiting from an Upper Exit. If the over-extension enables Hangar points, the Robot is no longer eligible for Hangar points.
This measurement is intended to be made as if the Robot is resting on a flat floor, not relative to the height of the Robot from the Field carpet.
For example, a Robot that is at an angle while driving over something may actually exceed the height limit when compared to the carpet of the Field.
Figure 7‑1 Robot height example
G107 Don’t overextend yourself. Robots may not extend more than 16 in. (~40 cm) beyond their Frame Perimeter.
Violation: Foul. Tech Foul if the over-extension blocks an opponent’s shot, scores a Cargo, or is the first thing that contacts Cargo exiting from an Upper Exit. If the over-extension enables Hangar points, the Robot is no longer eligible for Hangar points.
Examples of compliance and non-compliance of this rule are shown in Figure 7‑2.
Yellow bars represent the limits of the Frame Perimeter and are drawn in the same orientation of the Robot’s Frame Perimeter. Green bars represent a measured extension from the Frame Perimeter that does not exceed the limit defined in this rule. Red bars represent a measured extension from the Frame Perimeter that exceeds the limit in this rule. Robots A and C violate this rule, whereas Robot B does not.
Figure 7‑2 Examples of compliance and non-compliance of this rule
G108 Not too high. A Robot may not position itself such that any part of its Bumpers is higher than the High Rung for a greater than MOMENTARY period of time.
Violation: Robot is ineligible for any Hangar points.
G109 Avoid the PuRPle Plane. Robots may never extend beyond the PuRPle Plane.
Violation: Disabled.
G201 *Don’t expect to gain by doing others harm. Strategies clearly aimed at forcing the opponent Alliance to violate a rule are 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: Foul. If Repeated, Tech Foul.
G201 does not apply for strategies consistent with standard gameplay, for example a red Alliance Robot in their hangar zone in the final 30 seconds of the match contacts a blue alliance robot.
G201 requires an intentional act with limited or no opportunity for the team being acted on to avoid the penalty, such as:
a. forcing the opposing Robot to have greater-than-Momentary CONTROL of 3 Cargo or
b. a Robot raising an extension to touch their Mid Rung as an opponent is about hit them with no intention to actually climb
G202 *There’s a 5-count on Pins. Robots may not Pin an opponent’s Robot for more than 5 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 Robot is considered Pinned until the Robots have separated by at least 6 ft. (~183 cm) from each other, either Robot has moved 6 ft. from where the Pin initiated, or the PINNING ROBOT gets PINNED, whichever comes first. The Pinning Robot(s) must then wait for at least 3 seconds before attempting to Pin the same Robot again.
Violation: Foul, plus an additional Tech Foul for every 5 seconds in which the situation is not corrected.
A team’s desired direction of travel is not a consideration when determining if a Robot is Pinned.
If the PINNING ROBOT gets PINNED, the original PIN count terminates. Otherwise, if a ROBOT re-PINS the same ROBOT before the 3 seconds referenced in the last sentence of this rule, the REFEREE’S count resumes from the initial PIN (versus starting at 0).
G203 *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: Tech Foul, plus an additional Tech Foul for every 5 seconds in which the situation is not corrected.
Examples of violations of this rule include, but are not limited to:
a. fully blocking all access to either Terminal,
b. shutting down access to all opponents’ Cargo,
c. quarantining all opponents to a small area of the Field, and
d. blocking all access to the opponents’ hangar.
A single Robot blocking access to a particular area of the Field is not a violation of this rule.
2 Robots independently playing defense on 2 opponent Robots is not a violation of this rule.
Note, G204, G205, and G206 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.
G204 *Stay out of other Robots. A robot may not use a component outside its frame perimeter (except its bumpers) to initiate contact with an opponent robot inside the vertical projection of that opponent robot’s frame 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: Foul.
For the purposes of G204, “initiate contact” requires movement towards an opponent robot.
In a collision, it’s possible for both robots to initiate contact.
G205 *This isn’t combat robotics. A robot may not damage or functionally impair an opponent robot in either of the following ways:
A. deliberately, as perceived by a referee.
B. regardless of intent, by initiating contact inside the vertical projection of an opponent robot’s frame perimeter. Contact between the robot’s bumpers or components inside the robot’s frame perimeter and components inside an opening of an opponent’s bumpers is an exception to this rule.
Violation: Tech foul and yellow card. If opponent robot is unable to drive, Tech foul and red card
FIRST Robotics Competition can be a full-contact competition and may include rigorous game play. While this rule aims to limit severe damage to robots, teams should design their robots to be robust.
The exception in G205-B effectively means that robots with bumper gaps are at their own risk regarding damaging contact in these areas.
Examples of violations of this rule include, but are not limited to:
a. A robot leaves an arm extended, spins around to change course, and unintentionally hits and damages a component inside the frame perimeter of a nearby opponent robot.
b. A robot, in the process of trying to quickly reverse direction, tips up on a single pair of wheels, lands atop an opponent robot, and damages a component inside that opponent’s frame perimeter.
c. A robot high-speed rams and/or repeatedly smashes an opponent robot and causes damage. The referee infers that the robot was deliberately trying to the damage the opponent’s robot.
Examples of functionally impairing another robot include, but are not limited to:
d. opening an opponent’s relief valve such that the opponent’s air pressure drops and
e. powering off an opponent’s robot (this example also clearly results in a red card because the robot is no longer able to drive).
At the conclusion of the match, the Head referee may elect to visually inspect a robot to confirm violations of G205 made during a match and remove the violation if the damage cannot be verified.
For the purposes of G205, “initiating contact” requires movement towards an opponent robot.
In a collision, it’s possible for both robots to initiate contact.
G206 *Don’t tip or entangle. A robot may not deliberately, as perceived by a referee, attach to, tip, or entangle with an opponent robot.
Violation: Tech foul and yellow card. If continuous or opponent robot is unable to drive, Tech foul and red card.
Examples of violations of this rule include, but are not limited to:
a. using a wedge-like mechanism to tip over opponent robots,
b. making bumper-to-bumper contact with an opponent robot that is attempting to right itself after previously falling over and causing them to fall over again, and
c. causing an opponent robot to tip over by contacting the robot after it starts to tip if, in the judgement of the referee, that contact could have been avoided.
Tipping as an unintended consequence of normal robot to robot interaction, as perceived by the referee, is not a violation of G206.
G207 Let them shoot. A Robot may not contact (either directly or transitively through Cargo and regardless of who initiates contact) an opponent Robot whose Bumpers are contacting their Launch Pad.
Violation: Foul.
G208 Let them climb. A Robot may not contact (either directly or transitively through Cargo and regardless of who initiates contact)
A. an opponent Robot contacting their mid, high, and/or Traversal Rungs or
B. an opponent Robot whose Bumpers are at least partially in their Hangar Zone during the final 30 seconds of the Match.
Violation: The contacted opponent Robot is awarded Traversal Rung Hangar points at the end of the Match regardless of the opponent ROBOT’S eligibility for HANGAR points.
G209 Don’t climb on each other. A Robot may not be fully supported by a partner Robot.
Violation: Tech Foul. If violation occurs while either robot is in contact with their hangar, neither robot is eligible for hangar points.
G210 During Auto, no defense. During Auto, a Robot with any part of its Bumpers on the opposite side of the Field (i.e. on the other side of the Center Line from its Alliance's Tarmacs) may contact neither Cargo still in its staged location on the opposite side of the Field nor an opponent robot.
Violation: Tech Foul
G301 Be careful what you interact with. Robots and Operator Consoles are prohibited from the following actions with regards to interaction with Arena elements. Items A-C exclude Cargo. Items A-E exclude RUNGS.
A. grabbing,
B. grasping,
C. attaching to (including the use of a vacuum or hook fastener to anchor to the Field carpet and excluding use of the Driver Station hook-and-loop tape, plugging in to the provided power outlet, and plugging the provided Ethernet cable into the Operator Console),
D. becoming entangled with,
F. damaging.
Violation: Match won’t start until the situation is corrected. If during a Match, Tech Foul. If during a Match and Repeated or longer than Momentary, Yellow Card. If offense is via a Robot and the Head Referee determines that further damage is likely to occur, offending Robot will be Disabled. 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.
Cargo is expected to undergo a reasonable amount of wear and tear as they are handled by Robots, such as scratching or marking. Gouging, popping, tearing off pieces, or routinely marking Cargo are violations of this rule.
G302 Lower Exits are off limits. Robots may not reach into or straddle the Lower Exit. Momentary reaching into and/or Momentary straddling of the Lower Exit are exceptions to this rule.
Violation: Tech Foul. If Continuous or Repeated, Yellow Card.
G401 *Keep Cargo in bounds. Robots may not eject opponent Cargo from the Field other than through the Terminal (either directly or by bouncing off a Field element or other Robot).
Violation: Foul per Cargo.
G402 *Cargo: use as directed. Robots may neither deliberately use Cargo in an attempt to ease or amplify the challenge associated with Field elements nor deliberately strand opponent Cargo on top of a hangar or hub.
Violation: Tech Foul per Cargo.
Examples include, but are not limited to:
a. shooting Cargo at Robots and
b. corralling Cargo in the opponents’ Hangar Zone to clog/congest it.
G403 2 Cargo max. Robots may not have greater-than-Momentary control of more than 2 Cargo at a time, either directly or transitively through other objects.
A Robot is in control of Cargo if:
A. the Cargo is fully supported by the Robot,
B. the Cargo travels across the Field such that when the Robot changes direction, the Cargo travels with the Robot,
C. the Robot is holding Cargo against a Field element in attempt to guard or shield it, or
D. the robot is preventing a cargo from leaving a lower exit.
Violation: Foul per additional Cargo. If egregious, Yellow Card.
Egregious examples include but are not limited to the following:
a. simultaneous control of 5 Cargo
b. Continuous control of 3 or more Cargo
c. frequent control of 3 or more cargo (an approximate count for frequent in this context is if this rule is violated more than 3 times in a Match)
G404 Don’t hoard opposing Cargo. A Robot may not restrict access to more than 3 opposing Alliance Cargo except during the final 30 seconds of the Match.
Violation: Foul, plus an additional Tech Foul for every 5 seconds in which the situation is not corrected.
Examples of restricting access to Cargo includes, but are not limited to,
a. holding 2 opposing Alliance Cargo within your Robot and blocking an opponent from getting to 2 more opposing Alliance Cargo cornered behind your Robot, or
b. using Hangar contact protection afforded per G208-A to prevent an opponent from legally reaching 4 opposing Alliance Cargo cornered in the back of your Hangar.
In a scenario where a Robot is Pinning (per G202), Referees are instructed to disregard this rule so they can focus on the Pinning.
G405 Don’t catch Cargo. A Robot may not Repeatedly score or gain greater-than-Momentary control of Cargo released by an Upper Exit until and unless that Cargo contacts anything else besides that Robot or Cargo controlled by that Robot.
Violation: Foul per Cargo.
It is important to design your Robot to mitigate the chance your Robot could inadvertently or unintentionally catch Cargo as it leaves an Upper Exit.
8
Game Rules: Humans
FIRST is committed to Equity, Diversity, and Inclusion and as such, FIRST makes reasonable accommodations for persons with disabilities that request accommodation. If a participant needs an accommodation for an event, please talk to a volunteer at the event or contact local leadership before the event so they can help ensure the accommodation is provided.
Accommodations are adjustments that allow all people with disabilities to access the building and participate in the game. Accommodations are determined reasonable given they do not create an undue hardship or cause safety concerns.
H101 *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: Behavior will be discussed with team or individual. Violations of this rule are likely to escalate to yellow or Red Cards rapidly (i.e. the threshold for egregious violations is relatively low.)
Examples of inappropriate behavior include, but are not limited to:
a. use of offensive language or other uncivil conduct,
b. more than Momentary blockage of an opponent Human Player from the Terminal or their Cargo, and
c. use of CARGO as a projectile in an attempt to inhibit an opponent ROBOT.
Examples of particularly contemptible behavior that is likely to result in Arena ejection include, but are not limited to, the following:
d. assault, e.g. throwing something that hits another person (even if unintended),
e. threat, e.g. saying something like “if you don’t reverse that call, I’ll make you regret it,”
f. harassment, e.g. badgering someone with no new information after a decision’s been made or a question’s been answered,
g. bullying, e.g. using body or verbal language to cause another person to feel inadequate,
h. insulting, e.g. telling someone they don’t deserve to be on a drive team,
i. swearing at another person (versus swearing under one’s breath or at oneself), and
j. yelling at another person(s) in anger or frustration.
H102 *Enter only 1 Robot. Each registered FIRST Robotics Competition team may enter only 1 Robot (or “robot,” a robot -like assembly equipped with most of its drive base, i.e. its Major Mechanism that enables it to move around a Field) into a 2022 FIRST Robotics Competition Event.
“Entering” a Robot (or robot) into a FIRST Robotics Competition means bringing it to or using it at the event such that it’s an aid to your team (e.g. for spare parts, judging material, or for practice).
While “most of its drive base” is a subjective assessment, for the purposes of this rule, an assembly whose drive base is missing all wheels/treads, gearboxes, and belts/chains is not considered a “robot.” If any of those Components are incorporated, the assembly is now considered a “robot.”
This rule does not prohibit teams from bringing in robots from other FIRST programs for the purposes of awards presentations or pit displays.
Violation: Verbal warning. Egregious or subsequent violations at any point during the event will be addressed by the Head Referee, the Lead Robot INSPECTOR (LRI), and/or Event Management.
H103 *Humans, stay off the Field until green. Team members may only enter the Field if the Driver Station LED strings are green, unless explicitly instructed by a Referee or an FTA.
Violation: Verbal warning. If subsequent violations at any point during the event, Yellow Card.
Egregious violations of this rule to which H201 may apply include, but are not limited to:
a. pushing past the Field reset person blocking an open gate to get on the Field,
b. ignoring a warning to not go on the Field,
c. walking on to the Field during a Match, and
d. reaching into the Field and grabbing a Robot during a Match.
Violations of this rule apply to the entire team, not specifically to any 1 individual. For example, a member of Team 9999 enters the Field prior to lights going green after Match 3, and a different member enters the Field prior to lights going green after Match 25. The team receives a verbal warning for the first violation and a Yellow Card for the second.
H104 *Never step over the guardrail. Team members may only enter or exit the Field through open gates.
Violation: Verbal warning. If subsequent violations at any point during the event, Yellow Card.
Teams are encouraged to ensure that all members of their drive team are aware of this rule. It’s easy to violate, particularly when teams are doing their best to move on and off the Field quickly. The violations of this rule are intended to avoid nuisance penalties, but still enforce safety requirements around the Field. There is the potential for injury when stepping over the guardrail.
Violations of this rule apply to the entire team, not specifically to any 1 individual. For example, a member of Team 9999 steps over the guardrail prior to Match 3, and a different member steps over the guardrail prior to Match 25. The team receives a verbal warning for the first violation and a Yellow Card for the second.
H105 *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: Behavior will be discussed with team or individual. Violations of this rule are likely to escalate rapidly to yellow or Red Cards and may lead to dismissal from the event (i.e. the threshold for egregious violations is relatively low.)
Example 1: A Match is being played by Teams A, B, and C, in which Team C is encouraged by Team D to not engage with the Hangar at the end of the Match, resulting in Teams A, B, and C not earning a Ranking Point. Team D’s motivation for this behavior is to prevent Team A from rising in the Tournament rankings and negatively affecting Team D’s ranking. Team D has violated this rule.
Example 2: A Match is being played by Teams A, B, and C, in which Team A is assigned to participate as a Surrogate. Team D encourages Team A to not participate in the Match so that Team D gains ranking position over Teams B and C. Team D has violated this rule.
FIRST considers the action of a team influencing another team to throw a Match, to deliberately miss Ranking Points, etc. incompatible with FIRST values and not a strategy any team should employ.
H106 *Letting someone coerce you in to 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: Behavior will be discussed with team or individual. Violations of this rule are likely to escalate rapidly to yellow or Red Cards and may lead to dismissal from the event (i.e. the threshold for egregious violations is relatively low.)
Example 1: A Match is being played by Teams A, B, and C. Team D requests Team C ignore the Hangar at the end of the Match, resulting in Teams A, B, and C not being able to earn Hangar Bonus. Team C accepts this request from Team D. Team D’s motivation for this behavior is to prevent Team A from rising in the Tournament rankings negatively affecting Team D’s ranking. Team C has violated this rule.
Example 2: A Match is being played by Teams A, B, and C, in which Team A is assigned to participate as a Surrogate. Team A accepts Team D’s request to not participate in the Match so that Team D gains ranking position over Teams B and C. Team A has violated this rule.
FIRST considers the action of a team influencing another team to throw a Match, to deliberately miss Ranking Points, etc. incompatible with FIRST values and not a strategy any team should employ.
H107 *Don’t abuse Arena access. Team members (except Drivers, Human Players, and 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: Yellow Card.
The Technician’s role is to help the team prepare the Robot so it can perform at its full potential during a Match. The Technician, except as described at the end of Section 6.6 Drive Team, is not an additional Coach, Driver, or Human Player.
Team members in open-access spectator seating areas are not considered to be in a restricted area and are not prevented from assisting or using signaling devices. See E102 for related details.
H108 *Be careful what you interact with. Team members are prohibited from the following actions with regards to interaction with Arena elements.
A. climbing on or inside,
B. hanging from,
C. deforming, and
D. damaging.
Violation: Verbal warning. If subsequent violations at any point during the event, YELLOW CARD.
H201 *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. This includes violations of the event rules found on the FIRST® Robotics Competition District & Regional Events page.
Please see Section 11.2.1 Yellow and Red Cards for additional detail.
Violation: The Head Referee may assign a yellow or a Red Card.
The intent of this rule is to provide the Head Referees the flexibility necessary to keep the event running smoothly, as well as keep the safety of all the participants as the highest priority. There are certain behaviors that automatically result in a yellow or Red Card because we believe this behavior puts our community at risk. Those behaviors include, but are not limited to the list below:
a. inappropriate behavior as outlined in the blue box of H101,
b. jumping over the guardrail,
c. behaviors listed in the blue box in H103,
d. Pinning in excess of 15 seconds,
e. climbing on the Hub, and
f. exploiting the 5-second scoring assessment period after a MATCH to avoid rule violations (e.g. triggering an over-extension that enables HANGAR points or using a ROBOT’S residual energy to impact an opponent ROBOT on their HANGAR).
The Head Referee may assign a yellow or Red Card for a single instance of a rule violation such as the examples given in items a-e above, or for multiple instances of any single rule violation. Teams should be aware that any rule in this manual could escalate to a yellow or Red Card. The Head Referee has final authority on all rules and violations at an event.
H202 *1 student, 1 Head Referee. A team may only send 1 student from its drive team to address the Head Referee.
Violation: The Head Referee will not address additional, non-compliant team members or peripheral conversations.
Please see Referee Interaction for more information about process and expectations.
H301 *Be prompt/safe when coming to and going from the Field. Drive teams may not cause significant or multiple delays during the event to the start of a Match, the Field reset after a Match, or continuation of Matches after a Timeout.
Violation: If prior to the Match, the offending drive team’s Robot will be Disabled. If after the Match, Yellow Card.
Drive teams are expected to stage their Robots for a Match, and remove it from the Field afterwards, safely and swiftly. Examples of violations include, but are not limited to:
a. late arrival to the Field (including across different Matches and after a Field or Alliance Timeout),
b. failing to exit the Field once a Match is ready to begin (indicated by the green LEDs having turned off),
c. installing Bumpers, charging pneumatic systems, or any other Robot maintenance once on the Field,
d. time-consuming use of alignment devices that are external to the Robot (e.g. a drive team could bring and use a measuring tape, as long as there is no delay to the Match by doing so), and
e. failing to remove Operator Consoles from the Driver Stations in a timely manner.
At the conclusion of a Timeout, Robots are expected to be staged on the Field prior to the timer displaying 0 and ready for the Match to start.
There are no rules that prohibit use of hand tools (including battery operated tools) while setting up and/or removing Robots from the Field provided they do not cause significant delay or cause safety concerns.
H302 *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. during Timeouts, after Opening Ceremonies, before an immediate Match replay, etc.) and with the express permission from the FTA or a Referee.
Violation: Yellow Card
Teams are encouraged to consider this rule when developing their robots.
FMS will not enable Robots after the conclusion of the Match.
Tethering includes any wired or wireless connection used to electrically energize and/or control elements on the Robot. The safety of teams and volunteers in close proximity to Robots and Arena elements on the Field is of the utmost importance, therefore Robots or Robot Components may not be enabled in any way on the Field once the Match has concluded.
Robots need to be safely transported off the Field and back to the pits after the Match, and there may be bystanders, doorways, or height restrictions along the route.
H303 *You can’t bring/use anything you want. The only equipment that may be brought to the Arena and used by drive teams during a Match is listed below. Regardless of if equipment fits criteria below, it may not be employed in a way that breaks any other rules, introduces a safety hazard, blocks visibility for Field Staff or audience members, or jams or interferes with the remote sensing capabilities of another team or the Field.
A. the Operator Console,
B. non-powered signaling devices,
C. reasonable decorative items,
D. special clothing and/or equipment required due to a disability,
E. devices used solely for planning or tracking strategy,
F. devices used solely to record gameplay, and
G. non-powered Personal Protective Equipment (examples include, but aren’t limited to, gloves, eye protection, and hearing protection)
Items brought to the Arena under allowances B-G must meet all following conditions:
I. do not connect or attach to the Operator Console, Field, or Arena,
II. do not connect or attach to another Alliance member (other than items in category G),
III. do not communicate with anything or anyone outside of the Arena,
IV. do not communicate with the Technician,
V. do not include any form of enabled wireless electronic communication, and
VI. do not in any way affect the outcome of a Match, other than by allowing the drive team to
a. plan or track strategy for the purposes of communication of that strategy to other Alliance members or
b. use items allowed per B to communicate with the Robot.
Violation: Match will not start until situation remedied. If discovered or used inappropriately during a Match, Yellow Card.
Examples of equipment that may be considered a safety hazard in the confined space of the Alliance Area include, but are not limited to, a step stool or a large signaling device.
Examples of remote sensing capabilities include, but are not limited to, vision systems, acoustic range finders, sonars, and infrared proximity sensors.
Use of imagery that, to a reasonably astute observer, mimics the Vision Targets employed on the Field is a violation of this rule.
Examples of wireless communication include, but are not limited to, radios, walkie-talkies, cell phones, Bluetooth communications, and Wi-Fi.
H304 *By invitation only. Only drive teams for the current Match are allowed in their respective Alliance Areas or Terminal Areas.
Violation: Match won’t start until the situation is corrected.
H305 *Show up to your Matches. Upon each team’s Robot passing initial, complete inspection, the team must send at least 1 member of its drive team to the Arena and participate in each of the team’s assigned Qualification and Playoff Matches.
Violation: Red Card.
Figure 8‑1 Match participation flowchart
The team should inform the lead team queuer if the team’s Robot is not able to participate.
H306 *Identify yourself. Drive teams must wear proper identification while in the Arena. Proper identification consists of:
A. all drive team members wearing their designated buttons above the waist in a clear visible location at all times while in the Arena
B. the Coach wearing the “Coach” button
C. the Drivers and Human Players each wearing a “drive team” button
D. the Technician wearing the “Technician” button
E. each Human Player in a Terminal Area wearing their Alliance color apron around their waist
Teams are invited to customize the aprons included in their Kickoff Kit, provided the pocket and bottom 2 in. aren’t modified. A team may borrow a Field apron if they don’t have theirs or a REFEREE determines the apron unfit for a Match.
F. during a Playoff Match, the Alliance Captain clearly displaying the designated Alliance Captain identifier (e.g. hat or armband)
Violation: Match won’t start until the situation is corrected. Those not displaying identification must leave the Arena.
H307 *Plug in to/be in your Driver Station. The Operator Console must be used in the Driver Station to which the team is assigned, as indicated on the team sign.
Violation: Match won’t start until the situation is corrected. If during a Match, Disabled.
An intent of this rule is to prevent unsafe situations where long tethers to Operator Console devices increase tripping hazards as the operator moves about the Alliance Area. In the interest of avoiding nuisance penalties associated with a DRIVE TEAM member stepping outside of a prescribed area, we prefer to offer a general guideline as to what it means to use the Operator Console in the Alliance Area. Provided the Drive Team member is within close proximity of their Driver Station, there will be no repercussions. However, a Drive Team member located more than approximately half a Driver Station width away from their own Driver Station while using their operator console is likely violating this rule.
H308 *Don’t bang on the glass. Team members may never strike or hit the Driver Station plastic windows.
Violation: Verbal warning. If subsequent violations in more than 1 Match, Yellow Card.
H309 Know your Robot setup. When placed on the Field for a Match, each Robot must be:
A. in compliance with all Robot rules, i.e. has passed inspection (for exceptions regarding Practice Matches, see Section 10 Inspection & Eligibility Rules),
B. the only team-provided item left on the Field by the drive team,
C. confined to its Starting Configuration (reference R102 and R104),
D. positioned such that it is fully contained in 1 of the Alliance’s 2 Tarmacs, and
E. fully and solely supporting not more than 1 Cargo (as described in Section 6.1 Setup).
Violation: If fix is a quick remedy, the Match won’t start until all requirements are met. If it is not a quick remedy, the offending Robot will be Disabled and, at the discretion of the Head Referee, must be re-inspected.
If a Robot is Bypassed prior to the start of the Match, the drive team may not remove the Robot from the Field without permission from the Head Referee or the FTA.
H310 Know your drive team positions. Prior to the start of the Match, drive team members must be positioned as follows:
A. Drivers: inside their Alliance Area and behind the Starting Line,
B. Coaches: inside their Alliance Area and behind the Starting Line, and
C. Human Players:
a. 1 Human Player per Alliance deployed to each Terminal Area, and the HUMAN PLAYER in the TERMINAL AREA furthest from their ALLIANCE AREA behind the TERMINAL STARTING LINE,
b. any remaining Human Players: inside their Alliance Area and behind the Starting Line, and
D. Technicians: in the event-designated area near the Field.
Violation: Match won’t start until the situation is corrected.
H311 Leave the Cargo alone. Prior to the start of the Match, Human Players may not remove the Cargo from the Terminal.
Violation: Match won’t start until the situation is corrected.
H312 No Cargo shots after the MATCH. After the end of the Match (i.e. when the timer displays 0 seconds following teleop) and for the following 10 seconds, drive teams may not enter Cargo into the FIELD.
Violation: Foul and any CARGO scored as a result of a violation of this rule is negated.
H401 *Behind the lines. During Auto, drive team members staged behind a starting line or terminal starting line may not contact anything in front of those lines, unless for personal or equipment safety or granted permission by a Head Referee or FTA.
Violation: Foul per item contacted.
Pointing, gesturing, or otherwise extending across the Starting Line such that contact is not made with carpet or other Arena elements is not a violation of this rule.
An example of an exception for equipment safety is if an Operator Console starts to fall from, or has already fallen off of, the Driver Station shelf. In that circumstance, drive team members may step forward to catch it or pick it up off the ground and return it to the shelf.
H402 *Disconnect or set down controllers. Prior to the start of the Match, any control devices worn or held by Human Players and/or Drivers must be disconnected from the Operator Console.
Violation: Match won’t start until the situation is corrected.
For the purposes of FIRST Robotics Competition, any device connected to the Operator Console is considered a control device because Referees are not expected to differentiate between devices that can or cannot control the Robot.
H403 *Let the Robot do its thing. During Auto, drive teams may not directly or indirectly interact with Robots or Operator Consoles unless for personal safety, Operator Console safety, or pressing an E-Stop. A human player feeding cargo to their robot is an exception to this rule.
Violation: Foul and Yellow Card
H404 Auto Cargo delivery. During Auto, Cargo may only be introduced to the Field by a Human Player in a terminal area.
Violation: Foul per Cargo.
H501 *Coaches and other teams: hands off the controls. A Robot shall be operated only by the Drivers and/or Human Players of that team.
Violation: Disabled.
Exceptions may be made before a Match for major conflicts, e.g. religious holidays, major testing, transportations issues, etc.
H502 No wandering. Drivers, Coaches, and Human Players may not contact anything outside the area in which they started the Match (i.e. the Alliance Area or the Terminal Area). Technicians may not contact anything outside their designated area. Exceptions are granted in cases concerning safety and for actions that are inadvertent, Momentary, and inconsequential.
Violation: Foul.
H503 *Coaches, Cargo is off limits. Coaches may not touch Cargo, unless for safety purposes.
Violation: Foul per Cargo.
H504 Teleop Cargo delivery. During TELEOP, Cargo may only be introduced to the Field
A. by a Human Player and
B. through the Guard.
Violation: Foul per Cargo.
H505 Opponent Cargo is off limits. During a Match, Human Players may not contact opponent Cargo. Inconsequential and Momentary contact, and/or contact that, as perceived by a REFEREE, is intended to be helpful, are exceptions to this rule.
Violation: Foul per Cargo.
Inconsequential touching, such as shifting an opponent Cargo out of the way within the Terminal to retrieve your own, is not a violation of this rule.
H506 Only feed your ALLIANCE Robots. Human Players may not deliver their Cargo to opponent Robots.
Violation: Foul per Cargo.
H507 Drive Teams, watch your reach. Drive Team members may not reach beyond the PuRPle Plane.
9 ROBOT Construction Rules
The rules listed below explicitly address legal parts and materials and how those parts and materials may be used on a RAPID REACT 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 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.
Example 1: A team orders 2 Robot grippers from RoboHands Corp. and receives both items. They put 1 in their storeroom and plan to use it later. Into the other, they drill “lightening holes” to reduce weight. The first gripper is still classified as a COTS item, but the second gripper is now a Fabricated Item, as it has been modified.
Example 2: A team obtains openly available blueprints of a drive module commonly available from Wheels-R-Us Inc. and has local machine shop “We-Make-It, Inc.” manufacture a copy of the part for them. The produced part is not a COTS item, because it is not commonly carried as part of the standard stock of We-Make-It, Inc.
Example 3: A team obtains openly available design drawings from a professional publication during the pre-season and uses them to fabricate a gearbox for their Robot during the build period following Kickoff. The design drawings are considered a COTS item and may be used as “raw material” to fabricate the gearbox. The finished gearbox itself would be a Fabricated Item, and not a COTS item.
Example 4: A COTS part that has non-functional label markings added would still be considered a COTS part, but a COTS part that has device-specific mounting holes added is a Fabricated Item.
Example 5: A team has a COTS single-board processor version 1.0, which can no longer be purchased. Only the COTS single-board processor version 2.0 may be purchased. If the COTS single-board processor version 1.0 is functionally equivalent to its original condition, it may be used.
Example 6: A team has a COTS gearbox which has been discontinued. If the COTS gearbox is functionally equivalent to its original condition, it 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. must be 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 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.
D. should maintain sufficient stock or production capability to fill teams’ orders within a reasonable period during the season (less than 1 week). This criterion may not apply to custom-built items from a source that is both a Vendor and a fabricator.
For example, a Vendor may sell flexible belting that the team wishes to procure to use as treads on their drive system. The Vendor cuts the belting to a custom length from standard shelf stock that is typically available, welds it into a loop to make a tread, and ships it to a team. The fabrication of the tread takes the Vendor 2 weeks. This would be considered a Fabricated Item, and the 2-week ship time is acceptable. Alternately, the team may decide to fabricate the treads themselves. To satisfy this criterion, the Vendor would just have to ship a length of belting from shelf stock (i.e. a COTS item) to the team within 5 business days and leave the welding of the cuts to the team.
E. 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.
The intent of this definition it to be as inclusive as possible to permit access to all legitimate sources, while preventing ad hoc organizations from providing special-purpose products to a limited subset of teams in an attempt to circumvent the cost accounting rules.
FIRST desires to permit teams to have the broadest choice of legitimate sources possible, and to obtain COTS items from the sources that provide them with the best prices and level of service available. Teams also need to protect against long delays in availability of parts that will impact their ability to complete their Robot. The build season is brief, so the Vendor must be able to get their product, particularly FIRST unique items, to a team in a timely manner.
Ideally, chosen Vendors should have national distributors (e.g. Home Depot, Lowes, MSC, McMaster-Carr, etc.). Remember, FIRST Robotics Competition events are not always near home – when parts fail, local access to replacement materials is often critical.
Note that it is possible for an item (typically raw materials) to be neither COTS nor a Fabricated Item. For example, a 20 ft. (~610 cm) length of aluminum which has been cut into 5 ft. (~152 cm) pieces by the team for storage or transport is neither COTS (it’s not in the state received from the Vendor), nor a Fabricated Item (the cuts were not made to advance the part towards its final form on the Robot).
Teams may be asked to provide documentation proving legality of non-RAPID REACT 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.
R101 *Frame Perimeter must be fixed. The Robot (excluding Bumpers) must have a Frame 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 ¼ in. (~6 mm) such as bolt heads, fastener ends, weld beads, and rivets are not considered part of the Frame Perimeter.
To determine the Frame Perimeter, wrap a piece of string around the Robot (excluding Bumpers) at the Bumper Zone described in R402 and pull it taut. The string outlines the Frame Perimeter.
Example: A Robot’s chassis is shaped like the letter ‘V’, with a large gap between chassis elements on the front of the Robot. When wrapping a taut string around this chassis, the string extends across the gap and the resulting Frame Perimeter is a triangle with 3 sides.
Figure 9‑1 FRAME PERIMETER example
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 Frame Perimeter, with the exception of its Bumpers and minor protrusions such as bolt heads, fastener ends, rivets, cable ties, etc.
If a Robot is designed as intended and each side is pushed up against a vertical wall (in Starting Configuration and with Bumpers removed), only the Frame Perimeter (or minor protrusions) will be in contact with the wall.
The allowance for minor protrusions in this rule is intended to allow protrusions that are both minor in extension from the Frame Perimeter and cross-sectional area.
If a Robot uses interchangeable Mechanisms per I103, Teams should be prepared to show compliance with this rule and R105 in all configurations.
R103 *Robot weight limit. The Robot weight must not exceed 125 lbs. (~56 kg). 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 no more than 12 in. (~30 cm) of cable per leg, 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 Frame Perimeter greater than 120 in. (~304 cm) and may not be more than 4 ft. 4 in. (~132 cm) tall.
Be sure to consider the size of the Robot on its cart to make sure it will fit through doors. Also consider the size of the Robot to ensure that it will fit into a shipping crate, vehicle, etc.
Note that rules contained in Section 9.4 Bumper Rules may impose additional restrictions on Robot design.
R105 Robot extension limit. Robots may not extend more than 16 in. (~40 cm) beyond their Frame Perimeter.
Figure 9‑2 Frame Perimeter extension
Teams should expect to have to demonstrate a Robot’s ability to constrain itself per above during inspection. Constraints may be implemented with either hardware or software.
See Section 7 Game Rules: Robots for height and extension restrictions for various areas of the Field.
R201 *No digging into carpet. Traction devices must not have surface features that could damage the Arena (e.g. metal, sandpaper, hard plastic 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 sharp edges. Protrusions from the Robot and exposed surfaces on the Robot shall not pose hazards to the Arena elements (including CARGO) 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.
Examples of items that will violate this rule include (but are not limited to):
a. shields, curtains, or any other devices or materials designed or used to obstruct or limit the vision of any DRIVE TEAM members and/or interfere with their ability to safely control their Robot,
b. speakers, sirens, air horns, or other audio devices that generate sound at a level sufficient to be a distraction ,
c. any devices or decorations specifically intended to jam or interfere with the remote sensing capabilities of another Robot, including vision systems, acoustic range finders, sonars, infrared proximity detectors, etc. (e.g. including imagery on your Robot that, to a reasonably astute observer, mimics the retro-reflective features of vision targets described in Vision Targets),
d. exposed lasers other than Class I,
e. flammable gasses,
f. any device intended to produce flames or pyrotechnics,
g. hydraulic fluids or hydraulic items,
h. switches or contacts containing liquid mercury,
i. circuitry used to create voltages in excess of 24 Volts,
j. any ballast not secured sufficiently, including loose ballast e.g. sand, ball bearings, etc., such that it may become loose during a Match,
k. exposed, untreated hazardous materials (e.g. lead weights) used on the Robot. These materials may be permitted if painted, encapsulated, or otherwise sealed to prevent contact. These materials may not be machined in any way at an event.
l. tire sealant, and
m. high intensity light sources used on the Robot (e.g. super bright LED sources marketed as ‘military grade’ or ‘self-defense’) may only be illuminated for a brief time while targeting and may need to be shrouded to prevent any exposure to participants. Complaints about the use of such light sources will be followed by re-inspection and possible disablement of the device.
R204 *Cargo stays with the Field. Robots must allow removal of Cargo from the Robot and the Robot from Field elements while Disabled and powered off.
Robots will not be re-enabled after the Match, so teams must be sure that Cargo and Robots can be quickly, simply, and safely removed.
Teams are encouraged to consider H301 when developing their ROBOTS.
R205 *Don’t contaminate the Field. Lubricants may be used only to reduce friction within the Robot. Lubricants must not contaminate the Field or other Robots.
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.
Teams should be ready to show inspectors documentation of FMV for any Components that appear to be in the range of the $600 USD limit.
The Analog Devices IMU MXP Breakout Board, P/N ADIS16448, does not have a published FMV. This device is considered to comply with this rule regardless of its true FMV.
The FMV of a COTS item is its price defined by a Vendor for the part or an identical functional replacement. This price must be generally available to all FIRST Robotics Competition teams throughout the build and competition season (i.e. short-term sale prices or coupons do not reflect FMV), however teams are only expected to make a good faith effort at determining the item price and are not expected to monitor prices of Robot items throughout the season. The FMV is the cost of the item itself and does not include any duties, taxes, tariffs, shipping, or other costs that may vary by locality.
The FMV of COTS software is the price, set by the Vendor, to license the software (or piece of the software) that runs on the Robot for the period from Kickoff to the end of the FIRST Championship. The FMV of software licensed free-of-cost, including through the Virtual KOP, for use on the Robot is $0.
The FMV of FABRICATED parts is the value of the material and/or labor, except for labor provided by team members (including sponsor employees who are members of the team), members of other teams, and/or event provided machine shops. Material costs are accounted for as the cost of any purchasable quantity that can be used to make the individual part (i.e. the purchasable raw material is larger than the FABRICATED part).
Example 1: A team orders a custom bracket made by a company to the team's specification. The company’s material cost and normally charged labor rate apply.
Example 2: A team receives a donated sensor. The company would normally sell this item for $450 USD, which is therefore its FMV.
Example 3: A team purchases titanium tube stock for $400 USD and has it machined by a local machine shop. The machine shop is not considered a team sponsor but donates 2 hours of expended labor anyway. The team must include the estimated normal cost of the labor as if it were paid to the machine shop and add it to the $400 USD.
Example 4: A team purchases titanium tube stock for $400 USD and has it machined by a local machine shop that is a recognized sponsor of the team. If the machinists are considered members of the team, their labor costs do not apply. The total applicable cost for the part would be $400 USD.
It is in the best interests of the teams and FIRST to form relationships with as many organizations as possible. Recognizing supporting companies as sponsors of, and members in, the team is encouraged, even if the involvement of the sponsor is solely through the donation of fabrication labor.
Example 5: A team purchases titanium tube stock for $400 USD and has it machined by another team. The total applicable cost for the part would be $400 USD.
Example 6: A team purchases a widget at a garage sale or online auction for $300, but it’s available for sale from a Vendor for $700. The FMV is $700.
If a COTS item is part of a modular system that can be assembled in several possible configurations, then each individual module must fit within the price constraints defined in this rule.
If the modules are designed to assemble into a single configuration, and the assembly is functional in only that configuration, then the total cost of the complete assembly including all modules must fit within the price constraints defined in this rule.
In summary, if a Vendor sells a system or a kit, a team must use the entire system/kit FMV and not the value of its Component pieces.
Example 7: Vendor A sells a gearbox that can be used with a number of different gear sets, and can mate with 2 different motors they sell. A team purchases the gearbox, a gear set, and a motor, then assembles them together. Each part is treated separately for the purpose of determining FMV since the purchased pieces can each be used in various configurations.
Example 8: Vendor B sells a robotic arm assembly that a team wants to use. However, it costs $630 USD, so they cannot use it. The Vendor sells the “hand”, “wrist”, and “arm” as separate assemblies, for $210 USD each. A team wishes to purchase the 3 items separately, then reassemble them. This would not be legal, as they are really buying and using the entire assembly, which has a Fair Market Value of $630 USD.
Example 9: Vendor C sells a set of wheels or wheel modules that are often used in groups of 4. The wheels or modules can be used in other quantities or configurations. A team purchases 4 and uses them in the most common configuration. Each part is treated separately for the purpose of determining FMV, since the purchased pieces can be used in various configurations.
R302 *Custom parts, generally from this year only. Fabricated Items created before Kickoff are not permitted. Exceptions are:
A. Operator Console,
B. Bumpers,
C. battery assemblies as described in R103-B,
D. Fabricated Items consisting of 1 COTS electrical device (e.g. a motor or motor controller) and attached Components associated with any of the following modifications:
a. wires modified to facilitate connection to a Robot (including removal of existing connectors),
b. connectors and any materials to secure and insulate those connectors added (note: passive PCBs such as those used to adapt motor terminals to connectors are considered connectors),
c. motor shafts modified and/or gears, pulleys, or sprockets added, and
d. motors modified with a filtering capacitor as described in the blue box below R625.
E. COTS items with any of the following modifications:
a. non-functional decoration or labeling,
b. assembly of COTS items per manufacturer specs, unless the result constitutes a Major Mechanism as defined in I101, and
c. work that could be reasonably accomplished in fewer than 30 minutes with the use of handheld tools (e.g. drilling a small number of holes in a COTS part).
Please note that this means Fabricated Items from Robots entered in previous FIRST competitions may not be used on Robots in the RAPID REACT FIRST Robotics Competition (other than those allowed per R302-B through -E. Before the formal start of the build season, teams are encouraged to think as much as they please about their Robots. They may develop prototypes, create proof-of-concept models, and conduct design exercises. Teams may gather all the raw stock materials and COTS Components they want.
Parts with precision machined (mill, CNC, etc.) features may still meet part E.c of this rule if functionally equivalent features could reasonably be made within the restrictions specified.
Example 1: A team designs and builds a 2-speed shifting transmission during the fall as a training exercise. After Kickoff, they utilize all the design principles they learned in the fall to design their Robot. To optimize the transmission design for their Robot, they change the transmission gear ratios and reduce the size, and build 2 new transmissions, and place them on the Robot. All parts of this process are permitted activities.
Example 2: A team re-uses a RAPID REACT-legal motor from a previous Robot which has had connectors added to the wires. This is permitted, per exception D, because the motor is a COTS electrical Component.
Example 3: A team re-uses a piece of aluminum tubing from a previous Robot which has a precision machined bearing hole in it. On the current Robot, the bearing hole is not used. As the only function of the hole on the current Robot is material removal, which does not require precise tolerancing, a functionally equivalent hole could be made with a hand drill in under 30 minutes and the part is permitted per part E.c.
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.
Example 1: A team realizes that the transmission designed and built in the fall perfectly fits their need for a transmission to drive the Robot arm. They build an exact copy of the transmission from the original design plans, and bolt it to the Robot. This would be prohibited, as the transmission – although made during the competition season – was built from detailed designs developed prior to Kickoff.
Example 2: A team developed an omni-directional drive system for the 2019 competition. In July 2019 they refined and improved the control software, written in C++, to add more precision and capabilities. They decided to use a similar system for the RAPID REACT competition. They copied large sections of unmodified code over into the control software of the new Robot, also written in C++. This would be a violation of the schedule constraint and is not allowed.
Example 3: The same team decides to use LabVIEW as their software environment for RAPID REACT. Following Kickoff, they use the previously developed C++ code as a reference for the algorithms and calculations required to implement their omni-directional control solution. Because they developed new LabVIEW code as they ported over their algorithms, this is permitted.
Example 4: A different team develops a similar solution during the fall and plans to use the developed software on their competition Robot. After completing the software, they post it in a generally accessible public forum and make the code available to all teams. Because they have made their software publicly available before Kickoff, they can use it on their Robot.
Example 5: A team develops a transmission prior to Kickoff. After completing the project, they publish the CAD files on a generally accessible public forum and make them available to all teams. Because they have made the design publicly available before Kickoff, they can use the design to create an identical transmission, fabricated after Kickoff, for use on their RAPID REACT Robot.
R304 *During an event, only work during pit hours. During an event a team is attending (regardless of whether the team is physically at the event location), the team may neither work on nor practice with their Robot or Robot elements outside of the hours that pits are open, with the following exceptions:
A. exceptions listed in R302, other than R302-E-c and
B. software development.
For the purposes of this rule, official events begin as follows:
· Regionals, District Championships, and FIRST Championship: at the start of the first designated load-in period, according to the Public Schedule. If the Public Schedule is not available or there is no designated load-in period, the events begin at 4pm on the day prior to pits opening.
· District Events: when pits open
Examples of activity prohibited by this rule include:
a. working on the Robot at the team’s shop after load-in for the event has begun and
b. working on Robot parts at night at the team’s hotel.
Note that E108 and E401 impose additional restrictions on work done on the Robot or Robot materials while attending an event.
This rule is intended to increase equity between teams with significant travel to an event and those nearby (close teams would otherwise have an advantage by being able to work on their Robot, in their shop, until it’s time to go to the event).
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. Criteria used in writing these rules include the following:
• minimize variety of Bumpers so teams can expect consistency,
• minimize the amount of design challenge in creating Bumpers,
• minimize cost of Bumper materials, and
• maximize use of relatively ubiquitous materials.
R401 *Bumpers should protect all corners. Robots are required to use Bumpers to protect all outside corners of the Frame Perimeter. For adequate protection, at least 6 in. (~16 cm) of Bumper must be placed on each side of each outside corner (see Figure 9‑3) and must extend to within ¼ in. (~6 mm) of the Frame Perimeter corner. If a Frame Perimeter side is shorter than 12 in. (~31 cm), that entire FRAME PERIMETER side must be protected by a Bumper (see Figure 9‑4). A round or circular Frame Perimeter, or segment of the Frame Perimeter, is considered to have an infinite number of corners, therefore the entire frame or frame segment must be completely protected by Bumpers.
The dimension defined in this rule is measured along the Frame Perimeter. The portion of the Bumper that extends beyond the corner of the Frame Perimeter is not included in the 6 in. (~16 cm) requirement. See Figure 9‑3.
Figure 9‑3 Bumper corner examples
Figure 9‑4 Bumper around full side/corner
R402 *Bumpers must stay low. Bumpers must be located entirely within the Bumper Zone, which is the volume contained between the floor and a virtual horizontal plane 7½ in. (~19 cm) above the floor in reference to the Robot standing normally on a flat floor. Bumpers do not have to be parallel to the floor.
This measurement is intended to be made as if the Robot is resting on a flat floor (without changing the Robot configuration), not relative to the height of the Robot from the Field carpet. Examples include:
Example 1: A Robot that is at an angle while navigating the Field has its Bumpers outside the Bumper Zone. If this Robot were virtually transposed onto a flat floor, and its Bumpers are in the Bumper Zone, it meets the requirements of this rule.
Example 2: A Robot deploys a Mechanism which lifts the Bumpers outside the Bumper Zone (when virtually transposed onto a flat floor). This violates this rule.
R403 *Bumpers shouldn’t move. Bumpers must not be articulated, relative to the Frame Perimeter.
R404 *Bumpers must come off. Bumpers must be designed for quick and easy installation and removal to facilitate inspection and weighing.
As a guideline, Bumpers should be able to be installed or removed by 2 people in fewer than 5 minutes.
R405 *Bumpers indicate your alliance. Each Robot must be able to display red or blue Bumpers to reflect their Alliance color, as assigned in the Match schedule distributed at the event (as described in Section 11.1 Match Schedules). Bumper markings visible when installed on the Robot, other than the following, are prohibited:
A. those required per R406,
B. hook-and-loop tape or snap fasteners backed by the hard parts of the Bumper,
C. solid white FIRST logos between 4¾ in. (~12 cm) and 5¼ in. wide (~13 cm) (i.e. comparable to those available in the RAPID REACT Virtual Kit), and
D. narrow areas of underlying fabric exposed at seams, corners, or folds.
The Frame Perimeter facing surfaces of Bumpers are not “displayed” and thus R405 does not apply.
R406 *Team number on bumpers. Team numbers must be displayed and positioned on the Bumpers such that an observer walking around the perimeter of the Robot can unambiguously tell the team’s number from any point of view and meet the following additional criteria:
A. consist of only Arabic numerals at least 4 in. (~11 cm) high, at least ½ in. (~13 mm) in stroke width, and be either white in color or outlined in white with a minimum 1/16 in. (~2 mm) outline,
The ½ in. (~13 mm) stroke width requirement applies to the majority of the stroke. Font elements less than ½ in. (~13 mm) such as serifs, rounded edges, small hairlines or gaps, etc. are permitted as long as the majority of the stroke meets the sizing requirement and the numbers are unambiguous.
B. must not wrap around sharp corners (less than 160°) of the Frame Perimeter, and
C. may not substitute logos or icons for numerals.
There is no prohibition against splitting team numbers onto different sections of Bumper. The intent is that the team’s number is clearly visible and unambiguous so that Judges, Referees, Announcers, and other teams can easily identify competing Robots.
This marking is intended to display the team number only, not to intentionally change the surface characteristics of the Bumper. Excessive material usage as part of any team number marking will invite close scrutiny.
R407 *Bumper weight limit. Each set of Bumpers (including any fasteners and/or structures that attach them to the Robot) must weigh no more than 15 lbs. (~6 kg).
If a multi-part attachment system is utilized (e.g. interlocking brackets on the Robot and the Bumper), then the elements permanently attached to the Robot will be considered part of the Robot, and the elements attached to the Bumpers will be considered part of the Bumper. Each element must satisfy all applicable rules for the relevant system.
R408 *Bumper construction. Bumpers must be constructed as follows (see Figure 9‑7):
A. be backed by ¾ in. thick (nominal, ~19mm) by 5 in. ± ½ in. (~127 mm ± 12.7 mm) tall plywood, Oriented Strand Board (OSB) or solid wood (with the exception of balsa). Small clearance pockets and/or access holes in the wood backing are permitted, as long as they do not significantly affect the structural integrity of the Bumper.
¾ in. plywood and OSB refer to items sold by Vendors as that material and thickness, teams may not fabricate their own plywood or OSB. Other engineered woods such as Fiberboard or Particle Board are not likely to survive the rigors of FIRST Robotics Competition gameplay and thus not permitted per A.
Note: ¾ in. plywood is often marked according to the actual dimension (²³⁄₃₂”) not the nominal size. Plywood sold as ²³⁄₃₂” meets the requirements of A.
B. hard Bumper parts allowed per A, E, F, and G must not extend more than 1 in. (~25 mm) beyond the Frame Perimeter (measured as shown in Figure 9‑5).
Figure 9‑5 Hard parts of Bumper corners
C. use a stacked pair of approximately 2½ in. (nominal, ~63mm) round, petal, or hex “pool noodles” (solid or hollow) as the Bumper cushion material (see Figure 9‑7). All pool noodles used in a Bumper set (e.g. red set of Bumpers) may not be modified (with the exception of cutting to length or cutting to facilitate mating pool noodles at the corners as required by R409) or deformed and must be the same diameter, cross section, and density (e.g. all round hollow or all hex solid). Cushion material may extend up to 2½ in. (~63 mm) beyond the end of the plywood (see Figure 9‑8). To assist in applying the fabric covering, soft fasteners may be used to attach the pool noodles to the wood backing, so long as the cross section in Figure 9‑7 is not significantly altered (e.g. tape compressing the pool noodles).
All pool noodles used on a Robot must be the same in order to maintain the desired interaction between Robots in the cases of Bumper-to-Bumper contact. Bumpers containing pool noodles of vastly different construction may cause a “ramp” effect when interacting with other Bumpers.
Minor noodle compression as a result of smoothing Bumper fabric or rounding a Frame Perimeter corner is not considered deformed. Any compression beyond that, e.g. for the purposes of flattening the pool noodle, is deformation and a violation of C.
D. be covered with a rugged, smooth cloth. (multiple layers of cloth and seams are permitted if needed to accommodate R405 and/or R406, provided the cross section in Figure 9‑7 is not significantly altered).
Silk and bedding are not considered rugged cloths, however 1000D Cordura is. Tape (e.g. gaffer’s tape) matching the Bumper color is allowed to patch small holes on a temporary basis.
It is expected that there may be multiple layers of cloth as fabric is folded to accommodate the corners and seams of Bumpers.
The cloth must completely enclose all exterior surfaces of the wood and pool noodle material when the Bumper is installed on the Robot. The fabric covering the Bumpers must be solid in color.
E. optionally use metal angle, as shown in Figure 9‑7 or other fasteners (e.g. staples, screws, adhesives, etc.) to clamp cloth.
F. optionally use metal brackets (i.e. angle or sheet metal) or other fasteners (e.g. staples, screws, adhesives, etc.) to attach Bumper segments to each other (see Figure 9‑6).
Figure 9‑6 Example uses of brackets in Bumper corners
G. must attach to the Frame Perimeter of the Robot 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 attachment system must be designed to withstand vigorous game play. All removable fasteners (e.g. bolts, locking pins, pip-pins, etc.) will be considered part of the Bumpers.
Figure 9‑7 Bumper vertical cross section
R409 *Fill Bumper corners. Corner joints between Bumpers must be filled with pool noodle material. Examples of implementation are shown in Figure 9‑8.
Figure 9‑8 Soft parts of Bumper corners
R410 *Bumpers must be supported. Bumpers must be supported by the structure/frame of the Robot (see Figure 9‑9). To be considered supported, a minimum of ½ in. (~13 mm) at each end of each Bumper wood segment must be backed by the Frame Perimeter (≤¼ in. gap, ~6mm). “Ends” exclude hard Bumper parts which extend past the Frame Perimeter permitted by R408-B. Additionally, any gap between the backing material and the frame:
A. must not be greater than ¼ in. (~6 mm) deep or
B. not more than 8 in. (~20 cm) wide
Figure 9‑9 Bumper support examples
The intent of this rule is to make sure the Bumper wood is properly supported to minimize the likelihood of breakage on impact. Flexible Robot elements, such as thin plastic, do not accomplish this intent and are not considered “structure/frame” of the Robot.
R501 *Allowable motors. The only motors and actuators permitted include the following (in any quantity):
Table 9‑1 Motor allowances
|
Motor Name |
Part Numbers Available |
|
|
AndyMark 9015 |
am-0912 |
AndyMark 9015 |
|
AndyMark NeveRest |
am-3104 |
|
|
AndyMark PG |
am-2161 (alt. PN am-2765) |
am-2194 (alt. PN am-2766) |
|
AndyMark RedLine Motor |
am-3775 |
am-3775a |
|
AndyMark Snow Blower Motor |
am-2235 |
am-2235a |
|
Banebots |
am-3830 M7-RS775-18 RS775WC-8514 |
M5 – RS550-12 RS550VC-7527 RS550 |
|
CIM |
FR801-001 M4-R0062-12 AM802-001A 217-2000 PM25R-44F-1005 |
PM25R-45F-1004 PM25R-45F-1003 PMR25R-45F-1003 PMR25R-44F-1005 am-0255 |
|
CTR Electronics/VEX Robotics Falcon 500 |
217-6515 am-6515 |
19-708850 am-6515_Short |
|
Current/former KOP automotive motors |
Denso AE235100-0160 Denso 5-163800-RC1 Denso 262100-3030 |
Denso 262100-3040 Bosch 6 004 RA3 194-06 Johnson Electric JE-PLG-149 Johnson Electric JE-PLG-410 |
|
Nidec Dynamo BLDC Motor |
am-3740 |
DM3012-1063 |
|
Playing with Fusion Venom |
BDC-10001 |
|
|
REV Robotics HD Hex |
REV-41-1291 |
|
|
REV Robotics NEO Brushless |
REV-21-1650 |
|
|
REV Robotics NEO 550 |
REV-21-1651 |
|
|
VEX BAG |
217-3351 |
|
|
VEX Mini-CIM |
217-3371 |
|
|
West Coast Products RS775 Pro |
217-4347 |
|
|
Electrical solenoid actuators, no greater than 1 in. (nominal) stroke and rated electrical input power no greater than 10 watts (W) continuous duty at 12 volts (VDC) |
||
|
Fans, no greater than 120mm (nominal) size and rated electrical input power no greater than 10 watts (W) continuous duty at 12 volts (VDC) (if qualifying actuator is then used at 24V, it must be approved by the manufacturer for use at 24V) |
||
|
Hard drive motors part of a legal COTS computing device |
||
|
Factory installed vibration and autofocus motors resident in COTS computing devices (e.g. rumble motor in a smartphone). |
||
|
PWM COTS servos with a retail cost < $75. |
||
|
Motors integral to a COTS sensor (e.g. LIDAR, scanning sonar, etc.), provided the device is not modified except to facilitate mounting |
||
|
1 compressor compliant with R806 and used to compress air for the Robot’s pneumatic system |
||
For servos, note that the roboRIO is limited to a max current output of 2.2A on the 6V rail (12.4W of electrical input power). Teams should make sure that their total servo power usage remains below this limit at all times.
Given the extensive amount of motors allowed on the Robot, teams are encouraged to consider the total power available from the Robot battery during the design and build of the Robot. Drawing large amounts of current from many motors at the same time could lead to drops in Robot battery voltage that may result in tripping the main breaker or trigger the brownout protection of the roboRIO. For more information about the roboRIO brownout protection and measuring current draw using the PDP/PDH, see roboRIO Brownout and Understanding Current Draw.
AndyMark PG Gearmotors are sold with labeling based on the entire assembly. Assemblies labeled am-3651 through am-3656 contain legal motors specified in the table above. These motors may be used with or without the provided gearbox.
R502 *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 9‑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. The wiring harness of the Nidec Dynamo BLDC Motor may be modified as documented by FIRST in Nidec Dynamo BLDC Motor with Controller.
G. Minimal labeling may be applied to indicate device purpose, connectivity, functional performance, etc.
H. Any number of #10-32 plug screws may be removed from the Falcon 500.
I. Insulation may be applied to electrical terminals.
J. Repairs, provided the performance and specifications are unchanged.
K. Maintenance recommended by the manufacturer.
The intent of this rule is to allow teams to modify mounting tabs and the like, not to gain a weight reduction by potentially compromising the structural integrity of any motor.
R503 *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. DMC 60/DMC 60c Motor Controller (P/N 410-334-1, 410-334-2),
b. Jaguar Motor Controller (P/N MDL-BDC, MDL-BDC24, and 217-3367) connected to PWM only,
c. Nidec Dynamo, BLDC Motor with Controller to control integral actuator only (P/N 840205-000, am-3740)
d. SD540 Motor Controller (P/N SD540x1, SD540x2, SD540x4, SD540Bx1, SD540Bx2, SD540Bx4, SD540C),
e. Spark Motor Controller (P/N REV-11-1200),
f. Spark MAX Motor Controller (P/N REV-11-2158),
g. Talon FX Motor Controller (P/N 217-6515, 19-708850, am-6515, am-6515_Short) for controlling integral Falcon 500 only,
h. Talon Motor Controller (P/N CTRE_Talon, CTRE_Talon_SR, and am-2195),
i. Talon SRX Motor Controller (P/N 217-8080, am-2854, 14-838288),
j. Venom Motor with Controller (P/N BDC-10001) for controlling integral motor only,
k. Victor 884 Motor Controller (P/N VICTOR-884-12/12),
l. Victor 888 Motor Controller (P/N 217-2769),
m. Victor SP Motor Controller (P/N 217-9090, am-2855, 14-868380), and
n. 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).
Note: The Automation Direct Relays are single directional. Per R504 they may not be wired together in an attempt to provide bi-directional control.
R504 *Don’t overload controllers. Each power regulating device may control electrical loads per Table 9‑2. Unless otherwise noted, each power regulating device shall control 1 and only 1 electrical load.
Table 9‑2 Power regulating device allotments
|
Electrical Load |
Motor Controller |
Relay Module |
Pneumatics Controller |
|
AndyMark RedLine Motor Banebots CIM REV Robotics NEO Brushless REV Robotics NEO 550 VEX Mini-CIM WCP RS775 Pro |
Yes |
No |
No |
|
AndyMark 9015 VEXpro BAG |
Yes |
No |
No |
|
AndyMark PG KOP Automotive Motors NeveRest Snow Blower Motor REV Robotics HD Hex |
Yes |
Yes |
No |
|
CTR Electronics/VEX Falcon 500 Nidec Dynamo BLDC Motor w/ Controller Playing With Fusion Venom |
Yes |
No |
No |
|
Compressor |
No |
Yes |
Yes |
|
Pneumatic Solenoid Valves |
No |
Yes |
Yes |
|
Electric Solenoids |
Yes |
Yes |
Yes |
|
Custom Circuits |
Yes |
Yes |
Yes |
R505 *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), or
C. REV Robotics Servo Power Module (P/N REV-11-1144).
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.1 in. x 3 in. x 6.6 in., +/- .1 in. for each dimension (~ 180 mm x 76mm x 168 mm, +/- 2.5 mm for each dimension)
E. Nominal weight: 11lbs. to 14.5 lbs. (~5 kg. to 6.5 kg.)
F. Terminals: Nut and bolt style
Examples of batteries which meet these criteria include:
a. Enersys (P/N NP18-12, NP18-12B, NP18-12BFR),
b. MK Battery (P/N ES17-12),
c. Battery Mart (P/N SLA-12V18),
d. Sigma (P/N SP12-18),
e. Universal Battery (P/N UB12180),
f. Power Patrol (P/N SLA1116),
g. Werker Battery (P/N WKA12-18NB),
h. Power Sonic (P/N PS-12180NB),
i. Yuasa (P/N NP18-12B),
j. Panasonic (P/N LC-RD-1217),
k. Interstate Batteries (P/N BSL1116), and
l. Duracell Ultra Battery (P/N DURA12-18NB).
Teams should be aware that they may be asked to provide documentation of the specifications of any battery not listed above.
Batteries should be charged in accordance with manufacturer’s specification. (Please see the FIRST Safety Manual for additional information.)
R602 *Other batteries for cameras or computers only. COTS USB battery packs with a capacity of 100Wh or less (20000mAh at 5V) and 5V, 2.5 Amp max output per port, or batteries integral to and part of a COTS computing device or self-contained camera (e.g. laptop batteries, GoPro style camera, etc.) 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 peak 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.
For example, teams may not use additional batteries as extra weight on their Robots.
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 1 Robot battery, a single pair of Anderson Power Products (or APP) 2-pole SB type connectors, the 1 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), and the 1 power distribution device (CTR Electronics Power Distribution Panel, PDP, P/N am-2856, 217-4244, 14-806880 or REV Robotics Power Distribution Hub, PDH, P/N REV-11-1850) shall be connected with 6 AWG (7 SWG or 16 mm2) copper wire or larger, with no additional devices or modifications (with the exception of monitoring circuitry permitted by R625), as shown in Figure 9‑10.
Figure 9‑10 Electrical connection diagram
“SB type” refers to SB type only (e.g. SB-50, SB-120, etc.), not SBS or any other part type beginning with SB. All batteries supplied by FIRST (such as Spare Parts and international batteries) will have a red or pink SB50 connector installed which may not be removed.
The pink connectors included in the RAPID REACT KOP mate with the red SB50 connector.
R610 *1 breaker 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 12VDC WAGO connector pair (i.e. the load terminals, as shown in Figure 9‑10) of the PDP/PDH, not the M6 cap screws.
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.
Compliance with this rule is checked by observing a >3kΩ resistance between either the (+) or (-) post within the APP connector that is attached to the PDP/PDH and any point on the Robot.
All legal motor controllers with metal cases are electrically isolated. They may be mounted directly to Robot frame Components.
Note that some cameras, decorative lights, and sensors (e.g. some encoders, some IR sensors, etc.) have grounded enclosures or are manufactured with conductive plastics. These devices must be electrically isolated from the Robot frame to ensure compliance with this rule.
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.
Examples considered not “quickly and safely accessible” include breakers covered by an access panel or door, or mounted on, underneath or immediately adjacent to moving Components.
It is strongly recommended that the 120A circuit breaker location be clearly and obviously labeled so it can be easily found by Field Staff during a Match.
R613 *Electrical system must be inspectable. The PDP/PDH, 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 voltages exceeding 24V.
R615 *Power roboRIO as specified. The roboRIO power input must be connected to either:
A. the dedicated supply terminals on the PDP shown in Figure 9‑11 or
Figure 9‑11 roboRIO power source on a PDP
B. the terminals of 1 of the non-switchable fused channels on the PDH (20,21,22) with a 10A fuse installed in the associated fuse holder.
No other electrical load shall be connected to that channel.
Figure 9‑12 roboRIO power source on a PDH
R616 *Power radio as specified – Part 1. The wireless bridge (radio) power must be supplied by either:
A. the 12V 2A output of a CTR Electronics Voltage Regulator Module (VRM) (P/N am-2857, 217-4245), as shown in Figure 9‑13, and must be the only load connected to those terminals or
Figure 9‑13 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” Ethernet port on the wireless bridge.
Note that this prohibits using any other active POE injector device to power the radio but does not prohibit using any Passive Conductors to inject the VRM power into an Ethernet cable plugged into the radio port labeled “18-24v POE.”
R617 *Power radio as specified – Part 2. The device supplying power to the wireless bridge per R616 must be connected to either:
A. the designated supply terminals at the end of the PDP, as shown in Figure 9‑14. With the exception of a single CTR Electronics Pneumatics Control Module (PCM, P/N am-2858) or REV Robotics Pneumatic Hub (PH, P/N REV-11-1852), no other electrical load shall be connected to these PDP terminals.
Figure 9‑14 VRM, PCM, and RPM power source on a PDP
B. the terminals of 1 of the non-switchable fused channels on the PDH (20,21,22) with a 10A fuse installed in the associated fuse holder. No other electrical load shall be connected to that channel.
Figure 9‑15 VRM and RPM power source on a PDH
Please reference How to Wire an FRC Robot for wireless bridge wiring information.
R618 *Use PDP/PDH terminals as designed. Only 1 wire shall be connected to each terminal on the PDP/PDH.
If multi-point distribution of circuit power is needed (e.g. to provide power to multiple PCMs and/or VRMs from 1 20A circuit), then all incoming wires may be appropriately spliced into the main lead (e.g. using an insulated terminal block, crimped splice or soldered wire splice), and the single main lead inserted into the terminal to power the circuit.
R619 *Only use specified circuit breakers in PDP/PDH. The only circuit breakers permitted for use in the PDP/PDH are:
A. Snap Action VB3-A Series, terminal style F57,
B. Snap Action MX5-A or MX5-L Series, 40A rating or lower, and
C. REV Robotics ATO auto-resetting breakers 40A rating or lower.
R620 *Only use specified fuses in PDP/PDH. The only fuses permitted for use in the PDP/PDH are mini automotive blade fuses (ATM style) with the following values:
A. for the PDP, values matching the value printed on the device’s corresponding fuse holder and
B. for the PDH, 15A or lower with the exception of a single 20A fuse for powering a PCM or PH.
Note that these fuses must be pressed very firmly to seat properly. Improper seating can cause a device to reboot upon impact.
R621 *Protect circuits with appropriate circuit breakers. Each branch circuit must be protected by 1 and only 1 circuit breaker or fuse on the PDP/PDH per Table 9‑3. No other electrical load can be connected to the breaker or fuse supplying this circuit.
Table 9‑3 Branch circuit protection requirements
|
Branch Circuit |
Circuit Breaker Value |
Quantity Allowed Per Breaker |
|
Motor Controller |
Up to 40A |
1 |
|
Custom Circuit |
Up to 40A |
No limit |
|
Automation Direct Relay 40A (*6M40*) |
Up to 40A |
1 |
|
Fans permitted per R501 and not already part of COTS computing devices |
Up to 20A |
No limit |
|
Spike Relay Module |
Up to 20A |
1 |
|
Automation Direct Relay 25A (*6M25*) |
Up to 20A |
1 |
|
PCM/PH – with compressor |
Up to 20A |
1 |
|
Additional VRM (non-radio)/Additional PCM/PH (non-compressor) |
Up to 20A |
3 total |
|
Automation Direct Relay 12A (*6M12*) |
Up to 10A |
1 |
This rule does not prohibit the use of smaller value breakers in the PDP/PDH or any fuses or breakers within Custom Circuits for additional protection.
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 9‑4 Breaker and wire sizing
|
Application |
Minimum Wire Size |
|
31 – 40A breaker protected circuit |
12 AWG (13 SWG or 4 mm2) |
|
21 – 30A breaker protected circuit |
14 AWG (16 SWG or 2.5 mm2) |
|
6 – 20A breaker protected circuit
|
18 AWG (19 SWG or 1 mm2) |
|
11-20A fuse protected circuit |
|
|
Between the PDP dedicated terminals and the VRM/RPM or PCM/PH |
|
|
Compressor outputs from the PCM/PH |
|
|
Between the PDP/PDH and the roboRIO |
22 AWG (22 SWG or 0.5 mm2) |
|
Between the PDH and VRM/RPM |
|
|
≤5A breaker protected circuit |
|
|
≤10A fuse protected circuit |
|
|
VRM 2A circuits |
24 AWG (24 SWG or .25 mm2) |
|
roboRIO PWM port outputs |
26 AWG (27 SWG or 0.14 mm2) |
|
Signal Level circuits (i.e. circuits which draw ≤1A continuous and have a source incapable of delivering >1A, including but not limited to roboRIO non-PWM outputs, CAN signals, PCM/PH Solenoid outputs, VRM 500mA outputs, RPM outputs, and Arduino outputs) |
28 AWG (29 SWG or .08 mm2) |
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.
In order to show compliance with these rules, teams should use wire with clearly labeled sizes if possible. If unlabeled wiring is used, teams should be prepared to demonstrate that the wire used meets the requirements of this rule (e.g. wire samples and evidence that they are the required size).
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.
Slip rings containing mercury are prohibited per R203.
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, PDP/PDH, motor controllers, relays (per R503-B), motors and actuators (per R501), pneumatic solenoid valves, or other elements of the Robot control system (items explicitly mentioned in R701). 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.
A noise filter may be wired across motor leads or PWM leads. Such filters will not be considered Custom Circuits and violate neither this rule nor R717.
Acceptable signal filters must be fully insulated and must be 1 of the following:
· a 1 microfarad (1 µF) or less, non-polarized, capacitor may be applied across the power leads of any motor on your Robot (as close to the actual motor leads as reasonably possible) or
· a resistor may be used as a shunt load for the PWM control signal feeding a servo.
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 2022_v4.0 or later.
There are no rules that prohibit co-processors, provided commands originate from the roboRIO to enable and disable all power regulating devices. This includes motor controllers legally wired to the CAN bus.
R702 *Communicate with the Robot with the specified radio. 1 OpenMesh wireless bridge (P/N: OM5P-AN or OM5P-AC), 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.
R703 *Use specific Ethernet port for roboRIO. The roboRIO Ethernet port must be connected to the wireless bridge port labeled “18-24 vPOE” (either directly, via a network switch, via an RPM, or via a CAT5 Ethernet pigtail).
Note: Placing a switch between the roboRIO and radio may impede the ability for Field Staff to troubleshoot roboRIO connection issues on the Field. Teams may be asked to connect directly between the radio and the roboRIO as part of troubleshooting efforts.
R704 *Only use allowed ports and bandwidth to communicate with the robot. Communication between the Robot and the Operator Console may not exceed 4 Mbits/second and is restricted to network ports listed in Table 9‑5.
Table 9‑5 Open FMS ports
|
Port |
Designation |
Bi-directional? |
|
UDP/TCP 1180-1190 |
Camera data from the roboRIO to dashboard software when the camera is connected the roboRIO via USB |
Yes |
|
TCP 1735 |
SmartDashboard |
Yes |
|
UDP 1130 |
Dashboard-to-Robot control data |
Yes |
|
UDP 1140 |
Robot-to-Dashboard status data |
Yes |
|
HTTP 80 |
Camera connected via switch on the Robot |
Yes |
|
HTTP 443 |
Camera connected via switch on the Robot |
Yes |
|
UDP/TCP 554 |
Real-Time Streaming Protocol for h.264 camera streaming |
Yes |
|
UDP/TCP 1250 |
CTRE Diagnostics Server |
Yes |
|
UDP/TCP 5800-5810 |
Team use |
Yes |
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).
Note that the 4 Mbit limit will be strictly enforced by the wireless bridge.
The FMS Whitepaper has more details on how to check and optimize bandwidth usage.
While FIRST makes every effort to provide a wireless environment that allows teams access to a full 4 Mbits/second data rate (with about 100 Kbit used for Robot control and status), at some events wireless conditions may not accommodate this.
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 *No other wireless allowed. No form of wireless communication shall be used to communicate to, from, or within the Robot, except those required per R702, R706, and tags used for location detection systems if provided by the event.
Devices that employ signals in the visual spectrum (e.g. cameras) and non-RF sensors that don’t receive human-originated commands (e.g. “beam break” sensors or IR sensors on the Robot used to detect Field elements) are not wireless communication devices and thus this rule doesn’t apply.
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.
Teams are encouraged to mount the wireless bridge away from noise generating devices such as motors, PCM(s)/PH(s), and VRM(s)/RPM(s).
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).
Any RSL must be:
A. mounted on the Robot such that it is easily visible while standing 3 ft. (~ 100 cm) in front of the Robot,
B. connected to the “RSL” supply terminals on the roboRIO, and
C. wired for solid light operation, by placing a jumper between the “La” and “Lb” terminals on the light per Figure 9‑16.
Please see How to Wire an FRC Robot for connection details.
Figure 9‑16 RSL jumper wiring
R710 *Only specified modifications to control system devices permitted. The Driver Station Software, roboRIO, PDP/PDH, 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 R503-B), wireless bridge, 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:
Please note that the Driver Station Software is a separate application from the Dashboard. The Driver Station Software may not be modified, while teams are expected to customize their Dashboard code.
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 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.
Please note that while repairs are permitted, the allowance is independent of any manufacturer’s warranty. Teams make repairs at their own risk and should assume that any warranty or return options are forfeited. Be aware that diagnosing and repairing Components such as these can be difficult.
For more information about modification O, please see this OM5P-AC Radio Modification article.
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 R503-B), servo controller, and PWM motor controller shall be connected to a corresponding port (relays to Relay ports, servo controllers 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, with the exception of the Nidec Dynamo motor controller which must also be connected to the roboRIO Digital I/O.
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
A Passive Conductor is any device or circuit whose capability is limited to the conduction and/or static regulation of the electrical energy applied to it (e.g. wire, splices, connectors, printed wiring board, etc.).
An Active Device is any device capable of dynamically controlling and/or converting a source of electrical energy by the application of external electrical stimulus.
The “network of Passive Conductors” only applies to the pins being used for PWM output to motors or servos. This means that connecting an Active Device, such as a sensor to 1 MXP pin does not prevent other MXP pins from being used in accordance with B.
R714 *Control CAN motor controllers from the roboRIO. Each CAN motor controller must be controlled with signal 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.
As long as the CAN bus is wired legally so that the heartbeat from the roboRIO is maintained, all closed loop control features of the CAN motor controller may be used. (That is, commands originating from the roboRIO to configure, enable, and specify an operating point for all CAN motor controller closed loop modes fit the intent of R701).
R715 *Control PCM/PH(S) and Servo Hubs from roboRIO. Each PCM/PH 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 *Connect the PDP/PDH to the roboRIO CAN bus. The PDP/PDH CAN interface must be connected to the built-in CAN bus on the roboRIO (either directly or daisy-chained via another CAN bus device).
For documentation on how to wire the CAN bus connections see How to Wire an FRC Robot.
R717 *Don’t alter the CAN bus. No device that interferes with, alters, or blocks communications among the roboRIO and the PDP/PDH, PCMs/PHs, and/or CAN motor controllers on the bus will be permitted.
Only 1 wire should be inserted into each Weidmuller CAN connector terminal. For documentation on how to wire the CAN bus connections see How to Wire an FRC Robot.
R718 *USB to CAN adapter permitted. Additional CAN bus connections may be added to the roboRIO using the CTR Electronics CANivoreTM P/N 21-678682 USB-to-CAN adapter.
Any additional CAN bus added in this manner satisfies the requirements of R714 (i.e. you may connect motor controllers to this additional bus).
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 125psi (~862 kPa) or
B. installed downstream of the primary relieving regulator (see R809), and rated for pressure of at least 70psi (~483 kPa)
Any pressure specification such as “working,” “operating,” “maximum,” etc. may be used to satisfy the requirements of this rule.
It is recommended that all pneumatic items be rated by their manufacturers for a working pressure of at least 60 psi (~414 kPa).
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.
Do not, for example, paint, file, machine, or abrasively remove any part of a pneumatic Component – this would cause the part to become a prohibited item. Consider pneumatic Components sacred.
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,
Examples of acceptable valves include Parker PV609-2 or MV709-2.
B. pressure relief valves functionally equivalent to those provided in the KOP,
Examples of acceptable valves include Norgren 16-004-011, 16-004-003 or McMaster-Carr 48435K714.
To be considered functionally equivalent the valve must be preset or adjustable to 125 psi (~862 kPA) and capable of relieving at least 1 scfm (~472 cm3/s).
C. solenoid valves with a maximum ⅛ in. (nominal, ~3 mm) NPT, BSPP, or BSPT port diameter or integrated quick connect ¼ in. (nominal, ~6mm) outside diameter tubing connection,
D. additional pneumatic tubing, with a maximum ¼ in. (nominal, ~6 mm) 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 psi (~413 kPa),
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).
The following devices are not considered pneumatic devices and are not subject to pneumatic rules (though they must satisfy all other rules):
a. a device that creates a vacuum,
b. closed-loop COTS pneumatic (gas) shocks,
c. air-filled (pneumatic) wheels, and
d. pneumatic devices not used as part of a pneumatic system (i.e. used in a way that does not allow them to contain pressurized air)
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 9‑17.
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) 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 9‑17 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.1 cfm (~519 cm3/s) flow rate @ 12VDC at any pressure.
A Robot’s compressor may be substituted by another compressor, but a Robot may only have 1 designated compressor at a time, and all compressed air on the Robot must be sourced from a single compressor.
Note: Viair C-series compressors, which have a max working pressure of 120 PSI, are rated for intermittent pressures greater than 125 PSI and therefore meet the requirements of this rule.
R807 *Air storage pressure limit. Stored air pressure on the Robot must be no greater than 120 psi (~827 kPa). 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 psi (~413 kPa) and must be provided through a single primary adjustable, relieving, pressure regulator.
Examples of acceptable valves include Norgren regulator P/N R07-100-RNEA and Monnier P/N 101-3002-1.
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.
It is recommended that all Components in the high-pressure pneumatic circuit upstream from the regulator be rated for at least 115 psi (~793 kPa) working pressure.
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 or kPa.
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 psi (~861 kPa). The valve may or may not have been calibrated prior to being supplied to teams.
Instructions for adjusting the pressure relief valve can be found in the Pneumatics Manual.
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 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
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.
The REV Robotics Analog Pressure Sensor may only be used with PH compressor control and may not be used with roboRIO or PCM compressor control.
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 outputs from multiple solenoid valves must not be plumbed together.
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 22.0 or newer.
Teams are permitted to use a portable computing device of their choice (laptop computer, tablet, etc.) to host the Driver Station Software while participating in Matches.
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.
Teams are strongly encouraged to use pigtails on the Ethernet port used to connect to the FMS. Such pigtails will reduce wear and tear on the device’s port and, with proper strain relief employed, will protect the port from accidental damage.
R904 *Operator console physical requirements. The Operator Console must not
A. be longer than 5 ft. (~152 cm),
B. be deeper than 1 ft. 2 in. (~35 cm) (excluding any items that are held or worn by the Drivers during the Match),
C. extend more than 6 ft. 6 in. (~198 cm) above the floor, or
D. attach to the Field (except as permitted by G301).
There is a 4 ft. 6 in. (~137 cm) long by 2 in. (nominal) wide strip of hook-and-loop tape (“loop” side) along the center of the Driver Station support shelf that should be used to secure the Operator Console to the shelf, per G301. See Driver Station for details.
Please note that while there is no hard weight limit, Operator Consoles that weigh more than 30 lbs. (~13 kg.) will invite extra scrutiny as they are likely to present unsafe circumstances.
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.
Examples of prohibited wireless systems include, but are not limited to, active wireless network cards and Bluetooth devices. For the case of the FIRST Robotics Competition, a motion sensing input device (e.g. Microsoft Kinect) is not considered wireless communication and is allowed.
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.
10 Inspection & Eligibility Rules
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. 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, slot on the practice field, 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.
While there is no specific defined procedure in place for teams to be re-inspected prior to Playoff Matches, it is typical for INSPECTORS to use the re-inspection discretion described above to do a limited re-inspection on all Robots near the end of QUALIFICATIONS or beginning of Playoff Matches 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.
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.
An Inspection Checklist is available to help teams self-inspect their robot before their event. Teams are strongly encouraged to self-inspect prior to their event.
Teams attending Single-Day Events are strongly encouraged to use the Inspection Checklist before their event. They are required to self-inspect using the Inspection Checklist before an Inspector will do their official inspection using the Abbreviated Inspection Checklist.
I101 *It’s your team’s Robot. The Robot and its Major Mechanisms must be built by the FIRST Robotics Competition team.
This rule requires that the Robot and its Major Mechanisms were built by its team, but isn’t intended to prohibit or discourage assistance from other teams (e.g. fabricating elements, supporting construction, writing software, developing game strategy, contributing Components and/or Mechanisms, etc.)
Examples of Major Mechanisms include, but are not limited to, assemblies used to:
a. manipulate Cargo,
b. position a Robot to engage with the Hangar,
c. manipulate a Field element, and
d. move the Robot around the Field.
Examples that would generally not be considered Major Mechanisms, and thus probably aren’t subject to this rule include, but are not limited to, the following:
a. a gearbox assembly,
b. a Component or Mechanism that’s part of a Major Mechanism, and
c. COTS items.
Neither this rule nor the language in this blue box define specific thresholds for how much of a Major Mechanism must be the result of the team’s effort. This rule expects and requires the team’s honest assessment of whether they built the Major Mechanisms of their Robot.
Attempts to exploit loopholes in the definition of Major Mechanism in order to bypass this requirement are in the spirit of neither this rule nor the FIRST Robotics Competition. Examples of exploitation include:
a. assembling pieces of a Major Mechanism provided by another team, except COTS kits and
b. receiving a mostly complete Major Mechanism from another team and providing a small piece.
I102 *Get inspected before playing a Qualification/Playoff 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 start of the Match, the entire Alliance receives a Red Card for that Match.
Please take note of this rule. It is important that FIRST Robotics Competition teams ensure their Alliance partners have passed inspection. Allowing a partner that has not passed inspection to play puts the Alliance at risk of Red Cards. Teams should check with their Alliance partners early and help them pass inspection before competing.
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 lbs. (~68 kg) (note that while up to 150 lbs. (~68 kg) 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. A Robot that plays in a Match with an un-inspected modification may be retro-actively disqualified at the discretion of the LRI and Head Referee.
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.
This restriction is not intended to prevent a team from returning to a previous configuration (e.g. due to an unsuccessful upgrade or failure of a new Component). If a team is believed to be violating this rule, the LRI will discuss the situation with the team to understand the changes and, if appropriate, the LRI in conjunction with the team will select a single configuration with which the team will compete for the duration of the event.
Example 1: A Robot passes initial inspection (which includes Mechanism A). Its team then decides they want to use Mechanism B, which was not inspected. The weight of the Robot, A, and B is less than the weight limit in I103, but more than that in R103. I104 requires the Robot be re-inspected, and this rule allows the Robot, A, and B to be inspected collectively. If passed, the Robot may then compete in subsequent matches with A or B.
Example 2: A Robot passes initial inspection (which includes Mechanism A). Its team then decides they want to use Mechanism B, which was not inspected. The weight of the Robot, A, and B is greater than the weight limit in I103. This requires re-inspection per I104 and A is excluded to satisfy I103. B breaks, and the team decides to switch back to A. The Robot must be re-inspected per I104, and the team is not violating this rule.
Example 3: A team arrives at an event with a Robot, Mechanism A, and Mechanism B, which collectively weigh 175 lbs. The Robot passes initial inspection with A and plays a Match. The team switches to B, gets re-inspected, and plays again. The team switches back to A, gets re-inspected, and plays again. The team switches back to B and asks to be re-inspected. At this point, the LRI suspects the team may be violating this rule and has a discussion with the team to understand the changes being made. The team reveals that this rule has been violated, and the LRI works with them to select A or B for use for the remainder of the event.
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.
The team may be asked to demonstrate these interlocks during the inspection process.
I107 *No student, no inspection. At least 1 student team member must accompany the Robot for any inspection efforts.
Exceptions may be made for major conflicts, e.g. religious holidays, major testing, transportation issues, etc.
11 Tournaments
Each 2022 FIRST® Robotics Competition event is played in a tournament format. Each tournament consists of 3 sets of Matches called Practice Matches (not played at Single-Day Events and 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.
A Match schedule is used to coordinate Matches at an Event. Figure 11‑1 details information shown on each schedule.
Figure 11‑1 Sample Match schedule
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 technical staff. The Head Referee rulings are final. No event personnel, including the Head Referee, will review video, photos, artistic renderings, etc. of any Match, from any source, under any circumstances.
If a drive team needs clarification on a ruling or score, per H202, 1 student from that drive team should address the Head Referee after the Arena Reset Signal (e.g. Field lights turn green). A drive team member signals their desire to speak with the Head Referee by standing in the corresponding red or blue Question Box, which are located on the floor near each end of the scoring table. Depending on timing, the Head Referee may postpone any requested discussion until the end of the subsequent Match as necessary.
While FMS tracks quantities of Fouls, FIRST instructs Referees to not self-track details about Fouls and Tech Fouls; as a result, we don’t expect Referees to recall details about what Fouls and Tech Fouls were made, when they occurred, and against whom.
Any reasonable question is fair game in the Question Box, and Head Referees will make good faith efforts to provide helpful feedback (e.g. how/why certain Fouls are being called, why a particular Robot may be susceptible to certain Fouls based on its design or game play, how specific rules are being called or interpreted), but please know that they will likely not be able to supply specific details.
In addition to rule violations explicitly listed throughout the 2022 Game Manual, 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.
As noted in Section 6.5 Rule Violations and H201, the Head Referee may assign a Yellow Card as a warning, or a Red Card for DISQUALIFICATION in Match for egregious behavior inappropriate at a FIRST Robotics Competition event.
A yellow or Red Card is indicated by the Head Referee standing in front of the team’s Driver Station and holding a yellow and/or Red Card in the air.
Per Section 6.5 Rule Violations, 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 standing in front of the team’s Driver Station and 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, its team number is presented with a yellow background on the audience screen at the beginning of all subsequent Matches, including any replays, as a reminder to the team, the Referees, and the audience that they carry a Yellow Card.
Figure 11‑2 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 are cleared after Practice MATCHES and persist from Qualification MATCHES through subsequent tournament phases. The Head Referee may opt to perpetuate a verbal warning or Yellow Card earned during Practice Matches through to Qualification Matches for particularly egregious behavior.
During the Playoff Matches, a team receives a yellow or Red Card for their entire Alliance. If 2 Yellow Cards are accrued by an Alliance, the entire Alliance is issued a Red Card. A Red Card results in DISQUALIFICATION and the Alliance loses the Match. If both Alliances receive Red Cards, the Alliance which committed the action earning the Red Card first chronologically is Disqualified and loses the Match.
yellow and Red Cards are applied based on the following:
Table 11‑1 yellow and Red Card application
|
Time YELLOW or RED CARDS earned: |
MATCH to which CARD is applied: |
|
prior to the start of Qualification Matches |
Team’s first Qualification Match |
|
during the Qualification Matches |
Team’s current (or just-completed) Match. In the case where the team participated as a Surrogate in the current (or just completed) Match, the card is applied to the team’s previous Match (i.e. the team’s second Qualification Match) |
|
between the end of Qualification Matches and the start of Playoff Matches |
Alliance’s first Playoff Match |
|
during the Playoff Matches |
Alliance’s current (or just-completed) Match |
Please see examples of the application of yellow and Red Cards as shown in Section 6.5.1 Violation Details.
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, 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,
A broken Field element caused by Robot abuse that affects the outcome of the Match for their Alliance is not an Arena Fault.
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, and
D. errors by Field Staff (except those listed in Section 6.7 Other Logistics).
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.
The outcome of the Match is affected if an error occurs that, in the judgement of the Head Referee, changes which Alliance would have won the Match and/or the assignment of Ranking Points.
The outcome of an event is affected if an error occurs that, in the judgement of FIRST Headquarters, changes the assignment of Ranking Points or has a dramatic effect on points used for ranking criteria.
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.
Note that an Arena Fault that does not affect Match outcome, in the judgement of the Head Referee, does not lead to a Match replay. Examples include, but are not limited to:
a. a piece of Field plastic falls into the Field, far away from any human or Robot activity, and in such a way that it does not affect Match outcome,
b. delay in the playing of an Arena sound,
c. mismatch between the timer on the audience screen and the Arena timer, and
d. any adjustment or delay in assignment of a penalty (including those made after the Match).
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. The specific time that the Field is open will be communicated to teams at the event. Teams may bring specific questions or comments to the FTA.
T401 *Freeze, Robot. During the period when the Arena is open for measurement, Robots can be enabled, but may neither drive, extend outside their frame perimeter, nor interact with (e.g. score, push, pickup, etc.) Cargo, the Hub, the Hangar, or other Field elements.
Violation: Verbal warning. If subsequent violations at any point during the event or egregious Yellow Card.
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 at the FIRST Robotics Event Results site, 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 part of Single-Day Events and are not guaranteed at District Events due to event schedule constraints.
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.
The Qualification Match schedule is made available as soon as possible, but no later than 1 hour before Qualification MatchES are scheduled to begin (for Single-Day Events, the schedule is provided no later than 30 minutes before Qualification Matches are scheduled to begin). Teams receive 1 hard copy and it is also available at the FIRST Robotics Competition Event Results site, except during exceptional circumstances. Each Qualification schedule consists of a series of rounds in which each team plays 1 Match per round.
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. maximize time between each Match played for all teams
2. minimize the number of times a team plays opposite any team
3. minimize the number of times a team is allied with 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, however criterion 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.
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‑1.
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 in a Qualification Match or causes their Alliance to receive 0 Match points in a Playoff Match.
C. A “no-show” team is either Disqualified from or issued a Red Card for that Match (see H305). 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 truncated 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 11‑2.
Table 11‑2 Qualification Match ranking criteria
|
Order Sort |
Criteria |
|
1st |
Ranking Score |
|
2nd |
Average Alliance Match points, not including Fouls |
|
3rd |
Average Alliance Hangar points |
|
4th |
Average Alliance Taxi + Auto Cargo points |
|
5th |
Random sorting by the FMS |
In Playoff Matches, teams do not earn Ranking Points; they earn a Win, Loss or Tie. Within each series of the Playoff Match Bracket, the first Alliance to win 2 Matches advances.
In the case where the Quarterfinal or Semifinal Match scores for both Alliances are equal, the win is awarded to the Alliance per criteria listed in Table 11‑3. A Disqualified team, as determined by the Head Referee, causes their Alliance to receive 0 Match points in a Playoff Match.
In Finals Matches, the Champion Alliance is the first Alliance to win 2 Matches. 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 11‑3.
Table 11‑3 Playoff Match tiebreaker criteria
|
Order Sort |
Criteria |
|
1st |
Cumulative Foul and Tech Foul points due to opponent rule violations |
|
2nd |
Alliance Hangar points |
|
3rd |
Alliance Taxi + Auto Cargo points |
|
4th |
Match is replayed |
At the end of the Qualification Matches, the top 8 seeded teams become the Alliance Leads. The seeded 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.
If a team declines the Alliance Lead position or doesn’t send a student representative for Alliance selection, they are ineligible to participate in the Playoff Tournament. If the declining/absent team would have been an Alliance Lead, all lower ranked Alliance Leads are promoted 1 spot. The next highest-ranked team moves up to become the Alliance 8 Lead.
Each team chooses a student team representative who proceeds to the Arena at the designated time (typically before the lunch break on the final day of the event) to represent their team. The designated student representative from each Alliance in a Playoff Match is called the Alliance Captain.
The Alliance selection process consists of 2 rounds during which each Alliance Captain invites a team seeded below them in the standings to join their Alliance. The invited team must not already have declined an invitation.
Round 1: In descending order (Alliance 1 to Alliance 8), each Alliance Captain invites a single team. The invited team’s representative steps forward and either accepts or declines the invitation.
If the team accepts, it becomes a member of that Alliance. If an invitation from a top 8 Alliance to another Alliance Lead is accepted, all lower Alliance Leads are promoted 1 spot. The next highest-seeded, unselected team moves up to become the Alliance 8 Lead.
If the team declines, that team is not eligible to be picked again or to be a Backup Team (see Playoff Match Bracket), and the Alliance Captain extends another invitation to a different team. If an invitation from a top 8 Alliance to another Alliance Lead is declined, the declining team may still invite teams to join their Alliance; however, it cannot accept invitations from other Alliances.
The process continues until Alliance 8 makes a successful invitation.
Round 2: The same method is used for each Alliance Captain’s second choice except the selection order is reversed, with Alliance 8 picking first and Alliance 1 picking last. This process results in 8 Alliances of 3 teams each.
Of the remaining eligible teams, the highest seeded teams must either accept or decline to be included in a pool of available teams until there are up to 8 teams that accept to be added into the pool. Field Staff will coordinate the assembly of this BACKUP pool immediately after the top ranked Alliance has made their final pick. If a team is not available to accept inclusion in the BACKUP pool, it will be assumed they have declined the invitation.
The Playoff Matches take place following the completion of the Qualification Matches and the Alliance selection process. Playoff Matches are played in a bracket format as shown in Figure 11‑3.
Alliance Leads are assigned to Driver Station 2, the first picks are assigned to their left in Driver Station 1, and second picks are assigned to the Alliance Lead’s right in Driver Station 3. If a Backup Team is in play, they will be assigned to the Driver Station that was assigned to the drive team they’re replacing. Teams cannot change assignments.
For Quarterfinal Matches, the higher seeded Alliance is assigned to the red Alliance. Beyond the Quarterfinal Matches, the Alliance on the top of each Match in Figure 11‑3 is assigned to the red Alliance, regardless of whether they are the higher seeded Alliance in that particular Match.
Figure 11‑3 Playoff Match bracket
In order to allow time between Matches for all Alliances, the order of play is as follows:
|
Quarterfinal Round 1 |
Quarterfinal Round 2 |
Quarterfinal Round 3 |
Semifinals |
Finals |
|
Quarterfinal 1 (1 vs. 8) |
Quarterfinal 5 (1 vs. 8) |
Quarterfinal Tiebreaker 11 |
Semifinal 1 |
Final 1 |
|
Quarterfinal 2 (4 vs. 5) |
Quarterfinal 6 (4 vs. 5) |
Quarterfinal Tiebreaker 21 |
Semifinal 2 |
Field Timeout |
|
Quarterfinal 3 (2 vs. 7) |
Quarterfinal 7 (2 vs. 7) |
Quarterfinal Tiebreaker 31 |
Semifinal 3 |
Final 2 |
|
Quarterfinal 4 (3 vs. 6) |
Quarterfinal 8 (3 vs. 6) |
Quarterfinal Tiebreaker 41 |
Semifinal 4 |
Field Timeout |
|
|
Field Timeout1 |
Field Timeout1 |
Semifinal Tiebreaker 11 |
Final Tiebreakers
|
|
|
|
Any Replays due to ties1 |
Semifinal |
Any Replays due to ties1 |
|
|
|
|
Field Timeout1 |
|
|
|
|
|
Any Replays due to ties1 |
|
1 - if required
During the Playoff Matches, extra team members may be needed to maintain the Robot between Matches because of the distance between the Field and the pit area. Each team is permitted to have 3 additional pit crew members who can also help with needed Robot repairs/maintenance.
A Timeout is a period of up to 8 minutes between Matches which is used to pause Playoff Match progression.
During a Timeout, the Arena timer displays the time remaining in the Timeout. Both Alliances enjoy the complete 8-minute window. If an Alliance completes their repairs before the Arena timer expires, the Alliance Captain is encouraged to inform the Head Referee that they are ready to play. If both Alliances are ready to play before the Timeout expires, the next Match will start.
There are no Timeouts for Practice or Qualification Matches.
If circumstances require an Alliance to play in back-to-back Matches during the Playoff Matches, the Head Referee will issue a Field Timeout to allow teams to prepare for the next Match. Field Timeouts are the same time duration as Timeouts and begin once the HANGARS are clear of ROBOTS and the MATCH results have been posted.
Figure 11‑4 Timeout and BACKUP Coupon timeline if teams not in back-to back MATCHES
Figure 11‑5 TIMEOUT and BACKUP Coupon timeline if teams in back-to back MATCHES
Each Alliance in the Playoff tournament is issued 1 Timeout.
Teams are expected to have their Robots staged on the Field by the end of the Timeout. Teams that cause a delay to the start of a Match after a Timeout are at risk of being in violation of H301.
T701 *There’s a window for timeout coupons. If an Alliance wishes to use their Timeout, the Alliance Captain must submit their Timeout coupon to the Head Referee within 2 minutes of the Arena reset signal preceding their Match (if not a back-to-back MATCH) or when the HANGARS are clear and the MATCH results are posted (if a back-to-back MATCH). If there is no preceding Match, the Timeout coupon must be submitted no later than 2 minutes before the scheduled Match time. The Timeout begins at the end of the Team Timeout Coupon Window depicted in Figure 11‑4 and Figure 11‑5.
A request presented outside the defined parameters in this rule will be denied.
There are no cascading Timeouts. If an Alliance calls a Timeout during a Field Timeout, the Field Timeout will expire 2 minutes after the HANGARS are clear and MATCH results are posted, and the Alliance’s Timeout will begin.
If an Alliance wishes to call a Timeout during a Field Timeout, it must still do so within 2 minutes of the HANGARS being clear and the MATCH results being posted preceding their Match.
Timeouts are not transferrable between Alliances, meaning an Alliance cannot hand their designated Timeout coupon to another Alliance to use, however an Alliance may use their own coupon for any purpose they wish.
If a Playoff Match is replayed because of an Arena Fault which rendered a Robot inoperable, the Head Referee has the option of calling a Field Timeout.
In the Playoff Matches, it may be necessary for an Alliance to replace 1 of its members due to a faulty Robot. Examples of Robot faults include, but are not limited to, the following:
1. mechanical damage,
2. electrical issues, and
3. software problems.
In this situation, the Alliance Captain has the option to bring in only the highest seeded team from the pool of available teams to join its Alliance. 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.
The resulting Alliance is then composed of 4 teams. The replaced team remains a member of the Alliance for awards, but cannot return to play, even if their Robot is repaired.
Each Alliance is allotted 1 Backup Team coupon during the Playoff Matches. If a second Robot from the Alliance becomes inoperable, then the Alliance must play the following Matches with only 2 (or even 1) Robots.
Example: 3 teams, A, B and C, form an Alliance going into the Playoff Matches. The highest seeded team not on 1 of the 8 Alliances is Team D. During 1 of the Playoff Matches, Team C’s Robot suffers damage to its mechanical arm. The Alliance Captain decides to bring in Team D to replace Team C. Team C and their Robot are not eligible to play in any subsequent Playoff Matches. The new Alliance of Teams A, B, and D are successful in advancing to the Finals and win the event. Teams A, B, C, and D are all recognized as members of the Winning Alliance and receive awards.
In the case where a Backup Team is part of the Winning or Finalist Alliance, there will be a 4-team Winning or Finalist Alliance.
If during a Timeout an Alliance Captain determines that they need to call up a Backup Team, they must submit their Backup Team coupon to the Head Referee while there are still at least 2 minutes remaining on the Arena timer. After that point, they will not be allowed to utilize the Backup Team.
Alternatively, an Alliance Captain may choose to call up a Backup Team without using their Timeout by informing the Head Referee directly within 2 minutes of the Head Referee issuing the Arena reset signal preceding their Match. If there is no preceding Match, the Backup Team coupon must be submitted no later than 2 minutes before the scheduled Match time.
In the case where the Alliance Captain’s Robot is replaced by a Backup Team, the Alliance Captain is allowed as a sixteenth Alliance drive team member. This additional representative may only serve in an advisory role and is considered a Coach (e.g. can’t be a Human Player)
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.
T702 *No coupons if match stopped prematurely. An Alliance may not request a Timeout or a Backup Team after a Playoff Match is stopped by the Head Referee (e.g. due to an Arena Fault or a safety issue). The sole exception is if the replay is due to an Arena Fault that rendered a Robot inoperable.
Violation: A request presented outside parameters defined will be denied.
If a Playoff Match is replayed per this rule, the Head Referee has the option of calling a Field Timeout.
The scheduling algorithm described in Section 11.6.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. If any team is scheduled to play in back-to-back matches, the Head referee issues a field timeout unless a longer break is already scheduled to occur (e.g. lunch.) See Section 11.7.4 timeouts for details.
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 11‑3, 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) before Playoff MATCHES begin.
District points for Draft Order Acceptance (per Section 11.8.1.2 Alliance Selection Results) are awarded as if a full set of Alliances was selected (i.e. the second selection of the 3-seed Alliance still receive 3 points regardless of how many Alliances are formed). District points for Playoff performance consider an Alliance that has a bye to have achieved the typical 2 wins for advancing from that round (i.e. the Alliance members earn 10 district points).
Some events are restricted to hosting teams 1 day at a time and are called Single-Day Events. Single-Day Events have a minimum of 13 and a maximum of 24 teams.
District points are modified as described in Section 11.8.1 District Events.
Single-Day Events employ a 4-alliance Playoff bracket as shown in Figure 11‑6 (and if the event is a District, points are not awarded for advancement through the Quarterfinal round). These matches follow the same order as the Semifinal and Final rounds shown in Table 11‑4.
Figure 11‑6 Single-Day Event Playoff bracket
To create the 4 alliances, alliance selection proceeds in the same general fashion as described in Section 11.7.1, however with only 4 alliance Leads instead of 8.
While each day is independent of the other days with regards to the robot competition, judged awards span all days included in that event series (i.e. a team participating in the first day competes with teams participating in the second day for judged awards). All judging is conducted remotely, and full details are included in the 2022 Single-Day Event Plan.
Teams advance through the season depending on the events at which they compete: Regional or District. This section details how District teams advance from District qualifying events, to their District Championship.
District teams are ranked throughout the season based on the points they earn at their first 2 home District events they attend, as well as at their District Championship. Points are awarded to teams as follows:
Table 11‑5 District Point Assignment
|
Category |
Points |
|
Qualification Round Performance |
(For a typically sized District event, this will result in a minimum of 4 points being awarded for Qualification round performance. For events of all sizes, a maximum of 22 points will be awarded.) |
|
Alliance Captains |
Equal to 17 minus the Alliance Captain number (e.g. 14 points for Alliance #3 Captain) For Single-Day Events, Alliance Captains #1, 2, 3, and 4 receive 16, 14, 12, and 10 points respectively. |
|
Draft Order Acceptance |
Equal to 17 minus the Draft Order Acceptance Number (e.g. 12 points for the team that is fifth to accept an invitation) For Single-Day Events, first through eighth picks receive 16, 14, 12, 10, 8, 6, 4, and 2 points respectively. |
|
Playoff Advancement |
Points awarded based on team participation in individual playoff rounds, and whether or not the Alliance advances. See Section 11.8.1.3 for details. |
|
Judged Team Awards |
10 points for Chairman’s Award 8 points each for Engineering Inspiration and Rookie All Star Awards 5 points each for all other judged team awards |
|
Team Age |
10 points for 2021 and 2022 rookie teams 5 points for 2020 rookie teams |
|
Back-to-Back Play |
2 points for teams playing 2 Single-Day Events on 1 weekend, provided the 2 events are the team’s first 2 events |
Points earned at District Championships are multiplied by 3 and then added to points earned at District events, to determine the final season point total for the team.
If there is a tie in the season point total between teams, those items are broken using the following sorting criteria:
Table 11‑6 District team sort criteria
|
Order Sort |
Criteria |
|
1st |
Total Playoff Round Performance Points |
|
2nd |
Best Playoff Round Finish at a single event |
|
3rd |
Total Alliance Selection Results Points |
|
4th |
Highest Qualification Round Seed or Draft Order Acceptance (i.e. Highest Alliance Selection points at a single event) |
|
5th |
Total Qualification Round Performance Points |
|
6th |
Highest Individual Match Score, regardless of whether that score occurred in a Qualification or Playoff Match |
|
7th |
Second highest Individual Match Score, regardless of whether that score occurred in a Qualification or Playoff Match |
|
8th |
Third highest Individual Match Score, regardless of whether that score occurred in a Qualification or Playoff Match |
|
9th |
Random Selection |
11.8.1.1 Qualification Round
Performance
The calculation of Qualification performance points is done using the equation (an inverse error function) in Table 11‑5. The equation utilizes the following variables:
· R – the qualification rank of the team at the event at the conclusion of Qualification Matches (as reported by FMS)
· N – the number of FIRST Robotics Competition teams participating in the Qualification rounds at the event
· Alpha (α) – a static value (1.07) used to standardize the distribution of points at events
This formula generates an approximately normal distribution of Qualification Round Performance points at an event, based on rank, with most teams getting a moderate number of points, and fewer teams getting the highest or lowest numbers of points available.
Table 11‑7 displays sample Qualification Round Performance points for variously ranked teams at a 40-team event. The system will automatically generate the appropriate points for each team based on their rank and the number of teams at the event.
Table 11‑7 Sample Qualification Round point assignments
|
Rank |
1 |
2 |
3 |
4 |
… |
19 |
20 |
21 |
… |
37 |
38 |
39 |
40 |
|
Points |
22 |
21 |
20 |
19 |
… |
13 |
13 |
12 |
… |
6 |
6 |
5 |
4 |
11.8.1.2
Alliance Selection Results
This attribute measures both individual team qualification round seeding performance and recognition by peers.
Alliance Captains are recognized based on their qualification round seeding rank. This rank is a result of the rules of the game, which typically incorporate several team performance attributes, and are designed to eliminate ties in rank. Non-Alliance Captains are rewarded based on peer recognition. To be invited to join an Alliance, a team’s peers have decided that the team has attributes that are desirable. Giving points for Alliance selection also supports come-from-behind teams. A team taking several Matches to optimize their performance may be recognized as a late bloomer by a top seeded team, even if that performance isn’t reflected in the rankings because of poor performance in early Matches. These points also have the potential to recognize teams employing a minority strategy with their Robot. Teams with unique or divergent Robot capabilities that complement the strengths of other Alliance members may be selected to fill a strategic niche.
Note also that Alliance Captains are given the same number of points as the team drafted in the same sequence. For example, the third Alliance Captain gets the same number of points as the third draft. Numerical analysis supports the idea that Alliance Captains are about as strong in Robot performance as equivalently drafted teams. As an additional minor benefit, awarding the same points for Alliance Captains and equivalent drafts lubricates the acceptance of draft offers between Alliance Captains, which gives teams out of the top 8 (or 4, if a Single-Day Event) the chance to experience being Alliance Captains themselves.
11.8.1.3
Playoff Round
Performance
This attribute measures team performance as part of an Alliance.
All teams on the Alliance winning a particular playoff series, who participate in Matches with their Robots, receive 5 points per Match won. In most cases, teams receive 10 points at each of the Quarterfinal, Semifinal, and Final levels, unless a BACKUP Robot is called in to play. For Single-Day Events, there is no Quarterfinal level so teams can receive up to 20 points for winning at the Semifinal and Final levels.
11.8.1.4 Awards
This attribute measures team performance with respect to team awards judged at the event.
The points earned for team awards in this system are not intended to capture the full value of the award to the team winning the award, or to represent the full value of the award to FIRST. In many ways, the team’s experience in being selected for awards, especially the Chairman’s Award, the Engineering Inspiration Award, and the Rookie All Star Award (which is optional for District Championship events), is beyond measure, and could not be fully captured in its entirety by any points-based system. Points are being assigned to awards in this system only to help teams recognize that FIRST continues to be “More than RobotsSM,” with the emphasis on our cultural awards, and to assist in elevating award-winning teams above non-award-winning teams in the ranking system.
Teams only get points for team awards judged at the event. If an award is not judged (e.g. Rookie Highest Seed), is not for a team (e.g. the Dean’s List Award) or is not judged at the event (e.g. Safety Animation Award, sponsored by UL), no points are earned.
11.8.1.5
Team Age
This attribute recognizes the difficulty in being a rookie or relatively new team.
Points are awarded to 2020, 2021, and 2022 rookie teams in recognition of the unique challenges teams face in those early years, and to increase the chance that they will make it to the District Championship to compete with their Robots. Like our dedicated Rookie awards, these additional points are intended to recognize and motivate newer participants in FIRST Robotics Competition. These points are awarded once at the beginning of the season. Rookie year is calculated based on the year in which FIRST recognizes the team as a rookie.
The assignment of Team Age points is different in 2022 from previous seasons. Please see this blog post for additional information.
11.8.1.6 Regional Participation
District teams do not earn points for their actions at any Regionals they may attend, nor are eligible for FIRST Championship qualifying judged awards at those events. However, if a District team does earn a slot at the FIRST Championship while attending a Regional event, that slot does count as part of the total Championship allocation the District is receiving for the season.
A team competing in a District qualifies for their District Championship by meeting 1 of the following criteria:
A. District Chairman’s Award Winner,
B. District Ranking (based on total points earned at their first 2 home District events as detailed in District Events),
Teams do not earn points at third or subsequent District events, nor at any inter-district or Regional events at which they compete during the season.
If a team declines an invitation to the District Championship, the next highest uninvited team on the list is invited, and so on, until the event capacity is filled.
C. District Engineering Inspiration winner (qualifies to compete for the award only), and
D. District Rookie All Star winner (qualifies to compete for the award only).
The capacity of each District Championship is shown in Table 11‑8. Each District determines the number of teams that qualify for their District Championship. These limits are based on factors including but not limited to the total number of teams in the District, available venue capacity, etc.
Table 11‑8 2022 District Championship Capacities
|
District Championship |
Capacity |
|
FIRST Chesapeake District Championship |
60 |
|
FIRST Israel District Championship |
40 |
|
FIRST Mid-Atlantic District Championship |
60 |
|
FIRST North Carolina State Championship |
32 |
|
FIRST Ontario Provincial Championship |
80 |
|
FIRST in Texas District Championship |
80 |
|
Indiana State Championship |
32 |
|
Michigan State Championship |
160 |
|
New England District Championship |
80 |
|
Pacific Northwest District Championship |
50 |
|
Peachtree District State Championship |
32 |
Some District Championships have a sufficient number of teams to justify using more than 1 division. Teams are assigned divisions by FIRST using a process developed by FIRST in Michigan.
The process employs a “brute force iterative randomizer” and is executed as follows:
1. The district team list is sorted in order of cumulative district points earned as described in District Events.
2. The list is divided into quartiles based on rank (e.g. the first quartile has the top 25% ranked teams).
3. Division assignments are randomly generated using equal contribution from each quartile.
4. 3 criteria are calculated for each division:
a. average strength: the arithmetic mean of the district point values of teams in a division
b. distribution of strength: the Signal to Noise Ratio (SNR) of the district point values of teams in a division. SNR is calculated as follows:
=
arithmetic mean of the district points in a division
σ = standard deviation of the district points in a division
c. distribution of strength for “top” teams: The SNR of the district point values of teams in the first quartile of a division
5. The 3 criteria for each division are compared to the other division(s). If the difference between the division’s value and any other division’s value exceeds the limits in Table 11‑9, the criteria is not met.
Table 11‑9 District Championship division Evaluation Limits
|
|
2 divisions |
4 divisions |
|
Average strength |
1 |
2 |
|
Distribution of strength |
1 |
2.5 |
|
Distribution of strength for “top” teams |
1.5 |
2 |
6. If all 3 criteria met, event organizers publish the assignments. If any of the 3 criteria are not met, assignments are rejected, and the process returns to Step 3.
In these cases:
• Division winning Alliances play each other in District Championship Playoffs, employing the bracket below that corresponds to their District, until a winning Alliance for the event is determined.
Figure 11‑7 4 division District Championship Playoff Bracket
Figure 11‑8 2 division District Championship Playoff Bracket
• Teams participating in District Championship Playoffs earn Playoff round performance District points as described in Playoff Round Performance.
• If an Alliance in a District Championship Playoff has not yet adopted a BACKUP Robot per Backup Teams, the Alliance Captain may bring in only the highest seeded team from their division’s pool of available teams to join its Alliance.
At the 2022 FIRST Championship, teams are split into 6 divisions. The process used to assign teams to their division is as follows:
1. Rookies are assigned randomly, team by team, sequentially to divisions (i.e. a team in Division 1, a team in Division 2, a team in Division 3, a team in Division 4, a team in Division 5, a team in Division 6, then back to Division 1 again, until Rookies are all assigned to a division).
2. Step 1 is repeated with veteran teams.
Each division plays a standard tournament as described in Qualification Matches and Playoff Matches to produce the division Champions. Those 6 division Champions proceed to the Championship Playoffs, on the Einstein Fields, to determine the 2022 FIRST Robotics Competition Championship Winners, per FIRST Championship Playoffs.
Details on how teams earn eligibility to attend the FIRST Championship are posted on the FIRST Championship eligibility webpage.
There is no provision for Backup Teams at the FIRST Championship.
Instead, before each division Playoff Tournament, Alliances are selected per the process as described in Section 11.7.1 Alliance Selection Process, however the process continues with a third round of selection as follows.
Round 3: The same method is used for each Alliance Captain’s third choice except the selection order is reversed again, with Alliance 1 picking first and Alliance 8 picking last. This process results in 8 Alliances of 4 teams each.
Alliances may start with any 3 of the 4 Robots on their Alliance during division Playoff Matches and during the Championship Playoffs. The list of 3 teams participating in the Match and their selected Driver Stations is called the Lineup. A single representative from the team not on the Lineup is allowed as a sixteenth Alliance member. This additional representative may only serve in an advisory role and will be considered a Coach (e.g. can’t be a Human Player).
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 does not submit a Lineup for their first of the division Playoffs or the Championship Playoffs within 2 minutes before the scheduled Match time, the Lineup is the Alliance Lead, first Alliance selection, and second Alliance selection. If any of these 3 Robots are unable to play, the Alliance must play the Match with only 2 (or even 1) Robot(S).
If an Alliance would like to change their Lineup after their first division Playoff or Championship Playoff Match, the Alliance Captain must report the Lineup to the Head Referee, or their designee, in writing prior to end of the preceding Match (e.g. the LineupS for Quarterfinal 2 must be submitted before the end of Quarterfinal 1). If the Head Referee is busy and there is no designee defined, the Alliance Captain waits in the question box to report the Lineup.
Once the Lineup is declared, it cannot be changed unless there is a team or Field Timeout. If there is a Timeout, the Alliance Captain may submit a different Lineup, but must do so while there are still more than 2 minutes remaining in the Timeout.
Example: 4 teams, A, B, C and D, form an Alliance going into the Playoff Matches on their division Field. During 1 of the Playoff Matches, Team C’s Robot becomes inoperable. The Alliance decides to bring in Team D to replace Team C. Team C repairs their Robot and may play in any subsequent Playoff Matches replacing Team A, B, or D. All 4 Alliance members are also eligible to play Matches during the Championship Playoffs should the Alliance win the division Tournament.
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 the Arena Fault rendered a Robot inoperable, in which case the Lineup can be changed.
FIRST distributes buttons to the Alliance Captains during the Alliance Captain meeting, which takes place on the division Fields. These buttons provide the necessary access to the Arena for pit crew members.
T901 *Wear your buttons. Only team members wearing proper buttons are allowed on the Arena floor during division and Playoff Matches.
Violation: Match won’t start until the situation is corrected. Those not displaying identification must leave the Arena.
Teams should assume they may be chosen for an Alliance and think about the logistics of button distribution and set a plan prior to the Alliance selection process. It is each Alliance Captain’s responsibility to distribute buttons to their pit crew members.
The 6 division Champions play a round-robin style tournament to determine the 2022 FIRST Robotics Competition Champions. In this format, each division Champion plays 1 Match against each of the other division Champions. The order of Matches is shown in Table 11‑10.
Table 11‑10 FIRST Championship Match order
|
Match |
Mass |
Energy |
|||
|
Red |
Blue |
Red |
Blue |
||
|
1 |
1 |
Carver |
Turing |
|
|
|
2 |
|
|
Galileo |
Roebling |
|
|
3 |
Hopper |
Newton |
|
|
|
|
2 |
4 |
|
|
Carver |
Roebling |
|
5 |
Turing |
Newton |
|
|
|
|
6 |
|
|
Galileo |
Hopper |
|
|
3 |
7 |
Carver |
Newton |
|
|
|
8 |
|
|
Roebling |
Hopper |
|
|
9 |
Turing |
Galileo |
|
|
|
|
4 |
10 |
|
|
Hopper |
Carver |
|
11 |
Newton |
Galileo |
|
|
|
|
12 |
|
|
Roebling |
Turing |
|
|
5 |
13 |
Galileo |
Carver |
|
|
|
14 |
|
|
Hopper |
Turing |
|
|
15 |
Newton |
Roebling |
|
|
|
In the Championship Playoffs, Alliances do not earn Ranking Points; they earn Championship Points. Championship Points are units credited to an Alliance based on their performance in each Match and are awarded at the completion of each Round Robin tournament Match.
A. The winning Alliance receives 2 Championship Points.
B. The losing Alliance receives 0 Championship Points.
C. In the event of a tied score, each Alliance receives 1 Championship Point.
Exceptions to A-C are as follows:
D. A Disqualified team, as determined by the Head Referee, causes their Alliance to receive 0 Championship points.
The total number of Championship Points earned by a team throughout the round robin Matches divided by the number of round robin Matches in which they’ve been scheduled is their Championship Score (CS).
All teams participating in round robin Matches are ranked by Championship Score. If the number of teams in attendance is ‘n’, they are ranked ‘1’ through ‘n’, with ‘1’ being the team with the highest Championship Score and ‘n’ being the team with the lowest Championship Score.
Table 11‑11 Einstein Tournament Ranking Criteria
|
Order Sort |
Criteria |
|
1st |
Championship Score |
|
2nd |
Average Alliance Hangar points |
|
3rd |
Average Alliance Taxi + Auto Cargo points |
|
4th |
Average Alliance Match points, including Fouls |
|
5th |
If tie affects which Alliances advance to Playoffs, a tiebreaker Match is played between the affected Alliances. If tie is between Alliances advancing to Playoffs, FMS randomly seeds tied Alliances to determine Alliance color. |
The 2 Alliances with the highest Championship Scores at the conclusion of the round robin tournament advance to the Einstein Finals. In the Einstein Finals, Alliances do not earn points, they earn a Win, Loss or Tie. The first Alliance to win 2 Matches is declared the 2022 FIRST Robotics Competition Champions.
During the Einstein Finals, if the Match score of each Alliance is equal, the Match is replayed. In this circumstance, the Lineup may be changed.
There are no Timeouts for teams in the Einstein tournament.
12
Glossary
|
Term |
Definition |
|
Active Device |
any device capable of dynamically controlling and/or converting a source of electrical energy by the application of external electrical stimulus |
|
Alliance |
a cooperative of up to 4 FIRST Robotics Competition teams |
|
Alliance Captain |
The designated student representative from each Alliance in a Playoff Match |
|
Alliance Area |
a 30 ft. (~914 cm) wide by 8 ft. 10 in. (~269 cm) deep infinitely tall volume formed by, and including the Alliance Wall, the edge of the carpet, and Alliance colored tape |
|
Alliance Wall |
an arena element that consists of 3 Driver Stations and a Hangar Wall |
|
Arena |
a space which includes all elements of the game infrastructure that are required to play RAPID REACTSM: the Field, Cargo, and all equipment needed for Field and robot management |
|
Arena Fault |
an error in Arena operation |
|
Auto |
The first phase of each Match in which Robots operate without any drive team control or input |
|
Backup Team |
The team whose Robot and drive team replaces another Robot and drive team on an Alliance during the Playoff Matches |
|
Bumper |
a required assembly which attaches to the Robot frame. Bumpers protect Robots from damaging/being damaged by other Robots and Field elements |
|
Bumper Zone |
the volume contained between the floor and a virtual horizontal plane 7½ in. (~19 cm) above the floor in reference to the Robot standing normally on a flat floor |
|
Bypassed |
the state assigned to any Robot which is unable or ineligible to participate in that Match, as determined by the FTA, LRI, or Head Referee |
|
Cargo |
a red or blue oversized tennis ball, 9½ in. (~24 cm) in diameter, weighs 9½ oz. (~270 g), and has a fuzz surface |
|
Cargo Bonus |
a reward granted if 20 or more Alliance colored Cargo scored in the Hub. If at least 5 Alliance colored Cargo are scored in Auto, called a Quintet, this threshold drops to 18 |
|
Cargo Line |
a 3 ft. (~91 cm) black line that starts 1 ft. (~30 cm) from the intersection of the Terminal and the ALLIANCE WALL and runs parallel to and 1 ft. (~30 cm) from the Alliance Wall |
|
Center Line |
a white line that bisects the length of the Field at a ~66° angle to the guardrail |
|
CARGO RING |
1 of 14 small rings used to keep the CARGO in place prior to the start of the MATCH. Rings are ⅛ in. (~3mm) thick, 1¾ in. (~4 cm) diameter O-rings (McMaster Item#: 9452K63). |
|
Chute |
a plastic sheet with 1⅛ in. (~3 cm) tall aluminum angles spaced 6½ in. (~17 cm) from each other to form channels. |
|
Coach |
a guide or advisor |
|
Component |
any part in its most basic configuration, which cannot be disassembled without damaging or destroying the part or altering its fundamental function |
|
Continuous |
describes rule violations that happen for more than approximately 10 seconds |
|
Control |
the state of a cargo if any of the following are true: A. the CARGO is fully supported by the ROBOT, B. the CARGO travels across the FIELD such that when the ROBOT changes direction, the CARGO travels with the ROBOT, C. the ROBOT is holding CARGO against a FIELD element in attempt to guard or shield it, or D. the ROBOT is preventing a CARGO from leaving a LOWER EXIT. |
|
COTS |
an adjective that describes a standard (i.e. not custom order) part commonly available from a Vendor for all teams for purchase |
|
Custom Circuit |
Any active electrical item that is not an actuator (specified in R501) or core control system item (specified in R710) |
|
Disabled |
the state in which a Robot is commanded to deactivate all outputs, rendering the Robot inoperable |
|
Disqualified |
the state of a team in which they receive 0 Match points and 0 Ranking Points in a Qualification Match or causes their Alliance to receive 0 Match points in a Playoff Match |
|
Driver |
an operator and controller of the Robot |
|
Driver Station |
1 of 3 assigned positions in an Alliance Wall from where a drive team operates their Robot |
|
drive team |
a set of up to 5 people from the same FIRST Robotics Competition team responsible for team performance for a specific Match |
|
Fabricated Item |
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 |
|
Field |
a 27 ft. (~823 cm) by 54 ft. (~1646 cm) carpeted area bound by and including the inward- and upward-facing surfaces of the guardrails, inward-facing surfaces of the Alliance Walls, and the front vertical faces of the Terminal |
|
Field Staff |
Referees, FTAs, or other staff working around the Field |
|
FMS |
Field Management System |
|
Foul |
a credit of 4 points towards the opponent’s Match score |
|
Frame Perimeter |
fixed, non-articulated structural elements of the Robot contained within the Bumper Zone |
|
FTA |
a FIRST Technical Advisor |
|
Guard |
framing formed by all Terminal structure above the Chute |
|
Hangar |
an arena assembly which consists of truss structure, bases, 4 rungs, RUNG mounting brackets, floor protection, and 2 Launch Pads |
|
Hangar Bonus |
a reward granted if an Alliance is credited with at least 16 Hangar points |
|
Hangar Wall |
a 2 ft. 9 ⅝ in. (~85 cm) wide by 6 ft. 5¾ in. (~197 cm) tall structure located between Driver Station 1 and the guardrail |
|
Hangar Zone |
a 9 ft. 8 in. (~295 cm) wide, 10 ft. 8¾ in. (327 cm) deep, and infinitely tall volume defined by the Alliance Wall, guardrail, and Alliance colored tape. The Hangar Zone includes the tape. |
|
High Rung |
a Rung installed on the Hangar and positioned such that its top is 6 ft. 3⅝ in. (~192 cm) above floor protection carpet |
|
Hub |
a structure centered on the Field and shared between Alliances. It consists of 2 funnel-shaped goals (an Upper Hub and a lower Hub), upper and Lower Exits, and 4 fenders |
|
Human Player |
a Cargo manager |
|
Inspector |
a volunteer employed to accurately and efficiently assess the legality of a given part or robot |
|
KOP |
Kit of Parts, 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 |
|
Launch Pad |
a piece of ¼ in. (~6 mm) thick, 1 ft. 5¼ in. (~44 cm) tall, and 10 in. (~25 cm) wide HDPE of the corresponding Alliance color |
|
Lineup |
the list of 3 teams participating in the Match and their selected Driver Stations |
|
Lower Exit |
one of the 4 tunnels from which Cargo leaves the lower Hub |
|
lower Hub |
the lower of 2 funnel-shaped goals |
|
Low Rung |
a Rung installed on the Hangar and positioned such that its top is 4 ft. ¾ in. (~124 cm) above Field carpet |
|
LRI |
a Lead Robot INSPECTOR |
|
Major Mechanism |
a group of Components and/or Mechanisms assembled together to address at least 1 game challenge: Robot movement, Cargo manipulation, Field element manipulation, or performance of a scorable task without the assistance of another Robot |
|
Match |
a two minute and 30 second period of time in which Alliances play RAPID REACT |
|
Mechanism |
an assembly of Components that provide specific functionality on the Robot |
|
Mid Rung |
a Rung installed on the Hangar and positioned such that its top is 5 ft. ¼ in. (~153 cm) above floor protection carpet, and its center is 3 ft. 6 in. (~107 cm) from the center of the Low Rung |
|
Momentary |
describes rule violations that happen for fewer than approximately 3 seconds |
|
MXP |
myRIO Expansion port, the expansion port on the roboRIO |
|
Operator Console |
the set of Components and Mechanisms used by the Drivers and/or Human PlayerS to relay commands to the Robot |
|
Passive Conductor |
any device or circuit whose capability is limited to the conduction and/or static regulation of the electrical energy applied to it (e.g. wire, splices, connectors, printed wiring board, etc.) |
|
PH |
a Pneumatic Hub |
|
PCM |
a Pneumatic Control Module |
|
PDH |
a Power Distribution Hub |
|
PDP |
a Power Distribution Panel |
|
Pin |
the act in which a Robot is preventing the movement of an opponent Robot by contact, either direct or transitive (such as against a Field element) |
|
PuRPle Plane |
a virtual boundary which extends the width of the Terminal and is defined by the Field side edge of the Guard and the purple tape which runs parallel to the interior ramp |
|
quintet |
a scenario in which at least 5 Alliance colored Cargo are scored in Auto |
|
Red Card |
a penalty assessed for egregious Robot or team member behavior or rule violations which results in a team being Disqualified for the Match |
|
Referee |
an official who is certified by FIRST to enforce the rules of RAPID REACT |
|
Repeated |
describes rule violations that happen more than once within a Match |
|
Robot |
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 |
|
RP |
a Ranking Point |
|
RPM |
a Radio Power Module |
|
RS |
the Ranking Score |
|
RSL |
a Robot Signal Light |
|
Rung |
1 of 4 1¼ in. Schedule 40 steel pipes, with a 1.66 in. (~4 cm) outer diameter, and are powder coated to reflect the Alliance color |
|
Signal Level |
circuits which draw ≤1A continuous and have a source incapable of delivering >1A, including but not limited to roboRIO non-PWM outputs, CAN signals, PCM/PH Solenoid outputs, VRM 500mA outputs, RPM outputs, and Arduino outputs) |
|
Shadow Line |
a black line that lies directly below the MID RUNG |
|
Starting Configuration |
the physical configuration in which a Robot starts a Match |
|
Starting Line |
a white line spanning the width of the carpet and located 2 ft. 4 in. (~71 cm) from the back of the Driver Station diamond plate panel to the near edge of the tape. |
|
Student |
a person who has not completed high-school, secondary school, or the comparable level as of September 1 prior to Kickoff |
|
Surrogate |
a team randomly assigned by the Field Management System to play an extra Qualification Match |
|
Tarmac |
1 of 4 (2 per Alliance) 12 ft. 9 in. (~389 cm) wide by 7 ft. ¾ in. (~215 cm) deep infinitely tall volumes bounded by and including the Alliance colored tape |
|
taxi |
the state of a Robot whose Bumpers have completely left the Tarmac from which it started at any point during Auto |
|
Tech Foul |
a credit of 8 points toward the opponent’s Match score |
|
Technician |
a resource for Robot troubleshooting, setup, and removal from the Field |
|
Teleop |
The second phase of each Match |
|
Terminal Area |
1 of 2 7 ft. 8½ in, (~235 cm) wide by 6 ft. 9 in. (~206 cm) deep and infinitely tall volumes bounded by and including purple tape |
|
terminal starting line |
a white line spanning the width of the terminal area and located 2 ft. (~61 cm) from the back of the terminal area |
|
Terminal |
a Field element which consists of 1 ramp, 1 Guard, 1 PuRPle Plane, 1 Chute, and other structure elements shown in Figure 5‑20 |
|
Traversal Rung |
a Rung installed on the Hangar and positioned such that its top is 7 ft. 7 in. (~231 cm) above floor protection carpet |
|
Timeout |
a period of up to 8 minutes between Matches which is used to pause Playoff Match progression |
|
Upper Exit |
1 of the 4 extensions on which Cargo leaves the Upper Hub |
|
Upper Hub |
The higher of 2 funnel-shaped goals |
|
Vendor |
a legitimate business source for COTS items that satisfies all criteria listed in Section 9 Robot Construction Rules |
|
VRM |
a Voltage Regulator Module |
|
Yellow Card |
a warning issued by the Head Referee for egregious Robot or team member behavior or rule violations. A subsequent Yellow Card within the same tournament phase results in a Red Card |
FIRST®, the FIRST® logo, FIRST® Robotics Competition, FIRST® Tech Challenge, RAPID REACTSM, FIRST FORWARDSM, Gracious Professionalism®, and Coopertition® are trademarks of For Inspiration and Recognition of Science and Technology (FIRST). LEGO® is a trademark of the LEGO Group. FIRST® LEGO® League is a jointly held trademark of FIRST and the LEGO Group. All other trademarks are the property of their respective owners. ©2022 FIRST. All rights reserved.