-
Coaches
should review the
FVC Coaches Manual
-
All
should view the
"Quad Quandary"
challenge animation -
hi-res
low-res
-
All
should read the
"Quad
Quandary" challenge documentation - the
rules are important!
-
A good
supplementary source is "Vex
for the Technically Challenged" - many great
examples and ideas are represented in this document
-
Build sub-team
should go over kit inventory and familiarize themselves with the included
components
-
Build
sub-team should check out the
Innovation FIRST Inc. (IFI) site for additional
Vex-legal available components
-
Programming sub-team install easyC and start working with the coding
environment - use the most recent
Master Code,
Competition Template and documentation
-
Take
note of the official
FVC Forum and the
unofficial
FVC
forum (as well as the
Chief
Delphi FVC forum) - for news, ideas and issue
resolution
-
Build
team members should build a "Squarebot" as documented in the
manual for the Vex
Development kit.
-
Programming
sub-team can practice code execution with the "Squarebot" chassis
-
The team
should brainstorm on how to address the challenge - the strategies to
follow, the specific tactics to try - how to design a robot to meet those
goals!
-
The build team
should start the robot design process with the chassis first
-
A
sub-group should obtain materials and documentation to build a
full or
partial challenge field for practice - this could
be shared with other team(s)
-
easyC development
cycle - build, code, test, repeat as needed
-
Drive sub-team
should start to practice as robot design becomes stable
