> 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/getting-started/gimbal-balance.md).
# Gimbal Balance
This information page will help users balance the gimbal more easily.
## 1. FRONT-BACK TILT AXIS BALANCE
* Loosen the Tilt Front-Back Thumb Screw, then gently adjust the camera backward/forward until it doesn't swing and stays in any given position when released.
* Tighten the Tilt Front-Back Thumbs screw.
## 2. UP-DOWN TILT AXIS BALANCE
* Loosen the thumbscrew of Tilt vertical adjustment, then rotate the camera to 90° and slide front or back.
* When the proper vertical balance is achieved, the camera will stay level when you remove your hands.
* Tighten the Tilt thumbscrew after balancing.
## 3. ROLL AXIS BALANCE
* Loosen the thumbscrew Roll adjustment, then slide right or left.
* When the proper Roll balance is achieved, the camera will stay at the horizontal level.
* Tighten the Roll thumbscrew after balancing.
## 4. PAN AXIS BALANCE
* Tilt the Gimbal about 20° from the verticality, identify if the gimbal is front heavy or back heavy. Slide the pan axis slider until the camera does not swing.
* Loosen the thumbscrew, then gently slide the pan axis slider backward/forward until it doesn't swing and stay at any given position when released.
* Tighten the thumbscrew to make sure pan axis slider is locked in position.
---
# 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/getting-started/gimbal-balance.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.
.jpg?alt=media&token=072168ec-4555-4f06-b467-53849ae4496b)
.jpg?alt=media&token=a1790dda-6287-4a25-81e5-b132bd940682)
.jpg?alt=media&token=269873aa-6cb3-4f5f-9532-b7ff7ec8952a)
.jpg?alt=media&token=95a4f8d0-df2a-4380-beac-6645a1883f8b)