> For the complete documentation index, see [llms.txt](https://docs.wcrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wcrobotics.org/stem-camps/2021-camps/vexiq-camps.md). # VEX IQ Camps ## Schedule For more details, [click here](https://docs.google.com/presentation/d/e/2PACX-1vStZTudgbgdkTa496MSOEvdeuwtNGRL9O-lL7uDGRSg97DhYP71JdFhsWNf-UemnHK9w81d4l76It6A/pub?start=false\&loop=false\&delayms=3000\&slide=id.gd26b9cc14f_1_15). ![2021 STEM Camp Schedule (weeks 1-2)](/files/-MZjBRqheSomxSmE4qI4) ## Materials {% embed url="" %} ## Robot Olympics {% embed url="" %} VEX Resources for Robot Olympics Camp {% endembed %} ***Detailed Plans, based on VEX template (***[***Link to Google Doc***](https://docs.google.com/document/d/1YK0jnlj8ggt1TRsYjH26JBq6VIryLARMhVRkIwHDF0w/edit?usp=sharing)***):*** {% embed url="" %} ## Day 1 1. Students Install [VEXcodeIQ](https://chrome.google.com/webstore/detail/vexcode-iq/mgneogobocdccfjbdldekbjfdadhncol) on their Chromebooks. 2. Students build the **Autopilot** configuration with their kits. This may take about an hour. {% hint style="info" %} 3 ways to access the build directions: * Pamphlet included in each kit * [Online PDF](https://content.vexrobotics.com/vexiq/pdf/228-3428-750-Clawbot-IQ-Build-Instructions-Rev10-20150901.pdf) of complete build directions * [On this web page](https://education.vex.com/parent-wrapper-teacher.php?id=drive-forward-reverse), click Seek, then click Build Directions. {% endhint %} {% hint style="info" %} [Click here](https://education.vex.com/xyleme_content/drive-forward-reverse/web-teacher/66de2066-b255-45c7-93f0-1fa8483008b1.html) for suggested roles to build this in a group. {% endhint %} **After building:** 1. [Pair the controller](https://kb.vex.com/hc/en-us/articles/360035589752-How-to-Pair-the-VEX-IQ-Robot-Brain-with-the-VEX-IQ-Controller-for-Wireless-Operation) with the robot brain. 2. Students [practice driving](https://kb.vex.com/hc/en-us/articles/360035592512-Running-Driver-Control-Programs-on-the-VEX-IQ-Brain) the robot with the controller. 3. After practicing, students can compete in a few games of Robot Soccer! \ [Click here for the rules.](https://docs.google.com/document/d/1Zi9rH0NSSaCOM7qboZV0bSgdJFErXMyD2UbDA-US4Gw/edit#)\ Teachers, set up the field ahead of time. Use tape and tennis balls. 4. For the rest of today's time, complete the Level Up activities on page 2 of the rules for Robot Soccer. ### When there is 15 minutes left in the session: * Teacher may need to update the firmware in all kits, otherwise the programming abilities may not work on the Chromebooks. * Have the students plug everything from their kits into the brain. * Follow the [directions here](https://www.vexrobotics.com/iq/products/vexos) or in this video: {% embed url="" %} ## Day 2 {% hint style="info" %} Download the [VEXcodeIQ](https://chrome.google.com/webstore/detail/vexcode-iq/mgneogobocdccfjbdldekbjfdadhncol?hl=en-US) App on the Chromebooks so they can code. ***OR***\ If the chrome app doesn't load, use this website instead: {% endhint %} ### [Drive Forward and Reverse STEM Lab](https://education.vex.com/parent-wrapper-teacher.php?id=drive-forward-reverse) 1. Students already built the Autopilot robot yesterday, so they can jump straight to the "Play" section to begin programming. 2. In VEXcodeIQ on the Chromebooks, students click **File - Examples - Templates - Autopilot (Drivetrain)** 3. Follow the steps under the **Play** and then **Rethink** pages of the stem lab. ### [Turning STEM Lab](https://education.vex.com/parent-wrapper-teacher.php?id=turning) 1. Complete the **Play** and **Rethink** sections of the stem lab. 2. Emphasize how to save programs into one of the 4 slots in the brain. ### Extension: 1. Teacher sets up an obstacle course. Can students pre-program their robots to move from point A to point B while avoiding obstacles? 2. Which group can do it in the shortest time? 3. Can groups design an attachment to push/pull one or two tennis balls through the obstacle course? 4. Teams "joust" against one another: 1. Team A builds something to push a tennis ball forward (must be to the right of the robot) 2. Team B builds something that is supposed to knock the tennis ball out of Team A's robot. Could be designed to scoop, poke, or push the ball. 3. Both teams drive forward and see who wins the joust! {% hint style="info" %} Emphasize the Engineering Design Process! The more times you repeat the design/build/test process, the better your result! {% endhint %} ## Day 3 **Note:** Instead of aluminum soda cans, use the colorful plastic VEX blocks. ### [Speedy Delivery STEM Lab](https://education.vex.com/parent-wrapper-teacher.php?id=speedy-delivery-iq) 1. Students modify their robots into the Clawbot design. (recall the 3 ways to find buildig directions from day 1) 2. Complete the **Play** and **Rethink** (Package Dash) sections of the Speedy Delivery STEM Lab. Extension: 1. **Bonus Challenge:** Add sounds for when the robot is backing up and lights from the Touch LED to indicate when the robot has picked a package up and placed it in the loading dock. 2. **Increase complexity:** Add more packages (cans) that the robot must pick up! Multiple rounds can be played. ## Day 4 ### [Loop There it Is STEM Lab](https://education.vex.com/parent-wrapper-teacher.php?id=loop-there-it-is-iq) 1. Students complete the **Play** and **Rethink** sections. **Extension:** Add sounds from the brain and colored lights from the Touch LED to make your dance routine even more exciting! ### [To Do, or Not To Do STEM Lab](https://education.vex.com/parent-wrapper-teacher.php?id=to-do-or-not-to-do-iq) 1. Students complete the **Play** and **Rethink** sections. ## Day 5 ### [Clawbot with Controller STEM Lab](https://education.vex.com/parent-wrapper-teacher.php?id=clawbot-with-controller) 1. Students complete the **Play** and **Rethink** sections. ### [Robot Shot Put](https://docs.google.com/document/d/1LdLYjI1GxjuJ8wyV1pAHE29gqqtfN9P-zSL7DBx1qzY/edit#) ### [Robot Relay Race](https://docs.google.com/document/d/1XHgEAQohA1WZY1Hg_qisEtaq2DSStf3cQEfsuVQvq4w/edit#) ## Notes from 2021 Camp ### Week 1 * Day 1: Build the autopilot configuration and drive with the controller * Day 2: Program the autopilot to drive through a maze * Day 3: Build the Clawbot and drive it with the controller. Have a competition! Race to grab more blocks than the other group (hungry hungry hippos) * Day 4: For the first hour, some students finish building their clawbots. Some students can choose to program their clawbot to navigate a maze. Others can compete in hungry hungry hippos. ### Week 2 * Day 1: Build the autopilot configuration (most groups finished). For the last 45 minutes or so, play a game: * Four robots start out in a corner of a large square. Three tennis balls are placed in the middle of the arena. The object of the game is to push a tennis ball into an opponent's corner. If a ball reaches your corner, you're out. Play 1-minute matches, anyone who's out sits out the next game so new teams can join. The matches are quick so that if you lose, you can re-join soon. * Optional: Add blocks to the middle of the arena as obstacles. * Optional: Teams can build attachments to the front of their robots to make it better at pushing the tennis balls. * Day 2: Finish building the autopilot, or at least add the Gyro sensor (it just has to be vertical). Learn how to code so the robots can navigate various mazes. * Day 3: Build the Clawbot! Some groups may not completely finish, and will need to finish at the begining of day 4. * Day 4: Finish building clawbots, Hungry Hungry Hippos and other games with the clawbots! * Day 5: Part 1 - Program the clawbots to navigate mazes. Part 2 - Modify the clawbots to carry as many cubes as possible. Compete in the arena to collect as many cubes as you can! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.wcrobotics.org/stem-camps/2021-camps/vexiq-camps.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.