> For the complete documentation index, see [llms.txt](https://doc.open-tx.org/manual-for-opentx-2-2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.open-tx.org/manual-for-opentx-2-2/advanced-features/managing-throws.md).

# Managing Throws

There are two main things to consider when managing throws for a particular control surface.

They are:

* How far can the control surface physically travel?
* How far do you want it to travel?

There are several choices that can be made to resolve these issues:

* Use the [Outputs](/manual-for-opentx-2-2/software-overview/model_menus/outputs.md) screen to **limit** what is output by the radio.
* Use a [Curve](/manual-for-opentx-2-2/software-overview/model_menus/curves.md) in the [Inputs](/manual-for-opentx-2-2/software-overview/model_menus/inputs.md) screen.
* Use a [Curve](/manual-for-opentx-2-2/software-overview/model_menus/curves.md) in the [Mixer](/manual-for-opentx-2-2/software-overview/model_menus/mixer.md) screen.

## Using Outputs to limit travel

Using the Outputs screen is the simplest and most direct way to limit actual travel of the control surface.

For example, if you only want the aileron to travel a maximum of 50% and have the stick be able to travel the entire distance of its physical movement, just change the Min and Max numbers to 50.

![](/files/-MRzpNyb3YkhfavGQ1i6)

There is no way to assign a switch to to this setting, however, and the limits will apply to all flight modes.

A good example for when you would use this method is that even though an elevator could physically travel a full inch, doing that may make the plane behave badly and out of control.

Setting Outputs limits would reduce the possibility of the elavator traveling too far no matter what you put into the Inputs or Mixer screens.

Additionally, It is considered good pratice to set the physical limits using Outputs as it reduces the chance of accidently damaging the model while setting up Inputs and Mixers .

## Using a Curve in the Inputs/Mixer screen

You can achieve the same results as above by setting up a linear "curve" that looks like this:

![](/files/-MRzpNycgUgU7e_BQ836)

Both of the above setups will produce something that will look something like this:

![](/files/-MRzpNyduMBHYQW9cWEl) ![](/files/-MRzpNyeV6q4-lKVjFzF)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.open-tx.org/manual-for-opentx-2-2/advanced-features/managing-throws.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.