Skip to main content
Teacher Portal

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 - Eye Down. 1 per group

Tablet or Computer

 For students to use VEXcode GO. 1 per group

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

Code Base 2.0 - Eye Down Build Instructions (3D) or Code Base 2.0 - Eye Down Build Instructions (PDF)

 To add the Eye Sensor to the Code Base 2.0 Build. 1 per group

VEXcode GO

 For students to download and run a VEXcode GO project to view and collect Eye Sensor Data. 1 per group

Robotics Roles & Routines

(Google Doc / .docx / .pdf)

 For organizing group work and best practices for using the VEX GO Kit. 1 per group

Lab 2 Image Slideshow

(Google / .pptx / .pdf ) 

 For visual aids while teaching. 1 for the class to view

Bridge Inspection Report 

(Google Doc / .docx / .pdf )

For students to record data during the Play section.

Note: Students will only need the first four pages of the report for this Lab. Students will use the remaining pages in Lab 3.

 1 per group

Printing Data VEXcode GO Project

 To be downloaded and run to collect data from the bottom of the bridge in the Play section of the Lab. 1 per group.

Pencils

 For students to record data and complete the Robotics Roles & Routines sheet and the Bridge Inspection Report. 1 per student

VEX GO Field Tiles

 To create the bridge for each group. 1 per group

VEX GO Kit Boxes, or Several Books

 To create the supports for the Field Tile to rest on. 4-6 per group

Pin Tool

 To help remove pins or pry beams apart. 1 per group

Engage

Begin the lab by engaging with the students.

  1. Hook

    Set the scene that students will be Bridge Inspectors today. Explain that they are part of the Vexville Bridge Commission, and they have just received a claim that a bridge is cracked and may be unsafe!  They will inspect the bridge by collecting hue value data with the Eye Sensor, to determine if the claim is true. Talk about the bridge safety criteria, and ask students how they think it could be used to determine if the claim of a dangerous crack in the bridge is true or not.

  2. Leading Question

    What if we needed to collect data with the robot to determine if the claim about the crack in the bridge is true or not? How do you think we could use the data with the bridge safety criteria about the location of cracks to test the claim? 

  3. Build Code Base 2.0 - Eye Down

Play

Allow students to explore the concepts introduced.

Part 1

As bridge inspectors, students will gather distance and hue value data using the Print Console in VEXcode GO. To do this, students will open an run the Printing Data project (linked in the Materials List above), which will print data about the bottom of the bridge at regular intervals. This project should be downloaded to student devices prior to beginning the Play section of the Lab.

Note: The goal is for students to view and use the data that is printed to the Print Console in their reports, not to learn the coding concepts within the project. Students do not need to understand how the project is constructed in order to complete the Lab activities. The focus of the Lab is on the data the project produces, not the project itself.

Mid-Play Break

Students will discuss what they notice about the data that was printed to the Print Console in VEXcode GO during Play Part 1. They will discuss whether or not the data indicates a crack present in the bridge.

Part 2

Students will graph the data from the Print Console in their Bridge Inspection Reports. They will analyze their data by comparing it to the bridge safety criteria about the location of cracks, to determine if the data indicates that the bridge may be dangerous. 

Share

Allow students to discuss and display their learning.

Discussion Prompts

<  Back Return to Labs Next  >