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 extension. |
1 per group |
Lab 3 Image Slideshow Google Doc / .pptx / .pdf |
For visual aids to reference while teaching. |
1 for teacher facilitation |
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 not already built. |
1 per group |
Pre-built extension from previous Lab |
To collect trash by being attached to the Code Base robot. |
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. |
1 per group |
Data Collection Sheet Google Doc / .docx / .pdf
Lab 3 Example Data Collection Sheet Google Doc / .docx / .pdf |
For groups to document three trials of testing their code. |
1 per group |
Software for students to code the Code Base robot. |
1 per group | |
For groups to use VEXcode GO. |
1 per group | |
Pencils |
For students to fill out the Robotics Roles & Routines Worksheet and Data Collection Sheet. |
1 per group |
Pieces of “trash” |
Classroom items to be used as “trash” such as pom poms, erasers, crayons, etc. |
6 per group |
Tape |
To outline the challenge course for the Play section. |
1 per group |
Timer |
To use in the timed trials in Play Part 2. |
1 per group |
Measuring Tool |
To create a challenge course and for determining distances in pseudocode and projects. |
1 per group |
To help remove pins or pry beams apart. |
1 per group |
Engage
Begin the lab by engaging with the students.
-
Hook
It’s showtime! Ask students to examine the extension that they built in previous labs in this unit. How can you improve the build to collect more trash?
-
Leading Question
Looking at the example challenge course, what do you think your plan will be for how your robot will move?
- Build Code Base 2.0 with extension
Play
Allow students to explore the concepts introduced.
Part 1
Students will code their robot to complete a challenge course to collect pieces of “trash” inspired by ocean cleaning robots. Students will first write pseudocode to plan their project, then use their pseudocode to create a project that navigates the Code Base through a challenge course.
Mid-Play Break
Discuss student progress together, asking questions like: How did creating pseudocode help with creating your project? What worked with your project, and what didn’t? How did you use the mistakes to revise your project?
Part 2
Students will run test trials and document their results in order to improve their projects with each trial.
Share
Allow students to discuss and display their learning.
Discussion Prompts
- Did your robot move as you intended?
- What did you do to make changes to your plan?
- Were the behaviors of the other teams’ robots similar to your team’s robot? How were they similar? How were they different?
- What blocks did you use and why?