> 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/getting-started/i-o-connection.md).
# I/O Connection
## **G-Hadron Hub**
### **Gimbal Input**
Connector Type: **JST\_SM08B-GHS-TB(LF)(SN)**
**Diagram**
Pin order from the left to right.
### SBUS
Connector Type: **HARWIN\_M20-9960345 (TYP.CN)**
**Diagram**
PIN NUMBER
NAME
1
SBUS
2
5V
3
GND
Pin order from the left to right.
### USB-C and UART
#### **UART**
Connector Type: **JST\_SM03B-GHS-TB(LF)(SN).**
**Diagram**
PIN NUMBER
WIRE COLOR
NAME
1
BROWN
TX
2
ORANGE
RX
3
BLACK
GND
Pin order from the left to right.
### Power Cable
Connector Type: **Molex\_1054301102**
**Diagram**
PIN NUMBER
WIRE COLOR
NAME
1
RED
BAT+
2
BLACK
BAT-
Pin order from left to right.
## Camera Connector
Connector Type: **KEL\_XSLS00-52**
{% hint style="danger" %}
**WARNING:** The KEL connector is designed for up to **30 mating cycles**. To help maintain the connector and cable in good condition, please make sure the connector is properly aligned and insert/remove it gently and straight. Avoid pulling, bending, twisting the cable, or unnecessary repeated connection and disconnection.
***Please note that damage resulting from improper handling or exceeding the recommended mating cycles may not be covered under warranty.***
{% endhint %}
**Diagram**
PIN
NAME
PIN
NAME
27
NC
26
NC
28
HR_IMU_MISO
25
HR_CAM_SDA
29
HR_IMU_MOSI_SDA
24
HR_CAM_SCL
30
HR_IMU_SCK_SCL
23
HR_IMU_INT
31
HR_IMU_CS
22
EXT_VSYNC
32
GND
21
GND
33
MD2_N
20
HR_TC_MIPI_C_P
34
MD2_P
19
HR_TC_MIPI_C_N
35
GND
18
GND
36
M0_N
17
HR_TC_MIPI_D0_P
37
M0_P
16
HR_TC_MIPI_D0_N
38
GND
15
GND
39
MC_N
14
HR_TC_MIPI_D1_P
40
MC_P
13
HR_TC_MIPI_D1_N
41
GND
12
GND
42
MD1_N
11
HR_USB_RX_P
43
MD1_P
10
HR_USB_RX_N
44
GND
9
GND
45
M3_N
8
HR_USB_TX_P
46
M3_P
7
HR_USB_TX_N
47
GND
6
GND
48
HR_RST
5
HR_USB_D_P
49
HR_5V
4
HR_USB_D_N
50
HR_5V
3
GND
51
HR_5V
2
HR_USB_ID
52
HR_5V
1
HR_USB_VBUS
Pin the order from left to right.
## G-HADRON MAINBOARD
### **I/O Connection**
#### 1.UART
Connector Type: **SM06B-GHS-TB(LF)(SN)**
* **Function:** Communicate with G-Hadron gimbal and Ardupilot
* **Connection**: connect to **G-Hadron Hub** and **Ardupilot telem port**
* **Diagram:**
PIN NUMBER
WIRE COLOR
NAME
1
(Not connected)
5V
2
Green
TX1
3
Yellow
RX1
4
Brown
TX2
5
Blue
RX2
6
Black
Ground
Pin order from the left to right.
#### 2.HOST
Connector Type: Updating...
* **Function:** Stream video via HDMI/Ethernet by using C -> Ethernet or C -> HDMI cable
#### 3.**µSD CARD**
Connector Type: Updating...\
Supported size: Up to 128GB
#### 4.Power
Connector Type: **Molex\_1054301102**\
Diagram:
| PIN NUMBER | WIRE COLOR | NAME |
| ---------- | ---------- | ---- |
| 1 | | BAT+ |
| 2 | | BAT- |
[^1]:
---
# 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/getting-started/i-o-connection.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.
