> For the complete documentation index, see [llms.txt](https://docs.gremsy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gremsy.com/gimbals/aevo/gimbal-configuration/rotation-limit.md).
# Rotation Limit
Travel of Tilt and Roll axis can be limited using UP LIMIT and DOWN LIMIT. The Pan axis keeps the ability to pan 360 degrees itself.
**UP LIMIT**
* Set the up limit for Tilt or Roll axis (in 1 degree unit). The default values are -90 for Tilt and -45 for Roll.
**DOWN LIMIT**
* Set the down limit for Tilt or Roll axis (in 1 degree unit). The default values are 90 for Tilt and 45 for Roll.
**ROLL OFFSET**
* Set the Roll offset (in 0.1 degree unit) is only applicable when there is no remote control signal since remote control will override the roll angle. This is useful to fine trim the horizon. The default value is 0.
---
# 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://docs.gremsy.com/gimbals/aevo/gimbal-configuration/rotation-limit.md?ask=&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.
