> For the complete documentation index, see [llms.txt](https://docs.cubepilot.org/user-guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cubepilot.org/user-guides/cubepilot-ecosystem/cubepilot-partners/union-robotics/herelink-blue/herelink-blue-user-guide/air-unit/air-unit-interface-and-installation.md).

# Air Unit Interface & Installation

## Connector Inputs

![](/files/gR4cb4WMFeua9mItclah)

1. HDMI 2: Micro HDMI, for video input
2. HDMI 1: Micro HDMI, for video input (preferred)
3. Power: 6V - 12.6V max (3s Lipo supported) power input *\*avoid sharing BEC with servos*
4. Micro USB: For debug or upgrade, support OTG
5. Pair/Reset: For pairing and rest
6. LED 1,2: To indicate pairing status and transmission status
7. UART: 3.3V / 5V UART
8. S.bus: Tow 3.3V RC output
9. Antenna 1,2: MMCX, for signal transmission and communication

## Pin Out

![](/files/m3rYbAGfCVRQpfni0sih)

## Connector Routing

![](/files/LZthPIEtLpuWVsyIhtZZ)

## Installation

* Mount the Rover Unit securely to the drone
* Choose the best position to attache the rover unit antennas.
* Connect the antennas to ANT 1, ANT 2 (MMCX) on the Rover unit. There shall be no metal parts or any conductor attached to the antennas. 
* Connect S.bus on the Rover Unit to the RC IN on the Flight Controller.
* Connect UART on the Rover unit to the TELEM 1 or TELEM 2 on the Flight Controller.
* Connect 5V - 12.6V max (3s Lipo supported) battery to the power input on the Rover Unit.
* Connect a camera to HDMI 1 (preferred) on the Rover Unit. If you are sing two camera, connect the second camera to HDMI 2. You may switch from Stream 1 and Stream 2 on the Ground Station to display the corresponding video stream.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cubepilot.org/user-guides/cubepilot-ecosystem/cubepilot-partners/union-robotics/herelink-blue/herelink-blue-user-guide/air-unit/air-unit-interface-and-installation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.