> 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/motor-controller.md).

# VEX Motor Controller

The VEX Motor Controller is a device which converts a standard logic-level PWM servo control signal into motive power to drive a Motors.

{% hint style="danger" %}
This article is only relevant for old VEX Cortex system, which is no longer competitive.
{% endhint %}

![](https://phabricator.purduesigbots.com/file/data/etrlal4uipuwqzvaacuf/PHID-FILE-qlxacu4e34tv6ajfqnyf/vex_motor_controller.jpg)

A motor controller is not required for the [VEX Cortex](/vex-electronics/legacy/vex-cortex.md) ports 1 and 10.

The VEX Motor Controller performs the function of an ***H-Bridge***. Its FETs, or power output transistors, have a low enough ON resistance to not heat appreciably, even when controlling a [stalled](/electronics/general/stalling.md) motor. VEX Motor Controllers add an additional 24 inches of wire onto a motor, which can be a blessing to avoid a PWM extender or a curse when managing short wire runs.

VEX Motor Controllers are driven using a standard hobby servo control scheme, with a 1 ms pulse running full reverse, a 1.5 ms pulse stopping the motor, and a 2 ms pulse running full forward. A non-standard 200 us pulse will engage an active brake. These pulses typically appear on a 20 ms (50 Hz) duty cycle, but faster update rates up to 300 Hz may be possible with [PROS](/software/vex-programming-software/pros.md).

## Teams Contributed 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/vex-electronics/legacy/motor-controller.md?ask=<question>&goal=<user_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.