> 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/aevo/gimbal-configuration/filter.md).

# Filter

The purpose of the filters is to eliminate noise and vibration due to structural resonances in the camera, lens, or gimbal.

Setting the filters too high or too low can cause signal disturbances that can reduce the overall stabilization.

  GYRO FILTER

Defines the strength of the filter applied to Gyro sensor output. If the gimbal has oscillations that cannot be corrected by adjusting stiffness settings, the Gyro Filter is used to further tune the gimbal and remove the oscillation.

  OUTPUT FILTER

Defines the strength of the filter applied to motors output. If the gimbal has oscillations that cannot be corrected by adjusting stiffness settings, the Output Filter is used to further tune the gimbal and remove the oscillation.

1\. If the gimbal is vibrating at a high frequency after tuning, increase the filter values.

2\. If the gimbal is oscillating or rocking at a low frequency after tuning, decrease the filter values.

  DEFAULT VALUES

| Gyro Filter   | 6 |
| ------------- | - |
| Output Filter | 6 |

   


---

# 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/aevo/gimbal-configuration/filter.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.