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 to create the gates on the slalom course. |
1 per group |
VEX GO Tiles and Walls (or other classroom materials) |
To create the slalom course. |
4 Tiles and 8 Walls per slalom course |
Code Base 2.0 Build Instructions (3D) or Code Base 2.0 Build Instructions (PDF) |
For students to follow to build the Code Base 2.0. |
1 per group |
For students to use VEXcode GO. |
1 per group | |
For students to drive the Code Base. |
1 per group | |
For teachers and students to reference throughout the Lab. |
1 for teacher facilitation | |
To help remove pins or pry beams apart. |
1 per group | |
Editable Google Doc for organizing group work and best practices for using the VEX GO Kit. |
1 per group | |
Pencils |
For students to fill out the Robotics Roles & Routines Checklist. |
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 (optional) Google / .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
What challenges did you face when driving the Code Base with the remote control in the previous Lab? If we wanted to make the Code Base move the same way every time, would the remote control be successful? Discuss how coding the Code Base instead of using the remote control can make Code Base’s movements more accurate and repeatable.
Note: If students are new to VEX GO, use the Get Ready...Get VEX...GO! PDF book and Teacher’s Guide (Google / .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
How can we use code to drive the Code Base?
- Build Code Base 2.0
Play
Allow students to explore the concepts introduced.
Part 1
Students will open, name, save, and Start the ‘Drivetrain Moves and Turns’ example project in VEXcode GO to observe the Code Base’s behaviors of driving and turning. Students will then be shown how to access the Help feature in VEXcode GO to learn more about blocks from the Drivetrain category. Students will then experiment with changing parameters in the example project and re-starting it to observe how the changes affect the movement of the Code Base.
Mid-Play Break
Discuss the changes students made to the example project and how it affected the movement of the Code Base.
Part 2
Students will use the blocks they learned about from the example project to create a new project that moves the Code Base through the beginning of the slalom course from Lab 1.
Share
Allow students to discuss and display their learning.
Discussion Prompts
- What were the differences between driving the Code Base using the remote control versus coding?
- Which method (using the remote control versus coding) was more accurate?
- Which method was more repeatable?
- What changes did you make to your project in order to navigate the slalom course?