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 |
---|---|---|
Pre-Built Code Base 2.0 from Lab 1 |
To use for demo in the Engage section. |
1 for demonstration |
Pre-Built extension from Lab 1 |
To use for demo in the Engage section. |
1 for demonstration |
VEX GO Kit |
For students to use VEX GO Kit pieces to attach the extension arm to the Code Base robot. |
1 per group |
Code Base 2.0 Build Instructions (3D) or Code Base 2.0 Build Instructions (PDF) |
For students to reference when attaching the extension arm to the Code Base 2.0. |
1 per group |
Data Collection Sheet Google Doc / .docx / .pdf
Lab 2 Example Data Collection Sheet Google Doc / .docx / .pdf |
For groups to document 3 trials of testing their project. |
1 per group |
For groups to use when coding their Code Base robot and extension arm. |
1 per group | |
For groups to use VEXcode GO. |
1 per group | |
Pencil |
To fill out the Data Collection Sheet, Robotics Roles & Routines worksheet and Engineering Design Process Organizer. |
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 |
Engineering Design Process Organizer (optional) Google Doc / .docx / .pdf |
For groups to plan how they will attach the extension arm to the Code Base robot. |
1 per group |
Lab 2 Image Slideshow Google Doc / .pptx / .pdf |
For the teacher and student to reference throughout the Lab. |
1 for teacher facilitation. |
To help remove pins or pry beams apart. |
1 per group |
Engage
Begin the lab by engaging with the students.
-
Hook
How can we attach our extensions to our Code Base to collect trash? Is there only one way to attach the two parts? Do you think I could get it on my first try? What VEX GO pieces could we use?
-
Leading Question
What do you do when you fail? Is failure ok? What coping strategies can we decide on today if we fail?
- Build Code Base 2.0 with extension
Play
Allow students to explore the concepts introduced.
Part 1
Students will create pseudocode for the extension arm and the Code Base robot to drive in a square.
Mid-Play Break
Have each group share their ideas for pseudocode. Engage constructive criticism and encourage students to listen to similarities and differences in their own pseudocode.
Part 2
Students will now take their pseudocode and create a project. Groups will implement it using VEXcode GO. The students will code their robot in a sequence using forward, backward, left, and right to drive their robot in a square. Students will get 3 trials to make any necessary adjustments.
Share
Allow students to discuss and display their learning.
Discussion Prompts
- How did you break the problem down into smaller parts? Was this helpful?
- How does pseudocode help with planning how the robot will move?
- Since you only have three attempts to test, why is planning better than doing a guess-and-check?