> 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/v2.11/color-radios/model-settings/model-setup/throttle.md).

# Throttle

<figure><img src="https://content.gitbook.com/content/2n2y0XsJcrhXt3asceP0/blobs/Pmy5X0jfPp0RxRsWXlwh/throttle.png" alt=""><figcaption><p>Throttle page settings</p></figcaption></figure>

EdgeTX has to possibility to select a specific source and trim for the model throttle and allows for the following configuration options:

**Reverse:** When enabled, this option reverses the output direction of the configured throttle channel.

**Source:** The source that will be used for the throttle.

**Trim idle only**: When enabled, the throttle trim will only affect the bottom portion of the throttle band.

{% hint style="info" %}
For example, with **Trim idle only** enabled, the throttle stick at the lowest point might have a value of -80 and the center point will still be 0 and the highest point of 100. Without this enabled, the throttle stick at the lowest point might have a value of -80 however, the center point will be 20 and the highest point of 100.
{% endhint %}

**Trim switch:** The trim switch that will be used to trim the throttle. It is possible to substitute the throttle trim switch with the aileron, rudder, or elevator trim switches.


---

# 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/v2.11/color-radios/model-settings/model-setup/throttle.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.