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
  1. How-to
  2. Vibration Sensor (VB)
  3. Communication Protocol v2 & v3

How to configure event triggers

PreviousHow to have an FFT for threshold values without periodic messagesNextCommunication Protocol v4

Last updated 1 year ago

Event triggers are a powerful feature of the NEON Vibration Sensor. For every measure taken, the device will determine if the condition was met to send an event message with the condition declared as the trigger. The device will send an event message upon status change, meaning, when the condition is set from false to true and when is set from true to false.

To configure the event triggers the user must generate a downlink and send it through LoRa. The can be used to create the downlink. The event triggers can be configured in the NEON configurator in the Sensor Configuration tab > Events section for protocol v2, and in the Sensor Conditions tab > Event Conditions section for protocol v4.

Every event trigger is a combination of 2 fields that must be defined to set the condition in the device.

  1. Mode: determines the operational mode of the event trigger. This can monitor peak acceleration or RMS velocity in any of the three axes (x, y, or z).

  2. Mode value: the value that must be reached in the measurement to trigger the event.

Examples

Mode = RMS velocity X, and mode value = 100

The combination above will define an event trigger such as if any measurement of the RMS velocity on the X axis exceeds 100 mm/s an event message will be sent.

Mode = peak acceleration Z, and mode value = 50

The above set of parameters will establish an event trigger to send an event message if the peak acceleration of the Z axis reaches 50 m/s².

NEON configurator