> 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.md).

# GETTING STARTED

{% hint style="warning" %}
⚠️ **WARNING — Proper Gimbal Operation and Handling**

> Please follow the documentation carefully to ensure optimal performance and safe operation of your gimbal.
>
> **Before Powering On**
>
> * Always mount the **camera or dummy payload** and carefully balance the **Pan, Tilt, and Roll axes** before powering on the gimbal.
> * Make sure the gimbal is placed in a **level and stable position** before powering on.
> * Carefully check the **positive (+) and negative (−) power terminals** before connecting the power supply. **Reverse polarity may cause permanent damage to the gimbal and is not covered under warranty.**
>
> **Handling and Environmental Conditions**
>
> * Avoid **hard or high-impact landings**, as excessive impact may damage the gimbal or its internal components.
> * The product is rated **IP5X**. Do **not operate or expose the gimbal to rain or direct water spray**.
>
> **Gyroscope Calibration**
>
> * When moving the gimbal to a **different testing environment or location**, it is recommended to perform **Gyroscope Calibration (Gyro Calibration)** before flight to ensure optimal gimbal performance.
>   {% 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.gremsy.com/gimbals/gremsy-two-axis-t3v3/getting-started.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.