> 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-v2-and-v3/how-to-configure-event-triggers.md).

# How to configure event triggers

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 [NEON configurator](https://neon-configurator.twtg.io/) 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².


---

# 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-v2-and-v3/how-to-configure-event-triggers.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.