> 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/vex-electronics/legacy.md). # Legacy - [VEX Cortex](https://wiki.purduesigbots.com/vex-electronics/legacy/vex-cortex.md): The VEX Cortex is the older microcontroller that was used in VRC and VEXU - [Power Expander](https://wiki.purduesigbots.com/vex-electronics/legacy/power-expander.md): A VEX Power Expander is a device which allows up to four of the VEX Motors on a robot to run from a second VEX Battery while still under the control of the VEX Cortex or VEX PIC. - [VEX Motor Controller](https://wiki.purduesigbots.com/vex-electronics/legacy/motor-controller.md): The VEX Motor Controller is a device which converts a standard logic-level PWM servo control signal into motive power to drive a Motors. - [VEX Cortex Wiring Guide](https://wiki.purduesigbots.com/vex-electronics/legacy/legacy-wiring-guide.md): This guide provides general wiring tips for the legacy cortex system. --- # 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/vex-electronics/legacy.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.