> 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/follow-mode-settings.md).
# Follow Mode Settings
The most widely used mode of single operation is Follow mode where the gimbal operator controls to pan and tilt of the camera. The camera movement will mimic the user’s input from the top-mount while the footage remains stable. The follow mode can be configured to be either very linear and robotic, or smooth and cinematic.
Follow mode settings is available for Tilt axis and Pan axis.
**SPEED**
Defines how fast camera will follow the movement.
**SMOOTH**
Smooth out the camera movement by adjusting this parameter. The higher the value is the smoother camera moves but at the expense of more delay in following the movements.
**WINDOW**
When the movement is out of the window zone, the camera starts to move. Within the window zone, the camera maintains its direction.
**TILT LOCK**
If this option is selected, the tilt axis will maintain its angle and only be controlled by remote control.
**AIRBORNE**
This feature is not available on the T7.
---
# 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/follow-mode-settings.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.
