> 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/pixy-lr-s-port-v1/installation.md).
# INSTALLATION
### Step 1: Install the camera and balance the gimbal according to the type of LENS being used.
### Step 2: Connect cable from drone to gimbal
### Step 3: Connect gTune to load the profile corresponding to the type of cable being used.
*Note:*
* Use gTune version 1.4.9.4 or higher.
* Only change profile when changing cable type.
Choose the appropriate profile for the type of cable being used.
### Step 4: Auto tune to have a set of parameters suitable for the LENS in use.
*Note:* Only Auto tune when changing to a new LENS type.
Press the button to do Auto tune for the gimbal
Process in progress
After completing the Tune Gimbal process
There will be a notification, click **"WRITE PARAM"** and the gimbal will reboot and use the new parameters just tuned.
### Step 5: Connect the camera to Entire module inside gimbal.
{% hint style="danger" %}
This step is critical because it establishes the Wi-Fi connection between the camera and the **Entire** module inside the gimbal.
Once the connection is established, users can adjust camera settings such as **shutter speed**, **ISO**, and other supported parameters through the **MAVCAM** application or by using the **CD Tools** feature on the Herelink remote controller.
{% endhint %}
{% embed url="" %}
---
# 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/pixy-lr-s-port-v1/installation.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.
