> 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/payloads/general/gremsy-payload-control-type/control-mode.md).
# CONTROL MODE
#### There will be two different control mode based on the Mavlink protocol
Settings on the Camera Settings - QgroundControl when you connect the Gremsy Payload.
## 1. Standard RC Mode
* The control signal will be sent directly to gimbal via RC in the MAVlink-out protocol
* The user can control 3 axis of gimbal by using 3 RC channels independently
## 2. Gremsy RC Mode
* In this case, the user only have a dial wheel to control gimbal and a button to select which axis will be controlled.
* In this mode, the PAN signal will be used to control TILT or PAN axis depending on the selection change by TILT signal (assign to a button).
* The ROLL axis is always '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/payloads/general/gremsy-payload-control-type/control-mode.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.
