> 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/mio-two-axis/getting-started/i-o-connection.md).
# I/O Connection
## DIAGRAM CONNECTION
## I. **Mio Two-Axis Sub-Board I/O Connection:**
### **1. Power IN:**
\
\
\
Voltage input range from 15-52V.\
Connector Type: XT30UPB-M.
### **2. USB Type-C:** Use for debugging and configure.  
### **3. SBUS, PPM Control:**
\
\
Connector Type: Dupont 3pin 2.54mm.
### **4. COM2:**
\
\
\
Connector Type: BM06B-GHS-TBT(LF)(SN).
| Pin number | |
| :--------: | :--------: |
| 1 | 5V |
| 2 | UART2\_TXD |
| 3 | UART2\_RXD |
| 4 | NC |
| 5 | NC |
| 6 | GND |
\*Pin order is from the left to the right.
### **5. Auxiliary Connector:**
\
Connector Type: BM08B-GHS-TBT(LF)(SN)
| Pin number | |
| :--------: | :-: |
| 1 | S1 |
| 2 | S2 |
| 3 | S3 |
| 4 | S4 |
| 5 | S5 |
| 6 | S6 |
| 7 | GND |
| 8 | 12V |
\*Pin order is from the left to the right.
### 6. Micro HDMI
\
### 7. Power OUT
Voltage output: 12V\
Connector Type: XT30PW-F\
### 8. KEL CONNECTION
{% 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 %}
## II. Mio Two-Axis Tilt Board I/O Connection:
### 1. Auxiliary Connector
Connector Type: BM08B-GHS-TBT(LF)(SN)
| Pin number | |
| :--------: | :-: |
| 1 | S1 |
| 2 | S2 |
| 3 | S3 |
| 4 | S4 |
| 5 | S5 |
| 6 | S6 |
| 7 | GND |
| 8 | 12V |
***\*The pin order is from left to right.***
### 2. Micro HDMI
---
# 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/mio-two-axis/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.
