> 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/gremsy-two-axis-t3v3/getting-started/i-o-connections.md). # I/O CONNECTIONS Two-axis T3V3

## Power input

## USB-C port Signal USB-C 2.0 goes straight from Quick Release to Tilt gimbal

## Micro USB port Upgrade firmware gimbal

## **RC port** RC**:** Signal remote control gimbal Pin 1 is the leftmost

Pin	Name
1	+5V
2	SBUS signal remote
3	GND
4	Spektrum signal remote
5	+3V3
6	CAN_L
7	CAN_H

## HDMI output

## **COM2/4 port** COM2/4: signal UART of the gimbal, using the same T3V3 Pin 1 is the leftmost

Pin	Name
1	+5V
2	Tx2
3	Rx2
4	Tx4
5	Rx4
6	GND

## **AUX port** AUX: Aux port with S1-S4 optional signals for users to connect to other devices such as AV signal or camera trigger for additional functionality. The signal goes straight from QR to the tilt gimbal Pin 1 is the leftmost

Pin	Name
1	S1
2	S2
3	S3
4	S4
5	GND

--- # 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/gremsy-two-axis-t3v3/getting-started/i-o-connections.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.