Skip to main content

Input Trigger - Identify IO Parameter Triggers

Explains what the Input trigger parameter is, how to find it in Raw data, and how to identify which IO parameter triggered a record.

Updated this week

Introduction

The Input trigger parameter indicates which IO parameter triggered the creation of a specific record. Each value in this field corresponds to an IO ID from the FMIO Parameter List.

Understanding Input trigger is essential when analysing raw data, for example when diagnosing high data consumption or verifying which events generate records.

๐Ÿ’ก Tip: Only parameters that support and are configured with Event on Change or Hysteresis can trigger records.


1 Prerequisites

Before you begin, make sure to export the record data for your object in an Excel file:

  1. Go to the "Fleet Status" module

  2. Select the object from the list

  3. Click on the "History" tab

  4. Click on the "Analyze by coordinates" button

Once you see the "Analyze by coordinates" data check do the following:

  1. Select the date range for which to extract the data

  2. Click on the "XLS" button beside the date range

  3. Wait until the file download will appear

You will now have the full record data for the object for the selected period.


2 How to Find the Input Trigger Value

2.1 Open the Raw Data Report

Access the record data .xls file and locate the Input trigger column.

The values in this column represent the IO ID of the parameter that triggered each record.

2.2 Look Up the IO ID

  1. Search for the IO ID value you found in the Raw data report.

  2. The matching entry will tell you which parameter triggered the record.

2.3 Example

In the screenshot below, the records were triggered by Time and Movement sensor:

FMIO list showing Time parameter

FMIO list showing Movement sensor parameter


3 What Can Trigger a Record

A parameter can only trigger a record if it meets both of the following conditions:

  • The parameter supports event-based triggering.

  • The parameter is configured with Event on Change or Hysteresis in the device configuration.

Configuration showing Event on Change and Hysteresis options

โš ๏ธ Warning: If a parameter with Event on Change changes frequently (e.g. Movement sensor), it can generate a large number of records and lead to high data consumption.

Did this answer your question?