> 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/pixy-lr/set-up-with-px4.md).

# Set up with PX4

## Hardware Setup

Connect the Pixy LR UART (CTRL port) to the Telem2 on the PX4 system

<figure><img src="https://3309772875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnikHUDUd2JXqkOsnOi7l%2Fuploads%2FVZgikDqM2Q8bxEvxv4nJ%2Fimage.png?alt=media&amp;token=94889492-23ae-4af6-b6c9-94bc84b142e6" alt="" width="563"><figcaption></figcaption></figure>

## Setting on the remote control

Pixy LR is compatible with the Remote Control (RC) that supports the QGroundControl app (QGC). In this manual, all settings are made on **Herelink Remote Control;** the other controller does the same.

### SBUS channel settings

Pixy LR needs to set up 2 channels to control the gimbal: one channel is for controlling **rotation**, and the other is for choosing the controlling **axis.**

### Set up channels controlling the gimbal

Gimbal rotation control channel: CH6 (or any channels); use the wheel button on the Herelink remote:

<figure><img src="https://3309772875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnikHUDUd2JXqkOsnOi7l%2Fuploads%2FGRnxbEwyiYqB4duNwi07%2Fimage.png?alt=media&amp;token=521c3a5f-6b9b-4542-997e-694fce7502ad" alt=""><figcaption></figcaption></figure>

Gimbal axis selection channel: CH8 (or any channels); use the camera button on the Herelink remote.

<figure><img src="https://3309772875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnikHUDUd2JXqkOsnOi7l%2Fuploads%2Fmzcbeqc4aD7qMQufQcs9%2Fimage.png?alt=media&amp;token=0c314c98-f927-4029-b6b2-2d2e3d7b1275" alt=""><figcaption></figcaption></figure>

## Setting parameters

### Firmware Requirement

• Version: update to the latest version.\
• Support Mavlink v2 protocol

{% embed url="<https://github.com/Gremsy/PixyLR-Firmware/releases/latest>" %}

### Set up the telemetry baud rate

Pixy LR connects to FC at the baud rate of **115200**. In case of connecting Pixy LR to FC at any telemetry, note the telemetry setting at the corresponding baud rate.&#x20;

**Example for telemetry 2:**

• MAV\_1\_CONFIG: “TELEM 2”\
• SER\_TEL2\_BAUD: “115200 8N1"\
• MAV\_1\_FORWARD: "1"

### Set mount parameters

• MNT\_MODE\_IN: “RC”\
• MNT\_MODE\_OUT: “Unknown: 2”\
• MNT\_RC\_IN\_MODE: “1”\
• MNT\_MAN\_PITCH: “AUX3” // PAN/TILT choose axis\
• MNT\_MAN\_ROLL: “AUX2” // Zooming, High: Zoom in, Neutral: Stop, Low: Zoom out (current: only using mode control by angle)\
• MNT\_MAN\_YAW: “AUX1” // PAN/TILT move\
• COM\_RC\_IN\_MODE: “Unknown: 3”

### Set RC map channels

• RC\_MAP\_AUX1: “Channel 6” // set channel 6 to AUX1 (Yaw)\
• RC\_MAP\_AUX2: “Channel 7” // set channel 7 to AUX2 (Roll)\
• RC\_MAP\_AUX3: “Channel 8” // set channel 8 to AUX3 (Pitch)


---

# 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/pixy-lr/set-up-with-px4.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.
