> For the complete documentation index, see [llms.txt](https://manual.edgetx.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.edgetx.org/bw-radios/model-select/inputs-mixes-and-outputs.md).

# Inputs, Mixes & Outputs

To be able to support many different types of radio transmitters, EdgeTX uses a generic control data flow that can be applied to any radio transmitter. In this data flow, any of the radio's physical controls (sticks, switches, sliders, pots) can be mapped to an input in the software. These inputs can be directly assigned or combined with other inputs into a single mix. These mixes can be modified by applying weights, offsets, and curves and are then assigned a channel for output. Final adjustments to the control data are made (including subtrims, curves, endpoint, and center values) before finally sending the control data to the RF module. The flowchart below depicts a visual summary of this control data flow. Detailed information about the flow is provided in the following sections [Inputs](/bw-radios/model-select/inputs-mixes-and-outputs/inputs.md), [Mixes](/bw-radios/model-select/inputs-mixes-and-outputs/mixes.md), and [Outputs](/bw-radios/model-select/inputs-mixes-and-outputs/outputs.md).

<figure><img src="https://content.gitbook.com/content/P2t2HC29IiiujobytzG7/blobs/iQcHWwwkwsW7f8j3UnOS/inputflow.jpg" alt=""><figcaption><p>Control data flow</p></figcaption></figure>


---

# 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://manual.edgetx.org/bw-radios/model-select/inputs-mixes-and-outputs.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.