1 / 39

Table Introductions

Table Introductions. At each table: Write down your names, team #, and how long you’ve been involved with FIRST Add up the number of years your table has been in FIRST Introduce the team numbers and the total years of FIRST experience you have. Fun PoKo Numbers.

limei
Download Presentation

Table Introductions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Table Introductions • At each table: • Write down your names, team #, and how long you’ve been involved with FIRST • Add up the number of years your table has been in FIRST • Introduce the team numbers and the total years of FIRST experience you have

  2. Fun PoKo Numbers • 229 people from 16 FRC teams • FRC 3630, 3299, 3184 have been at all three of our design events • Lead mentor from FRC 4118 is attending the event from Florida

  3. Welcome to the second annualMinnesota Post Kick-Off!Presented by: Tweet to our Handle @mngofirst Include these Hash Tags: #omgrobots #mnpoko

  4. GOFIRST • FIRST Alumni Organization at the University of Minnesota- Twin Cities • Mentors FRC Teams • Volunteers at FRC events • Hosts FRC events • Participate in collegiate robots competitions

  5. What is the MN Post Kick Off? • Review the new 2012 FRC game • Analyze the rules • Q&A • Start Requirements & Objectives discussion • How to create a build schedule

  6. Review of the 2012 FRC Game • Video of 2012 FRC Game from Bryan S.

  7. Review of the 2012 FRC Game • Herding counts as possession • Can only posses 3 balls at a time • Touching the Key, Bridge, or alley is protected • Start with 2 balls preloaded • Inbounding via slot during entire game • Thrown over the wall in the last 30sec

  8. Review of the 2012 FRC Game • Major Changes to “Standard” Bot • Only 1 ,14” max extension from FP and a time [G21] • 28” x 38” x 60” at start • Up to 60” tall on your Defensive end • Up to 84” tall on your offensive end • Bumpers, 8” from each vertex

  9. Review of the 2012 FRC Game • Scoring • 3 pts for high goals • 2 pts for mid • 1 pts low • Auto • Above score +3pts

  10. Review of the 2012 FRC Game • Rim Heights: • Top Hoop is 98” • Middle Hoops are 61” • Bottom Hoops are 21”

  11. Review of the 2012 FRC Game • Scoring • Bridges • Points assessed to the Alliance, not per robot

  12. Review of the 2012 FRC Game • Fouls = +3pts for the other guys • Inbounding • Technical = +9pts for the other guys • Using Bball to balance a bridge [G14] • Flagrant breaking of height rules in Alliance Station [G20] • Flagrant breaking of 14” ext. limit [G21] • A full Alliance blockade of the court [G23] • Intentionally falling [G24] • Contact with opponents bridge [G25] • Touching opp robots in Key, Alley or Bridge [G28] • Can’t pin for more than 5 sec [G29]

  13. Review of the 2012 FRC Game • Scoring • How many points can you score and still lose? • How many points total can you score?

  14. Review of the 2012 FRC Game • Past Years to Review • 2006 Aim High for shooting • 2001 for balance, bridge, center bump • 2010 Limited number of Game Pieces

  15. Review of the 2012 FRC Game As a Team go back and further review the game together

  16. Requirements Management • Industry design process • Gives teams a place to start their design process • Clearly defines team strategy • Systematically focuses the design

  17. Requirements/Needs • Things the robot MUST do! • Rank your list • Black Box Robots • Be super specific • This defines the robot’s function and says nothing about the “HOW”

  18. Requirements/Needs • Things the robot MUST do! • First must be able to build • Pass Inspection • Check the rules each year! • Move?

  19. Objectives/WANTS Things the robot WANTS to do! • Black Box Robots • Rank your list • Be super specific • This defines the robot’s function and says nothing about the “HOW”

  20. Your team must be able to build it Pass Inspection Move Thing Thing Thing Thing Requirements Objectives The LIST

  21. Things that pull in opposite directions • Speed Vs Torque (Pushing Power) • Weight Vs Complexity • High reach Vs low center of gravity Trade-ables

  22. Your team must be able to build it Pass Inspection Move Thing Thing Thing Thing Requirements Objectives Start Your R/O List

  23. Team Bonding Activity • HIGH FIVE BUDDIES! • We expect to see this at all the MN regionals!

  24. Confirm the R/O lists as a Team • Historical Research • Conceptualization • Critical Design Review • Build Next Steps

  25. Chief Delphi- www.chiefdelphi.com • Blue Alliance- www.thebluealliance.com • Scouting Data- www.simbotics.org/resources/scouting-database • GOFIRST Encyclopedia Robotica Historical Research

  26. Historical Research

  27. Conceptualization • Start Thinking of Robot Designs! • All designs must meet the Requirements and Objectives your team has listed • Start with the chassis and work up • DO NOT GET EMOTIONALLY ATTACHED • Can’t say “Because I want to” or “Because another team did it”

  28. Conceptualization • Refine 3-4 Ideas • Down Select

  29. Conceptualization • Refine 2-3 Ideas • Prototype (Confidence Gathering) • If needed • Down Select

  30. Critical Design Review • The whole team participates • Look for possible flaws • Did you meet your requirements? • Go through your list number by number • How did the you meet each requirement? • Why did you make that decision?

  31. Creating a Build Schedule • Helps team stay on track • Conventional Schedule VS • Iterative Design Schedule

  32. Schedule Building, Conventional • Work backwards from ‘Ship’ day • 1 week for final testing/Driver Practice • Final integration • Final assembly • Construction • CDR • 30 minute prototypes • 10 minute prototypes • Design, Research

  33. Schedule Building, Iterative • Work backwards from ‘Ship’ day • 1 week for final testing/Driver Practice • Final integration • Final assembly • Iterate • 2-4 day work ups • 2 day prototypes • 30 minute prototypes • 10 minute prototypes • Design, Research

  34. Important Dates Chairmans, Woodie Flowers, Dean’s List are due: Thursday February 16th 11am February 18th, 2012

  35. Important Dates Pre-Ship Regional 2/18/2012 or 2/19/2012

  36. Important Dates ROBOT BAGS! Tuesday February 21st

  37. Bag and Tag • Put Bumpers in Bag • Bubble wrap things that are pointy

  38. Contact Info • E-mail: gofirst@umn.edu • Twitter: @MNGOFIRST • Facebook: /group/gofirst • Linkedin: • /groups/GOFIRST-Group-Organization-FIRST • Youtube: /umngofirst

  39. Questions?gofirst@umn.edu

More Related