Preparing for your
First FIRST® Competition
Oct, 2012
Welcome
• Purpose:
This presentation is intended to inform teams as to what they may expect when attending
their first event in terms of the inspection process and getting ready to compete.
• Things we will cover:
–
–
–
–
General things to know which will help you start your season.
Things to know and do before your first event.
Hardware and software inspection process overview.
Tips and tricks (best practices).
• This presentation is geared towards rookie teams, but contains
information to benefit veteran teams as well.
• Presentation material available at the FIRST website.
• Please ask questions as you have them.
Getting Started
Step 1: Read the game manual.
Step 2: Read everything else.
Step 3: Read the game manual again.
Knowing and understanding the robot rules, game rules, where
to locate on-line resources and help will give you a great start!
This information will help you a good game strategy, design
and implement a robot for that strategy, and help them
compete trouble free.
Knowing event deadlines, registration process, where to find
information, and where to get help will make the season run
more smoothly.
Getting Started
• There is a wealth of information on the FIRST site (tech guides and
reference, schedules, contacts, etc). Take advantage of it.
http://www.usfirst.org/roboticsprograms/ftc
• Chief Delphi is another great resource for help.
http://www.chiefdelphi.com
• Find a veteran team near that can mentor and help you get started.
• If more help is needed, work with your areas Affiliate Partner to
identify other resources that you could leverage.
Software Basics
•
Two different programming platforms available for use with the FTC kit:
– ROBOTC – Classical C programming (small additional cost).
– LabVIEW – Drag and drop programming (included in the kit).
•
Two different programming environments and experiences, but same results.
•
Each have a unique firmware that must be uploaded to the NXT (included with
programming environment, but watch for updates.)
•
Each has a specific programming template which teams MUST start with and add
their custom code to (comes with the programming environment.)
•
Each provides facilities for manipulating files (upload/download/delete) on the
NXT, controlling the robot (like in a match) and installing the NXT firmware.
•
Make sure you use this seasons software (programming environment, firmware,
and templates.) Robots using older version will not be accepted at the
competition.
Preparing Your NXT
Things to do right away:
• Upgrade your NXT to the latest firmware (LabVIEW or ROBOTC.)
• Name your NXT with your team number (i.e. 0123.) Naming the NXT is
done through a utility in the LabVIEW/ROBOTC programming
environment. If a team has more than one NXT, append a letter (i.e.
0123A).
Things that can wait until competition:
• Set the NXT Sleep timer to 30 minutes (or more) so it does not fall asleep
on the job (during a match). This is done directly on your NXT.
• Optional: Recommend turning off the NXT Bluetooth capability at the
competition. This is done from your NXT.
Software inspection will check for these items.
What is Samantha
• WI-FI based control system which augments (almost
replaces) NXT Bluetooth connectivity.
• More reliable and responsive than the NXT Bluetooth
solution PROVIDED you follow wiring recommendations.
• ROBOTC supports programming development over
Samantha (WI-FI).
USB / BT Connectivity
• USB direct connect (programming and control)
Team
Laptop
• Bluetooth (programming and control)
Team
Laptop
FCS Competition Connectivity
FCS <--> Router <--> Samantha <--> NXT
FCS
Router
Ethernet
Wi-Fi
USB
USB
USB
USB
Things to know about the
Samantha Module
• There is a button on the Samantha module that you must press at certain
times. Make sure you can get to it.
• There is a USB connector (Female-A) on the Samantha module which you
must access during software inspection.
• You may wish to direct connect your NXT to your laptop for programming
during a competition. You must unplug Samantha from the NXT to do this
and reconnect it before your next match.
• Samantha has 3 LED lights that give lots of information. Make sure they
are easily viewed (help the FTAs help you).
Conclusion: Protect, but DON’T BURY your Samantha module inside your
robot!
More things about Samantha
• You can use Samantha right out of the box, but you will need to
make some changes to your home network router.
OR
• You can use Samantha with your existing home network (as is),
but you will need to make some Samantha reconfiguration.
• Your Samantha module may be modified by the software
inspectors at each event. You may need to change it back if you
want to use after the event.
• You can do all your development without ever using Samantha,
HOWEVER, you MUST use Samantha at your competitions.
• Recommend testing your Samantha well in advance of your first
event to insure that it works!!!!
2012 Field Control System (FCS)
• Most FTC events will have a at least one practice field and one
competition field.
• The practice field will have an open WI-FI network (FTC_PIT) that
teams can connect their laptop and robot to while in the pit area.
Users may use this network to program, control, and practice with
their robot while in the Pit area.
• The competition field will have a secure WI-FI network (FTC_FIELD)
that only your robot will be able to connect up to. There is no need
for a team to bring their laptop to the competition field.
• The setup or use of team or personal WI-FI networks or hotspots
are prohibited at FTC competitions!!!
Alternate NXT Connectivity
Bluetooth Connectivity
Pros:
• Already built into your NXT.
• Allows for modification and testing of code (ROBOTC and LabVIEW).
Cons:
• You need a Bluetooth enabled laptop (or Blue tooth adapter)
• Can be finicky (i.e. problems establishing or dropping connections).
• It is highly recommended to turn off Bluetooth on the NXT during a match.
USB (wired) Connectivity
Pros:
• Already built into your NXT.
• Allows for modification and testing of code (ROBOTC and LabVIEW.)
• Very reliable.
• Don’t have to turn anything on or off (like Bluetooth.)
Cons:
• You have to disconnect/reconnect Samantha module.
• You have to drag a cable if driving your robot.
Control System Best Practices
• Insure that all power wire connections on the robot
motor/servo controllers are good and tight. This will prevent
power interruptions to the Samantha module.
• Replace the Tetrix battery connectors with something more
durable. Better yet, consider using the alternate Robot Power
Management wiring method.
• Static electricity (Electro-Static Discharge) can damage you
robot. This is a larger concern in dry environments. Learn
about it and avoid shocking your robot.
At the Contest
LOTS TO DO!!! – Typical schedule
•
•
•
•
•
•
•
•
•
•
}
Arrival and Check in (~ 7:30 AM)
Setup your Pit area
H/W inspection
S/W inspection
Judges Interview
Practice Matches
Opening ceremony (~ 10:00 AM)
Qualifying matches (lunch)
Elimination matches
Awards and closing.
Lots to do in
2.5 hours!!!
Helps to
Be Organized
And Stay Focused
Software Inspection
Objectives:
• Insure that the NXT is configured properly for competition.
• Configure Samantha for the competition field.
• Insure that the robot works as expected.
• Insure that the team’s drivers and coach know the match
process.
Two parts of s/w inspection:
• Configuration check
• Field test
The S/W inspection sheet is available in the Bowled Over!
game manual.
Software Inspection
NXT/Samantha configuration check:
• NXT Firmware version OK?
• Proper team number configured?
• Sleep timer 30 minutes or greater?
• Install competition field network keys.
• Connects to the FCS?
Field Test.
• Does the bot behave?
•
•
Waits, moves, stops, and pauses.
Does the drive team behave?
•
•
•
•
Know where/when to queue for match?
Know how to setup on the field?
Know their signals (ready, need help, etc.)?
Know what to do at end of match?
You can download the current version of the 2011 Field Control System FCS here and test this yourself.
Hardware Inspection
Each team will get the sole attention of a hardware inspector
for 10-15 minutes. They will check to insure that the robot
meets all the robot rules stated in the “Ring It Up!” game
manual.
• Robots must comply with all the Robot Rules in section 4.2 of the game
manual in order pass hardware inspection.
• If a robot violates one or more robot rules, the robot will have to be
modified by the team to be made compliant.
• If you do need to modify your robot, you will need some tools, so plan
ahead.
• Get to the event on time and make this a priority, as you must pass h/w
inspection to play
Hardware Inspection
• Teams have access to the same inspection sheets used
by the inspectors. Do a self-inspection before the
event and fix any issues. The hardware inspection
sheet is provided in Part 2 of the game manual.
• Not all inspectors are created equal. Two inspectors
may catch different things or have different opinions as
to what is a sharp edge. Play it safe and be
conservative when possible (leave no doubt!!!)
• Don’t forget your flag holder and team number of the
prescribed size.
Inspection Wrap-up
• Teams must meet ALL software rules to pass
software inspection.
• Teams must meet ALL hardware rules to pass
hardware inspection.
• Teams cannot compete until they pass both
software and hardware inspections.
• Make passing the inspections a priority!!!
General Tips and
Best Practices
•
Make sure your robot is done done a week before the event () and let your drivers
put some miles in it!!! Better to break and fix it before an event instead of during.
•
Do your own inspections BEFORE the event.
– Have several students do a h/w and s/w inspection using the inspection forms.
– Have them fix any issues they find and repeat inspections.
– Have a mentor do a final inspection (The Inspection Challenge).
•
Pack in advance and don’t forget anything (including your laptop and robot code).
•
Bring as many spare parts as the students can carry.
•
Put your team number on everything: tools, batteries, chargers, laptops, NXT,
cables, and even the students.
•
Make sure to charge ALL your batteries before the event (laptop, NXT, and
TETRIX®).
Tips and Best Practices
• Create and use checklists.
– “take to the event” checklist.
– Pre-match checklist.
– Post-match checklist.
• Bring a “loose” copy of your code (USB thumb drive, CD-ROM, etc.).
• Get to the event early (extra time is your friend!!!)
• Identify any special dietary needs and plan ahead for meals. Lunch/drinks
can generally be purchased from the event organizers.
• Bring an power strip and extension cord. An open receptacle is often hard
to find (let alone two.)
Tips and Best Practices
Benefits of having a robot cart:
– Serves as a convenient work platform.
– Prevents students from having to carry the bot (less risk to students
and robot).
– Place to carry emergency tools, parts, and spare batteries.
– Suggest inflatable wheels on your cart (less vibration, no scratching of
gym floors).
– “Deluxe model” - 12V battery and inverter for on board charging
TETRIX, NXT and laptop batteries.
– Ground effects lighting, flasher, etc….. Have your students “Trick Out
the Robot Ride!!!”
Resource Links
• FIRST FTC site:
http://www.usfirst.org/roboticsprograms/ftc
• Ring It Up! Game Information:
http://www.usfirst.org/roboticsprograms/ftc/game
• Programming Resources:
http://www.usfirst.org/roboticsprograms/ftc/programmingresources
http://www.robotc.net/ftc/
http://ni.com/ftc/
• Field Control System and Samantha Downloads:
http://www.usfirst.org/roboticsprograms/ftc/samantha-resources
Thank You!
Good luck this season and hope to
“see you in St. Louie!”
Mike Nicolai
mike.nicolai@lmco.com