> 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/tiny-gimbal/g-hadron/ethernet-telemetry-payload-control.md).
# ETHERNET TELEMETRY PAYLOAD CONTROL
G-hadron supports control over Ethernet telemetry. Please update to the latest firmware and follow the following instructions:
### **Setup with Herelink**
**In this example:**
* Using Ethernet telemetry to control G-Hadron (gimbal and camera).
* Using HDMI to do video streaming from Zio to QGroundControl.
**Setup on QGroundControl App**
**1. Disable all AutoConnect in General**
**2. Navigate to Comm Links, add new Comm Link for Ethernet telemetry**
**3. Create the new link as following**
**On the above example:**
```
Name: Zio
Type: UDP
Listening Port: 14565
Target Hosts: 192.168.144.200:14565 (Zio's IP)
```
**4. Check the new Ethernet connection**
* Connect the HDMI to Herelink v1.1
* Video Stream info will show as below after configuring successfully
**(Do not change)**
```
Video Source: RTSP Video Stream
RTSP URL: rtsp://192.168.55.100:8554/ghadron
Aspect Ratio: 1.777777
```
**Successful connection**
Receive On the PC using VLC:
* Goto Media -> Open Network Stream
*
Receive On the PC using Gstreamer
{% hint style="info" %}
gst-launch-1.0 rtspsrc latency=0 location=rtsp\://192.168.144.25:8554/ghadron ! decodebin ! videoconvert ! autovideosink sync=false
{% endhint %}
Configure video streaming settings
{% content-ref url="/spaces/nikHUDUd2JXqkOsnOi7l/pages/1OnJsNY2owsv8UVQDb48" %}
[PAYLOAD WEB SERVER](/tiny-gimbal/g-hadron/payload-web-server.md)
{% endcontent-ref %}
---
# 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/tiny-gimbal/g-hadron/ethernet-telemetry-payload-control.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.
