1. No category

2014-2015 FIRST Tech Challenge
®
Software Inspector Manual
2 | FIRST Tech Challenge Software Inspector Manual
Volunteer Thank You
Thank you for taking the time to volunteer for a FIRST Tech Challenge Event. FIRST and FTC rely
heavily on Volunteers to ensure Events run smoothly and are a fun experience for Teams and their
families, which could not happen without people like you. With over 4,000 Teams competing annually,
your dedication and commitment are paramount to the success of each Event and the FTC program.
Thank you for your time and effort in supporting the mission of FIRST!
Sponsor Thank You
Thank you to our generous sponsors for your continued support of the FIRST Tech Challenge!
Official Program Sponsor
CAD and Collaboration Sponsor
FIRST Tech Challenge Software Inspector Manual
Revision
1
2
Date
8/26/2014
10/16/2014
|3
Revision History
Description
Initial Release
General updates to language, formatting, etc.
Contents
Introduction ............................................................................................................................................ 5
What is the FIRST Tech Challenge? .................................................................................................. 5
FIRST Tech Challenge (FTC) Core Values ........................................................................................ 5
What is the FIRST Tech Challenge Software Inspector Manual? ........................................................... 6
Gracious ProfessionalismTM ................................................................................................................... 7
Gracious Professionalism for Volunteers ............................................................................................ 7
Youth Protection Program ...................................................................................................................... 8
Position Description ............................................................................................................................... 9
Software Inspector and Certification ................................................................................................... 9
Event Time Commitment .................................................................................................................... 9
Software Inspector Safety .................................................................................................................. 9
Volunteer Minimum Age Requirement ................................................................................................ 9
Key Volunteer Role Minimum Age Requirement............................................................................... 10
Organizational Chart ............................................................................................................................ 11
Role Responsibilities ........................................................................................................................... 12
Pre-Tournament Responsibilities ......................................................................................................... 12
Tournament Day Responsibilities ........................................................................................................ 12
Lead Software Inspector Responsibilities............................................................................................. 13
How Inspection Works ......................................................................................................................... 13
Field Inspection Setup ...................................................................................................................... 13
What Teams Must Bring to Software Inspection ............................................................................... 14
Software Inspection Process................................................................................................................ 14
Initiate Inspection ............................................................................................................................. 14
Software and Samantha Configuration checks ................................................................................. 15
Queuing Procedures Script .............................................................................................................. 15
Field Software Inspection Process ....................................................................................................... 17
Introduction ...................................................................................................................................... 17
Pre-Match Setup .............................................................................................................................. 17
The Match ........................................................................................................................................ 17
Post-Match ....................................................................................................................................... 18
Inspection Closeout .......................................................................................................................... 18
4 | FIRST Tech Challenge Software Inspector Manual
Inspection Troubleshooting .................................................................................................................. 20
Repeated Failures ............................................................................................................................ 20
End of the Day ..................................................................................................................................... 20
Appendices .......................................................................................................................................... 21
Appendix A – Software Inspection Checklist ........................................................................................ 22
Appendix B – Field Inspection Checklist .............................................................................................. 23
Appendix C – Samantha WiFi Communications Module ...................................................................... 24
Appendix D – Samantha Module Light Indicator Guide ........................................................................ 25
Appendix E: Inspection Script (for printing) .......................................................................................... 30
Initiate Inspection ............................................................................................................................. 30
Software and Samantha Configuration checks ................................................................................. 30
Queuing Procedures Script .............................................................................................................. 31
Go over the follow notes with Teams during Field Inspection: .......................................................... 32
Introduction ................................................................................................................................... 32
Pre-Match Setup ........................................................................................................................... 32
The Match..................................................................................................................................... 32
Appendix F: Resources........................................................................................................................ 33
Software Inspector Training video .................................................................................................... 33
Software Inspector Certification Test ................................................................................................ 33
Game Forum Q&A - http://ftcforum.usfirst.org/forum.php ................................................................. 33
FTC Game Manuals – Part 1 and 2 - http://www.usfirst.org/roboticsprograms/ftc/Game .................. 33
FIRST Headquarters Support ........................................................................................................... 33
USFIRST.ORG................................................................................................................................. 33
FIRST Tech Challenge Social Media ................................................................................................ 33
FIRST Tech Challenge Software Inspector Manual
|5
Introduction
What is the FIRST Tech Challenge?
®
FIRST Tech Challenge is a student-centered activity that focuses on giving students a unique and
stimulating experience. Each year, Teams participate in a new Game that requires them to design,
build, test, and program Autonomous and Driver-Operated Robots that must perform a series of tasks.
The Playing Field for the Game consists of the FIRST
Tech Challenge Game Pieces set up on a foam-mat
surface, surrounded by a metal and Lexan Field frame.
Each Tournament features Alliances, which are
comprised of two Teams, competing against one
another on the Playing Field. Teams work to overcome
obstacles and meet challenges, while learning from
and interacting with their peers and adult Mentors.
Students develop a greater appreciation of science and
technology and how they might use that knowledge to
impact the world around them in a positive manner.
They also cultivate life skills such as:




Details about setting up a
Playing Field can be found on the
FTC website after the yearly
Game challenge Kickoff.
Planning, brainstorming, and creative problem-solving.
Research and technical skills.
Collaboration and Teamwork.
Appreciation of differences and respect for the ideas and contributions of others.
To learn more about FTC and other FIRST Robotics Competitions, visit www.usfirst.org.
FIRST Tech Challenge (FTC) Core Values
Volunteers are integral to the FIRST community. The FIRST Tech Challenge relies on Volunteers
to run the program at many levels, from managing a region to Mentoring an individual Team. FTC
Affiliate Partners coordinate the program in each region or state. These FTC Partners fundraise,
run Tournaments, hold workshops and demonstrations, market FTC locally, handle public relations,
and recruit Volunteers and Teams. They are a tremendous resource for Mentors and FTC would
not exist without them.
FIRST asks everyone who participates in FTC to uphold the following values:











We act with integrity.
We are a Team.
We do the work to get the job done with guidance from our Coaches and Mentors.
We respect each other in the best spirit of Teamwork.
We honor the spirit of friendly Competition.
What we learn is more important than what we win.
We behave with courtesy and compassion for others at all times.
We share our experiences with others.
We display Gracious Professionalism in everything we do.
We have fun.
We encourage others to adopt these values.
6 | FIRST Tech Challenge Software Inspector Manual
What is the FIRST Tech Challenge Software Inspector Manual?
The purpose of the FIRST Tech Challenge Software
Inspector Manual is to:



Provide new Software Inspectors with a
foundation of knowledge to fulfill the role at
Events.
Familiarize new Software Inspectors with the
FIRST experience.
Help returning Software Inspectors refresh their
skills for the upcoming season.
The guide focuses on the skills and concepts needed for
the development of the following general goals:


Making Software Inspection a smooth process for
Volunteers and Teams.
Provide Software Inspectors with tips, tricks, and
techniques to make them feel confident and
capable in completing the expected role
responsibilities.
This guide would not be possible without the contributions of time, ideas, and resources provided
by the following Volunteers:


Content provided by Mike Nicolai.
2014 revision and editing work by Dan Edwards.
FIRST Tech Challenge Software Inspector Manual
|7
Gracious ProfessionalismTM
FIRST uses this term to describe the program’s intent. This is one of the most important concepts
that can be taught to a young person who is learning to get along in the work world. At FIRST, Team
members help other Team members, but they also help other Teams.
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.
Gracious Professionals make a valued
contribution in a manner pleasing to others and to
themselves.
An example of Gracious
Professionalism is patiently
listening to a Team’s question
and providing support despite
having several pressing
things to do on the day of the
Event.
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.
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.
Watch Dr. Woodie Flowers explain Gracious Professionalism in this short video.
“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, National Advisor for FIRST
Gracious Professionalism for Volunteers
It is a good idea to spend time going over this concept with Volunteers. Provide the Volunteers with
real-life examples of Gracious Professionalism in practice before, during, and after the Event and
recognize great Gracious Professionalism when you see it in action!
8 | FIRST Tech Challenge Software Inspector Manual
Youth Protection Program
FIRST requires all youth Team members to register in support
of our enhanced Youth Protection Program.
FIRST understands that an important component of protecting
children is knowing who the children are on our Teams. In
addition, having parent/guardian contact information increases
our ability to communicate important information, and also
provides us with a better understanding of who our programs
serve.
Coaches and Mentors are expected to read the Youth
Protection Program Guide, available here:
http://www.usfirst.org/aboutus/youth-protection-program
Forms are available here: http://www.usfirst.org/aboutus/youthprotection-program
Information on the US Screening process is available here:
http://www.usfirst.org/sites/default/files/uploadedFiles/About_Us/US-Youth-Protection-ClearanceProcess.pdf
All adults working closely
with the Team must be
registered and screened.
Information on the Canadian Screening process is available
here:
http://www.usfirst.org/sites/default/files/uploadedFiles/About_U
s/Canadian-Youth-Protection-Clearance.pdf
You can find FAQ and additional information about the FIRST
Youth Protection Program on the FIRST website at:
http://www.usfirst.org/aboutus/youth-protection-program
FIRST Tech Challenge Software Inspector Manual
|9
Position Description
The Software Inspectors and Hardware Inspectors work together to ensure Robots follow the guidelines
outlined in FIRST Tech Challenge Game Manual Part I and are ready to compete on the Field. All
Robots are required to pass a Software Inspection prior to competing at an Event. It is critical to ensure
that a Team has the appropriate software installed on their Robot to be able to connect to the Field
Control System, and that it behaves properly at the beginning and end of the Autonomous and DriverControlled periods. The Inspection process involves filling out a checklist for every Robot and placing a
label or other unique tag on the Robot after passing Inspection.
For the sake of Event consistency, Inspection rules must be enforced at every Official FTC Event.
Allowing a violation to pass at “just one Event” is not fair to the Teams that have taken the time and
trouble to make sure their Robot does pass Inspection.
FIRST Tech Challenge Tournaments squeeze a lot of activity into one day. One of the keys to running a
smooth and successful Event is for Teams and Volunteers to show up prepared. Teams spend
countless hours preparing for Competition day and we ask our Volunteers to prepare for Tournament
day as well.
Software Inspector and Certification
FIRST Tech Challenge requires Software Inspectors to be trained prior to Volunteering in the role.
Training, including review of the current year’s manual, supplemental manual review (ie: Game Manual
Part I), training video, and the Software Inspection certification test will take approximately two to three
hours.
Event Time Commitment
Most FIRST Tech Challenge Events are whole-day Events. While Software Inspection happens at the
start of the Event, many Software Inspectors fill other Volunteer roles at an Event, such as Field
Technical Assistant.
Software Inspector Safety
Dress for this role includes safety glasses or side shields on shatterproof prescription eyeglasses worn
at all times on and around the Competition Playing Fields and in the Pit areas. In addition, wear
comfortable clothing that will allow you to move easily and closed-toed shoes that will provide all-dayon-your-feet comfort and will not harm the foam Playing Field floor covering.
Volunteer Minimum Age Requirement
FIRST requires that FIRST Event Volunteers are at least 13 years old, however the Regional Planning
Committee has the option of increasing the age requirement as desired. Adult Volunteers may not have
children accompany them while Volunteering or be responsible for supervising their own children at the
Event. Children under the minimum age are welcome at FIRST Competitions with appropriate
supervision by someone other than a Volunteer.
10 | FIRST Tech Challenge Software Inspector Manual
Key Volunteer Role Minimum Age Requirement
Volunteers MUST be at least 18 years of age before being assigned to a Key Volunteer Role. Key
Volunteer positions include: Volunteer Coordinator, Head Referee, Judge Advisor, Field Manager, Field
Technical Advisor, Lead Hardware Inspector, Lead Software Inspector, and Lead Scorekeeper. When a
Volunteer who is applying for a Key Role is also a recent FIRST participant (participated in a FIRST
program within the last 4 years), this Volunteer falls under the category of an inexperienced Volunteer,
and should be assigned with an experienced Volunteer in the
Role in which the inexperienced Volunteer would like to serve.
Recognize that while we strongly encourage Alumni to
volunteer, it is important to talk through with this inexperienced
Volunteer that they need to be careful in personalizing their
experience and comparing the Teams and situations at this
specific Event to what they remember about their own
experiences.
FIRST Tech Challenge Software Inspector Manual
| 11
Organizational Chart
The Software Inspector reports to the Lead Software Inspector. Refer to the Organizational Chart below
for the relationship between roles and Volunteer reporting at Tournaments.
12 | FIRST Tech Challenge Software Inspector Manual
Role Responsibilities
It is the responsibility of the Software Inspector to:









Ensure that each Team’s Robot is configured with the correct settings and software/firmware
versions.
Verify that each Robot interacts with the Field Control System as expected.
Familiarize each Team with their pre-Match and post-Match responsibilities.
Familiarize each Team with the Match process by leading them through a ‘dry run’ Match.
Assess the Teams’ work and points out anything that is not in compliance with the rules.
Help Teams to be successful.
Facilitate information sharing among Teams.
Be fair and applies the same level of thoroughness for every Team.
Be a Gracious Professional.
Pre-Tournament Responsibilities
Software Inspectors are required to participate in training prior to the Event. This training is provided by
FIRST Headquarters. You will also be required to take a certification test prior to the Event, which is
also provided by FIRST Headquarters.
Required reading before training/certification



The Software Inspector Manual.
Section 5.2.3 of the Game Manual Part 1.
The Inspection Checklist.
It is important prior to the Event that the Software Inspector reviews these Manuals, and watches the
pre-recorded Software Inspector Training video. Upon registering, you will receive instructions on how to
complete your training and participate in the FIRST Tech Challenge Volunteer Forum.
Tournament Day Responsibilities
Once you arrive at the Event you will be tasked with setting up
the Inspection station. In your Inspection station you should
have:








Inspection Checklists.
Inspection Manual.
Section 5.2.3 of the Game Manual Part 1.
Team List.
Inspection stickers or other method of identifying
Robots that have passed Inspection that can be placed
on the Robot.
Flash drives with Event-specific network settings
provided by the Field Technical Advisor (FTA).
Chairs.
Safety Glasses.
FIRST Tech Challenge Software Inspector Manual
| 13
Lead Software Inspector Responsibilities
In addition, the Lead Software Inspector is responsible for:



Coordinating closely with the FTA and Tournament Director to understand any instructions
specific to this particular Event.
Coordinating, training, and if necessary, recruiting other Software Inspectors.
Keeping track of which Teams have passed Software Inspection, and coordinating with Pit
Admin, Queuing, and the FTA to ensure that all Teams are inspected in a timely manner.
How Inspection Works
Software Inspection consists of two parts:


Software Inspection Checklist and configuration of network settings onto the Samantha Module
Field Inspection
Inspectors verify software versions, establish Robot connectivity to the Field Control System, and
describe Team pre-Match and Queuing responsibilities. Inspection usually takes place at the queuing
tables near the Playing or Practice Fields, although the Playing Field is recommended. The Software
Inspection process begins in the Software Inspection Queuing area.
Once Teams arrive for Inspection with the required equipment and Team members, they will be
directed to one of the tables (optionally with a second Team) where one Inspector will conduct the first
part of the Software Inspection.
Once the Queuing Area Inspection is complete, Teams will be led (up to 4 at a time) to one of the
Playing Fields where the second part of the Software Inspection will take place. This Field Inspection is
a walk-through of the process used to conduct a Match. Each Team must demonstrate their ability to
control their Robot during a Match and to verify that it behaves as expected. In order to keep the
Inspection process moving, it is suggested that at least two Inspectors work each Field, with each
Inspector working with two Teams (one Alliance) at a time.
The information contained in the following pages defines the Software Inspection processes and the
Software Inspector’s actions. It is meant to help each Software Inspector become familiar with their role
and the actions they must perform. In addition to this information, an Inspection Checklist is used to
track Inspection results.
Timing of the Inspections is critical, as all Teams must pass Inspection before the Match list can be
generated. Please work to keep the Teams moving through the process in an efficient and orderly way.
Field Inspection Setup
Some Events will hold Software Inspection in the Pits and on a practice Field; others will hold Software
Inspection on the Playing Field. It is recommended that the Software Inspector be familiar with the Field
Electronics Setup Guide. Check to see that all areas are ready to go prior to Team Registration and
check-in as Inspection starts right away.
Software Inspectors will also need to work closely with the Field Control System (FCS) Operator and
the FTA to ensure that the Field and Field Control System (FCS) are properly set up and facilitate the
Match run-throughs. Ideally, coordinate with the FCS Operator to make sure that they will be present to
run the FCS during Field Inspections.
14 | FIRST Tech Challenge Software Inspector Manual
What Teams Must Bring to Software Inspection
Teams may perform either Hardware or Software Inspection first.
There is no required order, but Teams must pass both
Inspections in order to compete. The exception to this is if there
are any obvious safety issues or Robot problems that could
damage the Field. Any such issues must be remedied before
Teams are allowed onto the Field.
Teams do not need to
bring a laptop or a game
Controller to Inspection.
Before starting Software Inspection, Teams must have the following:




Team members (minimum of 2, maximum of 5):
o Coach (required).
o Driver 1 (required).
o Driver 2 (required unless single Driver).
o Alternate 1 (Inspection only and optional).
o Alternate 2 (Inspection only and optional).
Hardware
o Robot with NXT.
o Charged NXT battery pack.
o Charged TETRIX or MATRIX battery pack.
o Samantha unit securely mounted on the Robot.
o Charged 9V battery if using MATRIX.
Software Inspection Checklist (typically distributed to Teams during check-in). Teams should
ideally have already pre-Inspected their Robot and completed the Team self-check column of
the Inspection Checklist.
Safety Glasses.
Software Inspection Process
Initiate Inspection




Start a Software Inspection
Checklist for the Team (fill in
Team number, time, date, etc.)
Explain to Teams that Software
Inspection is a combination of
checking the software on their
Robot as well as a dry run of
the Queuing and Match
process.
Identify the following Team
members:
o Coach.
o Driver 1.
o Driver 2.
o Up to 2 alternates.
Explain to the Team that your
focus during the Inspection is
on communicating with the
Drivers rather than the Coach.
It is still important that the Coach listens to serve as a resource to the Drivers during the day.
FIRST Tech Challenge Software Inspector Manual


| 15
Safety Glasses are required for both Teams and Inspectors during Software Inspections. Use
caution and be aware that Robots may move unexpectedly during Inspection. Check that all
Team members are properly wearing Safety Glasses.
Identify each of the following pieces of equipment:
o Robot with NXT.
o Charged NXT battery pack.
o Charged TETRIX battery pack.
o Samantha wireless module (attached to 9V for MATRIX).
Software and Samantha Configuration checks




Have Teams power on NXT Controllers. TETRIX battery should remain off.
Verify that Teams have the correct settings on their NXT.
o Verify the NXT Controller is named for the 4 digit Team number. If the Team has more
than one NXT, the Team number may have a hyphen and a letter appended to it (6
characters total).
o Verify the NXT Firmware version. On the NXT Controller, from the main menu, go to
Settings > Firmware > View Firmware Version (ROBOTC = 3.62+, LabVIEW/NXTG=2012 SP1+).
o Ask the Team to show you that the Samostat program is loaded on the NXT.
o Ask the Team to show you that the Program Chooser program is loaded on the NXT.
o Verify sleep settings. On the NXT Controller, from the main menu go to Settings > Sleep.
Sleep timer should be set to NEVER. If you change this value, remind Teams they must
now power off their NXT manually to avoid accidentally draining the battery.
Flash the network configuration on the Samantha.
o Ensure that the Samantha is powered off.
o Disconnect the USB cable from the Samantha Samantha.
o Insert the flash drive into Samantha. This flash drive should be provided to you by the
FTA. It contains a file that will identify the correct network information (WiFi, etc.) for that
Event for each Team’s Samantha Module to ensure proper connection.
o Holding the red button on the Samantha, turn the power on and let go when the LEDs
light up.
o CRITICAL STEP: Watch for the lights on the Samantha to flash
red>>white>>blue>>white>>red twice (about 20-30-seconds) until the red (power) button
is solid, the white (WiFi) LED is blinking slowly and the blue (NXT) LED is off. Note that
the lights must cycle twice for the flash process to be successful.
o Turn the power off.
o Remove the flash drive, insert the USB cable from the NXT back into the Samantha, and
turn the power on for both the NXT and the Samantha. The blue LED will illuminate but
may pulse slightly. This “heartbeat” is an indicator that the NXT is communicating
properly with the Samantha.
It is recommended that the Samostat program is executed on the NXT to ensure the correct
Samantha firmware is loaded.
Queuing Procedures Script
The following is a description of what Teams should do prior to the Match. Review these points with
the Team to familiarize them with the Queuing Area and Playing Fields. Optionally, a dedicated
announcer may cover these points with Teams while they wait for their turn on the Field.

Preparing for a Match in the Pit area, Teams should:
o Verify that their Robot is mechanically ready to go.
16 | FIRST Tech Challenge Software Inspector Manual
o



Make any required software changes. No software changes will be permitted in the
Queuing Area.
o Make any required battery changes. No battery changes will be permitted in the Queuing
Area.
o Charge their NXT, and TETRIX/MATRIX/9V battery packs.
o Larger Events: Remind Teams that they will have approximately 30-45 minutes between
Matches to do code and battery changes. However, this does include Queuing and
commute time to and from the Pit area.
While waiting to be called:
o Match times are only estimates.
o We will proceed through the Matches as quickly as possible (we will not wait for the
scheduled start time).
o Teams should monitor Match progress on the Playing Fields by checking the Match
status display board in the Pit area.
o Volunteers will instruct Teams when to leave the Pit area for their Qualification Matches.
This will be approximately 20 minutes prior to the Match.
o If the Robot cannot make the Match, at least one member of the Drive Team must be
sent to the Fields to inform the Field Staff.
When called for a Match:
o Teams must bring only the following Team members:
 Coach (student or adult).
 Driver 1.
 Driver 2 (optional).
o Teams should gather the following equipment:
 Robot with NXT.
 Robot TETRIX/MATRIX and NXT battery packs.
 Samantha Module securely installed on the Robot.
o Drive Team MUST be properly wearing safety glasses.
At the Field:
o Report to the Lead Queuer in the Competition Queuing area.
o Install the provided Alliance Flag.
o Proceed to the Playing Field when directed to do so and quickly place your Robot onto
the Field.
o Immediately power up the NXT and TETRIX/MATRIX to turn on the Robot.
o Start the Autonomous program. A properly programmed Robot will now go into a “Wait
for Start” loop until it is enabled by the FCS.
o Stand in the assigned Driver position. The Queuer will inform each Team which Alliance
and Driver station position they will use for the Match. This information is also listed in
the Qualification Match list, and displayed on the Field monitors. It is critical that Teams
stand in the correct Alliance station position so that they will use the Controllers that
have been assigned to their Robot. Please emphasize this. It is ultimately the Team’s
responsibility to verify that they take their assigned position.
When all of the above steps have been completed, sign the Queuing Area Inspection form and direct
the Teams to the Playing Field where they will continue the rest of the Software Inspection.
FIRST Tech Challenge Software Inspector Manual
| 17
Field Software Inspection Process
At Field Inspection, go over the follow notes with Teams during Field Inspection:
Introduction


If doing Inspection on the Playing Fields,
operate both Fields at once if possible. If
you are able to have more than one
Inspector at a Field, both Inspectors for a
given Field should operate simultaneously.
Welcome Teams and escort them to the
Field.
Pre-Match Setup


Instruct Teams to place Robots onto the
Field:
o During the Qualification Matches,
Blue Alliance Robots are placed on
the Fields first.
o Red Alliance has the option of
waiting to place their Robot until
after the Blue Alliance has done so.
o If a Blue Alliance Robot is delayed,
the Red Alliance should not wait for the Blue Alliance Robot(s). They should go ahead
and place their Robots on the Playing Field and immediately power them on. The Red
Alliance may adjust the setup of their Robots after the last Blue Alliance Robot is placed
on the Playing Field.
o During the elimination Matches, the lower seeded (i.e. 3rd seed is lower than 2nd seed)
Alliance Robots will set up on the Playing Field first unless the higher seeded Alliance
waives their right to set up on the Playing Field Second.
Perform the following Robot checks (at a minimum) every time your Robot is placed on the
Playing Field:
o Power on the NXT and turn on the switch for the external battery.
o Select and execute the Autonomous program on the NXT.
o Return to your assigned Driver station, verify that you have the correct Controller for
your station, and then set your Controller back down.
The Match
Inspectors should convey the following to each Team:






The Match will consist of a 30-second Autonomous Period, followed by a two-minute DriverControlled period.
Teams should alert the FTA if they are having problems, and request FTA assistance.
Drivers should not touch their Controllers during the Autonomous period.
Pay attention to instructions from the Referees, FTA, and Game Announcer. Delays in
responding to their instructions will contribute to schedule delays.
When the FCS Operator is ready, instruct the Teams to signify that they are ready by giving a
“thumbs up”.
The Referee or Game Announcer will start the Autonomous portions of the Match with a
countdown: “3-2-1-GO!” The FCS Operator will click on the FCS “Start Match” button on “GO!”
18 | FIRST Tech Challenge Software Inspector Manual




Drivers should pick up their Logitech Controllers directly after the Autonomous period. Don’t wait
to be told to pick up the Controllers.
Pay attention to the Referees and Game Announcer so that the Driver-Controlled portion of the
Match can begin without delay.
Ask the Teams to attempt to drive their Robot. The Robots should not move at this point,
because the Driver Controlled period has not yet
started.
There will be a second round of “thumbs up” followed
It is critical that each Driver
by a second “3-2-1-GO!” to start the Driver-Controlled
picks up the proper Controller as
period. The FCS Operator will again press the
each has been assigned. Teams
continue button.
are responsible for checking to
Robot motion after the Driver-Controlled period ends
make sure that they have the
is not normal behavior and will cause the Team to
correct Controller and that the
FAIL Software Inspection. After the two-minute
Controllers have not been
swapped.
Driver-Controlled period, instruct Teams to attempt to
drive their Robot. Look for any Robots that continue
to operate beyond the end of the period.
Software Inspection Important Notes:




At the end of both the Autonomous and Driver-Controlled Period, look for any Robots that
continue to operate. Robot motion after the Autonomous period ends is not normal behavior and
will cause the Team to FAIL Software Inspection.
Robots that do not stop operating at the end of either the Autonomous or Driver-Controlled
period may not have the required Software template.
In the Event that you do not have enough time to run a full-length practice, please shorten the
total time to a uniform length of greater than 50 seconds. Whenever possible though, it is
preferred to give Teams the full two-minutes to test their Robots.
Do not hold up the Inspection process unduly for any one Team that is having technical issues.
Have a floater help with Robot troubleshooting if possible, or instruct Teams to go to Pit Admin
to ask another experienced Team for assistance.
Post-Match





Coaches and one Driver are requested to exit the Field area immediately following the Match.
This is to help reduce congestion around the Field during Reset.
Teams are not allowed to touch any Robot or Field Element after the Match ends until instructed
to do so by the Referees.
Remove all Game Elements from the Robot and leave them on the Field.
Return the Alliance Flag to the Queuing area.
Teams should alert the FTA if they had problems, and talk briefly with the FTA about what
happened and how to fix the problem.
Inspection Closeout



Congratulate Teams that were able to properly control their Robots during the Practice Match
and complete the Software Inspection.
Explain to Teams why they didn’t pass the Software Inspection.
Remind Teams that if a Team makes significant changes to their Robot or their programming
during the day, they must undergo another Inspection.
FIRST Tech Challenge Software Inspector Manual





| 19
Remind Teams to turn off any routers they may have, and to not attempt any ad hoc
connections with their Robots during the Event. Bluetooth is also not allowed during the Event,
and should be disabled on the NXT.
Have the Teams clear and Reset the Fields for the next group.
Complete the Inspections sheets as required. If the Team did not pass, note the reason on the
Inspection Sheet so that this can be addressed during re-Inspection, and give the Inspection
sheet back to the Team.
Instruct the Teams to return the completed (passed) Inspection Sheets to Pit Admin for
collection.
For Teams that passed, apply the Inspection sticker to their Robot, and notify the Lead Software
Inspector that the Team has passed Inspection.
20 | FIRST Tech Challenge Software Inspector Manual
Inspection Troubleshooting
Repeated Failures
If a Team repeatedly fails Inspection (Software or Hardware)
identify the Team to the Tournament Director and request that
they find someone to work directly with the Team. Our goal is for
every Team to be successful, so please make every effort to
assist the Team.
In the Event that a Team is unable to pass Inspection by the time
Inspection is over, even with assistance, the Affiliate Partner or
Tournament Director must decide how to proceed.
End of the Day
At the end of the day, walk away from the Tournament knowing
you have done your absolute best to help Teams have a fun
experience and that the Competition was fair for all Teams. This is
the ultimate goal of Volunteering at a FIRST Tech Challenge vent.
As long as the winner of the Tournament can say that they’ve won
fair and square, your job is done!
FIRST Tech Challenge Software Inspector Manual
2014-2015 FIRST Tech Challenge
®
Software Inspector Manual
Appendices
| 21
22 | FIRST Tech Challenge Software Inspector Manual
Appendix A – Software Inspection Checklist
Queuing Area Checklist
Team Number:
________________
Overall Status (circle): PASS / FAIL
Team Inspector Drive Team Members Present
NA
Coach
NA
Driver 1
NA
Driver 2 (optional)
NXT Configuration
NXT named with Team number (optional hyphenated letter appended)
NXT Firmware Version (circle one)
LabVIEW – 2012 spi or newer
NA
NA
ROBOTC – 3.62 or newer
Samostat program is loaded on the NXT
Program Chooser program is loaded on the NXT
NXT sleep timer is set to NEVER
Samantha Module has the latest firmware and network connection settings
flashed to it (see instructions below)
Queuing Process
Team understands that no software changes are allowed in Queue Area
Team understands that the Match Schedule is only an estimate. Matches
may start prior to or after the scheduled time and it is the Team’s
responsibility to monitor schedule changes and show up when required
Team knows where to receive Alliance Flags and where to return them after
the Match
RS2
RS3
RS4
RS5
RS6
I certify that the Robot is in the proper Software Configuration
Queuing Area Inspection Completed by: ____________________________
How to Flash Samantha Unit for Competition at Software Inspection
1. Obtain the flash drive created by the FTA/FCS Operator with the Samantha.hex file and
network key folders loaded.
2. Turn off the main Robot battery.
3. Remove the NXT USB cable from Samantha and insert the flash drive into the USB port
on the Samantha.
4. Hold down the red button on the Samantha, then power on the Robot battery. Release
the red button when the LEDs on the Samantha light up.
5. The Samantha LEDs will complete TWO cycles of: Red-White-Blue-White-Red.
6. After two full cycles are complete (approximately 40 seconds), power off the Robot,
remove the flash drive from the Samantha and re-connect the NXT USB cable.
Important: Ensure two full LED light cycles complete before removing the flash drive
from the Module.
FIRST Tech Challenge Software Inspector Manual
| 23
Appendix B – Field Inspection Checklist
Field Inspection Checklist
Team Number:
________________
Team Inspector Field Setup
NA
NA
Connection with Tournament-supplied FCS is successful
Robot Setup procedure on the Field is understood by the Team and
is successful
Robot Functionality
(Optional) Robot successfully ran an Autonomous program
Robot did not move prior to the start of the Autonomous period
except for servo initialization
Robot did not move between the Autonomous and Driver-Controlled
period
Robot’s Driver-Controlled mode started when commanded to do so
by the FCS
Robot stopped at the end of the Driver-Controlled period
Match Process
Team understands how to call for FTA assistance during a Match
Team understands they cannot touch any Robot or Field Element
after the Match ends until instructed to do so by the Referees
Teams understand they are to clear the Alliance Station as soon as
the Match ends with one Team member remaining to collect their
Robot
Rule
#
RS7
RS8
RS8
General Comments or Reason(s) for Failure (if any):
I hereby certify that this Team has demonstrated their understanding of the Match process, their ability
to properly control their Robot, and that their Robot operates as required during a Match.
______________________________
Software Field Inspector
______________________________
Team Student Representative
24 | FIRST Tech Challenge Software Inspector Manual
Appendix C – Samantha WiFi Communications Module
Teams may use either the 2010 or 2011 versions of the Samantha WiFi Communications Module. The
two versions are operationally identical. The only differences between the two versions are packaging
changes and upgraded status LEDs. The electronics, firmware, and network keys for both styles are
identical. Use the same USB flash drive to configure both types of Samantha units at Tournaments.
2010 – Samantha Unit
2011 – Samantha Unit
FIRST Tech Challenge Software Inspector Manual
| 25
Appendix D – Samantha Module Light Indicator Guide
The images in the left column of the table below display the sequence of lights you would see for the
actions listed in the right column. In real time, the LEDs would be flashing in the left to right sequence
they are pictured in, which is written out in code in the right column.
When the Samantha Module codes have been updated to include Brick Freeze, new images of that
sequence will be posted and a revised manual published.
Power On Reset
Performed when power is
applied to the Samantha
Module
LED Code Sequence
Red
One Blink
Red
One Blink
White
One Blink
Blue
One Blink
White
One Blink
Red
One Blink
Power On
If all is well, Red LED will
remain on after the Power
On Reset sequence
LED Code Sequence
Red
Solid
26 | FIRST Tech Challenge Software Inspector Manual
Network Found
The White LED will blink if
there is a Network Found
that Matches one in Network
Configurations on the
Samantha.
LED Code Sequence
Red
Solid
White
Blinking
Blue
Solid or Off (if
off, NXT Not
Ready)
NXT Ready
The Blue LED will remain on
when the NXT is powered
on.
LED Code Sequence
Red
Solid
White
Blinking
Blue
Solid
FIRST Tech Challenge Software Inspector Manual
Password
1st time Samantha is connected
to FCS w/ password. The RED
button MUST be pressed to
accept the password.
LED Code Sequence
Red
Solid
White
Solid
Blue
Solid
Red
Off
White
Off
Blue
Off
Heartbeat
After the password is
accepted, the Blue LED will
pulse, indicating data flow.
LED Code Sequence
Red
Solid
White
Solid
Blue
Pulse or
Flicker
NXT Not Ready
The NXT is not found, either
unplugged or not powered
on.
LED Code Sequence
Red
Solid
White
Blinking
Blue
Off
| 27
28 | FIRST Tech Challenge Software Inspector Manual
No Network Found
The NXT is found, but no
network has been found.
Reconfigure Network on
Samantha with the USB.
LED Code Sequence
Red
Solid
White
Off
Blue
Solid
Low Battery 1
The network is found, but the
Samantha battery level <10
Vdc.
LED Code Sequence
Red
Blinking
(Alternating
Pattern - R-WR-W-R-W)
White
Blinking
(Alternating
Pattern - R-WR-W-R-W)
Low Battery 2
The network and NXT are
found, but the Samantha
battery level <10Vdc. If
connected to the FCS, only
the Red LED will blink.
LED Code Sequence
Red
Blinking
White
Blinking or
Solid (if
connected to
FCS)
Solid
Blue
FIRST Tech Challenge Software Inspector Manual
NXT Fault
The NXT has either been
disconnected, lost power, or
is powering down.
LED Code Sequence
Red
Solid
White
Blinking
(Alternating
Pattern - W-BW-B-W-B-etc.)
Blinking
(Alternating
Pattern - W-BW-B-W-B-etc.)
Blue
This Appendix document is also available on the FTC FIRST website, called the Samantha Module
Light Indicator Guide, as well as instructions for downloading the content to have available offline at
Matches for reference. https://sites.google.com/site/ftcsamoledcodes/
| 29
30 | FIRST Tech Challenge Software Inspector Manual
Appendix E: Inspection Script (for printing)
Initiate Inspection






Start a Software Inspection Checklist for the Team (fill in Team number, time, date, etc.)
Explain to Teams that Software Inspection is a combination of checking the software on their
Robot as well as a dry run of the Queuing and Match process.
Identify the following Team members:
o Coach.
o Driver 1.
o Driver 2.
o Up to 2 alternates.
Explain to the Team that your focus during the Inspection is on communicating with the Drivers
rather than the Coach. It is still important that the Coach listens to serve as a resource to the
Drivers during the day.
Check that all Team members are properly wearing Safety Glasses.
Identify each of the following pieces of equipment:
o Robot with NXT.
o Charged NXT battery pack.
o Charged TETRIX battery pack.
o Samantha wireless module (attached to 9V for MATRIX).
Software and Samantha Configuration checks



Have Teams power on NXT Controllers. TETRIX battery should remain off.
Verify that Teams have the correct settings on their NXT.
o Verify the NXT Controller is named for the 4 digit Team number. If the Team has more
than one NXT, the Team number may have a hyphen and a letter appended to it (6
characters total).
o Verify the NXT Firmware version. On the NXT Controller, from the main menu, go to
Settings > Firmware > View Firmware Version (ROBOTC = 3.62+, LabVIEW/NXTG=2012 SP1+).
o Ask the Team to show you that the Samostat program is loaded on the NXT.
o Ask the Team to show you that the Program Chooser program is loaded on the NXT.
o Verify sleep settings. On the NXT Controller, from the main menu go to Settings > Sleep.
Sleep timer should be set to NEVER. If you change this value, remind Teams they must
now power off their NXT manually to avoid accidentally draining the battery.
Flash the network configuration on the Samantha.
o Ensure that the Samantha is powered off.
o Disconnect the USB cable from the Samantha Samantha.
o Insert the flash drive into Samantha. This flash drive should be provided to you by the
FTA. It contains a file that will identify the correct network information (WiFi, etc.) for that
Event for each Team’s Samantha Module to ensure proper connection.
o Holding the red button on the Samantha, turn the power on and let go when the LEDs
light up.
o CRITICAL STEP: Watch for the lights on the Samantha to flash
red>>white>>blue>>white>>red twice (about 20-30-seconds) until the red (power) button
is solid, the white (WiFi) LED is blinking slowly and the blue (NXT) LED is off. Note that
the lights must cycle twice for the flash process to be successful.
o Turn the power off.
o Remove the flash drive, insert the USB cable from the NXT back into the Samantha, and
turn the power on for both the NXT and the Samantha. The blue LED will illuminate but
FIRST Tech Challenge Software Inspector Manual

| 31
may pulse slightly. This “heartbeat” is an indicator that the NXT is communicating
properly with the Samantha.
It is recommended that the Samostat program is executed on the NXT to ensure the correct
Samantha firmware is loaded.
Queuing Procedures Script
The following is a description of what Teams should do prior to the Match. Review these points with
the Team to familiarize them with the Queuing Area and Playing Fields. Optionally, a dedicated
announcer may cover these points with Teams while they wait for their turn on the Field.




Preparing for a Match in the Pit area, Teams should:
o Verify that their Robot is mechanically ready to go.
o Make any required software changes. No software changes will be permitted in the
Queuing Area.
o Make any required battery changes. No battery changes will be permitted in the Queuing
Area.
o Charge their NXT, and TETRIX/MATRIX/9V battery packs.
o Larger Events: Remind Teams that they will have approximately 30-45 minutes between
Matches to do code and battery changes. However, this does include Queuing and
commute time to and from the Pit area.
While waiting to be called:
o Match times are only estimates.
o We will proceed through the Matches as quickly as possible (we will not wait for the
scheduled start time).
o Teams should monitor Match progress on the Playing Fields by checking the Match
status display board in the Pit area.
o Volunteers will instruct Teams when to leave the Pit area for their Qualification Matches.
This will be approximately 20 minutes prior to the Match.
o If the Robot cannot make the Match, at least one member of the Drive Team must be
sent to the Fields to inform the Field Staff.
When called for a Match:
o Teams must bring only the following Team members:
 Coach (student or adult).
 Driver 1.
 Driver 2 (optional).
o Teams should gather the following equipment:
 Robot with NXT.
 Robot TETRIX/MATRIX and NXT battery packs.
 Samantha Module securely installed on the Robot.
o Drive Team MUST be properly wearing safety glasses.
At the Field:
o Report to the Lead Queuer in the Competition Queuing area.
o Install the provided Alliance Flag.
o Proceed to the Playing Field when directed to do so, and quickly place your Robot onto
the Field.
o Immediately power up the NXT and TETRIX/MATRIX to turn on the Robot.
o Start the Autonomous program. A properly programmed Robot will now go into a “Wait
for Start” loop until it is enabled by the FCS.
o Stand in the assigned Driver position. The Queuer will inform each Team which Alliance
and Driver station position they will use for the Match. This information is also listed in
the Qualification Match list, and displayed on the Field monitors. It is critical that Teams
32 | FIRST Tech Challenge Software Inspector Manual
stand in the correct Alliance station position so that they will use the Controllers that
have been assigned to their Robot. Please emphasize this. It is ultimately the Team’s
responsibility to verify that they take their assigned position.
Go over the follow notes with Teams during Field Inspection:
Introduction
 Welcome Teams and escort them to the Field.
Pre-Match Setup
 Instruct Teams to place Robots onto the Field:
o During the Qualification Matches, Blue Alliance Robots are placed on the Fields first.
o Red Alliance has the option of waiting to place their Robot until after the Blue Alliance
has done so.
o If a Blue Alliance Robot is delayed, the Red Alliance should not wait for the Blue Alliance
Robot(s). They should go ahead and place their Robots on the Playing Field and
immediately power them on. The Red Alliance may adjust the setup of their Robots after
the last Blue Alliance Robot is placed on the Playing Field.
o During the elimination Matches, the lower seeded (i.e. 3rd seed is lower than 2nd seed)
Alliance Robots will set up on the Playing Field first unless the higher seeded Alliance
waives their right to set up on the Playing Field Second.
 Perform the following Robot checks (at a minimum) every time your Robot is placed on the
Playing Field:
o Power on the NXT and turn on the switch for the external battery.
o Select and execute the Autonomous program on the NXT.
o Return to your assigned Driver station, verify that you have the correct Controller for
your station, and then set your Controller back down.
The Match
 The Match will consist of a 30-second Autonomous Period, followed by a two-minute DriverControlled period.
 Drivers should not touch their Controllers during the Autonomous period.
 Pay attention to instructions from the Referees, FTA, and Game Announcer. Delays in
responding to their instructions will contribute to schedule delays.
 When the FCS Operator is ready, instruct the Teams to signify that they are ready by giving a
“thumbs up”.
 The Referee or Game Announcer will start the Autonomous portions of the Match with a
countdown: 3-2-1-GO! The FCS Operator will click on the FCS “Start Match” button on “GO!”
 Drivers should pick up their Logitech Controllers directly after the Autonomous period. Don’t wait
to be told to pick up the Controllers.
 Pay attention to the Referees and Game Announcer so that the Driver-Controlled portion of the
Match can begin without delay.
 Ask the Teams to attempt to drive their Robot. The Robots should not move at this point,
because the Driver Controlled period has not yet started.
 There will be a second round of “thumbs up” followed by a second 3-2-1-GO! to start the DriverControlled period. The FCS Operator will again press the continue button.
o Robot motion after the Driver-Controlled period ends is not normal behavior and will
cause the Team to FAIL Software Inspection. After the two-minute Driver-Controlled
period, instruct Teams to attempt to drive their Robot. Look for any Robots that continue
to operate beyond the end of the period.
FIRST Tech Challenge Software Inspector Manual
| 33
Appendix F: Resources
Software Inspector Training video
Will be released September 2014
Software Inspector Certification Test
When you your register and pass screening in VIMS to Volunteer at an event, instructions on how to
access the certification test will be emailed to you.
Game Forum Q&A - http://ftcforum.usfirst.org/forum.php
FTC Game Manuals – Part 1 and 2 - http://www.usfirst.org/roboticsprograms/ftc/Game
FIRST Headquarters Support
Phone: 603-666-3906
Email: [email protected]
USFIRST.ORG
FIRST Tech Challenge (FTC) Page – For everything FTC.
FTC Volunteer Resources – To access public Volunteer Manuals.
FTC Season Timeline – Find FTC events in your area.
FIRST Tech Challenge Social Media
FTC Twitter Feed - If you are on Twitter, follow the FTC twitter feed for news updates.
FTC Facebook page - If you are on Facebook, follow the FTC page for news updates.
FTC YouTube Channel – Contains training videos, Game animations, news clips, and more.
FTC Blog – Weekly articles for the FTC community, including Outstanding Volunteer
Recognition!
FTC Team Email Blasts – contain the most recent FTC news for Teams.
FTC Google+ community - If you are on Google+, follow the FTC community for news updates.