Configuring Telemetry

Vehicle telemetry allows you to collect and transmit data about a vehicle’s performance and operation, so that it can be remotely monitored and analyzed.

Under Services > Telemetry, you can configure the AirLink OS Telemetry settings as shown below:

Initializing Table Of Contents...

General

The following settings can be configured for AirLink OS Telemetry.

Vehicle Settings

Vehicle settings are a subset of telemetry. If vehicle telemetry reports are desired, then the following settings must be set to specify how telemetry has been installed in the vehicle.

Vehicle Odometer

Odometer is not a standard OBD-II data point. On heavy duty vehicles and some selected light duty vehicles, it can be read from the CANBUS. However when it is not available, it can be derived from speed and distrance travelled. Setting the derived odometer configures the starting point from which to calculate further distance from.

AMR Reports

The complete telemetry data set can be sent to AirVantage allowing for the viewing of all Advanced Mobility Reports(AMR).

Custom Reports

Custom reports allow you to tailor your reports to better suit your needs. Initially you would define the report with specific data content and then you would assign it to the trigger event.

REPORTS

Define reports with your specific data requirements that can be sent to ALMS and/or an MQTT broker.

PERIODIC TRIGGERS (Generate reports at fixed intervals)

Reports can be generated at fixed time intervals using Periodic Triggers.

UNCONDITIONAL TRIGGERS (Generate reports upon every data sample)

Reports can be generated when a data sample changes using Unconditional Triggers.

Example 1 : GPIO Input Cumulative

GPIO Input Cumulative is calculated using the following :

• Primary GPIO Input
• GPIO Input 2
• GPIO Input 3
• GPIO Input 4
• GPIO Input 5

The GPIO Input Cumulative will concatenate these five values in the above order. Any change in a GPIO Input will affect the GPIO Input Cumulative and therefore generate a report.

Example 2 : WAN Ready

A WAN Ready sample is generated when WAN connectivity of the router switches between up or down.

• Time A: XP1 Cellular is UP. XP2 Cellular is UP.
• Time B: XP1 Cellular is UP. XP2 Cellular is DOWN.

No sample is generated because the WAN connectivity for the device is still UP through XP1 Cellular.

• Time A: XP1 Cellular is UP. XP2 Cellular is UP.
• Time B: XP1 Cellular is DOWN. XP2 Cellular is DOWN.

A WAN Ready sample is generated because there are no interfaces with WAN connectivity UP.

Example 3 : Ignition Status

• Time A: Ignition is DOWN.
• Time B: Ignition is UP.
• Time C: Ignition is DOWN.

Two Ignition Status samples are generated because the Ignition Status changed.

Example 4 : Primary WAN

A PRIMARY WAN sample is generated whenever there is a switch in which interface is evaluated as primary.

• Time A: XP1 Cellular is UP and designated PRIMARY WAN. XP2 Cellular is also UP.
• Time B: XP1 Cellular is UP. XP2 Cellular is DOWN.

No PRIMARY WAN sample is generated in this example.

• Time A: XP1 Cellular is UP and designated PRIMARY WAN. XP2 Cellular is also UP.
• Time B: XP1 goes down. The PRIMARY WAN designation is re-evaluated to see if XP1 is still the PRIMARY WAN, and it is not. XP1 – Down. XP2 – New PRIMARY WAN.

A PRIMARY WAN sample is generated in this example.

DELTA TRIGGERS (Generate reports at minimum change in value or maximum elapsed time)

Reports can be generated using Delta Triggers when the sampled value has changed at least the configured amount since the last sample or a configured maximum time has passed.

LEVEL TRIGGERS (Generate a report for each monitored data sample that meets the trigger condition)

Reports can be generated when a configured condition is true.

Example : LEVEL Trigger

If you define a LEVEL trigger that reports vehicle speed when vehicle speed >= 55 KPH, then each sample at and above the red line would generate a report. These samples represent the moments when the configured level threshold for vehicle speed was true. (i.e. Samples C, D, E, F, G, H, L, M are all >= 55 KPH).

EDGE TRIGGERS (Generate one report when monitored condition becomes true)

A single report can be generated when a monitored condition crosses the configured edge threshold.

Example : EDGE Trigger

If you define an EDGE trigger to generate a report when vehicle speed >= 55 KPH, then samples C and L would each generate a report. These samples represent the moments when the configured EDGE threshold for vehicle speed was true. (i.e. Sample B is < 55 KPH and Sample C is >= 55 KPH; Sample K is < 55 KPH and Sample L is >= 55KPH).

Vehicle Behavior Reports

Vehicle behavior reports are data reports generated by the telemetry system that provide information about the driving behavior of a vehicle and its driver. These reports are based on various data points collected by the telemetry system, such as GPS location, acceleration, braking, and other driving-related data. The following settings can be configured to help identify abnormal events from which a vehicle behavior report would be generated.

MQTT

The MQTT section will only display if a custom report or a vehicle behavior report has the REPORT MODE set to an MQTT option.

A destination MQTT broker can be configured using the following settings.

6Q1099009902AC24/test {
  “atp.ser” :
   {
        “t”: 1693258321.3640001,
        “v” : “6Q1099009902AC24”
    },
        “ts” : 1693268920.464
}

More information about MQTT can be found here.