Oregon Robotics
Tournament and Outreach Program
II. Coaching/Mentoring
Techniques Workshop for
Mindstorms EV3
2017
Opening doors to the worlds of science
and technology for Oregon’s youth
1
Instructor Contacts
Terry Alexander
[email protected]
(503) 628-8029
Ken Cone
[email protected]
(503) 415-1465
Jim Ryan
[email protected]
971-215-6087
Roger Swanson
[email protected]
503-297-1824
2
FIRST - ORTOP
FIRST
(800) 871-8326
www.usfirst.org
-------------------------------------Loridee Wetzel – Program Manager
[email protected]
(503) 486-7622
www.ortop.org
3
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!!
4
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
5
We’re
asking you
Our Mission to help us!

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
6
Forming Your Team
7
Where Teams Come From

School Based




Club Based


Probably after school or evening
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
After school, evenings, or weekends
We encourage you to find and include
youngsters that normally would not have this
exposure
8
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
9
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
10
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
11
You Need Adults, Too!

Coach – The person in charge



Mentor – The technical guru



Organizes the team
Does not need to be a techie
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
12
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
13
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”


“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


Includes Field Setup, Missions, and Rules
Generate and share an innovative solution to the Challenge theme
Core Values
Judging rubrics
14
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!
15
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
16
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
17
FIRST ® LEGO®
League 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.
18
Equipping Your Team
19
Minimum Resources to Start



A robotics kit
A computer with
Windows Vista, Windows 7, 8, or 10
Mac OS X 10.7(Lion) to 10.11(ElCapitan)
A place to meet and practice




Classroom
Family room
Garage
Community Room
20
Additional Materials


2015 FIRST ® LEGO® League “Hydro Dynamics”
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/sites/default/files/FLL-TableBuild.pdf (This design is probably overkill)
4’x8’ bottom
2x4 railing around the sides (extra 2x4 thickness on
one side for some Field Setup kit models)
21
Robotics Kit Info

LEGO® League EV3 -- $470
Only from FIRST®
FIRST





®
Complete kit with two tubs and sorting trays
EV3 software
Ship to registered teams starting in mid-May
See slide at end for other EV3 purchase
options
22
Allowed Robot Parts






EV3 controller (1)
EV3 motors (4)
As many sensors as you like but only from this
set – touch, light, color, rotation, ultrasonic, and
gyro
They must all be LEGO-manufactured
MINDSTORMS sensors
Note: The HiTechnic color sensor is not allowed
Be sure to check the rules for this year for
any changes
23
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
24
Let’s Take a Break
As your first hands-on exercise for this
workshop, your instructor will explain
the Can-Do challenge
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.
26
Loop Block

Some of you may find the Loop block
useful.
This means
go forever.
Robot goes forward 1 rotation and
then backward 1 rotation and
continues that forever.
27
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
28
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
29
Wait vs. Sensor Blocks
Wait block keeps
reading what the sensor
is measuring and does
not move to the next
block until the condition
called for is met.
Sensor block reads the
value seen by the
sensor and immediately
goes to the next block.
30
Review Program Flow
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.
31
Managing Your Team
32
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 ??
33
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
34
Parent Involvement

Explain program/FIRST
League philosophy






®
LEGO®
Success = Participation
Explain team rules (attendance, respect, ...)
Discuss participation commitment for
kids
Review costs and funding sources
Communicate about tournaments
Solicit help
35
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)
36
(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
37
(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
38
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
39
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)
40
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
41
Foundation: Divide and conquer

Three basic robot functions:

Locomotion: how the robot moves


Navigation: how it knows where to go


Concepts: motors, gears/pulleys, wheels/tracks, friction,
steering
Concepts: time, sensors (rotation, touch, light,
ultrasonic, gyro)
Robotic Action: function it performs

Concepts: pushing, grabbing, lifting , dumping
42
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
School
www.stemcentric.com
43
Foundation: Engineering
Design Process
44
Address the Challenge

Pick up all information about the challenge
from FIRST® website when details announced
on August 29th
Very important
 Missions
to get all the
 Rules
pieces!!
 Field setup
 Game Updates (grows during the season)
 Project – details on research project
 Core Values
45
Address the Challenge

Team must learn missions 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
46
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
47
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
48
Get It Done
Considerations:

Introduce “design rule” concept

Shared, agreed upon design constants e.g.





Programs need to share inputs/outputs
Attachments need to go together



Motors B/C drive and motor C is on right
Which end is ‘forward’
Light sensor is always in port ‘3’
Base robot with quickly interchangeable attachments, or
Attachments can’t interfere with those for other missions
Target being done early (time for debug/rebuild)
49
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
50
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
51
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
52
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
53
Final Advice

Keep Meetings Fun


Be flexible



Usually means hands on LEGO building every meeting
Help keep them on task, but ultimately it is their project
The journey is as important as the result (Another way to
phrase Core Value #4)
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
54
With All the Focus on
the Robot and the Challenge…
Don’t Forget the Judging
https://www.firstinspires.org/sites/default/files/
uploads/resource_library/fll/animal-allies/fllrubrics-2016.pdf
Robot Design Judging

Panel of “experts” interviews teams




Prepare the team to:




Mechanical: Durability, Efficiency, Mechanization
Programming: Quality, Efficiency, Navigation
Strategy & Innovation: Process, Strategy, Innovation
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
56
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), . . .
57
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
58
FIRST ® LEGO® League
Core Values Team Observations



Tournament officials observe teams during
tournaments at all activities
Looking for exceptional positive or negative
demonstrations of FIRST ® LEGO® League
Core Values throughout the day
Observations can impact a team’s score
either positively or negatively
Hand out FIRST ® LEGO® League Core
Values Team Observation sheets
59
FIRST ® LEGO® League
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.
60
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/
63
Names of Parts



Google: lego part names
guide.lugnet.com/partsref
shop.lego.com/pab (Pick a Brick)
64
Contact Us
Web site: http://www.ortop.org
Email: [email protected]
Phone: (503) 486-7622
65
Robotics Kit Info – Cont.

LEGO Education EV3 Core Set -- $389.95




https://education.lego.com/en-us/middle-school/shop/mindstormsev3
Fewer parts with one tub and sorting trays
Download software
LEGO Retail – $349.99




http://www.lego.com/en-us/mindstorms/products/31313mindstorms-ev3
No tubs
Fewer sensors
Download software
67
Differences between EV3 Kits
Part
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
Free Download
Free Download
Free Download
Sorting Trays
2 tubs
1 tub
No tubs
Part Count
1324
541
550+ elements
Price
$439
$389.95
$349.99
Software