FTC 2012 2013 GameManual Part1

7/30/2019 FTC 2012 2013 GameManual Part1

1/32

FIRSTTech Challenge2012-2013 Game Manual Part 1:

Tournament Informaon, Awards and Robot Rules


2/32

Rev 7 - November 2012 FIRSTTech Challeng1

TEAMS MUST COMPLY WITH ALL RULES AND REQUIREMEN TS LAID OUT INTHIS DOC UMENT, THE GAME MANUAL RELEAS ED AT KICKOFF IN SEPTEM BER

AND ANY UPDATES ISSUED ON TH E Q&A SECTION OF TH E FTC FORUM AND AT

HTTP://FTCFORUM.USFIRS T.ORG/. FORUM RULINGS TAKE PRECED ENCE OVER

INFORMATION IN SEASON MANUALS.

IMPORTANT NOTICE:

Revision History

Rev Date Descripon

1 May-2012 Inial Release

2 June-2012 Secon 2.14 - Champion Alliance changed to Winning Alliance

Secon 3.3 - claricaon on pilot judging

Secon 4.2.2 reference to n changed to p

Secon 4.2.3 - NXT sleep mer sets to NEVER. previously language saidOFF

Secon 5.1 - processes changed to process

3 June-2012 Footer corrected to reect proper revision.

Secon 4.2.2 reference to changed to p

Page border modied to prevent footer from being truncated when printed

Appendix A: Header moved to proper locaonAppendix B removed from table of contents

Secon 5.5: Corrected reference to advancement criteria from 2.18 to 2.8

Secon 2.6 sub-secons renumbered for clarity

4 Sept 8 2012 Minor typographical correcons

5 Oct 18 2012 Updated language in About FIRST secon to reect proper grade range for

FTC.

Corrected address for Ocial FTC Forum in the noce above.

6 Nov 9 2012 Correcon on page 16 : Changed Secon 8 to Game Manual Part

2: Secon 2.4

7 Nov 28 2012 Page 16, Secon 2.4: Added verbiage clarifying requirement for BOM.


3/32

Rev 7 - November 2012 FIRSTTech Challenge2

Contents

Introducon ........................................................................................................................................................ 3

1. What is FIRST Tech Challenge? .................................................................................................................... 4

2. The Tournament ............................................................................................................................................. 5

3. Engineering Notebooks ................................................................................................................................ 13

4. The Robot ..................................................................................................................................................... 16

5. Judging & Award Criteria ............................................................................................................................. 22

6. Team Resources ........................................................................................................................................... 28

Appendix A: ............................................................................................................................................ 30


4/32


Introducon

About FIRST

to create a world where science and technology are celebrated where young people dream of

becoming science and technology heroes.

Dean Kamen, Founder, FIRST

FIRST (For Inspiraon and Recognion of Science and Technology) was founded by inventor Dean Kamento inspire young peoples interest and parcipaon in science and technology. Based in Manchester, New

Hampshire, FIRSTis a 501(c)(3) not-for-prot public charity.

As a volunteer-driven organizaon, FIRSTis built on partnerships with individuals as well as businesses,

educaonal instuons, and government. Some of the worlds most respected companies provide funding,

mentorship me and talent, and equipment to make FIRSTs mission a reality. As a team coach, you join over

90,000 commied and eecve volunteers who are key to introducing close to 250,000 young people to the

joy of problem solving through engineering.

FIRSTprovides four programs: the FIRSTRobocs Compeon (FRC) and the FIRSTTech Challenge (FTC) for

grades 7-12; FIRSTLEGO League (FLL) for 9 to 14 year-olds, and Junior FIRSTLEGO League (Jr.FLL) for 6 to

9 year-olds. Also located at FIRSTheadquarters is the research and development facility called FIRSTPlaceTM.FIRSTPlace is integral to game design, new program development, evaluaon, and professional development

ofFIRSTmentors.

We want to change the culture by celebrang

the mind. We need to show kids that its more

fun to design and create a video game than it is to

play one.

Dean Kamen,

Founder, FIRST

Dean Kamen is President of DEKA Research & Development Corporaon; a dynamic company focused on

the development of revoluonary new technologies that span a diverse set of applicaons. As an inventor,

physicist, and entrepreneur, Dean has dedicated his life to developing technologies that help people lead

beer lives. Deans proudest accomplishment is founding FIRST.


5/32


1. What is FIRST Tech Challenge?

FIRSTTech Challenge (FTC) had its beginnings in 2005 and grew out of a need for a mid-level robocs program

to transion teams from FIRST LEGO League to the FIRST Robocs Compeon. Piloted for two years as

the FIRSTVex Challenge, FTC became an ocial FIRSTprogram and was renamed FIRSTTech Challenge in 2007.

FIRSTTech Challenge is a student-centered acvity that is mentor supported and is about giving students

a unique and smulang experience. We want students to learn the value of teamwork and to respect

everyones ideas and contribuons to the team. FIRSTTech Challenge allows high school students to work

hand-in-hand with technical professionals to develop a soluon to the annual challenge. The students do

a majority of the work, but the mentor is there to oer guidance, suggesons, and coaching to keep the

students on task and successful. FIRSTvalues are about appreciang our dierences and learning what those

dierences add to our lives. FIRSTprograms succeed most fully when team members bring the FIRSTvalues

they learn back to their communies.

The FTC Compeon Kit challenges students creave problem-solving skills by enabling them to build robots

that do amazing things. When you bring dedicated, enthusiasc students and a mentor together, the results

can be phenomenal! Students design and construct roboc devices which can be autonomously programmed

or operator-controlled to perform various tasks.

FIRSTTech Challenge teams receive each years game during a September Kicko. The games rules andregulaons are provided on the www.usrst.org website.

1.1 Gracious Professionalism A FIRSTCredo

Dr. Woodie Flowers, Naonal Advisor for FIRST, speaks about Gracious Professionalism in this way: The

FIRSTspirit 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 ofFIRST. It is part of

what makes FIRSTdierent and wonderful.

Gracious Professionalism can and should mean dierent things to each of us. It is possible however, to outline

some of its meanings:

Gracious atudes and behaviors are win-win.

Gracious folks respect others and let that respect show in their acons.

Gracious professionals make a valued contribuon in a manner pleasing to others and to

themselves as they possess special knowledge and are trusted by society to use that knowledge

responsibly.

As Woodie says, In the long run, Gracious Professionalism is part of pursuing a meaningful life. One can add

to society and enjoy the sasfacon of knowing that you have acted with integrity and sensivity. Thats good

stu!

In FIRST, Gracious Professionalism means that we learn and compete like crazy, but treat one another

with respect and kindness in the process. We try to avoid leaving anyone feeling like they have lost. No

chest-thumping barbarian tough talk, but no scky sweet platudes either. Knowledge, pride and empathy

comfortably blended.


6/32


2. The Tournament

2.1 Overview

The FIRSTTech Challenge will be played in a tournament format. Each tournament will include pracce,

qualifying, and eliminaon matches. Aer the qualifying matches, teams will be ranked based on their match

performance. The top-ranked teams will select alliance partners and parcipate in the eliminaon matches to

determine the event champions.

This secon provides a general summary regarding a FIRSTcredo, mascots, uniforms, recommended items and

equipment for teams to bring, pit rules, event schedules, registraon, pracce rules and me slots, and robot

inspecons. Please read the following to get a feel for compeon schedules, registraon procedures, pracce

mes, and matches.

2.2 Tournament Denions

Alliance - Each FTC match is comprised of two, two-teamAlliances. At events with more than 20 teams,

the semi-nal and nal roundAlliances are made up of three teams each. However, only two of those

teams will compete during a match.

Alliance Captain The student representave from anAlliances highest ranked team chosen torepresent anAlliance duringAlliance Selecon and for the nal Eliminaon Matches. The enre team

may also be referred to as theAlliance Captain.

Alliance Selecon The process top-ranked teams choosingAlliances Partners for the Eliminaon

Matches.

Eliminaon Match A Match used to determine the Winning Alliance. Alliances of two or three teams

face o in a series ofmatches, with two teams per alliance playing in each match. The rst alliance to

win two matches will proceed to the next round.

Pracce Match A Match used to provide me for teams to get acquainted with the ocialplaying

eld.

Qualifying Match A Match used to determine the teams that qualify for theAlliance Selecon to

move on to the Eliminaon Matches. Alliances compete to earn Qualifying Points and Ranking Points.

Qualifying Points (QPs) The rst basis for ranking teams, Qualifying Points are awarded for winning

(two points) and tying (one point) a Qualifying Match.

Ranking Points (RPs) The second basis of ranking teams, Ranking Points are used as the ebreakers

when teams have equal Qualifying Points. Ranking Points are awarded in the amount of the nal score

of the losingAlliance in a Qualifying Match. The winningAlliance will receive the pre-penalized score

of the losingAlliance as their RP. The losingAlliance will receive the nal score (including penales) of

the losingAlliance as their RP.

Surrogate Match An addional Qualifying Match for some teams depending on the number of

teams in the tournament. A Surrogate Match will not count in the standings for Qualifying Points or

Ranking Points to the teams that are marked as playing as surrogates. However, these matches are

very important in the enre standings and should be played by all as if they were regular Qualicaon

Matches. Surrogate Matches will be marked as such on the ocial Qualifying Match schedule.

2.3 Tournament Event Schedule

Event schedules will be available through your Tournament Host prior to or at your tournament. Qualicaon

Match schedules are created on tournament day by the scoring system aer all teams have checked-in and


7/32


have begun or completed the inspecon process.

2.4 Courtesies and Rules

You will hear the expression Gracious Professionalism (GP) oen throughout your involvement in FTC. One

of FTCs main goals is to encourage all team members to conduct themselves with kindness, consideraon,

and sharing. We hear heartwarming stories of teams sharing parts, helping to build and/or repair compeng

robots, and helping rookie teams avoid preventable pialls. These examples of GP are some of the benets of

being involved with this organizaon.The pit is where the behind-the-scenes acon takes place. The FIRSTsta and volunteers want you to enjoy

the compeon. Follow the rules below while in the pit as well as in the audience so everyone can work and

compete in a safe, sportsmanlike, friendly, and orderly manner.

Bands: No live bands in the audience or pit.

Baery Safety: Charge your baeries in an open, well-venlated area.

Fire Exnguishers: Located at the pit administraon staon and in the compeon area.

Food: You should check with the event organizer before bringing food to an event, as some venues will not

allow outside food on-site due to contracts and agreements.

Music/Noise: No loud music, audio systems, whistles, banging scks, blow horns, etc. They prevent teams

from hearing important announcements. Power may be shut o and/or noisemakers conscated.

Internet/Wireless Network Access: Teams may not setup a wireless computer network for any purpose

(i.e. Internet access, team communicaon, team computer to robot, etc.) Teams are required to

use the wireless computer network provided by the Tournament Organizers or venue for all robot

communicaon. Internet access for the teams will be at the discreon of the Tournament Director.

Radios/Walkie-Talkies: Teams are not allowed to use Radios and walkie-talkies anywhere in the tournament

facility.Sales: Because of site regulaons/contracts, FIRSTcannot allow teams or individuals to sell items, such as

T-shirts, pins, etc. at any events.

Seat Saving: Sing together in a group during compeon matches makes the game more excing and

fun. Its where you can show support for your team. Since there is oen not enough seang to

accommodate everyone, there has to be a policy regarding seang. Teams are not allowed to save

seang space.

Team Safety Captain: Each team appoints a safety captain who will help maintain safety at events, especially

in the pit. He or she will remind aendees about safety rules listed below.

Safety Glasses: All team members and onlookers must wear ANSI Z87.1 cered safety glasses in the pit and

near the compeon area. If you wear prescripon glasses, you must wear safety goggles over them

or aach safety side shields to them. Teams are required to bring enough safety glasses/goggles to

supply to team members and guests.

Running: There is no running in the pit.

Painng: There is no painng in the pit.

Soldering, Gluing, Brazing, or other Large Power Tools: These acvies and tools are not allowed in the pit


8/32


areas or at the compeons unless the tournament director specically allows them.

2.5 Eye Protecon and Safety

FIRSTrequires all teams to bring and supply ANSI Z87.1 cered safety glasses for their members and guests

for each compeon. Students and adult team members and guests must wear them to protect their eyes

while working on the robot, when observing robot building/repair work, and while compeng.

Operators, players, and coaches will not be allowed in the compeon area without them. Regular glasses and

sunglasses do not qualify as safety glasses. If you wear prescripon glasses, you must wear safety goggles overthem or aach safety side shields.

2.6 Event Day Overview

1. Team Check-in

2. Robot Hardware and Soware Inspecon

3. Judges Interviews

4. Drivers Meeng

5. Pracce Matches

6. Opening Ceremony

7. Qualicaon Matches

8. Alliance Selecon

9. Eliminaon Matches

10. Awards and Closing Ceremony

2.6.1 Team Check-In

As a team arrives at the venue, the Coach or other adult mentor should register the team with the tournamentocials. During check-in, the Coach will receive a packet of informaon for the team that may include drive

team badges, a judging schedule, a map of the facilies and pits, and other informaon that is very important

to the teams. The Coach should review all the material to make sure the packet is complete. At this me, the

team should set up their Pit area and get familiar with the venue such as where the pracce and playing elds

are, where judging will take place, and review the schedule of events for the day.

2.6.2 Robot Hardware and Soware Inspecon

FTC robots will be required to pass hardware and soware inspecons before being cleared to compete.

This inspecon will ensure that all FTC robot rules and regulaons are met. A copy of the ocial FTC Robot

Inspecon Sheet is located in another secon. The Robot Inspecon Sheet should be used by teams as a

guide to pre-inspect their robot prior to tournament day. A Bill of Materials (BOM) of non-TETRIX (or non-

MATRIX) parts must be presented at Hardware Inspecon.

2.6.3 Judges Interviews

At FIRSTTech Challenge events, there are generally three parts to the judging process: 1) interview with judges

2) evaluaon of performance during the tournament, and 3) evaluaon of the Engineering Notebook. Each

team will have a ten to een minute fact nding discussion/interview with a panel of two or three judges.

The Judges Interviews generally take place before any qualicaon matches so that the enre team may be

interviewed. When teams arrive at the event, the interview schedule should be included in the registraon


9/32


materials. Make sure you know when your team will be interviewed and arrive to the interview room early.

Please have at least two student team representaves and the robot available; the enre team is encouraged

to parcipate. Mentors (no more than two) are welcome to observe the Judges Interview at most events, but

should not parcipate (see Secon 4.7 for more details).

2.6.4 Drivers Meeng

The Drivers Meeng takes place prior to the start of qualicaon rounds and is a me when the drive team

meets with the referees. During this me, the head referee gives a brief overview of what is expected ofteams and any venue specic informaon, such as queuing paths, and explain any signals and commands they

will give during matches.

2.6.5 Pracce Matches

At the event, pracce matches may be played in the morning unl the drivers meeng begins. Every eort wil

be made to equalize pracce me for all teams, but may also be conducted on a rst-come, rst-served basis.

These matches may be scored, but the scores do not aect team ranking.

2.6.6 Opening Ceremony

The Opening Ceremony is the ocial kicko of the events acvies for the teams, the fans, and the public.During the Opening Ceremony, a tournament ocial or the emcee will welcome the teams and the public,

introduce dignitaries and other special guests, and introduce the judges and the referees. Then the game

will be described (usually with a video) and the naonal anthems of all the teams countries will be played.

Immediately aer, the Qualicaon Match takes place.

If your team is in any of the rst four matches on the day of your event, volunteers will ask you to line up

before the opening ceremonies. Matches begin right aer its conclusion. Please, make sure your team is on

me in case you have an early match.

2.6.7 Qualicaon Matches

The qualifying match schedule will be available prior to opening ceremonies on the day of the event. Thisschedule will indicate alliance partners and match pairings. It will also indicate the alliances color (red or

blue) and the posion in the alliance staon (1 or 2) for the drive team. Robots may be placed in either of the

alliances starng locaons. These matches will start immediately aer the Opening Ceremonies in accordance

with the qualicaon match schedule. The queue team will work together throughout the day to line up

teams for the matches and maintain the schedule. It is very important to pay aenon to the match schedule

and listen for announcements throughout the day. You will need to know when you will compete, nd out the

number of the ending match before lunch, and which match is the last match of the tournament day.

Teams will be randomly assigned to matches and alliances. All teams will be scored based on the same

number of qualifying matches. In some cases, a team will be asked to play a surrogate match which will not

count towards their standings during the event. This addional match will be denoted on the match scheduleand/or announced to the teams prior to the start of the qualifying matches.

At the conclusion of each match, Qualifying Points (QP) will be awarded:

Winning teams of a qualifying match each receive two (2) QP.

Losing teams of a qualifying match receive zero (0) QP.

If a qualifying match ends in a e, all four teams receive one (1) QP.

If a team is disqualied, they receive zero (0) QP.

Teams will also receive Ranking Points (RP) based on the following:


10/32


The number of ranking points assigned for each match, is that of the losing alliances score. The

winning alliance will receive the pre-penalized score of the losing alliance as their RP. The losing

alliance will receive the nal score (including penales) of the losing alliance as their RP.

In the event of a e, both alliances will receive the same RP (equal to the e score).

If a team is disqualied, they receive zero (0) RP.

If both teams on an alliance are disqualied, the teams on the winning alliance will be awarded

their own score as their RP for that match.

Teams with non-funconing robots may receive credit for a qualifying match if their robot has passedinspecon and at least one member of the drive team is present in the alliance staon for the scheduled

match. If no member of a team is present in the driver staon at the start of a match, that team is declared a

no show and will receive zero (0) QP and zero (0) RP.

At the conclusion of all Qualicaon Matches, the teams will be ranked from rst through last on the basis of

their total Qualifying Points (QPs). If mulple teams have the same QP total, then teams will be ranked on the

basis of their total Ranking Points (RPs). If mulple teams have the same RP total as well, then teams will be

ranked on the basis of their highest match score. If sll ed, the next highest match score will be used unl the

e is broken. In the unlikely event that there is sll a e based on idencal match scores, then the teams will

be ranked by a random electronic draw.

2.6.8 Alliance Selecon

The number of teams in the Eliminaon Matches will be based on the number of teams in the tournament. If

there are 21 or more teams in the tournament, the Eliminaon Matches will consist of alliances of 3 teams

each. If there are 20 teams or less, then the alliances will consist of 2 teams each. There will be a total of four

(4) alliances that will compete in the Eliminaon Bracket.

The alliance selecon process will consist of a number of rounds of selecons, such that all alliance captains

will form eliminaon match alliances consisng of the requisite number of teams. These alliances will

parcipate in a ladder-type tournament to determine the events Winning Alliance. The alliance selecon

process is as follows:

Each team will choose one student to act as the teams representave. These representaves will

proceed to the compeon area at the designated me to represent their teams in the alliance

selecon. It is recommended that the representave also bring their robot to the compeon area

as teams making selecons may not know team names or numbers, but do know what the robots

look like.

In order of tournament ranking, the student representave of the highest ranked team not already

in an alliance will be asked to step forward as the Alliance Captain to invite another available team

to join their alliance.

A team is available if they are not already part of an alliance, or have not already declined an

alliance invitaon. If the team accepts, it is moved into that alliance. If a team declines, they

CANNOT be invited into another alliance, but are sll available to select their own alliance if the

opportunity arises. If a team declines, the alliance captain from the inving team must then extend

an invitaon to another team.

The process connues unl all alliance captains have been designated and chosen one alliance

partner.

If there are more than 20 teams, the same method is used for each alliance captains second

choice (the third member of the alliance) from highest seed to lowest seed ( i.e. 1 -> 2 -> 3 -> 4).

Any teams remaining aer the lowest seeded captain makes their choice will not compete in the

Eliminaon Matches.


11/32


2.6.9 Eliminaon Matches

The Eliminaon Matches are very excing. This is when

the alliances determine who will be the Champion of the

event. The matches are played in a seeded ladder format

where the top seed goes up against the lowest seed, 2nd

best seed vs. the 2nd lowest seed, and so on.In the eliminaon matches, teams do not get qualifying

points; they get a win, loss or e. Within each bracket

of the eliminaon, matches will be played to determine

which alliance advances. The advancing alliance is the

rst one to win two matches. Any ed matches will be

replayed unl one alliance has two wins, and advances.

An example tournament bracket appears here:

During each round of the eliminaon matches, two teams from an alliance will compete on the playing eld.

If the alliance has three teams on it, the team that sits out the rst match in an eliminaon series must play

in the second match, with no excepons. If the alliances play more than two matches in any round, anycombinaon of two alliance robots may be used. Teams should consider the robustness of the robots when

picking alliance partners.

If a team is disqualied during an eliminaon match, then their enre alliance is disqualied, and the match

will be recorded as a loss. Prior to each eliminaon match, the alliance captain must let the referee know

which two teams will be playing in the upcoming match.

2.6.10 Awards and Closing Ceremony

The Awards and Closing Ceremony celebrates the accomplishments of the teams during the season and

how they all did during the event. The ceremony will begin as soon as the last match is played, however

some awards may be given out earlier in the event day (depending on the tournament ocials). During theceremony, all teams will be recognized for their accomplishments as the awards are handed out. The Winning

Alliance teams and the Finalist Alliance teams will also be recognized. Finally, the Inspire Award winner will

also be announced.

2.7 Tournament Types

There are several types of events and tournaments that teams and other organizers hold throughout the FTC

season and o-season. These are categorized in the following secons.

2.7.1 Local Events

Anyone can host a local event, also known as a scrimmage, to prepare for a Championship or Qualier, or asan alternave to aending other events. If you choose to create and host a local event, you are responsible for

nding a locaon, organizing the format for the day, and inving other teams to parcipate. You may also have

to secure the eld elements, computers, and other items depending on how you would like the local event to

look and feel.

2.7.2 Qualifying Tournaments

Hosted and managed by FTC Aliate Partners or Partner-appointed hosts. Qualifying Tournaments follow the

same judging and game guidelines and format of Championship Tournaments. Qualifying Tournaments are

usually held prior to Championship Tournaments in regions where there are many FTC teams. The number of

SF1

SF2

Semi Finals Finals Champion

#4 Seed

#1 Seed

#2 Seed

Winner of SF1

Winner of Finals

Winner of SF2

#3 Seed


12/32


teams advancing to the state Championship Tournament depends on the capacity of the state Championship

Tournament, the number of Qualifying Tournaments and the number of teams aending the Qualifying

Tournament. The Advancement Criteria for moving up to the next level of tournament is detailed in Secon

2.2 below.

2.7.3 Championship Tournaments

Hosted and managed by an FTC Aliate Partner, Championship tournaments abide by certain standards in

format, judging, awards, and overall quality. Some Championship tournaments require that teams win at aqualifying tournament in order to advance to the Championship. Championships may include teams from

a geographic region, province, state, country, or several countries. Advancement eligibility for the World

Championship is the same as moving on from Qualifying Tournaments to the local Championship Tournament

and is based on the number of teams that are invited to the World Championships.

2.8 Advancement Criteria

Teams will advance to the next level of compeon in the order indicated below according to the number of

spots available. The advancement criteria will be applied to teams advancing from Qualifying Tournament to

Championship Tournaments and from Championship Tournaments to the World Championship Tournament.

In the event that the team listed has already advanced or there is no team ng that descripon (as in 2ndteam selected at smaller events), the advancement will connue in order.

1. Qualier Host Team (NOTE: Assuming that the team competes at one other tournament within

the region and has met the criteria set forth by the Aliate Partner in the agreement. This

advancement applies to Qualifying Tournament hosts only, and does NOT apply to host teams of

Championship Tournaments).

2. Inspire Award Winner

3. Winning Alliance Captain

4. Inspire Award 2nd place

5. Winning Alliance, 1st team selected

6. Inspire Award 3rd place

7. Winning Alliance, 2nd team selected

8. Think Award Winner

9. Finalist Alliance Captain

10. Connect Award Winner

11. Finalist Alliance, 1st team selected

12. Rockwell Collins Innovate Award Winner

13. Finalist Alliance, 2nd team selected

14. PTC Design Award Winner15. Highest Ranked Team not previously advanced

16. Movate Award Winner

17. Highest Ranked Team not previously advanced

2.9 Tournament Rules

Referees have ulmate game play and scoring authority during the compeon. Their rulings are

nal.


13/32


a. The referees may not review any recorded match replays or pictures.

b. Any quesons for the referees must be brought forward by one student drive team member

per team within the me period of two (2) matches following the disputed match. Students are

expected to support their quesons by referencing specic rules or posts to the Q&A secon of the

ocial FTC Forum.

c. Team members are not allowed onto the playing eld for any reason other than to place or retrieve

their robots. Inspecon of the playing eld elements by team members for the express purpose

of determining scoring is prohibited. Individuals and Teams that violate this rule will be subjectto possible team penales that could include match disqualicaons or even removal from the

tournament.

Only three team representaves permied in the compeon area; two (2) student drivers, and

one (1) coach who are idened by badges designang driver or coach. These badges are

interchangeable within a team in between matches. Only student team members wearing a badge

designated as driver may drive the robot during the match.

There are no me outs during the qualifying rounds. The matches must progress according to

schedule. If a robot cannot report for a match, at least one member of the team should report to

the playing eld for the match.

Teams are guaranteed a minimum of ve minutes (5:00) between parcipang in consecuve

matches.

During the eliminaon rounds, each alliance will be alloed ONE me out of no more than three

minutes (3:00). Time outs must be called at least two minutes (2:00) prior to their next matchs

starng me. The me out will begin at the me their match was going to start.

All team members and their guests, including coaches, must wear ANSI 87.1 cered safety glasses

or prescripon glasses with side shields while in the pits or alliance staons during matches.

NOTE:FIRSTrequires all teams to bring and supply, for each compeon, ANSI-approved non-shaded

safety glasses for its team members, mentors, and guests. For our purposes, amber lenses that allow

for enhanced vision are considered nted, not shaded, and their use is allowed at FIRSTevents.

Sunglasses or deeply shaded safety glasses used in our indoor event environment are not acceptable.

2.10 Team Spirit

Compeng as a team is fun as well as rewarding. Part of the pleasure and reward of being a team member is

the way the team styles itself with team T-shirts, trading buons, hats, cheers, cheerleaders, and costumes.

2.11 Team Styling

When deciding on a team name or acronym, consider how you can work a theme around it to make your team

more fun and recognizable. Refer to Secon 5.5 for informaon about FIRSTand FTC logo use requirements.

2.12 Banners and Flags

Sponsors provide FIRSTwith banners so we can display them in specied areas as a way of thanking them for

their generosity. We encourage teams to bring team ags and/or sponsor banners, but we ask that you adhere

to the following:


14/32


Do not use them to secon o seang. Saving group seats is not permied.

Hang banners in your pit staon only, not on the pit walls.

You may bring banners to the compeon area, but please do not hang them there. This area is

designated for ocial FIRSTsponsors banners.

2.13 Spectators and Equee

Teams are permied to have 2 student drivers and 1 coach (the Drive Team) at the playing eld during

their scheduled matches. Spectators are not allowed in the compeon area at any me and must remain

outside of the designated compeon area. Some events may provide media passes for one addional team

member to gain access to a designated media area. Access to this area is only permied with a media pass

and only while the media representaves team is on the playing eld. Spectators blocking the sidelines or

accessing the media area without a pass will be asked to move. Repeated violaons of this rule may cause the

associated team to be disqualied.

2.14 Scoung

This informaon has been provided by the 2007 FRC Chairmans Award winners, FRC Team #365, the Miracle

Workerz:

Teams use dierent methods to record informaon about other teams paper, computer, hand-held PDAs,

etc. Use whatever method is most comfortable for your team. Scoung is important to determine how you

complement other teams in your alliance and how you match up against your opponents. No maer how

you record it, focus on informaon which will be useful to your team when you meet your alliance partners to

discuss strategy.

Some possible areas to gather informaon include:

CAPABILITIES what can the robot/team do and what cant it do?

STRATEGIES what does the robot / team do during the match? How do they play the game?

PERFORMANCE how well does the robot / team do what it aempts? What are the robots

strengths and weaknesses?

AUTONOMOUS what does the robot do in autonomous mode? Does the team have mulple

program opons?

The more data points you can collect on strategies and performance, the beer understanding you will have

of a given team. Informaon on a teams capabilies can be obtained by vising the team in the pit area or

watching match play.

3. Engineering Notebooks3.1 Overview

This secon describes the requirements for creang the Engineering Notebook, including formang

guidelines, Judges ps, and the use of various forms of engineering support. It also provides links for sample

pages from an award winning FTC Engineering Notebook.

3.2 What is an Engineering Notebook?

One of the goals ofFIRSTand FTC is to recognize the engineering design process and the journey that a team

makes during the phases of the problem denion, concept design, system-level design, detailed design, test


15/32


and vericaon, and producon.

Throughout the building of your robot you will come across obstacles, lessons learned, and the need to draw

things out on paper. This is where you and your team will use an engineering notebook. These notebooks will

follow your team from kicko throughout the compeons. Judges will review your engineering notebook to

beer understand your journey, design, and team.

Note: Refer to the judging criteria in the Awards & Judging Criteria secon for more details on how your

engineering notebook will be judged.

3.3 The Notebook

Teams may choose to record their season with either handwrien or electronic or online documents. No

disncon is made between handwrien and electronic Engineering Notebooks during judging.

Electronic/Online: Teams may choose to use electronic or online programs to create their Engineering

Notebook. For the purposes of judging, teams must print out their Engineering Notebooks and place

them in a binder, no larger than 1.5. All pages must be numbered and in order. Only one copy is

required per team. Some events are pilong a video judging process for the 2012-2013 season. Your

local Aliate Partner will nofy you if your event is pilong this and will let you know how to submit

materials.

Wrien: Spiral-bound, Laboratory, or documentaon notebooks are available through your school or local

staonary supply store or you may use the notebook supplied by Rockwell Collins delivered to you in

your Kit of Parts. Use the following criteria:

1. Do not use a loose-leaf notebook.

2. Numbered pages are recommended (but not necessary) so that pages cannot be substuted or

deleted.

3. Only one Engineering Notebook is required per team.

4. Mulple teams may not share an Engineering Notebook.

3.4 Guidelines/Format

The FTC engineering notebook is a complete documentaon of your teams robot design. This documentaon

should include sketches, discussions and team meengs, design evoluon, processes, obstacles, and each team

members thoughts throughout the journey for the enre season. A new notebook should be created for each

new season. The guidelines are:

1. Document EVERYTHING!!

2. Engineering Notebooks should be organized enough to have an outsider understand your team and

your journey.

3. Wrien entries should be in permanent ink not pencil.

4. Start your notebook by introducing each team member and mentor with a brief biography of their

name, age (or school year), interests, and reasons for joining your FTC team.

Tip: Pictures along with the bios would serve as a great visual for the judges to get to know each

member of your team.

5. Start a fresh page at every meeng. The date, and start/stop mes should be recorded when

starng a new page. Each day should start with two columns:

a. Task Column What is your team doing and discovering?


16/32


b. Reecons Column Where your team records thoughts on what is happening and any

quesons that need to be answered.

6. Entries should be made by every team member, inialed, and dated.

7. All designs and changes to your robot should be recorded directly into your notebook. The

inclusion of all details and sketches are preferable. Notes and calculaons should be done in your

notebook, NOT on loose paper.

Tip: A judging panel is always interested to see a unique design or playing strategy. On the other hand,

a design without the substance to support its reasoning is not viewed as highly.

8. In the case of an error, draw a single line through the incorrect data. Do NOT erase or use

correcon uid. All correcons should be inialed and dated.

9. Use both sides of a page. Never leave any white space: X out or crosshatch all unused space, and

inial and date.

10. To insert pictures or outside informaon into your notebook, tape the picture into your notebook

and outline with permanent ink, to note that it was there in case it falls out. Put the corresponding

page number on that inserted page.

Tip: Pictures or sketches of your robot designs are recommended as part of a thorough documentaon.

11. Insert a copy of your robots Bill of Materials (BOM) as part of your Engineering Notebook asrequired by rules in the annual Game Manual.

Tip: Bring a second copy of the BOM for robot hardware inspecon.

12. The Engineering Notebook is also a good place to discuss and show team acvies that are

done throughout the teams season. These acvies can be placed in a separate secon of the

Engineering Notebook or chronologically within the design pages.

13. Include your team number inside your engineering notebook and on the cover so it is clear who to

return it to aer the judges have seen it.

3.5 Judges Tips

1. Every notebook is a work in progress, forever changing and developing. Judges do not want to see

a nal copy notebook if yours is handwrien; they want the real thing complete with misspellings

stains, worn edges and wrinkled pages. Just remember to keep it real!

2. When turning notebooks into the judges at your event, place scky tabs at the top of the page on

your top 6-12 best moments as a team. Judges will use these pages as their preliminary review of

your notebook.

3. Customize your Engineering Notebook to reect your teams personality. At the end of the season,

this notebook will be a great piece of memorabilia for your team.

3.6 Notebook Examples

Scanned copies of award-winning Engineering Notebook examples are posted on the FTC website. It is strongly

encouraged for teams to look over these as great examples of what the judges will be looking for when reading

through your Engineering Notebooks.


17/32


4. The Robot

4.1 Overview

A FIRSTTech Challenge Robot is a remotely operated vehicle designed and built by a registered FIRSTTech

Challenge team to perform specic tasks when compeng in the annual game challenge. This secon provides

rules and requirements for the design and construcon of your Robot. Please ensure that you are familiar the

Robot and game rules before beginning Robot design.

4.2 Robot Rules

The intent of the FTC Game Design Commiee (GDC) is to create games that can be played with Robots

constructed with the TETRIX, MATRIX, and/or LEGO robocs system kits using basic tools and equipment.

Anyone that has aended a tournament knows that FTC teams think outside the kit-of-parts to create unique

and creave robots. For the 2012-2013 season the GDC has upped the creave potenal for robot design by

removing many of the legacy restricons for mechanical/structural items. The GDC hopes that veteran FTC

students will enjoy the increased freedom of choice and the resulng simplicaon of hardware inspecon.

4.2.1 General Robot Rules

Only ONE Robot will be allowed to compete per registered FIRSTTech Challenge team. It

is expected that teams will make changes to their Robot throughout the season and at

compeons.

a. It is against the intent of this rule to compete with one Robot while a second is being modied or

assembled at a tournament.

b. It is against the intent of this rule to switch back and forth between mulple Robots at a

tournament.

Every Robot will be required to pass a full inspecon before being cleared to compete. This

inspecon ensures that all FTC Robot rules and regulaons are met. Teams are required to

conduct a self-inspecon of their robot and submit the completed hardware and soware

inspecon forms at tournament check-in or at another designated place. Teams must present a

bill of materials (BOM) lisng any parts used on their robot along with the rule or Q&A post that

allows the part. Lego, Tetrix, and Matrix parts as well as fasteners do not need to be included in

the BOM. It is not necessary to list the quanty of each part in the BOM. A template for a BOM is

available for download from www.usrst.org/c/game.

a. All Robot conguraons must be inspected before being used in compeon.

b. If signicant changes are made to a Robot aer it has passed the inial inspecon, it must be re-

inspected before it will be allowed to compete.

c. Referees or inspectors may request the re-inspecon of a Robot. The Robot is not allowed to

parcipate in a match unl it passes re-inspecon. Refusal to submit to re-inspecon will result in

disqualicaon of the team.

d. Game Manual Part 2: Secon 2.4 contains copies of the robot inspecon forms and provides

addional informaon about the inspecon process.

The following types of mechanisms and components are not allowed:

a. Those that could potenally damage Playing Field components.


18/32


b. Those that could potenally damage or ip other compeng Robots.

c. Those that contain hazardous materials (e.g. mercury switches).

d. Those that pose an unnecessary risk of entanglement.

e. Those that contain sharp edges or corners.

At the beginning of any match, the maximum allowed size of a Robot is 18 x 18 x 18 (45.72cm

x 45.72cm x 45.72cm).

a. During inspecon, the Robot will be placed into a sizing box which has interior dimensions

matching the above size constraints. To pass inspecon, a Robot must t within the box without

exerng force on the sides or top of the box. The sizing box test is described in Secon 8.

b. Robots may expand beyond the starng size constraint aer the start of a match.

c. Any restraints used to maintain starng size (i.e. zip es, rubber bands, string, etc.) MUST remain

aached to the Robot for the duraon of the match.

The Robot main power switch MUST be mounted/posioned to be readily accessible and visible

to compeon personnel.

Baeries MUST be securely aached to the robot.

The NXT controller and Samantha WiFi Communicaon Module MUST be accessible and visible

by compeon personnel.

a. The NXT baery MUST be easily removable with minimal disassembly of the Robot.

b. The USB ports and buons on the NXT and Samantha WiFi Communicaon Module MUST be easily

accessible.

c. The NXT Controller liquid crystal display and Samantha WiFi Communicaon Module LEDs MUST be

readily visible.

d. The NXT Controller and Samantha WiFi Communicaon Module shall be mounted such that theyare protected from contact with the Playing Field elements or other Robots. These and other

electrical components (baeries, motor and servo controllers, switches, etc.) make poor bumpers

and are unlikely to survive the rigors of game play when aached in a Robot-to-Robot contact area.

Robots MUST include a mounng device to securely hold one tournament supplied FTC Robot

Alliance Idencaon Flag throughout an enre match. Because of the need to clearly idenfy

a Robots Alliance, the ag MUST be mounted at the TOP of the Robot and be clearly visible

throughout the match. Flag posts are typically a soda straw with dimensions that are close to

0.250 (0.635cm) OD x 0.200 (0.5cm) ID x 8.250 (20.955cm) length with a triangular ag 4.000

(10.16cm) high x 6.000 (15.24cm) wide. These may vary from event to event. Mounng devicesthat damage the ag post are not acceptable.

Robots MUST prominently display their team number (numerals only, e.g. 1234).

a. The judges, referees, and announcers must be able to easily idenfy Robots by team number.

b. Team number must be visible from at least two sides of the Robot (180 degrees apart).

c. The numerals must each be at least three inches high, at least in 0.5 (1.27cm) stroke width and in a

contrasng color from their background.

d. Team numbers must be robust enough to withstand the rigors of match play.

e. Team numbers and their mounng surface are not required to be made of specically allowed


19/32


materials so long as the materials do not aect the funcon or performance of the Robot. Examples

of recommended number materials include: i) self-adhesive numbers (i.e. mailbox, or vinyl

numbers); ii) ink jet or laser printed numbers on laminated paper or adhesive-backed paper.

Energy used by FIRSTTech Challenge Robots, (i.e., stored at the start of a MATCH), shall come

only from the following sources:

a. Electrical energy derived from the onboard TETRIX or MATRIX baery pack, HiTechnic 9-volt Baery

Box for the sensor mulplexer, the baery for the visible LEDs, and the NXT baery.

b. Compressed air stored in the LEGO pneumac system.

c. A change in the posion of the Robot center of gravity.

d. Storage achieved by deformaon of Robot parts. Teams must be very careful when incorporang

spring-like mechanisms or other items to store energy on their Robot by means of part or material

deformaon. A Robot may be rejected at inspecon if, in the judgment of the inspector, such items

are unsafe.

Game elements launched by Robots should not have a velocity greater than that required

to reach a maximum of four (4) feet (1.2 meters) above the playing eld surface, nor travel a

horizontal distance greater than ten (10) feet (3 meters) from the point that the game element

ends contact with the robot.

4.2.2 ROBOT PARTS AND MATERIALS RULES

Only TETRIX, LEGO, and/or MATRIX preformed robocs components (i.e. gears, wheels, extruded

parts) may be used.

a. The following TETRIX components may not be used: R/C Controller (Product Id W34243 or

W36117), R/C Receiver (Product Id W35496), Infrared Electronic Ball (Product Id W991458),DC Motor Speed Controller (Product Id W34244), Wireless Camera Kit (Product Id W37291),

Autonomous Mounng Deck (W37799), and R/C Mounng Deck (W37663).

In addion to the TETRIX, LEGO, and/or MATRIX components, teams may use addional materials

to construct their robots providing they meet the following constraints:

a. Commercial O The Shelf (COTS) assemblies are not permied with the excepon of the following:

1. Linear Slides.

2. Non-motorized Turntables and Lazy Susans.

3. Lead Screws and threaded rod plus compable nuts.

4. Servo blocks (e.g. ServoCity Part # SB608SH and SB609SH).

5. #25 chain and compable connector links and half-links.

The intent of is to augment the TETRIX, LEGO and MATRIX robot system kits with a few select

assemblies/mechanisms that might be useful for this years game challenge. For the purpose of this

rule, assemblies are considered to be component parts that have been ed together.

b. Prefabricated and/or Preformed COTS plascs or metal are not permied (i.e. buckets, cups,

grippers, gears, etc.).

1. Plasc or metal sheet, plasc spacers, and extruded aluminum are not considered to be


20/32


prefabricated and are allowed with no restricons on dimension or quanty provided no

other rules are violated.

c. LEGO plasc building parts are allowed.

d. The following addional structural parts, fasteners, and materials are allowed provided that they

dont violate other rules, such as safety, entanglement, , etc. This includes no limits on

quanty and size of the following materials:

1. Raw Material (e.g. metal, plasc, etc.) provided that it is readily available to all teams from

standard distributors (e.g. McMaster-Carr, Home Depot, Grainger, etc.). The denion ofRaw Material are items before being processed or manufactured into a funconal form.

2. Standard bearings and bushings.

3. Fasteners (e.g. nuts, bolts, screws, pop rivets, Velcro, etc.).

4. Rope, cord, cable, monolament, etc.

5. Rubber bands.

6. Surgical or Latex Tubing.

7. Non-metallic cable es (also known as Zip Ties).

8. Non-Slip Pad without an adhesive backing (e.g. McMaster Carr Part #69275T54 or Home

Depot SKU #134555). Packaging material must list the product as Non-Slip Pad. Robot electronics are constrained to the following:

a. Exactly one (1) LEGO MINDSTORMS NXT Controller MUST be used. Addional microprocessors

are not permied unless they are an integral part of an allowed part or aached to the HiTechnic

SuperPro Prototype or the NXT Prototype Boards.

b. The NXT controller must be powered either by the NXT rechargeable AC baery (W979798), NXT DC

Baery (W979639), or six (6) AA baeries.

c. Exactly one (1) of the following baery packs: 1) TETRIX rechargeable baery pack; or 2) MATRIX

baery pack. Only one of these baery packs is allowed on the Robot. These baery packs may

only used to power HiTechnic DC Motor Controllers, HiTechnic Servo Controllers, the Samantha WiF

module, and visible light LEDs.

d. Exactly one (1) power switch that turns the robot on or o. The power switch MUST be installed

between the baery and the rst DC Motor or Servo Controller.

e. Any quanty of TETRIX (HiTechnic) or MATRIX Motor and Servo Controllers are permied provided

that the quanty doesnt exceed the technical specicaons for these devices, the NXT, and the

soware.

f. A maximum total of eight (8) MATRIX or TETRIX motors and twelve (12) servos are allowed,

provided that they are compable with and controlled by TETRIX (HiTechnic) or MATRIX controllers

(180 Degree HiTEC HS-475HB or HS-485HB and Connuous Rotaon W39177 & HiTEC HSR-1425CR

in any combinaon).

g. LEGO approved/cered motors may be used with the following constraints (per NXT motor port):

1. One (1) NXT Interacve Servo Motor (LEGO Part # W979842)

2. One (1) XL Power Funcon Motor (LEGO Part # W778882)

3. Two (2) E Power Funcon Motors (LEGO Part # W979670)

4. Two (2) M Power Funcon Motors (LEGO Part # W978883)

5. One (1) E Motor and one (1) M Motor

6. You are allowed to use any number of NXT conversion cables to connect the Power Funcon

Motors with the NXT (LEGO Part #s W770323, W778886, or W778871)


21/32


7. You are NOT allowed to use any of the Power Funcon Baery Packs (LEGO Part #s W778881

or W778878)

h. Exactly one (1) Samantha WiFi Communicaon Module with one USB A-B cable to go from the

Samantha module to the NXT (24/60.96 cm or shorter is recommended) must be used. No other

wireless communicaon is permied during match play.

i. Only LEGO Approved NXT and RCX sensors (as indicated by the LEGO cered hardware label), and

HiTechnic NXT compable sensors are allowed to be directly connected to the NXT, the HiTechnic

Sensor Mulplexor, and the HiTechnic Touch Sensor Mulplexor.j. The HiTechnic NXT Touch Sensor Mulplexer (MUX) and NXT Sensor Mulplexer (MUX) are allowed.

The HiTechnic 9-volt Baery Box that is sold as part of the NXT Sensor Mulplexer set may be used

in conjuncon with each NXT Mulplexer (i.e. one Baery Box per Sensor Mulplexer). It may be

used only in conjuncon with the NXT Sensor Mulplexer(s) to provide power for the MUX.

k. HiTechnic SuperPro Prototype Board, and the NXT Prototype Boards (both solderable and

solderless) are allowed with the following constraints:

1. All power used in the circuits connected to the Prototype Board must be derived from the

power connecons provided within the board. No baeries or external power sources are

allowed.

2. Circuits may connect only to the named connecons provided by the Prototype Board (i.e.A4-A0, B5-B0, 3V, 4V, 9V, 5V, GND).

3. Communicaon to the NXT Controller may only occur through the included NXT connector.

4. Any compable sensor may be connected to the Prototype Board, provided that no other

rules are violated. Sensors may be distributed throughout the Robot; they do not need to be

physically aached to the Prototype Board.

5. Addional circuit boards may be connected to the Prototype Board as needed.

6. The processor included in the Prototype Board may not be reprogrammed.

7. Circuits included as part of the HiTechnic Prototype Board may not cause interference

with any Robot on the playing eld, any part of the eld management system or any game

element.

l. LEGO-Approved NXT extension cables are allowed. Approved cables are currently only available

from LEGO and HiTechnic.

m. LEGO-Approved NXT Conversion Cables to connect RCX sensors or Power Funcon Motors to the

NXT (LEGO Part #s W770323, W778886, or W778871) are allowed.

n. Anderson PowerPole, and similar crimp or quick connect style connectors for joining electrical wires

are allowed. Power spliers may also be used (and are strongly recommended) to make wiring

easier.

o. Non-NXT power, motor control, servo, and encoder wires and their connectors may be extended,

custom made, or COTS subject to the following constraints:

1. Baery wires are 16 AWG or larger

2. Samantha power wires are 18 AWG or larger

3. Motor control wires are 22 AWG or larger

4. PWM wires are 20 AWG or 22 AWG

5. Power and motor control wires are strongly recommended to use consistent color coding

with dierent colors used for the Posive (red, white, brown, or black with a stripe are

recommended) and Negave/Common (black or blue are recommended) wires.

p. Visible light LEDs with their connected electronic circuits are allowed. Power for the LEDs may be


22/32


provided by the main robot baery pack (TETRIX or MATRIX) or by no more than one (1) baery of

any type not to exceed 9 volts.

q. Wire and cable management products of any type are permied (e.g. cable es, cord clips, sleeving

etc.).

r. Wire insulaon materials of any type are permied when used to insulate electrical wires or secure

motor control wires to motors (e.g. electrical tape, heat shrink, etc.).

s. Electrical components that are not specically allowed by the rules (i.e. sensors, baeries,

microprocessors, etc.) are not permied. Motors, sensors, controllers, and any other electricalcomponents may not be altered from their original state in ANY way unless specically allowed by

the Robot rules. Also, the connectors on the TETRIX and MATRIX baery packs may be replaced or

augmented with any compable connector described in n above.

LEGO pneumac elements are allowed. Teams may not modify LEGO pneumac elements to

aempt to change the pressure limits of the elements.

Electrical solder, tape, and any type of glue/cement are allowed.

Any type of COTS lubricant is allowed, provided that it doesnt contaminate the playing eld,

game elements, other Robots, etc.

Robots may contain decoraons provided that that they are non-funconal; do not aect how

the robot interacts with the playing eld, eld elements, or other robots; do not require external

power except as specied in rule p; do not aect the outcome of the match; are not

hazardous to themselves or other teams; and are in the spirit of Gracious Professionalism.

4.2.3 ROBOT SOFTWARE RULES

The Robot must be designed to be controlled by no more than two (2) Logitech Gamepads.

Ocial FTC tournaments will provide either the Logitech DualAcon or Logitech F310 gamepads

in any combinaon for the compeon playing elds.

Each team MUST name their NXT with their ocial FTC Team number (e.g. 1234). Spare

NXTs should be named with the team number followed by a hyphen then a leer designaon

beginning with B (e.g. 1234-B, 1234-C). Should a spare NXT be loaned to another team,

the receiving team should rename the NXT with their corresponding team number along with the

hyphenated leer designaon showing the Field Control System that it is a spare.

Programming for the FIRSTTech Challenge must be done with an approved programminglanguage, using MANDATORY FTC Compeon Templates, and corresponding rmware.

Approved programming languages are:

a. ROBOTC version 3.0 or later (rmware version 9.0 or later)

b. LabVIEW for LEGO MINDSTORMS (NXT Firmware version 1.31 or later)

Templates for all programming choices are available at hp://www.usrst.org/c. If updates are

announced later in the season, teams must update to the latest version prior to me of compeon.

The Samostat program MUST be installed on the NXT. Once installed, the team does not have


23/32


to install Samostat again unless a new version of the Samostat code is released, the programming

environment is updated, or rmware is re-installed on the NXT.

The Program Chooser program MUST be installed on the NXT. The Program Chooser enables

teams to select the program started by the FCS for the Driver-Controlled poron of the match

without having to connect the NXT to a computer. Once installed, the team does not have to

install it again unless rmware is re-installed on the NXT, a new version of the Program Chooser

code is released, or the programming environment is updated.

The NXT MINDSTORMS Controller Sleep Timer must be set to NEVER.

Robots will connect to the tournament supplied Field Control System (FCS) located at each eld.

Teams must demonstrate that their Robot switches between Autonomous mode and Driver-

Controlled mode correctly using the latest version of the FCS. This is done during Soware

Inspecon.

5. Judging & Award Criteria

5.1 Overview

This chapter provides a complete descripon of all of the FTC Awards; the judging process, criteria and

philosophy that teams need to be aware of in preparaon for parcipang at FTC Tournaments.

In addion to winning points during the compeon, the awards represent another posive way for mentors

to insll important values like teamwork, creavity, innovaon, and the value of the engineering design

process. These judging guidelines are a part of the road map to success.

5.2 FTC Award Eligibility

To ensure fairness to all teams and to provide equal opportunity for all teams to win an award at anFTC Championship tournament, teams are only eligible to win an award at the rst three Championship

tournaments that they aend. Those teams who compete in more than three Championship

tournaments do so for the purpose of being involved in the fun and excitement of the tournament and

not with the intenon of winning mulple awards.

Teams are allowed to win the Inspire Award only once during each tournament level (Qualifying and

Championship). Once a team wins the Inspire Award at a Qualifying tournament, they are only eligible to win

the other judged or alliance awards at subsequent Qualifying tournaments. The same restricon applies to

teams aending mulple Championship tournaments.

Teams have spent several weeks designing, building, programming their robot, and learning what it takes to be

a part of a team. For many FTC teams, the event is the reward for all their hard work throughout the season.While there are several types of events, they all oer a fun and excing way for teams to demonstrate the

result of their eorts.

5.3 FTC Award Categories

5.3.1 FTC Inspire Award

This formally judged award is given to the team that truly embodied the challenge of the FTC program

The team that receives this award is chosen by the judges as having best represented a role model FTC

Team. This Team is a top contender for all other judging categories and is a strong competor on the


24/32


eld. The Inspire Award Winner is an inspiraon to other teams, acng with Gracious Professionalism

both on and o the playing eld. This team understands how to communicate their experiences and

knowledge to other teams, sponsors, and the judges.

In past seasons, the winner of the Inspire Award at each Championship event received an automac

invitaon to the FTC World Championship Event. Once a team has won an Inspire Award at a

Championship, they are no longer eligible to win the Inspire Award at addional championship

tournaments they may aend. Similarly, once a team wins an Inspire Award at a Qualifying

tournament, they are no longer eligible to win the Inspire Award at subsequent Qualicaontournaments.

Guidelines for the Inspire Award

Team must demonstrate respect and Gracious Professionalism both for team members and fellow

teams

Engineering Notebook must be submied, and must impress the judges

Team must work beyond their robot to help spread awareness of the team, FIRST, and FTC within

the community

Team displays good communicaon and teamwork skills within the team as well as with their

alliances

Team communicates clearly about their robot design to the judges

Team presents themselves well in the judges interview

Robot eecvely competes in the game challenge and impresses the judges

Team and robot consistently perform well during matches

Team is a strong contender for all other judged awards

5.3.2 Rockwell Collins Innovate Award

The Rockwell Collins Innovate Award celebrates a team that not only thinks outside the box, but alsohas the ingenuity and invenveness to make their designs come to life. This judged award is given to

the team that has the most innovave and creave robot design soluon to any or all specic eld

elements or components in the FTC game. Elements of this award include elegant design, robustness,

and out of the box thinking related to design. This award may address the design of the whole robot,

or of a sub-assembly aached to the robot. The creave component must work consistently, but a

robot does not have to work all the me during matches to be considered for this award. The teams

Engineering Notebook should be marked with journal entries to show the design of the component(s)

and the teams robot in order to be eligible for this award, and entries should describe succinctly how

the team arrived at that soluon.

Guidelines for the Rockwell Collins Innovate Award.

Robot or robot sub-assembly must be elegant and unique in its design

Creave component must work reliably

Team must submit an Engineering Notebook

Robot is stable, robust and controllable

Robot design is ecient and consistent with team plan and strategy


25/32


5.3.3 PTC Design Award

This judged award recognizes design elements of the robot that are both funconal and aesthec.

All successful robots have innovave design aspects; however, the PTC Design Award is presented to

teams that incorporate industrial design elements into their soluon. These design elements could

simplify the robots appearance by giving it a clean look, be decorave in nature, or otherwise express

the creavity of the team. The winning design should not compromise the praccal operaon of the

robots but complement its purpose. This award is sponsored by Parametric Technology Corporaon

(PTC), developers of the CAD tools, Creo and Mathcad. PTC gives licenses to the FTC student teamsfor these soware products to help them with their designs. Use of these tools is not required to be

eligible, however, teams that use them in their design are given extra consideraon for this award.

Guidelines for the PTC Design Award

Team must submit an Engineering Notebook with detailed robot design drawings

Robot dierenates itself from others

Design is both aesthec and funconal

Well considered basis for the design (i.e. inspiraon, funcon, etc.)

5.3.4 Connect Award

This judged award is given to the team that most connected with their local community and the

engineering community. A true FIRSTteam is more than a sum of its parts, and recognizes that

its schools and communies play an essenal part to their success. The recipient of this award is

recognized for helping the community understand FIRST, the FTC, and the team itself. The team that

wins this award is aggressively seeking engineers and exploring the opportunies available in the world

of engineering, science and technology. In addion, this team has a clear fundraising goal and plan to

achieve that goal (if the teams organizaon allows fundraising).

Guidelines for the Connect Award

Team provides clear examples of outreach to community

Team has worked to develop an in-person or a virtual connecon with the engineering, science or

technology community

Team has a business plan or other way of determining their fundraising needs and a plan to achieve

their fundraising goal if allowed to fundraise

Team has a plan to give back to their community

5.3.5 Movate Award

This judged award celebrates the team that exemplies the essence of the FTC compeon through

team spirit and enthusiasm. They show their spirit through costumes and fun ouits, a team cheer or

outstanding spirit. This team has also made a collecve eort to make FIRSTknown throughout their

school and community.

Guidelines for the Movate Award

Team spirit is consistent throughout the team and the compeon.

Team is enthusiasc


26/32


The team funcons well as a unit

Team enthusiasm is evident in community outreach

5.3.6 Think Award

This judged award is given to the team that best reects the journey the team took as they

experienced the engineering design process during the build season. The engineering notebook is the

key reference for judges to help idenfy the most deserving team. The Teams engineering notebookshould focus on the design and build stage of the teams robot. Journal entries of interest to judges

for this award will include those describing the steps, brainstorms, designs, re-designs, successes, and

those interesng moments when things werent going as planned. A team is not be a candidate for

this award if they have not completed the secon of the engineering notebook describing the teams

experience.

Guidelines for the Think Award

Team must submit an engineering notebook

Engineering notebook must demonstrate that the team has a clear understanding of the

engineering design process, with pictures or drawings and details documenng all stages of robotdesign

Engineering notebook must be organized and follow the formang guidelines provided by FIRST

Collaboraon and co-ownership are dominant themes in the engineering notebook or in the judges

interview

Note: Teams should review the engineering notebook secon of this manual for a complete

descripon and format specicaons.

5.3.7 Promote Award (Oponal)This judged award is oponal and may not be given at all tournaments. Please contact your tournament

organizer to determine if it will be given at an event you aend.

The Promote Award is given to the team that is most successful in creang a compelling video message

for the public designed to change our culture and celebrate science, technology, engineering and math.

Guidelines for the Promote Award

Team must present a thoughul and high-quality video which appeals to the general public.

Strong producon value is important, but the message and impact of the video are of greater

weight for the judges. Creavity in interpreng the annually assigned theme is desired.

Submissions for this award will be considered for the Inspire Award but are not required.

Team must have rights to any music used in the video.

Winning videos will be submied to FIRSTand used to promote the higher values of the FTC. Teams

may win the Promote Award only once at a Championship level event and only once at a qualifying

level event.


27/32


Team must submit a one-minute long PSA video one full week prior to the event to be eligible for this

award. Addional submissions are welcome but will not be eligible for awards. The submission process

for this award may vary by tournament. Please check with your tournaments organizer for details.

PSA Subject for 2012-2013 Season

Create a one-minute public service announcement (PSA) video that begins with the following

sentence: What Ill carry with me from FIRST

5.3.8 Compass Award (Oponal)

An FTC Team is about more than building robots, and compeng at tournaments, it is a journey to a

desnaon through trial and error, success and failure, with challenging new technology and obstacles

to navigate where no road maps are provided. How does a team nd their way?

The Compass Award recognizes an adult Coach or Mentor who has provided outstanding guidance

and support for a team throughout the year. The winner of the Compass Award will be determined

from candidates nominated by FTC team members, via a 40-60 second video submission, highlighng

how their Mentor has helped them become a champion team. We want to hear what sets the Mentor

apart.

Guidelines for the Compass Award

Only one video submission per team will be considered. Teams may submit new or updated videos

at each tournament.

The video must be submied at least one week prior to tournament day. Instrucons for

subming videos may vary from tournament to tournament. Please check with your tournaments

organizer for details.

Videos must not be longer than 60 seconds (including introducon and credits if you choose to use

them).

Videos must be submied in AVI, WMV or MOV format. Remember that the winning video may be

shown on a large screen during the awards ceremony. Use the best resoluon you have available for

your nal version.

Video presentaons are condenal, and may not be made public or shared with other teams prior

to the award presentaon.

Team must have rights to any music used on the video.

Team must submit an Engineering Notebook.

5.3.9 Judges Award

During the course of the compeon, the judging panel may encounter a team whose unique eorts,

performance or dynamics merit recognion, yet doesnt t into any of the exisng award categories.

To recognize these unique teams, FIRSToers a customizable judges award. The judging panel may

select a team to be honored, as well as the name of the judges award.

5.3.10 Winning Alliance Award

This award will be given to the winning alliance represented in the nal match.


28/32


5.3.11 Finalist Alliance Award

This award will be given to the nalist alliance represented in the nal match.

5.4 Judging Process, Schedule, and Team Preparaon

The schedules at the FTC tournaments may vary from site to site. Exact mes for both the matches and

meeng with judges cannot be given within this manual. All teams receive this schedule prior to or during

check-in at the compeon.

5.4.1 Judging Process

At FTC Championship Tournaments, there will be three parts to the judging process: 1) interview with judges,

2) evaluaon of performance, and 3) evaluaon of the Engineering Notebook. Each team will have an

interview with a panel of two or three judges. No awards will be determined on the basis of this interview

alone. Judges use the guidelines provided in this chapter to assess each team.

Teams should present their engineering notebooks at the Pit Administraon Table during check-in unlessotherwise directed by the tournament ocials. The engineering notebooks are provided to the judges prior to

the team interviews.

Aer the judges review the submied Engineering Notebooks, complete the inial team interviews and

evaluate the team and robot performance during matches, they convene to review their assessments and

create a list of top candidates for the various judged awards. Judges may require addional impromptu

discussions with teams if necessary. Deliberaons are usually completed during the eliminaon matches.

When the judges have nished their deliberaons, the engineering notebooks are returned to teams.

Teams are asked to bring their robot to the judge interview. This is the best chance for teams to explain and

demonstrate their robot design to the judges in a quiet and relaxed environment.

5.4.2 Judging Schedule

The judging generally takes place in a separate area(s) away from the noise of the compeon and pit. Teams

follow the schedule that outlines team interview mes and locaons. In some cases, teams may receive

this informaon in advance, but more oen, teams will receive this informaon when they check-in on the

morning of the event.

Upon arrival please familiarize yourself with where the judging will occur and allow enough me to get there.

To keep this process on me throughout the event, we require that all teams arrive at the judge queuing area

ve minutes before their scheduled judging interview.

5.4.3 Team Preparaon

Teams are encouraged to use the award guidelines to assess where they are within an award category and

help them establish higher goals. These guidelines are the same ones used by the judges during each FTC

tournament, and at the FTC World Championship.

The judges want to know highlights about the team; its history and make up; what the team achieved during

the compeon season; and the experiences that were gained. Team representaves abilies to answer the

quesons or elaborate on robot design funcons or aributes are evaluated during the team interview. Check

with the event organizer to see if Mentors and Coaches are allowed to observe the team interview. Mentors

may not contribute to the judging process. Mentors should always keep in mind that FTC is a student-centered


29/32


acvity and it is about giving the students a unique and smulang experience in all aspects of the program.

5.5 FTC World Championship Event Eligibility

The culminaon of the FIRSTevent season is the FIRSTChampionship Event held in St. Louis, MO. This event

represents the conclusion of the season for Jr. FIRSTLEGO League (Jr. FLL), FIRSTLEGO League (FLL), the FIRST

Tech Challenge (FTC), and the FIRSTRobocs Compeon (FRC). This is a fun and excing experience for teams

in all programs to parcipate.

FIRSTTech Challenge Teams earn their way to the FTC World Championship with their performance on and

o the eld. Advancement Criteria for the FTC World Championship is outlined in Secon 2.8 and is similar to

advancing from local Qualiers to local Championship tournaments. Teams are responsible for their own entry

fees, lodging, and travel costs to the FTC World Championship.

6. Team Resources

6.1 Overview

This chapter provides teams with necessary informaon for contacng FTC sta, accessing technical support,using the FTC Q&A system, and using the FIRSTand FTC logos.

6.2 FIRSTContact Informaon

Teams can reach the FTC sta by e-mail at [email protected]. The oce is open Monday through Friday

from 9:00 a.m. to 5:00 p.m., EST. Be sure to provide your team number in your message and leave contact

informaon.

6.3 Geng Answers to your Quesons

For general informaon and quesons regarding the FTC, please send an e-mail request to:[email protected].

For specic informaon and quesons regarding the FTC program in your area, please contact your regions

Aliate Partner. Search for your areas Aliate Partner on the FTC web site: www.usrst.org/regionalcontact.

aspx.

For quesons regarding the annual FTC game (released in September), please have your team leader log into

the FIRSTTIMS (Team Informaon Management System) to see your FTC team forum login under the Whats

New informaon once your team has registered and paid. The FTC Forum opens in September.

Note: Accounts are updated weekly by the FIRSTIT Department. If you have trouble accessing the forums,

please feel free to contact FIRSTat the informaon above.

6.4 Rules for Forum Parcipaon

In order to ask ocial game quesons in the FTC Forum, you must register and acvate your account. The FTC

Game Q&A is accessed directly at cforum.usrst.org or by browsing to forums.usrst.org and following the

FIRSTTech Challenge link found under the FIRSTPrograms heading. Please do not use the FRC Game Q&A

for FTC Quesons.

Anyone can read this moderated forum. Only a single team leader is allowed to ask quesons on the forum.

Before posng a queson, please make sure it has not already been answered. Game quesons are not

answered aer 5:00 PM EST on Thursday during the compeon season. Quesons asked aer this me


30/32


are answered aer the events have concluded for that weekend. As the forum is moderated, quesons and

answers will be visible only aer they have been reviewed and answered.

For detailed informaon on the FTC program, robot kit and accessories, playing eld, etc., visit the following

websites:

FTC informaon, game informaon, FAQs, and team resources: www.usrst.org/robocsprograms/c/

FTC Game Q&A: cforum.usrst.org

6.5 Team Development Support

In addion to the sta at FIRSTHeadquarters, an addional regional level of support is available through the

FIRSTTech Challenge Aliate Partners, FIRSTRegional Directors, FIRSTSenior Mentors, and VISTA Volunteers.

The FTC Aliate Partners coordinate all FTC acvies within a state, province, or region, and should be your

foremost resource for help with the program. To nd an Aliate Partner, Regional Director, Senior Mentor, or

VISTA volunteer available in your area, please contact FIRSTat [email protected].

6.6 Using the FIRST and FTC Logos

We encourage Teams to develop and promote team identy. It is a great way to help FIRSTjudges, announcers,

and audiences recognize your team at the compeon, and it is also a way to help Teams create excitement in

their communies.

Teams have incredibly creave opportunies in terms of designing your own identy. There are many examples

of how teams brand their eorts with websites, team logos on robots, T-shirts, hats, banners, iers, and

giveaways.

You can download the FIRSTand FTC logos and Logo Standards informaon from the FTC web site at:

www.usrst.org/robocsprograms/resourcecenter.aspx?id=17122. Keep in mind the following when workingwith the FIRSTand FTC logos:

Posive Promoon: Use the FIRSTand FTC logos in a manner that is posive and promotes FIRST.

Unmodied: Use the FIRSTand FTC logos without modicaon. This means that you will use our name and

the triangle, circle, square as you see it on our website or leerhead. You can use it in red, blue, and

white, or in black and white.

Modicaon Permission: If you have an interest in modifying the FIRSTand FTC logos, you must FIRST

contact FIRST. Please submit a wrien request leng us know why you want to modify the logo,

how you plan to do it, and where you plan to apply it. Send an e-mail request to the FIRSTMarkengDepartment, [email protected].

Adversing Use Approval: All teams and sponsors must obtain approval from FIRSTprior to incorporang

our logo in any adversing. Send an e-mail request for adversing approval to:

[email protected].


31/32


Team Number:

Team Name:

Needs

ImprovementFair Good Excellent

Think Award Engineering Notebook is Required

Notebook is well organized and follows the proper format.

Notebook describes the physical construcon of the robot

Notebook describes team strategy, objecves, and reasoning behind the design.

Content reects the creave design process: idenfying the problem, research, brain-

storming, choosing the best soluon, developing and prototyping.

Rockwell Collins Innovate Award Engineering Notebook is Required

A robust, well-engineered robot that demonstrates the execuon of a planned design that

shows creavity and out of the box thinking.

Robot has a compeve drive system tailored to support the strengths of the teams game

strategy.

Robot has an exceponal manipulator for game objects that performs consistently and

eecvely.

Team has a well-planned str

FTC 2012 2013 GameManual Part1

Documents

Transcript of FTC 2012 2013 GameManual Part1