VEX GO - Mars Rover-Surface Operations - Unit Overview

Grades

3+ (Ages 8+)

Time

40 minutes per lab

Unit Essential Question(s)

How do I solve a challenge with the Code Base and VEXcode GO?

Unit Understandings

The following concepts will be covered throughout this Unit:

How students can work together with VEXcode GO and a Code Base to solve problems.
How to create a plan that correctly orders behaviors in a sequence to solve a challenge. This can be done both individually and collaboratively.
How to communicate behaviors, through words and gestures, that the Code Base will need to execute in order to accomplish a task.

Lab Summary

Click on the following tabs for a summary of what the students will do and learn in each lab.

Lab 1 - Collect a Sample

Main Focus Question: How can I drive my Code Base to an object?

Students will discuss what they know about Mars and how scientists can learn more about the Red Planet. They will build the Code Base - LED Bumper Top, to act as the Mars rover.
Students will then build a project in VEXcode GO, together with their teacher, to drive and collect a sample with the Code Base.
Students will then add blocks to their projects to turn the Code Base around and drive it back to the base. As students test their projects, they will place a small object, like an eraser, on top of the Code Base, to represent the sample, when the robot pauses to collect it.

Lab 2 - Collect and Bury Mission

Main Focus Question: How can I drive my Code Base to multiple objects?

Students will start by discussing things they know that change over time and connect those to testing on Mars. They will walk through building a VEXcode GO project together as a class to drive the Code Base to collect a sample, return to the base, and "bury" the sample.
In the Play section, students will be challenged to create a project where the Code Base drives to collect a sample, returns to the base, and "buries” the sample three times.
Because groups will approach this problem in different ways, students will share their projects and explain why they chose that path and that code for their Code Base.

Unit Standards

Unit Standards will be addressed in every Lab within the Unit.

Computer Science Teachers Association (CSTA)

CSTA 1A-AP-10: Develop programs with sequences and simple loops, to express ideas or address a problem.

How Standard is Achieved: In Lab 1, students will build a VEXcode GO project to drive the Code Base to collect and return a sample. They will need to sequence the project so that the Code Base drives to the location, signals that the sample is being collected by having the LED Bumper Sensor glow red for 3 seconds. After the sample is collected, the LED will stop glowing, the Code Base will turn around and drive back to the base to return the sample. The LED Bumper Sensor will glow red again for 3 seconds to indicate that the sample is being returned.

In Lab 2, students will build a project in VEXcode GO to drive the Code Base to collect and return three samples. They will develop projects using a sequence so that the Code Base drives to a location, collects a sample, has the LED Bumper Sensor glow red as it collects the sample, returns to the base, drops off the sample, and the LED Bumper Sensor glows red again indicate the sample has been "buried."

Common Core State Standards (CCSS)

CCSS.ELA-LITERACY.L.3.6: Acquire and use accurately grade-appropriate conversational, general academic, and domain-specific words and phrases, including those that signal spatial and temporal relationships.

How Standard is Achieved: In Lab 1, students will describe the intended movement of the Code Base using spatial language as they build their VEXcode GO project. After testing the project, students will explain how the Code Base moved, and compare that to the intended behaviors.

In Lab 2, students will create a VEXcode GO project where the Code Base collects three samples at different locations. As they build their projects, they will be asked to explain, using accurate spatial and sequencing language, how they want the Code Base to move in order to complete the task. After testing the project, students will compare how they intended the Code Base to move and how the robot actually behaved.

< Return to Labs Next >