Fall 2011 Robot Design Project

To build design skills, Team 1640's main Fall Project is the complete design of a robot to play an old FRC game (from before the team's collective memory). We selected the 2003 game, Stack Attack for this exercise.

Within the scope of this project, we will:

1. Run a Kickoff
2. Develop Strategy (the whats)
3. Extend the Strategy to Functional Requirements (Functional Specifications)
4. Map the functional specification to devices & systems specifications
5. Prototype and model potential devices and systems
6. Design the devices and systems
7. Integrate these into a comprehensive robot design
8. Develop a BoM and procurement schedule

Practice Kickoff

The Project started with a well-attended Practice Kickoff on 17-September.

Strategy & Functions

Strategy - How will we play the game and win

HIGH PRIORITY - MUST DO (WELL)

• A Fast Autonomous Ramp Run was agreed to be the first strategic priority. Ramp Run means running at the crates on the top of the ramp at the start of autonomous and knocking/pushing all of most of these over into our alliance scoring zone and doing this before the opposition robots can do the same.
• Own the Ramp - Be able to defend the ramp to prevent or limit the ability of opposing robots to cross the ramp while also being able to allow alliance robots to cross as needed.
• Be on the ramp top at the end of the match
• Restrict access to the top of the ramp to opposing robots at the match end (a continuation of Own the Ramp to the end game).
• High robot reliability
• Ability to rapidly service damaged critical systems.

LOWER PRIORITY - NICE TO HAVE

• As a scoring Plan B, pick up and possess a stack of between 2 and 4 crates and protect these internally through the game. Deposit in scoring zone towards end of teleop. May need to defend this stack, requiring a trade-off decision between the stack & bonus points.
• Be able to pull crates out of corners and into scoring zone.
• Be able to efficiently tranfer crates over pipes.
• Be able to pass under pipes.

Functions - What must the robot do (and how well) in order to execute the strategy

MUST HAVE

• Control & Drivetrain - Superlative autonomous navigation during Ramp Run
• Control & Drivetrain - Short time from autonomous start to top of ramp
• Scoring - Large crate-pushing profile at autonomous top of ramp
• Control & Drivetrain - High momentum at autonomous top of ramp
• Drivetrain - High traction - all ramp surfaces (high friction coefficient, µ & mass)
• Drivetrain - Power (Propulsive Force) to block opposition on ramp (need not exceed maximum static frictive force)
• Scoring - High-velocity impact with ramp crates must drive the crates forward
• Drivetrain - Perceived benefit to being able to strafe to defend ramp
• Drivetrain - Perceived benefit for Pivot in speed to top of ramp (not verified)
• Stability - Don't tip - keep CoM low & central
• All systems - Robust, reliable design
• All systems - Modularity and documented, tested and trained replacement processes to facilitate rapid repair

WANT/NICE TO HAVE

• Ability in autonomous to locate, pick up and possess a stack of opposition crates
• Ability to deploy possessed stack of crate, ideally on top of an upright crate
• Ability to angage and pull crates at any orientation on field surface
• Ability to deploy possedded stack of crates over pipe
• Ability to pass under pipe

---