The Health check tab allows you to monitor the status of devices installed on units and quickly identify any deviations in their operation. You can track various metrics such as battery level, number and frequency of messages sent, voltage, ignition state, and more.
Configuring health check
To start monitoring the technical state of a device, follow the steps below.
- If the health check criterion you want to track requires a sensor, create it. See the required sensors in the List of criteria section.
- For each criterion you want to track, specify how long the device must comply with a criterion to trigger an incident:
- 1 minute
- 10 minutes
- 1 hour
- 1 day
After that, the system starts tracking the health check criterion. If its conditions are met within the specified period, an incident is registered for the device. These incidents are displayed in real time on the Dashboard tab in the Device health check status block and in the dedicated blocks for each criterion (see more details in the List of criteria section).
Historical data on incidents is not available in the system.
Disabling health check criteria
To stop monitoring a health check criterion, select Not tracked from the drop-down list next to the criterion name.
List of criteria
The Health check tab contains the criteria which you can use to monitor the device health. They are divided into three groups based on the source of data used for criterion tracking.
Sensors
The criteria in this group are tracked based on a sensor configured in the unit properties.
| Criterion | Description |
|---|---|
| Device battery level less than 20% | Uses the sensor selected in the Device battery field on the Advanced tab of the unit properties. Tracks the device battery level. An incident is registered if the battery level is less than 20% during the selected period. Statistics for the criterion are available in the Device health check status and Device battery level blocks of the Dashboard tab. Missing sensor data doesn't trigger an incident. This criterion uses raw sensor data before filtering is applied, and after applying the calculation table, validation, or expressions specified in the Parameter field of the sensor properties. |
| Voltage outside the range of 12 to 13 V | Requires a voltage sensor. Tracks the voltage of the onboard network, tracker battery, or other voltage source that should be within the range of 12–13 V. An incident is registered if the sensor value falls outside this range during the selected period. If multiple sensors are available, each one is monitored. Statistics for the criterion are available in the Device health check status and Voltage level blocks of the Dashboard tab. Missing sensor data doesn't trigger an incident. This criterion uses raw sensor data before filtering is applied, and after applying the calculation table, validation, or expressions specified in the Parameter field of the sensor properties. |
| Ignition off | Requires an engine ignition sensor. Tracks whether the vehicle ignition is on. An incident is registered if the sensor value remains "off" and doesn't change to "on" during the selected period. If multiple sensors are available, each one is monitored. Statistics for the criterion are available in the Device health check status and Ignition state blocks of the Dashboard tab. Missing sensor data doesn't trigger an incident. |
| No changes in fuel data | Requires a fuel level sensor. Tracks whether there have been any changes in the values of the fuel level sensor. An incident is registered if the fuel level sensor values remain unchanged during the selected period. If multiple sensors are available, each one is monitored. Statistics for the criterion are available in the Device health check status and Fuel data changes blocks of the Dashboard tab. Missing sensor data doesn't trigger an incident. This criterion uses raw sensor data before filtering is applied, and after applying the calculation table, validation, or expressions specified in the Parameter field of the sensor properties. |
Data transmission frequency
This criterion is tracked based on the message frequency sent by a unit.
| Criterion | Description |
|---|---|
| More than 200 messages an hour | Tracks the number of messages received in the last hour (calculated from the current time). An incident is registered if the device sends more than 200 messages for the last hour during the selected period. Statistics for the criterion are available in the Device health check status and Number of messages per hour blocks of the Dashboard tab. |
GPS data
The criteria in this group are tracked using the basic data from unit messages such as coordinates, number of satellites and message availability.
| Criterion | Description |
|---|---|
| No messages | Tracks whether the device is sending any messages. An incident is registered if no messages are received during the selected period. Statistics for the criterion are available in the Device health check status and Messages blocks of the Dashboard tab. |
| No GPS data | Tracks the coordinates in the device messages. An incident is registered if no coordinates are received during the selected period. Statistics for the criterion are available in the Device health check status and GPS data blocks of the Dashboard tab. |
| Fewer than 4 satellites | Tracks the number of satellites used to determine the device location. An incident is registered if fewer than four satellites are used during the selected period. Statistics for the criterion are available in the Device health check status and Number of satellites blocks of the Dashboard tab. |
| Distance between messages more than 100 km | Tracks the distance between the coordinates of the two most recent messages. An incident is registered if this distance exceeds 100 km during the selected period. Each new message is compared to the previous one. Statistics for the criterion are available in the Device health check status and Distance between messages blocks of the Dashboard tab. |
Download PDF file
Download Word document