> For the complete documentation index, see [llms.txt](https://docs.freeflysystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freeflysystems.com/ecosystem/payloads/lr1-payload/lr1-lenses-and-expansion/expansion-ports.md).

# Expansion Ports

Connector: JST GH 4-Pin

The two 4-pin GH connectors are expansion ports for adding thermal cameras, wide cameras, laser range finders, and other custom modules. They are both USB 2.0 connections.\
\
Connector: JST GH 3-pin

The 3-pin GH connector provides 5v and 12v power out.

{% hint style="danger" %}
Warning - do not short 12V or 5V to ground or each other. This will cause permanent damage to the LR1 Payload!
{% endhint %}

{% hint style="info" %}
Adding additional payloads will require a rebalance and autotuning tuning.

M3 holes on the camera can be used to mount small weights to balance the payload when using an external module.
{% endhint %}


---

# 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.freeflysystems.com/ecosystem/payloads/lr1-payload/lr1-lenses-and-expansion/expansion-ports.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.