Summary
Materials Needed
The following is a list of all the materials that are needed to complete the VEX GO Lab. These materials include student facing materials as well as teacher facilitation materials. It is recommended that you assign two students to each VEX GO Kit.
In some Labs, links to teaching resources in a slideshow format have been included. These slides can help provide context and inspiration for your students. Teachers will be guided in how to implement the slides with suggestions throughout the lab. All slides are editable, and can be projected for students or used as a teacher resource. To edit the Google Slides, make a copy into your personal Drive and edit as needed.
Other editable documents have been included to assist in implementing the Labs in a small group format. Print the worksheets as is or copy and edit those documents to suit the needs of your classroom. Example Data Collection sheet setups have been included for certain experiments as well as the original blank copy. While they offer suggestions for setup, these documents are all editable to best suit your classroom and the needs of your students.
Materials | Purpose | Recommendation |
---|---|---|
VEX GO Kit |
For students to build the Code Base 2.0 and possible additions for their project. |
1 per group |
Code Base 2.0 Build Instructions (3D) or Code Base 2.0 Build Instructions (PDF) |
For students to build the Code Base 2.0 if they have not already. |
1 per group |
Pre-built Code Base 2.0 |
From previous Labs. For students to test projects. |
1 per group |
For students to create and start projects on the Code Base. |
1 per group | |
Robotics Roles & Routines Google Doc / .docx / .pdf |
Editable Google Doc for organizing group work and best practices for using the VEX GO Kit. For students to build the Code Base if they have not already. |
1 per group |
Blueprint Worksheet Google Doc / .docx / .pdf |
Editable Google Doc for students to storyboard and plan their project. |
1 per group |
For the students to use VEXcode GO. |
1 per group | |
Lab 4 Image Slideshow Google Doc / .pptx / .pdf |
For teachers and students to reference throughout the Lab. |
1 for teacher facilitation |
Pencil |
For students to write and sketch ideas for their project plan. |
1 per group |
Measuring Tool |
For students to measure distances in their project plan for Play sections. |
1 per group |
To help remove pins or pry beams apart. |
1 per group | |
Get Ready...Get VEX...GO! PDF Book (optional) |
To read with students to introduce them to VEX GO through a story and introductory build. | 1 for demonstration purposes |
Get Ready...Get VEX...GO! Teacher's Guide Google Doc / .pptx / .pdf |
For additional prompts when introducing students to VEX GO with the PDF Book. | 1 for teacher use |
Engage
Begin the lab by engaging with the students.
-
Hook
Who remembers the three types of jobs that robots complete?
Connect this Lab to Lab 1, where students learned that robots do jobs that are dirty, dull, or dangerous. Show examples of different job scenarios.Note: If students are new to VEX GO, use the Get Ready...Get VEX...GO! PDF book and Teacher’s Guide (Google Doc/.pptx/.pdf) to introduce them to learning and building with VEX GO. Add an additional 10-15 minutes to your lesson time to accommodate this additional activity.
-
Leading Question
Now, we are going to choose a dirty, dull, or dangerous job scenario for our Code Base robot and plan our projects.
- Build Code Base 2.0
Play
Allow students to explore the concepts introduced.
Part 1
Students will choose a scenario and create a project plan using the Blueprint Worksheet. Students can include plans to build an addition to the Code Base robot using VEX GO pieces.
Mid-Play Break
Students will share their project plans in a class discussion.
Part 2
Students will create and start their projects. Students should identify what task their robots were asked to complete.
Share
Allow students to discuss and display their learning.
Discussion Prompts
- If a Code Base needed to complete this task multiple times, what could you add to the project?
- What if you didn’t know the exact distance that the Code Base needed to move forward? What could you add?
- What if the Code Base was facing the wrong direction to begin the project? What could you add?