Settings

The Settings tab contains parameters that can be configured by the system administrator using preset configurations. These are ready-made templates that can be applied to objects.
Contact the administrator to add the necessary settings to your contract. They will appear on this tab. The settings will be automatically applied to all objects in the contract.
In the Settings tab, you define parameters that affect how the device works in the system. For example, here you can configure the trip and parking detector, trip segmentation, and data filtering.
Settings
1. Speed source
Select the speed source to ensure accurate vehicle movement data.
By default, the system uses GPS speed, but you can select another parameter if needed, for example, CAN bus speed.
If CAN speed is selected:
  • The speed shown in the History chart will be taken from CAN
  • Movement calculations in basic reports (Trips, Driving Time, Parking, etc.) will be based on CAN speed
  • Driving time and stop detection will also be calculated using CAN speed
If the selected parameter does not contain speed data, the system will automatically switch back to the default GPS speed.
Make sure you select a parameter that actually represents speed. If you accidentally choose mileage or another value, the calculations may be incorrect.
In the Speed source block, you can use the Formula field to convert the parameter value into the correct speed format.
CAN bus speed is not always transmitted in the required unit. For example, it may be received in knots or meters per second. In this case, you can use a formula to convert the technical value into the correct unit for display and calculations in the system.
For example, if speed is received in m/s, use the formula: * 3.6 (This converts meters per second to km/h.)
Settings
2. Track builder
With this function, you can configure:
  • Minimum speed at which the system begins recording a trip
  • Minimum time between trips — the system will separate trips if this interval passes between the end of one and the start of another
  • Minimum parking time — how long the vehicle must remain stationary before it is registered as parking
  • Maximum distance between tracking points — if points exceed this distance, the system will treat them as separate trips
3. Consider ignition, fix speed, mileage by CAN
Consider ignition — a trip is only recorded when the vehicle ignition is on
Fix speed — restores movement speed if data is missing or corrupted
Mileage by CAN — trip history and reports will use CAN bus mileage instead of GPS. This is more accurate in cases where GPS signal is lost
4. Divide trips into segments by time
This function splits each trip into time intervals. For example, every 2 or 4 hours.
Instead of a single record for the whole day, you’ll get shorter segments. This is useful for generating trip sheets for specific periods.
5. Events filter
Set parameters for validating received data:
  • Minimum number of satellites required for accurate coordinates. Typically at least 3. Some devices work with 2, but accuracy is lower.
  • Maximum HDOP value — HDOP (Horizontal Dilution of Precision) indicates location accuracy. The lower the value, the more precise the coordinates. If HDOP is higher than the threshold you set, the system will discard the data.
The system also automatically filters out messages without coordinates or with zero latitude/longitude, even if the device did not mark them as invalid.
  • Maximum speed value — points with a speed higher than this threshold will be filtered out in history tracks and speed/mileage/violation reports.
6. Formula
The Formula field allows you to filter data packets when building tracks.
It works as follows:
The formula returns either TRUE or FALSE for each packet. If the result is TRUE — the packet is excluded. If the result is FALSE — the packet is included in the track.
Examples: =%S%<5 — excludes all packets with speed less than 5 km/h.
=%S%<5 || %S%>200 — excludes packets where speed is below 5 km/h or above 200 km/h.
You can also create more complex formulas using logical operators, brackets, and multiple conditions.

Valid flag in raw data

Valid is a field in the raw packet data that shows whether the packet is considered reliable for further coordinate processing.
Valid = 0 means that the packet is considered invalid. Such packets are stored in the system, but are excluded from processing when tracks, geofences, and other data that require reliable coordinates are recalculated.
The Valid = 0 flag is assigned only in the following cases:
— the packet has no coordinates or contains zero latitude or longitude values
— the packet matches the condition specified in the filtering formula
After such a packet is saved, its participation in recalculation can no longer be changed: it will not be used during repeated data processing.
Filters by satellite count, speed, and other parameters from the Events filter block work differently. They are applied dynamically, only during data recalculation. If you change these filter parameters and run recalculation again, the result may change.
For example, if the minimum satellite count is set to 4 in the object settings, packets with fewer satellites may be excluded when tracks and reports are recalculated. However, the packets themselves do not receive the Valid = 0 flag.
If you need such packets to be marked as invalid immediately, use a filtering formula. For example: %satsinview% < 4
This formula marks packets where the satellite count is less than 4 as Valid = 0. These packets are stored in the system, but are not used when tracks, geofences, and other data are recalculated.
7. Misc
Speed limit — the system notifies you when speed exceeds the set limit.
Connection loss — the system notifies you if connection is lost and not restored within the set time.
Idle time — the system registers idle periods when the object remains stationary beyond the set limit.
Next to these fields, there are additional control icons:
Bell icon — notification management for the limit:
— notifications are enabled
— notifications are disabled
The limit itself continues to function regardless of the notification status: data is still recorded in the system and displayed in reports.
To change the mode, click the icon.
Ignition key icon (available for the “Idle” field) — determines whether the ignition status is considered when calculating idle time:
— idle is recorded only when the ignition is ON
— idle is calculated regardless of the ignition status
Don’t forget to click Save to apply your changes.