> 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/team-administration/hosting-competitions/tournament-manager/competition-electronics.md).

# Competition Electronics

There are two key electronics sold by Vex to support field control and competitions:

![](https://3510336827-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M7yGVyBrcpSR8SDSikj%2Fuploads%2FagTJx05Fk3CBBE2tJK2e%2FField%20Electronics%20Cropped.png?alt=media\&token=ae85f5cf-ff45-4766-930b-9617c78b4785)

The Match Controller is used to interface between a computer running Tournament Manager and the competition field. One is needed for each field and should be placed alongside the field. The Driver Interface is used to connect teams to the field setup. The teams connect their V5 controllers to the VEXnet port. The 2 match controllers at each field (one for each alliance) are connected to the Match Controller through CAT5 cables.

![Example field setup](https://3510336827-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M7yGVyBrcpSR8SDSikj%2Fuploads%2FnrxUasHvA4nclcNUXrrZ%2FExample%20Field%20Electronics%20setup.png?alt=media\&token=4dca9252-61b2-47d8-ae91-f2cdad60fc0e)

Above is an example field setup for a small competition. It is physically very straight forward when at a small scale. The lines above represent the only cable that are required to run the match. This however does not show any displays for the competitors and audience, as well as other fields including skills fields. Much of this requires a network to be setup instead of running display cables directly from the main computer.


---

# 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/team-administration/hosting-competitions/tournament-manager/competition-electronics.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.