> 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/communication-protocol-v4/how-to-obtain-the-fft-data.md).

# How to obtain the FFT data

By default, the FFT data is turned off on the NEON vibration sensor. To activate the FFT a configuration downlink must be generated and sent via LoRa. Please refer to the [configuration ](/docs/configuration/online-configurator.md)section for guidance on how to configure a NEON sensor. The settings to turn on the FFT in the NEON vibration sensor are explained next.

1. Go to the **Schedule Spectrum** tab. 
2. Select the command (set to add the configuration, replace to change all FFT settings with the new one, or execute to only do the task once). This step should be skipped if the configuration is done through SolidRed. 
3.  Set the timing
4. Define the vibration settings for the FFT
5. Select the spectrum type (acceleration, velocity, or envelope)
6. Set the time to transmit. Generally, it is recommended to set the time to transmit close to the timing.

By applying these settings, the sensor will start measuring and transmitting FFT data periodically based on the established timing. 


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.twtg.io/docs/how-to/vibration-sensor-vb/communication-protocol-v4/how-to-obtain-the-fft-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.