ii. coaching/mentoring techniques workshop for mindstorms ev3
TRANSCRIPT
1
Oregon Robotics Tournament and Outreach Program
II. Coaching/Mentoring Techniques Workshop for
Mindstorms EV3
2019
Opening doors to the worlds of science and technology for Oregon’s youth
2
Instructor Contacts
Roger Swanson
503-297-1824
Jim Ryan
503-803-0388
Terry Alexander
(503) 970-9243
Ken Cone
(503) 415-1465
Don Nelson
[email protected](503) 550-8028
3
FIRST - ORTOP
FIRST
(800) 871-8326
www.usfirst.org
--------------------------------------
Loridee Wetzel – Program Manager
(503) 486-7622, ext.102
www.ortop.org
4
Today’s Goals
Focus on being a coach or mentor for a FIRST ® LEGO® League team
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!!
5
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.orgCoaches Handbook
6
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
We’re
asking you
to help us!
7
Forming Your Team
8
Where Teams Come From School Based
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
9
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
10
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
11
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
12
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
13
Coach – The Person in Charge Single point of contact for team
Understands the FIRST ® LEGO® League 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
14
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:
“Challenge” Includes Field Setup, Missions, and Rules
“Challenge 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 https://www.firstinspires.org/resource-library/fll/judging-rubrics
15
Coach: Set Team Goals Provides focus, helps team recognize success
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!
16
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 FIRST ® LEGO® League can work as mentors
17
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
18
FIRST ® Core Values
Discovery: We explore new skills and ideas.
Innovation: We use creativity and persistence to solve problems.
Impact: We apply what we learn to improve our world.
Inclusion: We respect each other and embrace differences.
Teamwork: We are stronger when we work together.
Fun: We enjoy and celebrate what we do!
19
Equipping Your Team
20
Minimum Resources to Start
A robotics kit
A computer with Windows Vista, Windows 7, 8, or 10Mac OS X 10.7(Lion) to 10.11(ElCapitan)
A place to meet and practice
Classroom
Family room
Garage
Community Room
21
Additional Materials
FIRST ® LEGO® League CITY SHAPERSM Challenge Set (order with team registration) Each team must have access to a Challenge Set
Includes Mission Model Set and Field Mat
Practice table (design on FLL website) https://www.firstinspires.org/sites/default/files/uploads/resource_library/fll/table
-build.pdf (This design is probably overkill)
4’x8’ bottom
2x3 (or 2x4) railing around the sides (double railing on one side for some Challenge Set models)
Team Management Resources https://www.firstinspires.org/resource-library/fll/team-management-resources
Coach resources and handbook, participation rules, social media guide, Youth Protection forms, etc
22
Robotics Kit Info
FIRST ® LEGO® League EV3 -- $490*
Only from FIRST®
Complete kit with two tubs and sorting trays
EV3 software
Ship to registered teams after payment
See slide at end for other EV3 purchase options
* SPARK PRIME ships starting in August
23
Robotics Kit Info
What we know about SPARK PRIME
Starts shipping in August
Cost expected to be $329.99
Expansion set (which include the color sensor) should be $99.95
Motors, sensors, and connector cables are not compatible with EV3
Uses ‘scratch’ for programming (not EV3)
Hub (i.e. ‘brick”) completely redesigned: square corners, 6 I/O ports, rechargeable battery, built in gyro,
no display screen (5x5 LED light display), micro USB port
24
Allowed Robot Parts
Controller (1): EV3, NXT, RCX or SPARK PRIME
Motors (4): any type
As many sensors as you like but only from this set – touch, light, color, rotation, ultrasonic, and gyro
They must all be LEGO-manufactured sensors
Note: The HiTechnic color sensor is not allowed
Be sure to check this year’s rules for any changes, especially due to SPARK PRIME
25
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
Promotes kids feeling like a ‘team’
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
Loop Block
Some of you may find the Loop block useful.
27
Robot goes forward 1 rotation and then backward 1 rotation and continues that forever.
This means go forever.
CanDo Challenge Rules
The instructor will place some number of cans on the white mat inside the black circle.
You design the hardware and software of your robot to push the cans out of the circle as quickly as possible.
You may place your robot anywhere inside the circle and then start it.
28
29
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
CanDo Challenge Discussion
Don’t confuse orange Wait blocks, which you should know how to use, with yellow Sensor blocks, which we discuss in the Programming Workshop
30
Wait vs. Sensor Blocks
31
Sensor block reads the value seen by the sensor and immediately goes to the next block.
Wait block keeps reading what the sensor is measuring and does not move to the next block until the condition called for is met.
Review Program Flow
32
Turns the motor on and immediately goes to the next block.
Turns the motor on but does not go to the next block until one rotation has been completed.
Control stays on this block until the light sensor reads reflected light that is less than 50.
33
Managing Your Team
34
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 ??
35
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 EV3 assembly booklet to build something
Something they can all do at once
Explain the real situation to the parents
36
Parent Involvement
Explain program/FIRST ® LEGO®
League philosophy Success = Participation
Explain team rules (attendance, respect, ...)
Discuss participation commitment for kids
Review costs and funding sources
Communicate about tournaments
Solicit help
37
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 Robot Game)
38
(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
39
(Approx) Project Timeline
Assume 12 week season (24 meetings)
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 Solution must be shared with others
These tasks run concurrently with the Field Challenge Timeline on the previous slide
40
Time Management (cont.)
The team has two main outputs: Robot/programs to perform in Robot Game
Presentation to address Project Challenge
The tasks on the previous two timeline slides run concurrently Usually works best if work on both right from the
beginning, rather than one first then the other.
Typically need approx. equal amounts of time for each Can time share during each meeting, dedicate half
each meeting to each, or do alternating meetings.
41
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
42
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 (MyBlocks)
Include topics related to project:
Research methods
Presentation formats
43
Foundation: Mechanics
Robot basics: have team evaluate 2-3 different robots with instructions
Discuss the engineering criteria and constraints based on the challenges (space constraints, navigation challenges)
Discuss trade-offs (+/-) of each robot model
Team decides/combines for challenge robot
Gives team design tradeoff experience
Build Field Kit
Dedicate 1 meeting, divide up elements
Ad hoc extra meeting for leftovers
44
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, gyro)
Robotic Action: function it performs
Concepts: pushing, grabbing, lifting , dumping
45
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 EV3 tutorial developed by Dale Yocum, Engineering Program Director at Catlin Gabel Schoolwww.stemcentric.com
46
Foundation: Engineering Design Process
47
Foundation: Engineering Notebook
‘Engineering Notebook’ available from FIRST
Can be downloaded from FIRST FLL Challenge and Resources page
Use is optional, but can help in focusing team effort, and documenting what worked and what didn’t
Has forms for guiding team through brainstorming and mission planning.
48
Address the Challenge Pick up all information about the challenge
from FIRST® website when details announced on August 1st
Missions
Rules
Field setup
Challenge Updates (grows during the season)
Project – details on project challenge
Core Values
Very important to get all the pieces!!
49
Address the Challenge Team must learn missions and rules:
Send home copy and learn missions and rules, and project topic
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
50
Address the Challenge
Have your team group the 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
Use same approach for project ideas Brainstorm potential list of problems
Individuals research their idea and potential solutions
Individuals present and group chooses one
51
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
52
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 to debug/rebuild/share)
53
Practice Like the Tournament Field Competition Runs (Follow 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
54
Practice Like the Tournament
Judging Panels (Robot Design, Project, Core Values)
Use Coach Handbook rubrics
Parents as judges
Work on smooth, clear delivery
Practice setup and delivery of project in 5 minutes
Ask a variety of questions
Practice teamwork exercises
55
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
56
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
57
Final Advice Keep Meetings Fun
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
59
Robot Design Judging
Panel of “experts” interviews teams Mechanical: Durability, Efficiency, Mechanization
Programming: Quality, Efficiency, Navigation
Strategy & Innovation: Process, Strategy, Innovation
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
60
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
Media can only be used to enhance live presentation
All team members must participate in the Project judging presentation
Format
5 minute presentation (including set up time)
5 minute interview questions by judges
Can include posters, skits, models, props, costumes, . . .
61
Project Judging (cont.)
Project presentation must meet three criteria:
Clearly identify the problem the team picked that meets this year’s criteria
Explain the team’s innovative solution
Describe how the team shared their solution with others prior to the tournament
62
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 Core Values
63
FIRST ® Core Values Observations
Tournament officials observe teams during tournaments at all activities
Looking for exceptional positive or negative demonstrations of FIRST ® Core Values throughout the day
Observations can impact a team’s score either positively or negatively
Hand out FIRST ® Core Values Team Observation sheets
64
FIRST ® Core ValuesBest 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)
67
Sources of ideas
Constructopedias/Manuals/Guides
NXT Software Tutorial:
http://www.stemcentric.com/ev3-tutorial/
FIRST “Team Resources” page:https://www.firstinspires.org/resource-library/fll/team-management-resources
Minnesota FLL – High Tech Kids:http://www.hightechkids.org/
68
Names of Parts
Google: lego part names
guide.lugnet.com/partsref
shop.lego.com/pab (Pick a Brick)
71
Robotics Kit Info – Cont. LEGO Education EV3 Core Set -- $411.95
https://education.lego.com/en-us/products/lego-mindstorms-education-ev3-core-set-/5003400
Fewer parts with one tub and sorting trays
Download software
LEGO Retail – $349.99 http://www.lego.com/en-us/mindstorms/products/31313-
mindstorms-ev3
No tubs
Fewer sensors
Download software
Differences between EV3 KitsPart FLL Kit Education Kit Retail Kit
Core + Expansion set
Core Set Core Set
EV3 1 1 1
Motors 3 3 3
Touch Sensors 2 2 1
Gyro Sensors 1 1 0
Ultrasonic Sensors 1 1 0
Color Sensors 1 1 1
Rechargeable Battery
Yes Yes No
Software Free Download Free Download Free Download
Sorting Trays 2 tubs 1 tub No tubs
Part Count 1324 541 601
Price $489.95 $411.95 $349.99