> For the complete documentation index, see [llms.txt](https://wiki.purduesigbots.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.purduesigbots.com/software/competition-specific/operator-control.md). # Operator Control The **operator control** phase is the second half of a VEX Robotics Challenge match, where human drivers take control using a [VEX Joystick](/vex-electronics/vex-electronics/vex-joystick.md). In high school, this phase lasts for the lion's share of the game (1 minute and 45 seconds of the 2 minute match), but in VEX U, this mode is shortened to 1 minute and 15 seconds. Some rules of the game may change during this period, in an effort to encourage new strategies or place a bonus on scoring during the Autonomous Period. ## Dynamics Autonomous code seldom continues into the operator control phase, but small [scripted portions](/software/general/finite-state-machine.md) and [PID controllers](/software/control-algorithms/pid-controller.md) are often implemented to manage low-level tasks such as supporting an arm or running an intake. Parity among teams during this period is largely related to the skill of the drivers, obtained mostly through accumulated on-field practice time. Attending practice competitions and getting quality time on the field with a finished robot makes big payoffs during this phase. Near the end of the match, a special scoring element usually comes into play. Examples of this would include the Negation Barrel in VEX Gateway, the Parking Bonus in VEX Sack Attack, and the Hanging Bonus in VEX Toss Up. ### Contributing Teams to this Article: * [BLRS](https://purduesigbots.com) (Purdue SIGBots) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://wiki.purduesigbots.com/software/competition-specific/operator-control.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.