> For the complete documentation index, see [llms.txt](https://docs.twtg.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.twtg.io/docs/how-to/vibration-sensor-vb/how-to-enable-hanning-window.md).

# How to enable Hanning Window

A Hanning window is a mathematical function used in Fast Fourier Transform (FFT) analysis, particularly for vibration data, to minimize spectral leakage. Spectral leakage occurs when a signal is truncated in time, introducing artifacts in the frequency domain due to sharp edges at the signal boundaries. The Hanning window tapers the signal smoothly to zero at both ends, applying a cosine-shaped weighting function. This reduces the discontinuities at the edges, which helps improve the accuracy of frequency representation, especially for non-periodic signals. While it slightly broadens the spectral peaks, it provides a good balance between amplitude accuracy and frequency resolution, making it widely used in vibration analysis.

To enable this function, depending on the protocol version being used, use the following steps:

### Protocol v2 & v3

The Hanning Window needs to be enabled by configuring the device. Using the NEON configurator, in the section related to the data configuration, go over the **Selection** section and choose **Enable Hanning Window** to **Yes**.

<figure><img src="https://3244664496-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmA7CIluFghEyu6utdk9z%2Fuploads%2F5OKWuuKdzwj2mI2hTDUE%2Fimage.png?alt=media&amp;token=f8c90a56-7863-45cc-aeaa-34e18b8a5cc3" alt=""><figcaption></figcaption></figure>

### Protocol v4

In Protocol v4 the Hanning Window is always enabled so the user will always received FFTs using the Hanning Window.


---

# 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.twtg.io/docs/how-to/vibration-sensor-vb/how-to-enable-hanning-window.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.
