TWTG Documentation
Service Desk
Starting Guide
Starting Guide
  • Introduction
  • LoRa & LoRaWAN
    • LoRa
      • LoRa vs WirelessHART
      • LoRa vs BLE
    • LoRaWAN
      • Infrastructure
  • Installation & Provisioning
    • Box Content
    • Installation
      • Pressure Gauge (PG)
      • Pressure Sensor (PS)
      • Temperature Sensor (TS)
      • Temperature Transmitter (TT)
      • Vibration Sensor (VB)
      • Contact Sensor (VS-CS)
      • Valve Sensor - Multiturn (VS-MT)
      • Valve Sensor - Quarter Turn (VS-QT)
    • Provisioning
      • 📄Step 1: Product manual
      • 🔑Step 2: Identify the keys
      • 💻Step 3: Add the device to the LNS
      • ⚙️Step 4: Encoder & Decoder in the LNS
      • 🟩Step 5: Activating the device
  • Data & Communication
    • Communication Protocol
    • Measurements & Messages
    • Schedules
    • Data Visualization
  • Configuration
    • Online Configurator
    • Configure a Device
  • How-to
    • General
      • How to troubleshoot a NEON device not connecting to the network
      • How to fix a bad connection
      • How to replace a battery
    • Pressure Gauge (PG)
      • How to configure event triggers
    • Pressure Sensor (PS)
      • How to configure event triggers
    • Temperature Sensor (TS)
      • How to configure event triggers
      • How to change the configuration of the device from using FSB1 to FSB2 in US915
      • How to configure the frequency of measurements and messages
    • Temperature Transmitter (TT)
      • How to configure event triggers
      • How to use a temperature element different from type K
      • How to use a PT100/RTD
      • How to configure the frequency of measurements and messages
    • Vibration Sensor (VB)
      • Communication Protocol v2 & v3
        • How to obtain the FFT data
        • How to have an FFT for threshold values without periodic messages
        • How to configure event triggers
      • Communication Protocol v4
        • How to Get Started with the New Features of the NEON Vibration Sensor v4
      • How to configure the frequency of measurements and messages
      • How to replace the sensor or probe
      • How to debug a not connected sensor
      • How to debug a not paired sensor
      • How to enable Hanning Window
  • General Information
    • Available Regions
    • LoRaWAN Region
    • Hazardous Locations
    • Device Maintenance
    • Support & Troubleshooting
    • FAQs
Powered by GitBook
On this page
  • Protocol v2 & v3
  • Protocol v4
  1. How-to
  2. Vibration Sensor (VB)

How to enable Hanning Window

PreviousHow to debug a not paired sensorNextAvailable Regions

Last updated 5 months ago

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.

Protocol v4

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