Setting Triggers

Our enDAQ products have a variety of trigger settings to help preserve battery life and ease processing needs later on to only record events of interest.  

All of the following content assumes your recorder is running the latest firmware revision. If anything below does not match your UI, then see the updating instructions.

In this Article

Video Tutorial: Trigger Configuration

Triggers Overview

Located to the right of the ‘General’ tab in the configuration settings window is the ‘Triggers’ tab. Triggers are configuration settings useful when a user is only looking to have a sensor start recording after a certain event occurs or at a specific date and time or for a specific length of time.

In order to set each trigger value, the box next to the trigger must be checked. depending on the state of "Wait for All Sensor Conditions" the recorder will begin recording when any (if unset) or all sensor conditions have been met. No sensor input will be considered before the timestamp configured under "Start trigger sequence at specific time", and sensor input will be optionally considered during a recording delay/interval countdown.

For example, if "Delay Or Trigger" is selected along with a sequence start time at 9 AM, with a delay of 10 seconds, and pressure, temperature, and acceleration trigger are selected, but NOT "Wait for All Sensor Conditions", after a button press the recorder will sleep until 9 AM, then sleep for a maximum of 10 seconds, or less if any of the 3 configured sensor conditions is met.

If the recorder was configured to "Delay Then Trigger" above, then after 9 AM, the recorder would sleep for a minimum of 10 seconds, and then wait for any sensor condition to be met. 

When a sensor is waiting for a trigger, the LEDs on the sensor will flash Red, then Red & Green, alternating until the trigger is reached. When waiting for the main accelerometer trigger (to guarantee pre-trigger samples) the flashing will be at a faster rate.

Time-Based Triggers

Trigger Mode

Delay Then Trigger

This mode will set a MINIMUM delay before recording starts. Recording Delay/Interval functions normally, and no sensors are powered on until this delay expires. 

Delay Or Trigger

This mode will set a MAXIMUM delay before recording starts. The recorder will sleep for at most the configured time and will power up sensors to cut this waiting period short if any configured condition is met. This is useful in case an event is expected, but data is still desired in case the event happens late or not at all. An example use case is when you would like periodic checkpoints on the health of the system as well as capturing specific events.

Recording Delay/Interval

The Recording Delay/Interval trigger tells a sensor to wait a user-determined number of seconds AFTER THE BUTTON IS PRESSED before beginning a recording. This trigger is useful for applications where the installation of the sensor and when the sensor should start recording are not the same instance in time, but the latter will be in the near future. This trigger is also useful for extending the battery life of the sensor. This is also a useful trigger to use in conjunction with the re-triggerable setting and limited recording time. For example, if the user wants to record 10 seconds of every minute. The Wake After Delay will be set to 50 seconds, the recording time should be limited to 10 seconds, and the re-triggerable box should be checked.

Wake at a Specific time

The Wake at a specific time trigger is similar to the Wake After Delay trigger but allows the user to select a specific date and time in the distant future for the sensor to begin a recording AFTER THE BUTTON IS PRESSED. The Wake at a specific time trigger allows the user to set the trigger for UTC or the specific time zone of the user. This trigger is useful if the user will not have access to the sensor for an extended period of time before a recording is needed. This trigger is also useful in similar applications for extending the battery life of the sensor and preventing unwanted data from being recorded. In all configurations, the sensor will remain in a deep sleep until this time has passed. This setting is unaffected by "Delay Then/Or Trigger".


Please note that, due to the UTC offset, this setting can sometimes be difficult to understand and program correctly. We encourage you to do some testing on your desk before proceeding to your end test.

Recording Time Limit & Retrigger

Recording Time Limit

The Recording Time Limit trigger allows a user to set the number of seconds a sensor will record for AFTER THE BUTTON IS PRESSED. This trigger is useful in applications where the user intends to use the sensor for measurements of short duration. Setting this trigger will prevent unwanted data from being recorded after the desired measurement has been taken.


Setting this configuration allows the sensor to take multiple data files without user interaction. The Retrigger option is a useful configuration setting for when multiple recordings of specific events need to be measured. This function can be coupled with the Limit recording time to trigger to generate multiple, smaller recording files over the course of a test. Tip: For users looking to take periodic measurements, this can be achieved by coupling the Recording Time Limit with Retrigger. For example, a 1-minute recording every 15 minutes could be achieved by programming a 60 second recording time limit and an 840 recording delay as shown.


For users looking to take periodic measurements, this can be achieved by coupling the Recording Time Limit with Retrigger. For example, a 1-minute recording every 15 minutes could be achieved by programming a 60 second recording time limit and an 840 recording delay as shown.

Sensor Triggers

Wait for All Sensor Conditions

If this field is selected, then recording will not start until all sensor conditions have been met in the same time slice. For instance, the accelerometer input will not be considered if a temperature trigger is configured but the measured temperature is outside the configured range. 

Conversely, if this field is not selected then any single sensor condition matching will cause the recorder to start recording.

Pressure and Temperature Triggers

The Pressure and Temperature triggers perform the same function, but with different measurements. Each trigger has an upper and lower value that must be set. These upper and lower values are what the sensor looks for to know whether it should begin a recording or wait. If a temperature or pressure event occurs that exceeds the upper or lower values, the sensor will consider this condition met and will start recording if "Wait for All" is not selected, or if this is the only trigger.


Please note that, although the device can use temperature or pressure to start a recording, it will not stop the recording if the temperature/pressure returns to a level inside the trigger range. Limit the recording length and turn on re-triggerable if you are only interested in data when it is outside the specific temperature and/or pressure range.


The pressure and temperature trigger windows set the window to exit before starting a recording. For example, if a pressure trigger window of 90 kPa to 110 kPa is set, the device will start recording at pressures below 90 kPa or above 110 kPa.

Acceleration Triggers (Main)

The acceleration trigger should be used when the application asks that only vibrations exceeding a specific acceleration should be measured. This is a useful trigger for measuring shock events, and when coupled with the Limit recording time to trigger, the battery life can be extended for a sensor and save the user from obtaining unwanted data.

The main acceleration trigger uses the piezoelectric or piezoresistive accelerometer which is on the analog chain. There are several important distinctions between the analog/main trigger and the DC trigger:

  • Main accelerometer triggers have to power the whole system, but only save data once the trigger has been reached, meaning that battery life is only marginally reduced
  • But this setting guarantees pretrigger samples as explained in more depth below
  • The main/analog accelerometers also typically have DC offsets and gain calibration compensations needed. These compensations occur in post-processing the data and aren't directly handled while recording data, which means that they aren't taken into account when setting triggers.


Please note that, although the accelerometer is calibrated, this calibration is not "seen" during triggering and recording. This includes the DC offset. It is advised that trigger levels always exceed at least 1/5 the recording range of the accelerometer.

But if the user would prefer to use the main accelerometer as the trigger and get as close as possible to the true trigger condition, you will need to determine the offset values of an accelerometer, do the following:

  1. Set the sensor on a flat surface and take a recording. Do not apply an external vibration to the Slam Stick.
  2. After 10 seconds, stop the recording and open the data file in the enDAQ Lab software (see the ‘Analysis’ section for information on how to view data in the enDAQ Lab software)
  3. Select “Data” (at the top of the viewing window)
  4. Select “Remove Mean” and then “Do Not Remove Rolling Mean”
  5. Observe the ‘g’ value that each axis corresponds to in the data. Those are the baseline values that should be used when setting an Acceleration trigger. Depending on the orientation of the device, the offset may or may not differ.


The offset values should be used as a baseline for setting the Acceleration trigger values and it is suggested that the Acceleration trigger value be set to no less than 0.5g away from the offset value.

Acceleration Trigger (DC)

This trigger uses the DC MEMS accelerometer for triggering. If pretrigger samples are not needed, Midé recommends using this trigger over the analog accelerometer trigger for three reasons:

  1. There is no concern over the moving DC offset for this accelerometer. 
  2. This accelerometer is much lower power and the rest of the system can be disabled so it will last longer in this trigger mode. 
  3. You can trigger a specific axis.

One thing to pay attention to is the gravity vector though for this accelerometer. If you set the trigger level to 0.5g in the Z-axis and the sensor is sitting on a desk, it will trigger because it reads a 1g acceleration due to gravity.

Pretrigger Samples

In some applications, it is imperative to not only know that an event occurred but to also understand the event itself which will require as much raw data as possible. There are no pretrigger samples generated when using the DC accelerometer, only when using the main (analog) accelerometer.  For vibration test applications this is typically not a concern, but shock testing will need to use the main accelerometer to fully capture the event. To illustrate how these affect the actual data, let's see an example. The two tests used the same recorder with two different configurations as shown. On the left, the DC accelerometer trigger is used, the one on the right shows the main accelerometer trigger.

The recorder was dropped on an industrial carpet in an office space (very thin, concrete below it) with a drop height of 2 inches. The data is shown below. At initial glance, the first test appears to have only captured a ~40g shock event. In actuality, because it was using a low-power trigger mode, the first peak was completely missed, those other peaks are when the recorder bounced on the carpet.

To illustrate how the beginning of the drop test was missed, in the next example the device is dropped on a pillow, again from only 2 inches. On the left with the low-power trigger mode, by the time the accelerometers start saving data, the initial part of the pulse has occurred and therefore missed. On the right, the initial drop (even showing the effect of gravity in free-fall) is captured before the recorder impacts the pillow.

The data generated in these tests can be downloaded by clicking here.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.