Coder

As a Coder for the VEX IQ Robotics Competition, you are responsible for writing the instructions that tell the Robot’s "Brain" how to function.

1. The Student-Centered Coding Rule

The most important rule is that you must be the one writing the code.

• Student Ownership: All final code used in the competition must be your work. Adults can help you programming concepts or guide you through a flowchart to understand logic, but they are not allowed to write code or provide premade commands for you to copy and paste.

• No AI Assistance: You are prohibited from using Large Language Models (like AI) to create or improve your competition code.

• Explaining Your Work: You must be able to explain every part of your code to judges or event staff. You should even be able to recreate similar code on the spot if asked to prove it represents your actual skill level.

• Using Templates: It is okay to start with VEX "Hero Bot" code or public libraries, but you are encouraged to modify and improve them as you learn.

2. Technical Requirements

Your code must work within the limits of the VEX IQ hardware:

• The Brain: You are limited to using one VEX IQ Robot Brain.

• Motors: You can program a maximum of six VEX IQ Smart Motors.

• Firmware: Your Robot’s Brain must be updated to the correct firmware version (VEXos 2.2.1 or newer for Gen 1; 1.0.8 or newer for Gen 2).

• Sensors: You are encouraged to use sensor feedback (like motor encoders or the Vision Sensor) to help the Drivers control the robot more accurately.

3. Coding for Different Match Types

You need to write programs for two very different types of gameplay:

• Teamwork Matches: These are mostly controlled by Drivers, but you can write pre-programmed routines to help them. Important: If your team only has one Drive Team Member present, the Robot must stop all operation (including your code) after the first 35 seconds of the match.

• Autonomous Coding Skills Matches: This is a 60-second match where the Robot runs entirely on your code with no human help.

  • You must start the program by pressing a button on the Brain or triggering a sensor.

  • You are not allowed to use the Controller to start or run the robot during these matches.

4. Safety and Fair Play

• End of Match: All Robot movement must cease exactly when the timer reaches zero. If your code causes the Robot to keep moving after the match ends, any points scored during that time will not count, and you will receive a violation.

• No Interference: Your code should not be designed to intentionally damage the field or other Robots.

5. Collaboration and Documentation

• One Team Only: You can only write code for one team per season. You cannot "switch" teams just to program multiple Robots.

• The Notebook: Work with your team’s Notebookers to document your build process, including how you tested the build and how decisions were made for fixing things that didn't work.