Oregon Robotics Tournament and Outreach Program II. Coaching/Mentoring Techniques Workshop for Mindstorms EV3 Bathrooms down the hall 2014 Opening doors to the worlds of science and technology for Oregon’s youth

Instructor Contacts Ken Cone ken_cone@gmail.com (503) 415-1465 Jim Ryan james.r.ryan@intel.com 971-215-6087 Terry Hamm terry.hamm@gmail.com (503) 720-5157 Roger Swanson swanson@hevanet.com 503-297-1824 Technologist MS/CS 10 yr 2 coaching, 7 judging Dale Jordan Dale_A_Jordan@msn.com

Cathy Swider - Project Administrator FIRST - ORTOP FIRST (800) 871-8326 www.usfirst.org Cathy Swider - Project Administrator Cathy_Swider@ous.edu (503) 725-2920 www.ortop.org

Today’s Goals Focus on being a coach or mentor using Mindstorms EV3 robotics kits I hope you leave: Feeling more comfortable about your role Having some more tools in your bag of tricks Understanding better what it takes to solve a challenge. Having gotten your questions answered Have some fun!! Be encouraging

Agenda Review our Mission Forming your team Equipping your team Use EV3 Robots from last week to program more with the Mindstorms EV3 Software Managing your team Judging at the tournament Resources: firstlegoleague.org Coaches Handbook Show videos + robots Robot jpg getting first points More simple 274 Senior soln

We’re asking you to help us! Our Mission Program not just about building robots and competing in tournaments Teach skills Specific technical skills General life skills Show that technical problem solving can be fun The youngsters do the work – FLL Core Values and Coaches’ Promise Open up the possibility of technical careers One secret opportunity Teamwork Play and have fun

Forming Your Team More retails

Where Teams Come From School Based Club Based Independent team In class: Perhaps 45 minutes a day After school: Perhaps 1.5 hours; 2 to 4 times a week Special block: Several hours once a week Club Based Probably after school or evening Independent team After school, evenings, or weekends We encourage you to find and include youngsters that normally would not have this exposure Home schooled, Wisc girls team at world fest

Not a Drop-In Program This is a project oriented program Parents and team members need to understand the commitment required Team members need to be available on a consistent basis to move their parts of the project forward from the first meetings through the season-end tournaments Ask kids for their level of comittment

Where to Meet Large enough space to handle the number of youngsters on the team Space for challenge field setup – 4’x8’ Access to a computer Storage space between meetings Challenge table Partially built robot LEGO parts

Team size High initial interest may fade Sub-teams of 2-3 can work in parallel Experiment with prototypes Learn programming techniques Work on the project Maximum team size allowed is 10 5 to 7 team members is probably ideal

You Need Adults, Too! Coach – The person in charge Organizes the team Does not need to be a techie Mentor – The technical guru Provides technical advice Provides the technical basics One person can play both roles But, don’t go it alone Recruit other adults to supervise sub-teams

Coach – The Person in Charge Single point of contact for team Understands the FLL and ORTOP programs Management expertise more important than technical expertise Point of contact for FIRST® and ORTOP info Recruits the team Registers the team Arranges for equipment Schedules meetings Sets the philosophy and instills team spirit Is a good role model Use web sites ortop and fll

Coach – Need to know Responsible for ensuring the Team knows the rules and requirements for the current year’s Challenge Details on FIRST® website: http://firstlegoleague.org/challenge/thechallenge Be sure you access the following key elements: “Robot Game” Includes Field Setup, Missions, and Rules “Robot Game Updates” Provides detailed interpretations and rule changes for missions and game rules. Updated frequently throughout the season, until Friday of Tournament weekend. Project Generate and share an innovative solution to the Challenge theme Core Values Judging rubrics

Coach: Set Team Goals Scale to experience level of team Samples Learn to program (...learn to use subroutines) Learn about (topic of year) Participate in tournament Complete at least 1 mission (more for experienced teams) Everyone participates HAVE FUN! Not to many missions

Mentor – The Technical Advisor Technical Advisor to assist the coach Facilitates both robot design and programming skill sets Helps set achievable goals Encourages structured problem solving Follow typical engineering project models Experiment with one variable at a time Graduates of FLL can work as mentors

General Advice to All Adults This is the kids’ project, not yours Be a good role model Keep a positive attitude Encourage teamwork and insist on mutual respect Don’t over emphasize “winning” – demonstrating a solution at a tournament is success Have fun Emphasis star

FLL Core Values We are a team. We do the work to find solutions with guidance from our coaches and mentors. We know our coaches and mentors don’t have all the answers; we learn together. We honor the spirit of friendly competition. What we discover is more important than what we win. We share our experiences with others. We display Gracious Professionalism™ and Coopertition™ in everything we do. We have fun. Kids will learn + poster

Equipping Your Team

Minimum Resources to Start A robotics kit A computer with Windows Vista, Windows 7 or 8 Mac OS X 10.6, 10.7, 10.8 A place to meet and practice Classroom Family room Garage Community Room Win 8 and mac No tablets though

Additional Materials 2014 FLL “World Class” Field Setup Kit (FSK) (only available from FLL - $75) Each team must have access to a FSK Mission Model Set Field Mat Practice table (design on FLL website) http://www.firstlegoleague.org/media/twocol.aspx?id=247 Click on Field Setup link 4’x8’ bottom 2x4 railing around the sides (extra 2x4 thickness on one side for some Field Setup kit models) Just came out and already has youtube videos

Robotics Kit Info Kits NXT-based kits EV3-based kits Ship to registered teams starting in mid-May OK to purchase a retail kit or order directly from www.legoeducation.us NXT-based kits $435 if ordered during FLL registration EV3-based kits $499 if ordered during FLL registration

Robotics Kit Info – NXT-Based FLL NXT -- $435 Only from FIRST® Complete kit with two tubs and sorting trays NXT software LEGO Education NXT Base Set -- $299.95 http://shop.education.lego.com/legoed/education/MINDSTORMS+Education+NXT/category/EDU_PRD_LINE_106 Fewer parts with one tub and sorting trays, no software LEGO Retail -- $279.99 http://shop.lego.com/en-US/LEGO-MINDSTORMS-NXT-2-0-8547?p=8547 Fewer parts with no sorting trays Includes NXT software

Robotics Kit Info – EV3-Based FLL EV3 -- $499 Only from FIRST® Complete kit with two tubs and sorting trays EV3 software LEGO Education EV3 Core Set -- $339.95 https://shop.education.lego.com/legoed/education/MINDSTORMS+Education+EV3/category/EDU_PRD_LINE_107 Fewer parts with one tub and sorting trays No software LEGO Retail – $449.05 24 24

Differences between NXT Kits Part FLL Kit Retail Kit Education Kit NXT 1 Motors 3 Touch Sensors 2 Light Sensors Sound Sensors Distance Sensors Color Sensors Rechargeable Battery Yes No batteries NXT Software Buy No -- $80 Sorting Trays 2 boxes No 1 box Part Count 1,000+ 612 431 Price $435 $280 $295

Differences between EV3 Kits Part FLL Kit Education Kit Retail Kit EV3 1 Motors 3 Touch Sensors 2 Light Sensors Gyro Sensors Ultrasonic Sensors Color Sensors Rechargeable Battery Yes No Software Purchase CD $99.95 Download for free Sorting Trays 2 boxes 1 box Part Count ?? ½ FLL Kit 600 elements Price $499 $339.95 $349.95 Expansion set has 850 elements

Allowed Robot Parts NXT controller (1) or EV3 controller (1) Motors NXT (3) EV3 (4) As many sensors as you like but only from this set – touch, light, color, rotation, ultrasonic They must all be LEGO-manufactured MINDSTORMS sensors Note: The HiTechnic color sensor is not allowed A color sensor comes in the NXT retail kit but not in the other two     27 27

Team Uniforms?? Many teams do something for the tournaments Team shirts, hats, etc Theme clothing Team sponsor advertising on a T-shirt, etc. is OK Helps adults keep track of team

Let’s Take a Break As your first hands-on exercise for this workshop, your instructor will explain the Can-Do challenge But first a NXT programming tutorial

CanDo Challenge Discussion Simple project, but good learning tool Unexpected things happen – cans get caught under the wheel, it goes the “wrong” direction Take it in smaller steps – “Let’s see what happens before it hits a can” Mechanical problems may do you in Clarify the “rules” – know the requirements Experiment – “Just go try it. We can rework it.” Keep it simple

Managing Your Team

Meeting Organization How often and how long to meet Most teams meet 1-3 times per week After school, evenings, weekends as team desires Some add extras as get closer to end > 1 hr (set up and take down) < 3 hrs (attention span) At least 2 adults present during meetings – can use parents who take turns Set ground rules -- E.g. don’t turn kids loose to walk home by themselves after dark Refreshments / snacks ??

Team Kick-off Meeting Welcome parents/guardians Set expectations with kids and adults Send kids off to build with LEGO parts Get assistant to help Use NXT or EV3 assembly booklet to build something Something they can all do at once Explain the real situation to the parents

Parent Involvement Explain program/FLL philosophy Success = Participation Explain team rules (attendance, respect, ...) Discuss participation commitment for kids Review costs and funding sources Communicate about tournaments Solicit help

You Have A Team, Now What? (Time Management) Divide the season Build A Foundation Address the Challenge Get It Done Practice like the Tournament Participate in Tournament (Judging and Field Challenge)

(Approx) Field Challenge Timeline Assume 12 week season (24 meetings) 4 weeks: Build Foundation 6 weeks: Complete Challenge 2 weeks: Practice / Minor changes You may need to adjust these suggestions based on the time you have available to meet with your team

(Approx) Research Project Timeline 1 wk: Basic Research 2 wks: Narrow and Select Project Topic 1 wk: Focused Research 6 wks: Conduct Project / Prepare Presentation 2 wks: Practice and Present to Others These tasks run concurrently with the Field Challenge Timeline on the previous slide Use the DVD from registration or look online at usfirst.org

Build a Foundation Introduce techniques and concepts Build or bring demos Discuss advantages and disadvantages Let kids figure out how to apply concept to Challenge One approach: use 5-10 minutes at start of each meeting to introduce concepts Pick 1-2 subjects per session Can be more for first meetings / new teams May stop about ½ way thru season – A bit late to incorporate new concepts unless they are stuck

Foundation: Sample Concepts Pick one or two new subjects per session Structural strength: bracing vs. snapped pieces Gear ratios: torque vs. speed Traction: tracks vs. wheels Friction: tires vs. skids Programming techniques: linear vs. loops vs. subroutines

Foundation: Mechanics Robot basics: have team build 2-3 different robots with instructions e.g. one per meeting Discuss “+”, “-” of designs Team decides/combines for challenge robot Gives team general robot building and design tradeoff experience Build Field Kit Dedicate 1 meeting, divide up elements Ad hoc extra meeting for leftovers

Foundation: Divide and conquer Three basic robot functions: Locomotion: how the robot moves Concepts: motors, gears/pulleys, wheels/tracks, friction, steering Navigation: how it knows where to go Concepts: time, sensors (rotation, touch, light, ultrasonic) Robotic Action: function it performs Concepts: pushing, grabbing, lifting , dumping

Foundation: Programming Introduce basic programming Can use Workshop handouts Introduce sensors If meetings start before Challenge is announced, can use mini-challenges to introduce concepts Use Catlin NXT/EV3 tutorials www.stemcentric.com

Foundation: Structured Problem Solving Teach them elements of structured approach to solving large problems Defining problem Brainstorming Evaluating alternatives Choosing alternative Implementing Evaluating & testing Want consistency 9 out of 10 runs work…. Fewer missions and better success

Address the Challenge Pick up all information about the challenge from FIRST® website when details announced on August 26th Missions Rules Field setup Game Updates (grows during the season) Project – details on research project Core Values Both field challenge and project/research challenge

Address the Challenge Team must learn mission and rules: Send home copy and learn missions and rules Discuss and test understanding at later team meetings Can overlap with ‘build foundation’ meetings You might want to find a “rules expert” among your team members

Address the Challenge Have team group missions Members brainstorm/generate prioritized list: Can prioritize group by ease, location, or points Can group by program or trips out of base Individuals present and team selects which to start with Refer to team goals for how many to try Can add more if finish 1st set and still have time

Address the Challenge Team decides how to divide responsibilities A) Builders / Programmers B) Mission based (build/program by mission) C) ?? Need duplicate coverage for illness/absences Probably want area specialists (build, program, research, etc.) BUT Recommended ground rule: Everyone contributes to all aspects of team’s work

Get It Done Considerations: Introduce “design rule” concept Shared, agreed upon design constants e.g. Motors B/C drive and motor C is on right Which end is ‘forward’ Light sensor is always in port ‘3’ Programs need to share inputs/outputs Attachments need to go together Base robot with quickly interchangeable attachments, or Attachments can’t interfere with those for other missions Target being done early (time for debug/rebuild)

Practice Like the Tournament Field Competition Runs (tournament rules) Start with individual missions/groups, then all together 2 ½ min, 2 members at the table at once Practice working under time pressure Switching between missions, programs Try to limit big last minute changes to missions/robot

Practice Like the Tournament Judging Panels (Robot Design, Project, Core Values) Use Coach Handbook rubrics Parents as judges Work on smooth, clear delivery Ask a variety of questions Practice teamwork exercises

Final Advice: Budgeting Resources Physical resource effectiveness limits: No more than 2 (3 max) at one keyboard No more than 2-3 building one item Can’t research presentation and program robot on same computer at same time Consider time sharing 2 computers, one robot kit; divide team 1/3 building, 1/3 programming, 1/3 researching Rotate during meeting

Final Advice: Set Expectations For a Positive Tone Encourage risk taking It’s OK to fail – they are learning opportunities Key is to manage the risk Encourage experimentation Expect failure – focus on what is learned as a result Problem solving takes time – Edison’s experience with light bulb filament

Final Advice Keep Meetings Fun Be flexible Watch for teaching moments Usually means hands on LEGO building every meeting Be flexible Help keep them on task, but ultimately it is their project The journey is as important as the result Watch for teaching moments Engineers need ‘hard skills’ Mechanical Design, Programming, Analysis, Problem Solving, Experimentation, and Documentation AND ‘soft skills’ Timeliness, Teamwork, Tact and Compromise, Confidence, Courtesy, Perseverance, and Planning

With All the Focus on the Robot and the Challenge… Don’t Forget the Judging

Robot Design Judging Panel of “experts” interviews teams Robot design: Creativity and robustness Programming: Creativity and robustness Prepare the team to: Give a 1 minute overview of their robot design noting “sources of inspiration” Answer questions about the design of the robot and its program Demonstrate at least one mission on the challenge field Bring a printout of the program 55 55

Project Judging Another good learning opportunity Research skills and presentation skills (remember the marketing kid? ) Good engineering requires research and communication Must be a live presentation Format – includes setup time 5 minute presentation, 5 minute interview Posterboards, skits, models, Powerpoint (not the best format, can waste time with setup), . . .

Core Values Judging A separate 10 minute judging session Teams will do a surprise teamwork activity At Championship tournament the teams bring a Core Values “tri-fold” or poster with them and give a short, less than 2 minutes, presentation on the contents Judges interact with teams to evaluate how the teams meet the FLL Core Values

FLL Core Values Team Observations Tournament officials observe teams during tournaments at all activities Looking for exceptional positive or negative demonstrations of FLL Core Values throughout the day Observations can impact a team’s score either positively or negatively Hand out FLL Core Values Team Observation sheets

FLL Core Values Best Practices Youngsters design, build, and program their robots Youngsters are responsible for project work ORTOP rule: During tournament, no adult may touch the computer keyboard, mouse, robot, robot attachments, or project materials. ORTOP rule: No adult may give specific verbal directives on programming and building or during table competition at a tournament. Tournament guidelines should be in effect at team meetings.

What if …? Teams may use software or mechanical designs that they find on the Internet Good engineers build on the design work of others and don’t reinvent the wheel We encourage the use of our building instructions to get your team started with its first robot But, there are responsibilities that go with this!!

Use of Third Party Materials Team decides what to use and why they want to use it They must be able to explain how the software or mechanical design works and why they included it They must give credit to any such third party material that they use (Bring your “sources of inspiration” list to the Robot Design judging)

Sources of ideas Constructopedias/Manuals/Guides NXT Software Tutorial: http://www.stemcentric.com/ev3-tutorial/ FIRST “Team Resources” page: http://firstlegoleague.org/challenge/teamresources Minnesota FLL – High Tech Kids: http://www.hightechkids.org/

Names of Parts Google: lego part names guide.lugnet.com/partsref shop.lego.com/pab (Pick a Brick)

Contact Us Web site: http://www.ortop.org Email: questions@ortop.org Phone: 503-725-2920

Final Hands-On Exercise Discuss and program a simple line following algorithm that will follow the circle on the Can-Do Challenge mat.