> 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/gremsy-tiny-series/lynx/third-parties-integration/mavlink-autopilot.md).

# MAVLINK AUTOPILOT

#### **Gremsy Payload Integration with Mavlink-based Autopilot Systems**

**Integration Capabilities**

Gremsy payloads support standard communication protocols to interface smoothly with Pixhawk systems, including:

* **MAVLink v2 Protocol**: Compatible with popular firmware such as PX4 and ArduPilot. The payload can receive and respond to gimbal control commands from the autopilot, including angle control, ROI (Region of Interest) tracking, and camera navigation along waypoints.
* **UART/Serial Communication**: Gremsy gimbals offer UART ports for direct communication with the flight controller. Baud rate and protocol settings can be configured to match the specific autopilot setup.
* **Ethernet Interface**: Enables high-speed, low-latency communication for advanced use cases:
  * **UDP Protocol** for real-time gimbal and camera control commands from onboard computers or ground stations.
  * **RTSP (Real-Time Streaming Protocol)** for live video streaming from the payload camera to ground control software or network video recorders.

## General Hardware Connection

1. **Flight Stack without onboard computer**\
   E.g: Cube Pilot, Pixhawk series with Herelink v1.1 remote<br>

   <figure><img src="https://3309772875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnikHUDUd2JXqkOsnOi7l%2Fuploads%2FT0rvDN3tWOZCWq2KVBFm%2Fimage.png?alt=media&amp;token=f4406d26-df9f-48d8-8d30-fb0c664ee35d" alt=""><figcaption></figcaption></figure>
2. **Flight Stack with onboard computer built-in**\
   E.g: Skynode, VOXL2 with Herelink v1.1

<figure><img src="https://3309772875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnikHUDUd2JXqkOsnOi7l%2Fuploads%2FM7S6bHmvv67V1we0By2j%2Fimage.png?alt=media&amp;token=033a6626-cb0e-4bd1-8704-d63cc592a423" alt=""><figcaption></figcaption></figure>


---

# 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/gremsy-tiny-series/lynx/third-parties-integration/mavlink-autopilot.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.