Jump to content
  • EN

Template:FTX Features: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
 
(27 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<!--
=DRIVING BEHAVIOR=
==Data Acquisition scenario==
=== <u>Introduction</u> ===
'''Data Acquisition Modes''' allow you to control how the device '''collects''' and '''sends''' records under different network (Home vs. Roaming) and movement (Moving vs. On Stop) conditions. By tailoring data acquisition profiles, you can optimize data usage and power consumption, ensuring that relevant information is captured and transmitted at appropriate intervals.<br>


For example, you might configure the device to:
==Crash detection==
* Generate a record every '''1 minute''' when '''Home''' and '''Moving'''
[[File:FTX crash detection.png|alt=|right|500px]]
* Generate a record every '''10 minutes''' when '''Roaming''' and '''Moving'''
The Crash detection feature detects and logs vehicle crash events using accelerometer data. The device offers two primary crash detection methods:
=== <u>Prerequisites</u> ===
* Basic Crash Detection – Monitors the X and Y axes for sudden spikes in acceleration.
'''Connectivity'''
* Advanced Crash Detection – Builds on Basic Crash but also captures additional metrics (e.g., direction, maximum/average acceleration) and uses all three accelerometer axes.
* The device must support GPRS (or cellular) connectivity to send data to a remote server. <br>
* A Crash Trace option is also available, which collects high-frequency accelerometer samples and GNSS data before, during, and after a crash, providing detailed insight into the event.
===Prerequisites===
* GNSS (Optional) is required if you plan to capture concurrent GNSS data during a crash trace or rely on GNSS-based scenarios.
===Parameter Description===
'''Crash Scenario Threshold'''
* Basic Crash calculates the acceleration magnitude on X and Y axes only (to avoid triggering on gravity).
* Advanced Crash (when enabled) calculates magnitude on all three axes typically resulting in higher measured values.
'''Basic Crash Detection'''
* Crash Event AVL ID: 247
* Crash Detection Priority (Parameter ID 1024700): Set to Low or High to enable/disable the scenario.
'''Threshold & Duration'''
* When the accelerometer magnitude exceeds the configured threshold for the configured duration, the device flags a crash.
* The crash state continues until the acceleration drops 30% below the threshold (hysteresis) to prevent multiple crash events from small fluctuations.
'''Advanced Crash Detection'''
* Enabled if Basic Crash is enabled and Parameter ID 13102 is set to “enabled.”
* In addition to basic detection, it:
** Calculates crash duration and direction
** Captures maximum and average magnitudes, plus amplitudes on each axis.
* These extended metrics are included in the same AVL record (ID 247) once the crash ends.
'''Crash Trace'''
* When Crash Trace is enabled, the device collects high-frequency accelerometer data (~400 samples/second) plus GNSS data (1 sample/second).
* Upon a crash event (AVL ID 247 with value = 1), data continues to be collected for a configured period before and after the crash.
* A second crash record (AVL ID 247, “full crash trace” type) is generated once all data is processed, accompanied by AVL ID 257 for accelerometer axis data.
* Crash Trace timestamps match the actual collection times, providing a detailed timeline of the event.
===Basic Operation===
'''Basic Crash Detection'''
* IMU Reading: Each new acceleration vector is compared against the configured threshold.
* Threshold Exceeded: If the threshold is met or exceeded for the configured duration, the device flags a crash as “ongoing.”
* Hysteresis Check: The crash continues until acceleration falls 30% below the threshold.
* Crash Event: Once the acceleration returns below threshold, a Crash Event (AVL ID 247) is generated, and the crash is marked as ended.
'''Advanced Crash Detection'''
* Basic Detection as Trigger: Advanced Crash runs alongside Basic Crash. When Basic Crash sees a threshold exceedance, Advanced Crash also begins data collection on all three axes.
* Extended Metrics: As long as the device is in a crash state, the algorithm accumulates samples to compute maximum and average magnitudes/amplitudes, as well as crash direction.
* Crash End & Record: When the crash ends (per Basic Crash hysteresis), Advanced Crash finalizes its calculations and outputs a single AVL record (ID 247) with the extended data fields.
'''Crash Trace'''
* Data Collection: Accelerometer (~400 Hz) and GNSS (1 Hz) data are continuously buffered.
* Crash Start: If a crash is detected, a preliminary Crash Event (AVL ID 247, value=1) is generated. The device continues collecting data for the specified time window after the crash trigger.
* Crash End: The device finalizes the crash trace data and generates a full crash trace record (AVL ID 247 which includes:
** AVL ID 257: High-frequency accelerometer data.
** GNSS PVT data.
** Crash trace event type.
* Logging & Timestamps: The record’s timestamps correspond to the actual collection times, capturing the event’s progression before, during, and after the crash.
'''Records & Logging'''
* All crash scenarios culminate in event records with AVL ID 247.
* Advanced Crash adds extended crash metrics into the same event record.
* Crash Trace finalizes with an additional record containing AVL ID 257 for high-frequency accelerometer samples.


'''Network Mode Awareness'''
==Private / Business mode==
* The device should correctly identify whether it is in '''Home''' or '''Roaming''' mode.  
[[File:Private business mode TCT panel.png|right|500px]]
'''Movement Detection'''
This feature enables employees to use company vehicles for personal purposes while maintaining compliance with EU General Data Protection Regulation requirements. When Private mode is active, the device masks location data and other sensitive information to prevent unauthorized tracking. Business mode restores full data visibility for standard fleet operations.
* The device needs a method (e.g., GNSS speed threshold, accelerometer, or ignition source) to determine whether it is currently '''Moving''' or '''On Stop'''.
'''Configuration Access'''
* A configuration tool or firmware interface is required to set the acquisition intervals and thresholds for each combination of '''GSM''' and '''Movement''' modes.


=== <u>Parameter Description</u> ===
Private/Business Mode is used in fleet operations where employees may drive company vehicles for both work and personal needs. It helps ensure privacy during personal use by disabling location reporting, while still providing full tracking and operational data during business use.
'''Data Acquisition Profiles''' <br>


Each combination of '''GSM Mode''' (Home, Roaming) and '''Movement Mode''' (Moving, On Stop) can have its own acquisition settings. Typical parameters within each profile include:
In the TCT Features section, the Private / Business Mode allows the user to configure when the private mode should activate and deactivate by selecting one of the available feature triggers: a weekly scheduler or an external trigger type.
 
Additionally, the user can define how the system should handle GNSS and odometer data while private mode is active.
* '''Min Saved Records'''
The feature also supports automatic deactivation of private mode when specific events are detected, such as Unplug, Towing, and other configured triggers.
**  The minimum number of coordinates (records) that must be accumulated before the device attempts to send data to the server.
=== Prerequisites and Important Settings ===  
* '''Send Period'''
* After exiting any sleep mode, DOUT and Private/Business state will '''automatically return''' to the values they had before entering the sleep mode.
**  Defines how often (in seconds or minutes) the device checks whether it has met the '''Min Saved Records''' threshold. If enough records are available, the device sends them; otherwise, it waits until the next send period.<br>
=== Basic Operation ===  
 
* In the Private/Business window, the user can set the priority level used for sending messages (HIGH or LOW priority).
'''Note''': The device internally uses GMT+0 without daylight saving.<br>
* The DOUT control function allows indicating the state of Private Mode.When Private Mode is detected as ON, the configured DOUT output will also be switched ON.
 
==== DOUT State in Sleep mode ====
 
In different sleep modes, DOUT behavior and Private/Business states are:
'''Data Collection Methods'''
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
 
<tr>
The device can collect records using one or more of the following methods '''simultaneously''':
<th style="width:15%; vertical-align: middle; text-align: center;">MODE</th>
'''Time-Based Data Acquisition (Min Period)'''
<th style="width:15%; vertical-align: middle; text-align: center;">DOUT STATE</th>
* Acquires a record each time a specified interval of time passes.
<th style="width:50%; vertical-align: middle; text-align: center;">PRIVATE/BUSINESS MODE STATE</th>
* Setting this to zero '''disables''' time-based acquisition.
</tr>
'''Distance-Based Data Acquisition (Min Distance)'''
<tr>
* Acquires a record when the device’s traveled distance (from the last recorded coordinate) exceeds a specified value (in meters).
<td style="vertical-align: middle; text-align: left;">Online Sleep</td>
* Setting this to zero '''disables''' distance-based acquisition.
<td style="vertical-align: middle; text-align: left;">Last state before entering sleep</td>
'''Angle-Based Data Acquisition (Min Angle)'''
<td style="vertical-align: middle; text-align: left;">Last state before entering sleep</td>
* Acquires a record when the angle difference between the last recorded coordinate and the current heading exceeds a defined threshold (in degrees).
</tr>
* Setting this to zero disables angle-based acquisition.
<tr>
'''Speed-Based Data Acquisition (Min Speed Delta)'''
<td style="vertical-align: middle; text-align: left;">Deep Sleep</td>
* Acquires a record when the difference in speed (from the last recorded speed) exceeds a defined threshold (in km/h or m/s, depending on configuration).
<td style="vertical-align: middle; text-align: left;">Last state before entering sleep</td>
* Setting this to zero '''disables''' speed-based acquisition.
<td style="vertical-align: middle; text-align: left;">Last state before entering Deep Sleep</td>
 
</tr>
=== <u>Expected Behavior</u> ===
<tr>
 
<td style="vertical-align: middle; text-align: left;">Power Off Sleep</td>
'''Record Collection'''
<td style="vertical-align: middle; text-align: left;">DOUT is OFF</td>
* The device continuously checks for any of the enabled conditions (time, distance, angle, speed).
<td style="vertical-align: middle; text-align: left;">Last state before entering Power Off Sleep</td>
* If any threshold is met (e.g., Min Period elapsed, Min Distance exceeded), a new record is stored in internal memory.
</tr>
'''Record Storage & Batching'''
* Records are accumulated until Min Saved Records is reached or the Send Period timer expires.
* If neither condition is met, the device continues to collect data without initiating a connection.
'''Data Transmission'''
* Once '''Min Saved Records''' is reached or the '''Send Period''' elapses (whichever comes first), the device attempts to send all stored records to the server.
* If the device is in '''Roaming''' mode, it may use less frequent intervals to reduce data costs (based on your configuration).
'''Profile Switching'''
* The device automatically switches to the corresponding profile when it detects changes in '''GSM Mode''' (Home ↔ Roaming) or '''Movement Mode''' (Moving ↔ On Stop).
* For instance, if the vehicle transitions from moving to a standstill, the device switches from the “Moving” to the “On Stop” settings.
'''Configuration Overrides'''
* Certain high-priority events (e.g., crashes, alarms) may override the data acquisition intervals and send records immediately, regardless of the configured mode.
 
 
 
==Eye-Sensor custom monitoring scenario==
=== <u>Overview</u> ===
The Custom Monitoring scenario utilizes the '''Teltonika Telematics EYE Sensor''' to track device '''appearance/disappearance events''' and update selected '''IO elements'''. This scenario is based '''on Bluetooth Low Energy (BLE) advertisement data''' provided by the EYE Sensor.<br>
 
'''Purpose''':
* Detect when a device '''appears or disappears''' from the monitored area.
* Fill '''chosen IO elements''' with relevant data.
* Ensure '''periodic updates''' based on user-defined preferences.
'''Default Behavior''':
* The '''Custom Monitoring scenario is enabled by default''' but can be manually '''enabled/disabled''' by the user.
 
=== <u>Functionality</u> ===
 
'''Device Appearance & Disappearance Tracking''':
* The scenario continuously monitors BLE advertisement data.
* When a device '''enters or leaves the monitored area''', it '''logs an event''' and updates the IO elements.
'''User-Defined IO Elements''':
* The user can '''select specific IO elements''' to store data.
* These IO elements are updated when the device is detected or lost.
'''Periodic Data Updates''':
* The scenario ensures '''regular updates''' of the chosen IO elements.
* Helps in '''continuous monitoring''' and '''historical analysis''' of device activity.
'''Global vs. User Configuration''':
* By default, the scenario operates under a '''global configuration'''.
* Users have the option to '''customize the settings''' or disable the feature if needed.
 
=== <u>Prerequisites</u> ===
 
To use the '''Custom Monitoring''' scenario effectively, the following requirements must be met:
'''Compatible Device''':
* The monitoring device must support '''BLE-based communication''' with '''Teltonika EYE Sensors'''.
'''Firmware & Configuration''':
* The tracking device must be running '''compatible firmware''' that supports Custom Monitoring.
* The scenario must be '''enabled''' in the device settings (default '''setting: ON).
IO Element Selection''':
a. The user must specify which '''IO elements''' should be updated when the device '''appears or disappears'''.
'''Power & Connectivity''':
* The '''EYE Sensor''' must be powered and within '''BLE range''' of the monitoring device.
* The monitoring device must have '''Bluetooth enabled''' to receive BLE advertisements.
 
==Private/Business Scenario==
=== <u>Overview</u> ===
The '''Private/Business Mode''' feature allows users to '''hide personal information''' when a business vehicle is used for private purposes. This ensures '''privacy protection''' by preventing location tracking and odometer updates when the vehicle is in '''Private Mode'''.
* '''Private Mode''': The device will indicate that the vehicle is in private mode and will '''not send coordinates''' to the server. Additionally, the odometer can be stopped to prevent distance tracking.
* '''Business Mode''': The device will function normally, with all data being sent and recorded without restrictions.
This feature is crucial for '''fleet management''' and '''business-owned vehicles''' where employees may use company vehicles for personal use.
 
=== <u>Functionality</u> ===
The '''Private/Business Mode''' works as follows:
'''Mode Selection''':
* When '''Private Mode is ON''', the vehicle's location is '''not shared''', and optionally, odometer tracking can be '''disabled'''.
* When P'''rivate Mode is OFF''' (Business Mode ON), the device works as usual, sending all data to the server.
'''Triggering Mechanisms''':
* '''Digital Inputs (DINs)''': A set of '''configurable digital inputs''' can trigger Private Mode when activated.
* '''Weekly Schedule''': The system can '''automatically switch modes''' based on a configured weekly schedule.
* '''Special Conditions''': Private Mode can also be activated/deactivated by events like '''towing, unplug detection, crash detection, or auto-geofencing'''.
'''GNSS Data Masking''':
* The system can '''mask GPS data''' in different ways when Private Mode is active:
** '''Option 1''': No masking (data is still visible).
** '''Option 2''': GNSS data is replaced with '''zeros'''.
** '''Option 3''': GNSS data remains at the '''last known good position''' before Private Mode was enabled.
'''Odometer Control''':
* When Private Mode is ON, odometer tracking can be '''disabled''' to prevent distance accumulation during personal use.
'''DOUT Control''':
* The device can '''trigger an external output (DOUT)''' when switching modes (e.g., to activate an indicator light showing the current mode).
'''Daylight Saving Adjustments''':
* The system supports '''automatic daylight saving time adjustments''', ensuring that the schedule remains accurate throughout the year.
 
=== <u>Prerequisites</u> ===
To ensure proper operation of the '''Private/Business Mode''', the following conditions must be met:
'''Device Compatibility''':
* The tracking device must support '''Private/Business Mode functionality'''.
* The device should have '''digital inputs (DINs)''' or s'''chedule configuration options enabled'''.
'''Firmware & Configuration''':
* The device must run a firmware version that supports '''Private/Business Mode'''.
* The mode-switching triggers (DINs, schedule, or special conditions) must be '''properly configured''' in the device settings.
'''GNSS & IO Elements Setup''':
* If using '''GPS masking''', ensure the appropriate masking option is selected.
* If using '''odometer stop''', confirm that it is '''enabled''' in the configuration.
'''Power & Connectivity''':
* The device should be '''powered on''' and '''connected''' to receive trigger signals.
* If using a '''weekly schedule''', ensure the system's '''time zone and daylight saving settings''' are correctly configured.
'''Trigger Setup''':
* If using '''digital inputs (DINs)''' to switch modes, ensure the correct DINs are assigned in the configuration.
* If using a '''weekly schedule''', configure the start and end times for business mode on each required day.
 
 
==False Mounting Scenario==
=== <u>Introduction</u> ===
The '''False Mounting Scenario''' is designed to detect '''incorrect device mounting''' using '''GNSS and IMU data'''. Improper mounting can cause '''false acceleration readings''', leading to incorrect scenario triggers and inaccurate data. This feature ensures the '''device operates correctly''' by detecting mounting issues and notifying users when adjustments are needed.
 
=== <u>Prerequisites</u> ===
Before enabling the False Mounting Scenario, ensure the following:
'''Device Compatibility''':
* The device must support '''IMU (Inertial Measurement Unit) and GNSS data'''.
* The scenario should be enabled in the '''device configuration settings'''.
'''Firmware & Configuration''':
* Ensure the device firmware '''supports the False Mounting Scenario'''.
* The scenario must be '''properly configured''' in the device settings.
'''GNSS & IMU Requirements''':
* A '''valid GNSS fix''' is required.
* The GNSS speed must be '''above 10 km/h''' for accurate detection.
* '''Accelerometer calibration status must be Full.'''
Power & Ignition Conditions:
* The '''ignition must be ON''' for the scenario to activate.
* If ignition is OFF, the scenario will '''not run or will reset'''.
'''Environmental Factors''':
* The device should not be '''exposed to extreme vibrations''' outside of normal usage conditions.
* '''Proper device mounting''' is required before scenario activation to establish a baseline.
 
=== <u>Why It Is Needed</u> ===
Incorrect mounting can result in:
* '''Inaccurate IMU data readings'''
* '''False acceleration detections'''
* '''Incorrect scenario activation'''
* '''Unreliable device behavior'''
By detecting false mounting conditions, the system helps users '''correct device placement''' for optimal performance.
 
=== <u>How It Works</u> ===
The scenario follows these steps:<br>
 
'''Checks if the scenario is enabled''' in the configuration.<br>
'''
Verifies all conditions''' required to run the scenario:
* '''Ignition is ON'''
* '''Accelerometer calibration status is Full'''
* '''PVT (Position, Velocity, Time) is valid''' (GNSS fix and speed above 10 km/h)
* '''Device is not already flagged''' for false mounting
'''Runs the scenario''' to evaluate mounting conditions.<br>
 
'''Uses condition checkers''' (e.g., High Vibrations Checker) to detect false mounting.<br>
 
'''Clears scenario data''' when the '''ignition is turned off'''.
 
=== <u>Condition Checkers</u> ===
The '''Faulty Device Mounting I/O Element (IOAVL 1452)''' determines the mounting status:
* '''0''' → Correctly mounted (No issue detected).
* '''1''' → High vibrations detected (Possible incorrect mounting).
Currently, the scenario includes the '''High Vibrations Checker''', with more condition checkers planned for future updates.<br>
 
=== <u>High Vibrations Checker</u> ===
This checker detects false mounting by '''comparing GNSS and IMU acceleration differences''' over a specific time period. The evaluation period depends on the '''GNSS fix rate''':
 
<table class="nd-othertables_2" style="width:80%; margin-bottom: 30px;">
    <tr>
        <th style="width:10%; text-align: left;">'''GNSS Fix Rate'''</th>
        <th style="width:10%; text-align: left;">'''Evaluation Period (x ms)'''</th>
 
        <th rowspan="13" style="width:30%; text-align: center; vertical-align: middle;">
        </th>
 
    <tr>
        <td style="text-align: left;">1 Hz</td>
        <td style="text-align: left;">1000 ms</td>
    </tr>
    <tr>
        <td style="text-align: left;">2 Hz</td>
        <td style="text-align: left;">500 ms</td>
    </tr>
    <tr>
        <td style="text-align: left;">5 Hz</td>
        <td style="text-align: left;">200 ms</td>
    </tr>
    <tr>
        <td style="text-align: left;">10 Hz</td>
        <td style="text-align: left;">100 ms</td>
    </tr>
</table>
</table>
After exiting any sleep mode, DOUT and Private/Business state return to the state they were in before entering the sleep mode.


'''False Mounting Triggers When''':
GNSS Data Masking defines how the device will handle location information (GNSS data) while in Private Mode:
* '''Max difference between GNSS and IMU acceleration''' on '''X or Y axis''' exceeds 4'''00 mg'''.
* '''IMU acceleration change''' on '''X or Y axis''' exceeds '''500 mg''' within the evaluation period.


'''(Thresholds are based on testing and may change over time.)
* No masking – GNSS information is not hidden.
'''
* GNSS data is sent as zero – In every record sent to the server, the GNSS fields (latitude, longitude, altitude, angle, and number of satellites) are set to "0". Additionally, GSM Cell ID and GSM Area Code information will not be sent.
* GNSS data is sent as last known good position – The last valid GNSS data (latitude, longitude, altitude) recorded before entering Private Mode is sent in every record.
The following I/O elements are sent as "0":
* GSM Cell ID (AVL ID 205)
* GSM Area Code (AVL ID 206)
* Private Mode Odometer Stop - when enabled, the device does not accumulate odometer data while Private Mode is active.
* Private Business Deactivation – enables the system to automatically deactivate Private Mode based on selected scenarios.
Available scenarios include: Towing, Unplug, Crash and Autogeofence. The user can select one, several, or all scenarios from the dropdown menu.


=== <u>Expected Behavior</u> ===
''NOTE! If  Trigger type is  set to '''External''', the user must press the button or switch again to re enable Private Mode. If Trigger type is set to '''Weekly Schedule''', the user must wait until the next scheduled activation time for Private Mode to be enabled again.''
====Feature Triggers====
This section allows the user to configure the trigger logic that switches the feature between '''Private Mode''' and '''Business Mode'''.


'''Correct Mounting''':
<big>'''Trigger Types'''</big>
* '''IOAVL 1452 = 0''' → Device is correctly mounted.<br>


'''Incorrect Mounting''':
'''1. External'''
* '''IOAVL 1452 > 0''' → False mounting detected.


==Eye-Sensor activity monitoring scenario==
External triggers can be configured using Digital Inputs (DINs).
When External is selected, the user can choose a specific DIN for the trigger logic.


=== <u>Introduction</u> ===
DIN Mode Options:
* Button Mode. The selected DIN operates as a button. Private Mode is activated or deactivated when the DIN status changes (triggered on the status transition).
* Switch Mode. The selected DIN operates as a switch. Private Mode is controlled based on the current DIN value:
** DIN = HIGH → Private Mode enabled
** DIN = LOW → Private Mode disabled


The '''Activity Monitoring''' Scenario is designed to track the presence of '''Teltonika Telematics EYE Sensor''' devices by monitoring their '''BLE advertisement data'''. This functionality allows the system to detect when a device '''appears''' or '''disappears''' from the monitored area, ensuring continuous tracking and logging of sensor activity.
<big>'''2. Weekly Schedule'''</big>
When the EYE Sensor is in the field, the scenario updates all '''IO elements''' provided by the device and generates periodic records to maintain an accurate activity log.
[[File:Private Business mode Weekly schedule.png|right|500px]]
A weekly schedule can be configured to automatically enable Private Mode at specific times based on the user defined schedule.


=== <u>Functionality</u> ===
Enables automatic switching between Private Mode and Business Mode based on configured time, date, daylight saving rules and time zones.
The '''Activity Monitoring Scenario''' operates as follows:


'''Detecting BLE Advertisements:'''
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
* The scenario listens for BLE advertisement signals from EYE Sensor devices.
<tr>
* If a device is detected, it is added to the active monitoring list.
<th style="width:15%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
'''Monitoring Device Presence:'''
<th style="width:15%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
* The system continuously checks for '''appear/disappear events.'''
<th style="width:50%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
* If a device stops sending signals (disappears), the scenario updates the monitored device list accordingly.
<th style="width:20%; vertical-align: middle; text-align: center;">VALUES</th>
'''Updating IO Elements:'''
</tr>
* When a device is active, the scenario updates '''all IO elements''' provided by the EYE Sensor.
<tr>
* Periodic records are generated to ensure real-time status updates.
<td>Private/Business mode</td>
'''Scenario Enable/Disable Option:'''
<td>391</td>
* While the scenario is part of the '''global configuration''', users have the option to '''enable or disable it manually.'''
<td>Private/Business mode where:<br>
* By default, the '''Activity Monitoring Scenario is always enabled.'''
0 - Private mode OFF (Business mode ON);<br>
 
1 - Private mode ON (Business mode OFF);</td>
=== <u>Prerequisites</u> ===
<td>Min: 0<br>Default: 0<br>Max: 1</td>
To ensure proper operation of the '''Activity Monitoring Scenario''', the following conditions must be met:
</tr>
'''Device Compatibility:'''
<tr>
* The scenario requires a '''Teltonika Telematics EYE Sensor''' with BLE functionality.
<td>Private/Business mode triggers</td>
* The tracking device must support '''BLE scanning and advertisement processing.'''
<td>11811</td>
'''Firmware & Configuration:'''
<td>Private/Business mode triggers. When a trigger is activated it activates the private mode. When the trigger goes low the private mode is turned OFF and device works in a business mode. Implemented using bit mask so that multiple choices could be selected where:<br>0 - no trigger;<br>1 - DIN1;<br>2 - DIN2;<br>3 - DIN3;<br>4 - DIN4;</td>
* The device must run a firmware version that supports '''Activity Monitoring'''.
<td>Min: 0<br>Default: 0<br>Max: 15</td>
* The scenario must be '''enabled in the device’s configuration settings''' (if not using the default setting).
</tr>
'''BLE Signal Conditions:'''
<tr>
* The EYE Sensor must be '''within range''' of the tracking device’s BLE receiver.
<td>Private/Business DOUT control</td>
* BLE signal interference should be minimized to ensure '''consistent detection'''.
<td>11812</td>
'''Power & Connectivity:'''
<td>Private/Business DOUT. When the private mode is active the selected DOUT is turned ON, when the private mode is OFF DOUT needs to go low also. Parameter values:<br>0 - DOUT control disabled;<br>1 - DOUT1;<br>2 - DOUT2;<br>3 - DOUT3;<br>4 - DOUT4;</td>
* The tracking device should be '''powered on''' and capable of processing BLE advertisements.
<td>Min: 0<br>Default: 0<br>Max: 4</td>
* A '''stable power supply''' is required to maintain continuous monitoring.
</tr>
'''Data Collection & Logging:'''
<tr>
* The device must be configured to '''log periodic records''' for accurate activity tracking.
<td>GPS data masking</td>
* Ensure the system has sufficient '''storage capacity''' for storing sensor data.
<td>11813</td>
 
<td>GPS data masking describes how the GPS data is being masked when the device is in private mode. The parameter values are:<br>0 - No masking;<br>1 - GNSS data is sent as zero;<br>2 - GNSS data is sent as last good known position</td>
 
<td>Min: 0<br>Default: 1<br>Max: 2</td>
==Eye-Sensor magnet detection scenario==
</tr>
 
<tr>
=== <u>Introduction</u> ===
<td>Private mode odometer stop</td>
This scenario enables '''magnet detection''' using the '''Teltonika Telematics EYE Sensor''', allowing users to track '''door, gate, or valve openings and closings''' based on magnet presence. When a magnet is detected or removed, the device generates an '''I/O event''', notifying the user of the state change.
<td>11815</td>
 
<td>If enabled stops odometer calculation for Odometer and Trip scenarios in Private mode:<br>0 - Disabled;<br>1 - Enabled;</td>
=== <u>Prerequisites</u> ===
<td>Min: 0<br>Default: 0<br>Max: 1</td>
 
</tr>
To use this scenario, the following conditions must be met:<br>
<tr>
 
<td>Private mode deactivation triggers</td>
'''Compatible Hardware''' – Requires a Teltonika EYE Sensor capable of magnet detection.<br>
<td>11816</td>
 
<td>Private mode deactivation triggers. When a trigger is activated it deactivates the private mode. Implemented using bit mask so that multiple choices could be selected where:<br>
'''BLE Support''' – The tracking device must support Bluetooth Low Energy (BLE) scanning.<br>
0 - no trigger;<br>
 
1 - Towing detected;<br>
'''Scenario Activation''' – The scenario is enabled by default but can be manually enabled/disabled by the user.
2 - Unplug detected;<br>
 
3 - Towing or Unplug detected;<br>
=== <u>How It Works</u> ===
4 - Crash detected;<br>
* The '''EYE Sensor''' monitors for the presence or absence of a magnet.
5 - Towing or Crash detected;<br>
* When the '''magnet is detected''', the scenario registers a '''closed state''' (e.g., door closed).
6 - Unplug or Crash detected;<br>
* When the '''magnet is removed''', the scenario registers an '''open state''' (e.g., door opened).
7 - Towing, Unplug or Crash detected;<br>
* The device generates an '''I/O event''' upon any state change.
8 - Autogeofence triggered;<br>
 
9 - Towing or Autogeofence triggered;<br>
=== <u>Scenario States</u> ===
10 - Unplug or Autogeofence triggered;<br>
 
11 - Towing, Unplug or Autogeofence triggered;<br>
'''Magnet Present (Closed State)''':
12 - Crash or Autogeofence triggered;<br>
* The sensor '''detects the magnet''', indicating that the '''door, gate, or valve is closed'''.
13 - Towing, Crash or Autogeofence triggered;<br>
* An '''I/O event is recorded''' to log the closed state.
14 - Unplug, Crash or Autogeofence triggered;<br>
'''Magnet Removed (Open State)''':
15 - Towing, Unplug, Crash or Autogeofence triggered</td>
* The sensor no longer detects the magnet, indicating that the '''door, gate, or valve is open'''.
<td>Min: 0<br>Default: 15<br>Max: 15</td>
* An '''I/O event is recorded''' to log the open state.
</tr>
'''User-Controlled Activation''':
<tr>
* The scenario is '''enabled by default''', but users can '''manually enable or disable''' it as needed.
<td>Private/Business mode Weekly Schedule Monday Enable</td>
 
<td>11818</td>
==Eye-Sensor Temperature/Humidity monitoring scenario==
<td>If enabled automatically disables private mode on Monday during configured time:<br>
 
0 - Disabled;<br>
=== <u>Introduction</u> ===
1 - Enabled</td>
This scenario monitors '''Bluetooth Low Energy (BLE) temperature and humidity sensors''', dynamically tracking detected devices and logging environmental changes.
<td>Min: 0<br>Default: 1<br>Max: 1</td>
=== <u>Prerequisites</u> ===
</tr>
To ensure the scenario functions correctly, the following conditions must be met:<br>
<tr>
 
<td>Private/Business mode Weekly Schedule start time of a Business mode on Monday</td>
'''BLE Support''' – The device must support '''BLE scanning''' to detect temperature and humidity sensors.<br>
<td>11819</td>
 
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Monday</td>
'''Compatible BLE Sensors''' – The scenario works with '''BLE temperature and humidity sensors''' that broadcast their data.<br>
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
 
</tr>
'''BLE Event Handling''' – The device must process the following '''BLE events''':
<tr>
* ble.device_detected – Triggered when a new BLE sensor is detected.
<td>Private/Business mode Weekly Schedule end time of a Business mode on Monday</td>
* ble.device_expired – Triggered when a BLE sensor is no longer detected.
<td>11820</td>
 
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Monday</td>
=== <u>How It Works</u> ===
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
* The scenario '''automatically tracks BLE sensors''' in real time.
</tr>
* When a '''new sensor is detected''', the scenario '''adds it to the monitored list''' and logs its data.
<tr>
* If a '''previously monitored sensor disappears''', it is '''marked as expired''', and the scenario updates its status.
<td>Private/Business mode Weekly Schedule Tuesday Enable</td>
* The device '''updates IO elements''' to reflect temperature and humidity changes.
<td>11821</td>
 
<td>If enabled automatically disables private mode on Tuesday during configured time:<br>
=== <u>Scenario States</u> ===
0 - Disabled;<br>
'''Device Detection''':
1 - Enabled</td>
* When a BLE sensor is detected (ble.device_detected), the scenario adds it to the active monitoring list.
<td>Min: 0<br>Default: 1<br>Max: 1</td>
* It differentiates between '''newly detected sensors''' and those that are '''already being tracked'''.
</tr>
'''Data Monitoring & Logging''':
<tr>
* The scenario continuously monitors temperature and humidity values.
<td>Private/Business mode Weekly Schedule start time of a Business mode on Tuesday</td>
* If significant changes occur, '''an event is recorded''' to log the updated readings.
<td>11822</td>
* The scenario updates '''IO elements''' to reflect the latest environmental data.
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Tuesday</td>
'''Device Expiration''':
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
* If a BLE sensor is no longer detected for a configured time (ble.device_expired), the scenario marks it as expired.
</tr>
* The scenario removes it from the active monitoring list and updates IO elements accordingly.
<tr>
'''Continuous Tracking''':
<td>Private/Business mode Weekly Schedule end time of a Business mode on Tuesday</td>
* As new BLE sensors appear and old ones expire, the scenario '''dynamically''' '''manages the list''' of monitored devices.
<td>11823</td>
* This ensures that only currently active sensors are logged and processed.
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Tuesday</td>
 
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
=== <u>Expected Behavior</u> ===
</tr>
* '''Real-time monitoring''' of BLE temperature and humidity sensors.
<tr>
* '''Automatic tracking''' of newly detected and expired sensors.
<td>Private/Business mode Weekly Schedule Wednesday Enable</td>
* '''Logging of temperature and humidity changes''' for records and reports.
<td>11824</td>
* '''IO element updates''' to reflect the latest sensor readings.
<td>If enabled automatically disables private mode on Wednesday during configured time:<br>
 
0 - Disabled;<br>
==Manual Geofence scenario==
1 - Enabled</td>
 
<td>Min: 0<br>Default: 1<br>Max: 1</td>
=== <u>Prerequisites</u> ===
</tr>
 
<tr>
Users can configure '''up to 50 Manual Geofence scenarios''' at the same time.
<td>Private/Business mode Weekly Schedule start time of a Business mode on Wednesday</td>
Each geozone can be one of two shapes:
<td>11825</td>
* '''Circle''': Defined by center coordinates (Latitude, Longitude) and a radius.
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Wednesday</td>
* '''Rectangle''': Defined by two corner coordinates (northwest and southeast).
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
 
</tr>
=== <u>Configurable Parameters</u> ===
<tr>
 
<td>Private/Business mode Weekly Schedule end time of a Business mode on Wednesday</td>
Each Manual Geofence scenario includes the following settings:<br>
<td>11826</td>
 
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Wednesday</td>
'''Priority''': Enables or disables the scenario.<br>
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
 
</tr>
'''Shape Type''':<br>
<tr>
* '''Circle''' – Requires center coordinates and radius.
<td>Private/Business mode Weekly Schedule Thursday Enable</td>
* '''Rectangle''' – Requires two sets of corner coordinates.
<td>11827</td>
 
<td>If enabled automatically disables private mode on Thursday during configured time:<br>
'''Event Type''': Defines when an event is generated:
0 - Disabled;<br>
 
1 - Enabled</td>
* '''On Enter''': Event is triggered when the device enters the geozone.
<td>Min: 0<br>Default: 1<br>Max: 1</td>
* '''On Exit''': Event is triggered when the device exits the geozone.
</tr>
* '''On Both''': Events are triggered for both entering and exiting.
<tr>
 
<td>Private/Business mode Weekly Schedule start time of a Business mode on Thursday</td>
'''Speed Limit Threshold''':
<td>11828</td>
 
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Thursday</td>
* '''Toggle''': Enable or disable speed monitoring.
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
* '''Max Speed (km/h)''': Speed limit for triggering speeding events.
</tr>
 
<tr>
'''Geozone Parameters''':
<td>Private/Business mode Weekly Schedule end time of a Business mode on Thursday</td>
 
<td>11829</td>
* '''Circle Radius (m)''': Defines the size of a circular geozone.
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Thursday</td>
* '''Frame Border (m)''': Expands the geozone slightly when entering to prevent false exit events.
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
 
</tr>
'''Coordinate Parameters''':
<tr>
 
<td>Private/Business mode Weekly Schedule Friday Enable</td>
* '''Circle''': Requires one set of coordinates (Latitude, Longitude).
<td>11830</td>
* '''Rectangle''': Requires two sets of coordinates (northwest and southeast).
<td>If enabled automatically disables private mode on Friday during configured time:<br>
 
0 - Disabled;<br>
=== <u>How It Works</u> ===
1 - Enabled</td>
Each configured Manual Geofence scenario runs every second and checks if its conditions are met. The geozone tracks two main states:
<td>Min: 0<br>Default: 1<br>Max: 1</td>
 
</tr>
'''In-Zone''': Indicates whether the device is inside the geozone.
<tr>
 
<td>Private/Business mode Weekly Schedule start time of a Business mode on Friday</td>
'''Speeding''': Indicates whether the device is exceeding the speed limit while inside the geozone.
<td>11831</td>
 
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Friday</td>
When a state change occurs (entering/exiting the geozone or starting/stopping speeding), an event is recorded.
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
 
</tr>
=== <u>Expected Behavior</u> ===
<tr>
 
<td>Private/Business mode Weekly Schedule end time of a Business mode on Friday</td>
With these settings, the device will:<br>
<td>11832</td>
 
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Friday</td>
Detect and '''record entry and exit events''' when a vehicle crosses geozone boundaries.
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
Monitor '''speed violations''' inside geozones and generate start/stop speeding events if enabled.<br>
</tr>
 
<tr>
Prevent '''false exit detections''' using the frame border setting.
<td>Private/Business mode Weekly Schedule Saturday Enable</td>
This scenario helps track vehicle movements within '''custom-defined geozones''', ensuring compliance with predefined routes and speed limits.
<td>11833</td>
 
<td>If enabled automatically disables private mode on Saturday during configured time:<br>
==Time synchronization scenarios==
0 - Disabled;<br>
 
1 - Enabled;</td>
=== <u>Introduction</u> ===
<td>Min: 0<br>Default: 1<br>Max: 1</td>
 
</tr>
Accurate system time is essential for proper event logging, record timestamping, and scheduling. The device supports '''two''' primary time synchronization sources: '''GNSS''' and '''SNTP'''. When one source becomes unavailable, the device can fall back to the other to maintain accurate time.
<tr>
 
<td>Private/Business mode Weekly Schedule start time of a Business mode on Saturday</td>
=== <u>Prerequisites</u> ===
<td>11834</td>
 
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Saturday</td>
'''Network Connectivity'''
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
* To use SNTP, the device must be able to connect to the internet
</tr>
'''Configuration Access'''
<tr>
* TCT NTP settings (e.g., synchronization interval, NTP server domains) must be accessible for setup or modification.
<td>Private/Business mode Weekly Schedule end time of a Business mode on Saturday</td>
 
<td>11835</td>
=== <u>Parameter Description</u> ===
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Saturday</td>
'''GNSS Time Synchronization'''
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
* Trigger Condition: If a valid GNSS fix is available and the '''difference''' between the GNSS-provided time and the internal RTC is '''≥ 3 seconds''' for a continuous period of '''5 seconds''', a time correction occurs.
</tr>
* Subsequent Synchronizations: After the first successful sync, the wait time before the device checks for another 3-second difference increases to '''5 minutes''' to prevent excessive corrections.
<tr>
'''SNTP Time Synchronization'''
<td>Private/Business mode Weekly Schedule Sunday Enable</td>
* Trigger Condition: If the device '''lacks a GNSS fix''' for '''60 seconds''', it attempts to synchronize time via '''SNTP'''.
<td>11836</td>
* Resynchronization Interval: Defined by TCT NTP settings (default is '''3 hours''').
<td>If enabled automatically disables private mode on Sunday during configured time:<br>
* NTP Servers: Two servers can be configured; by default, '''pool.ntp.org''' is the primary server and '''time.google.com''' is the fallback. If the first server is unreachable, the device automatically attempts the second.
0 - Disabled;<br>
 
1 - Enabled</td>
=== <u>Expected Behavior</u> ===
<td>Min: 0<br>Default: 1<br>Max: 1</td>
'''GNSS Time Sync Process'''
</tr>
* When GNSS is active, the device continuously compares GNSS time to the internal clock.
<tr>
* If the '''3-second offset''' persists for '''5 seconds''', the clock is updated immediately.
<td>Private/Business mode Weekly Schedule start time of a Business mode on Sunday</td>
* After the first correction, the device waits '''5 minutes''' before checking for another large time discrepancy.
<td>11837</td>
'''SNTP Time Sync Process'''
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Sunday</td>
* If '''no GNSS fix''' is available for '''60 seconds''' (e.g., poor satellite signal, modem off, etc.), the device initiates an SNTP request.
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
* If the primary NTP server is unreachable, it tries the secondary server.
</tr>
* The device repeats this SNTP synchronization after the configured interval (default '''3 hours''').
<tr>
'''Fallback Mechanism'''
<td>Private/Business mode Weekly Schedule end time of a Business mode on Sunday</td>
* GNSS is the first choice for time synchronization.
<td>11838</td>
* When GNSS is not available, SNTP ensures the device clock remains accurate until a valid GNSS fix is restored.
<td>Starting from a configured time until end time disables Private mode and enables Business mode on Sunday</td>
 
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
==Movement scenarios==
</tr>
 
<tr>
=== <u>Prerequisites</u> ===
<td>Private/Business Weekly Schedule Time zone</td>
 
<td>11839</td>
A functional IMU (inertial measurement unit) within the device is required to track and report movement data.
<td>Time in minutes from GMT +00:00. Example: GMT +02:00 is 120</td>
 
<td>Min: -720<br>Default: 0<br>Max: 1440</td>
'''Configuration Tool Access'''
</tr>
* You need the ability to enable or configure Instant/Delayed Movement scenarios and link them to Ignition or Movement.
<tr>
 
<td>Private/Business Weekly Schedule Daylight saving enable</td>
=== <u>Parameter Description</u> ===
<td>11840</td>
 
<td>If enabled automatically adjusts the time for daylight saving;<br>
'''Instant Movement Scenario'''
0 - Disabled;<br>
* Processes '''each sample''' from the IMU sensor.
1 - Enabled</td>
* Generates an '''IO (ID = 303)''' whenever the movement state changes (from idle to moving or moving to idle).
<td>Min: 0<br>Default: 0<br>Max: 1</td>
* Uses internal noise-level estimation; when the vehicle is not moving, the noise level should be minimal.
</tr>
'''Delayed Movement Scenario'''
<tr>
* Relies on the '''Instant Movement''' IO in combination with two delays:
<td>Private/Business Weekly Schedule Daylight saving start week</td>
** '''Start Movement Delay''' – Time the IMU signal must show continuous movement before confirming the vehicle is “moving.”
<td>11841</td>
** '''Stop Movement Delay''' – Time the IMU signal must show no movement before confirming the vehicle is “idle.”
<td>Sets the week when daylight saving starts:<br>
* Events generated through the accelerometer can serve as a source for '''Ignition''' or '''Movement''', allowing further device logic to depend on the detected state.
1 - First week of a month;<br>
 
2 - Second week of a month;<br>
=== <u>Expected Behavior</u> ===
3 - Third week of a month;<br>
 
4 - Fourth week of a month;<br>
'''Instant Movement Detection'''
5 - Last week of a month</td>
* The device continuously monitors each IMU reading.
<td>Min: 0<br>Default: 0<br>Max: 4</td>
* Once the noise threshold is exceeded (indicating motion), IO '''303''' changes from “idle” to “moving.”
</tr>
* If the motion subsides, IO '''303''' reverts to “idle.”
<tr>
'''Delayed Movement Confirmation'''
<td>Private/Business Weekly Schedule Daylight saving start month</td>
* When '''Instant Movement''' reports a change to “moving,” the '''Start Movement Delay''' timer begins. If the motion persists for the entire duration, the device confirms it as “moving.”
<td>11842</td>
* Conversely, once motion ceases and the device reports “idle,” the '''Stop Movement Delay''' timer begins. After this timer elapses without any further movement, the device confirms it as “idle.”
<td>Sets the month when daylight saving starts. A month is represented by a number from 1 to 12</td>
'''Integration with Ignition or Movement'''
<td>Min: 1<br>Default: 1<br>Max: 12</td>
* These Instant or Delayed Movement scenarios can be mapped to the device’s '''Ignition''' or '''Movement''' settings, providing an alternative to traditional ignition detection or GNSS-based movement detection.
</tr>
'''Event Generation'''
<tr>
* When configured, changes in the movement state (detected by IMU) can trigger records or alerts.
<td>Private/Business Weekly Schedule Daylight saving start weekday</td>
* This data can also be used by the device for status reporting, logging, and various user-defined scenarios.
<td>11843</td>
 
<td>Sets the weekday when daylight saving starts:<br>
==LED scenarios==
1 - Monday;<br>
 
2 - Tuesday;<br>
=== <u>Introduction</u> ===
3 - Wednesday;<br>
The device includes '''Navigation''' and '''Status''' '''LEDs''' to provide immediate visual feedback about its operational state. These LEDs inform whether the GNSS is active and acquiring a fix, and whether the device’s GPRS session is established. The feature can be disabled through configuration if a “stealth” mode is required.
4 - Thursday;<br>
 
5 - Friday;<br>
=== <u>Prerequisites</u> ===
6 - Saturday;<br>
 
7 - Sunday</td>
'''Hardware Support'''
<td>Min: 0<br>Default: 0<br>Max: 6</td>
* The device must have functional '''Navigation''' and '''Status''' '''LED''' indicators.
</tr>
'''Configuration Access'''
<tr>
* You must be able to enable or disable LED indications through the device’s configuration tool.
<td>Private/Business Weekly Schedule Daylight saving start time</td>
 
<td>11844</td>
=== <u>Parameter Description</u> ===
<td>Sets the time in minutes when daylight saving starts. A start time is represented by a number from 0 to 1440, where the number represents the minutes from midnight</td>
 
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
'''Navigation LED Indications'''
</tr>
 
<tr>
<table class="nd-othertables_2" style="width:80%; margin-bottom: 30px;">
<td>Private/Business Weekly Schedule Daylight saving end week</td>
    <tr>
<td>11845</td>
        <th style="width:10%; text-align: left;">'''Behavior'''</th>
<td>Sets the week when daylight saving ends:<br>
        <th style="width:10%; text-align: left;">'''Meaning'''</th>
1 - First week of a month;<br>
 
2 - Second week of a month;<br>
        <th rowspan="13" style="width:30%; text-align: center; vertical-align: middle;">
3 - Third week of a month;<br>
        </th>
4 - Fourth week of a month;<br>
 
5 - Last week of a month</td>
    <tr>
<td>Min: 0<br>Default: 0<br>Max: 4</td>
        <td style="text-align: left;">'''Permanently Switched On'''</td>
</tr>
        <td style="text-align: left;">GNSS is running, but a fix has '''not''' been acquired.</td>
<tr>
    </tr>
<td>Private/Business Weekly Schedule Daylight saving end month</td>
    <tr>
<td>11846</td>
        <td style="text-align: left;">'''Short Blink Every Second'''</td>
<td>Sets the month when daylight saving ends. A month is represented by a number from 1 to 12</td>
        <td style="text-align: left;">GNSS is running, and a fix '''has''' been acquired.</td>
<td>Min: 1<br>Default: 1<br>Max: 12</td>
    </tr>
</tr>
    <tr>
<tr>
        <td style="text-align: left;">'''Off'''</td>
<td>Private/Business Weekly Schedule Daylight saving end weekday</td>
        <td style="text-align: left;">GNSS is powered off (e.g., device not active or in sleep).</td>
<td>11847</td>
    </tr>
<td>Sets the weekday when daylight saving ends:<br>
1 - Monday;<br>
2 - Tuesday;<br>
3 - Wednesday;<br>
4 - Thursday;<br>
5 - Friday;<br>
6 - Saturday;<br>
7 - Sunday</td>
<td>Min: 0<br>Default: 0<br>Max: 6</td>
</tr>
<tr>
<td>Private/Business Weekly Schedule Daylight saving end time</td>
<td>11848</td>
<td>Sets the time in minutes when daylight saving ends. An end time is represented by a number from 0 to 1440, where the number represents the minutes from midnight</td>
<td>Min: 0<br>Default: 0<br>Max: 1440</td>
</tr>
<tr>
<td>Private/Business trigger type</td>
<td>11849</td>
<td>Sets Private/Business trigger type:<br>
0 - External trigger such as DIN;<br>
1 - Weekly schedule</td>
<td>Min: 0<br>Default: 0<br>Max: 1</td>
</tr>
<tr>
<td>Private/Business DIN mode</td>
<td>11851</td>
<td>Sets Private/Business DIN mode:<br>
0 - Button: triggers on state change Low -&gt; High;<br>
1 - Switch: triggers on state change Low -&gt; High and High -&gt; Low</td>
<td>Min: 0<br>Default: 0<br>Max: 1</td>
</tr>
</table>
</table>
'''Status LED Indications'''
<table class="nd-othertables_2" style="width:80%; margin-bottom: 30px;">
    <tr>
        <th style="width:10%; text-align: left;">'''Behavior'''</th>
        <th style="width:10%; text-align: left;">'''Meaning'''</th>
        <th rowspan="13" style="width:30%; text-align: center; vertical-align: middle;">
        </th>
    <tr>
        <td style="text-align: left;">'''Blinking Every Second'''</td>
        <td style="text-align: left;">Device is active; '''GPRS session''' is established.</td>
    </tr>
    <tr>
        <td style="text-align: left;">'''On (Solid Light)'''</td>
        <td style="text-align: left;">Device is active; no GPRS session.</td>
    <tr>
        <td style="text-align: left;">'''Off'''</td>
        <td style="text-align: left;">Device is powered off or not operating.</td>
    </tr>
   
</table>
=== <u>Expected Behavior</u> ===
'''Navigation LED Sequence'''
* When powered and searching for a GNSS fix, the '''Navigation LED''' will remain '''On''' until a fix is acquired.
* Once a valid fix is found, the LED will '''blink once every second''' to indicate successful GNSS positioning.
* If the GNSS module is turned off (due to configuration or sleep mode), the '''Navigation LED''' will be '''Off'''.
'''Status LED Sequence'''
* If the device has an active GPRS connection, the '''Status LED''' will '''blink every second'''.
* If the device is active but no GPRS session is established, the '''Status LED''' will remain '''On''' (solid).
* If the device is not powered or is in deep sleep, the '''Status LED''' will be '''Off'''.
'''Disabling LED Indications'''
* If stealth or power savings are desired, the LEDs can be disabled via the configuration tool. This setting will turn both LEDs off, regardless of GNSS or GPRS status.
==IMU (Accelerometer) scenarios==
=== <u>Introduction</u> ===
Two primary scenarios manage IMU-based movement:
'''Instant Movement''':
* Processes every IMU reading and updates an IO (ID = '''303''') whenever the movement state changes.
* Relies on internal noise-level estimation to decide if the vehicle is truly moving or idle.
'''Delayed Movement''':
* Uses the Instant '''Movement IO''' in conjunction with two adjustable delays—'''Start Movement Delay''' and '''Stop Movement Delay'''—to confirm and stabilize movement or idle states.
* Generates movement or idle events that can be used as ignition or movement sources.
=== <u>Prerequisites</u> ===
'''IMU Hardware Support'''
* The device must be equipped with an IMU module that is fully functional.
'''Firmware / Configuration Access'''
* You need access to the device’s configuration tool to enable and set parameters for both Instant and Delayed Movement scenarios (e.g., Config IDs '''19001''' and '''19002''').
'''Device Firmware Compatibility'''
* Ensure the firmware supports IMU-based movement detection. Always refer to release notes for any hardware or firmware requirements.
=== <u>Parameter Description</u> ===
<table class="nd-othertables_2" style="width:80%; margin-bottom: 30px;">
    <tr>
        <th style="width:10%; text-align: left;">'''Parameter'''</th>
        <th style="width:10%; text-align: left;">'''Config ID'''</th>
        <th style="width:20%; text-align: left;">'''Units'''</th>
        <th style="width:10%; text-align: left;">'''Min'''</th>
        <th style="width:10%; text-align: left;">'''Max'''</th>
        <th style="width:20%; text-align: left;">'''Default'''</th>
        <th style="width:20%; text-align: left;">'''Description'''</th>
        <th rowspan="13" style="width:30%; text-align: center; vertical-align: middle;">
        </th>
    <tr>
        <td style="text-align: left;">Motion start detection delay</td>
        <td style="text-align: left;">19001</td>
        <td style="text-align: left;">Seconds</td>
        <td style="text-align: left;">1</td>
        <td style="text-align: left;">60</td>
        <td style="text-align: left;">2</td>
        <td style="text-align: left;">The algorithm reports '''motion start''' only if the IMU detects movement continuously for the entire duration of this delay. If the threshold is exceeded at any point during this time, the vehicle is considered moving.</td>
    </tr>
    <tr>
        <td style="text-align: left;">Motion stop detection delay</td>
        <td style="text-align: left;">19002</td>
        <td style="text-align: left;">Seconds</td>
        <td style="text-align: left;">5</td>
        <td style="text-align: left;">65535</td>
        <td style="text-align: left;">60</td>
        <td style="text-align: left;">The algorithm reports '''motion stop''' only if the IMU detects no movement (below threshold) continuously for the entire duration of this delay. If the threshold is not exceeded for this time, the vehicle is considered idle.</td>
    </tr>
</table>
'''Example Configuration Screenshots'''
* '''Movement Source Selection''':
[[File:FTX-accel-as-movement-source.png|600px]]
* '''Delays Configuration''':
[[File:FTX-accel-as-movement-params.png|800px]]
=== <u>Expected Behavior</u> ===
'''Instant Movement Scenario'''
* The IMU sensor is sampled continuously, and an IO event (ID = '''303''') is triggered whenever the device transitions from “idle” to “moving” or vice versa.
* A noise threshold helps filter out minor vibrations, ensuring only genuine movement causes a state change.
'''Delayed Movement Scenario'''
* Relies on the IO (ID = '''303''') from the Instant Movement scenario.
* Once '''Instant Movement''' indicates activity, the '''Start Movement Delay''' (ID '''19001''') timer begins. Only if movement persists for the entire duration is the vehicle confirmed to be in a “moving” state.
* Likewise, if Instant Movement indicates no activity (idle), the '''Stop Movement Delay''' (ID '''19002''') timer starts. If no motion is detected throughout that delay, the vehicle is confirmed to be idle.
'''Integration with Ignition/Movement'''
* When either scenario confirms a state change (e.g., from idle to moving), that event can serve as the '''Ignition''' or '''Movement''' source in the device’s configuration.
* This enables advanced logic—such as controlling data logging intervals, sending notifications, or updating trip reports—based on accelerometer-driven movement states rather than engine-based signals or GNSS data alone.
'''Record Generation & Logging'''
* If configured, the device can generate periodic or event-based records whenever movement states change.
* These records can be transmitted in real time (if high-priority) or included in periodic data (if low-priority), depending on your device settings.
==Immobilizer scenario==
=== <u>Introduction</u> ===
This feature provides an additional layer of vehicle protection by requiring driver authorization after ignition is turned on. The immobilizer ensures that the vehicle starter remains blocked until an approved authorization method—such as an iButton or iBeacon—is detected.
=== <u>Key Features of the Immobilizer</u> ===
* '''Configurable ignition timeout''': Determines the time after ignition deactivation when the driver is deauthorized.
* '''Output control''': Selects a dedicated relay pin to block or unblock the vehicle starter circuit.
* '''Record generation''': Creates periodic and eventual records with configurable priority.
=== <u>Immobilizer States</u> ===
'''Not Authorized / Waiting for Authorization'''
* Triggered when the ignition is turned '''ON'''.
* If output control is enabled, the device sets the output pin to '''high''', blocking the starter.
* The device waits for an authorization signal (e.g., iButton or iBeacon detection).
* If authorization is confirmed (timestamp of presence check is later than ignition ON timestamp), the output pin is set to '''low''', and the state changes to '''Authorized'''.
'''Authorized'''
* The vehicle starter is '''unblocked''', allowing the driver to start the vehicle.
* Authorization remains valid as long as the ignition signal stays '''ON'''.
==Scheduled wakeup scenario==
=== <u>Introduction</u> ===
The ''Scheduled Wakeup'' scenario enables users to configure '''a device wakeup at specific times''' to '''generate and send a record'''. This feature operates in '''any power mode''', ensuring that the device can wake up and transmit data even when '''not in sleep mode'''.
'''Purpose''':
* Schedule periodic wakeups for record transmission.
* Ensure data updates even when the device is in deep sleep.
* Adjust wakeup times based on transmission delays.
'''Default Configuration''':
* o Wakeup times are set using a '''list of uint16 variables''' in '''HHmm format''' (range: '''0000 – 2359''').
** Example:
*** '''12:00 → 1200'''
*** '''01:45 → 145'''
*** '''01:45 → 145'''
* '''Unconfigured timestamps default''' to 2500.
=== <u>Key Features</u> ===
'''Wakeup Time Compensation'''
* Accounts for the time required to '''wake up, sync time, get GNSS fix, and send data'''.
* After each record transmission, the '''device adjusts the next wakeup time''' based on the time taken.
* If the wakeup process exceeds '''10 minutes''', the adjustment is ignored, and the next wakeup follows the original schedule.
'''Finding the Closest Wakeup Time'''
* The system evaluates a'''ll configured wakeup times''' for the '''current day'''.
* If no valid wakeup times remain, it '''checks the next day's schedule'''.
* The closest wakeup time is determined by:
** '''Calculating the time difference''' between the current time and the next scheduled wakeup.
** Adjusting for '''how many days away''' the next wakeup occurs.
* If no wakeup times are found for an '''entire week''', the scenario will '''not set a timer'''.
'''Time Synchronization Repeat'''
* Ensures that the device '''knows the correct time and day''' for scheduled wakeups.
* If the device '''fails to sync time''', it will:
** Attempt to sync time '''every 15 minutes''' while in sleep mode.
** If unsuccessful, it will dou'''ble the sleep time''' (e.g., '''30 min → 1 hr → 2 hrs''', etc.).
** The sleep duration increases '''until it reaches a maximum of 24 hours'''.
** The process repeats '''until successful time synchronization, the device is turned off, or the battery dies'''.
=== <u>Prerequisites</u> ===
To use the '''Scheduled Wakeup Scenario''', the following must be met:
'''Device Compatibility:'''
* The tracking device must support '''scheduled wakeups and record transmission'''.
'''Time Configuration:'''
* Wakeup times must be '''set in the configurator''' with the correct '''timezone'''.
'''Power & Connectivity:'''
* If the device is in '''deep sleep''', it must have enough battery to wake up and send records.
'''GNSS & Modem Activation:'''
* The device must be able to '''synchronize time and establish a network connection'''.
==Ignition ON counter==
[[File:FTX Ignition ON counter.png|alt=|right|500px]]
=== <u>Introduction</u> ===
The ''Ignition ON Counter'' Monitoring feature continuously tracks how long a vehicle’s ignition remains in the ON state. It serves as an invaluable tool for maintenance schedules, driver oversight, and any application where total engine running time matters.
=== <u>How It Works</u> ===
Counter Increments
* Every 500 ms (half a second) that the ignition is ON, the counter increases by that same half-second.
Persistent Data
* The ignition-on counter is stored in non-volatile memory (NVM). This ensures the counter’s value remains intact across device restarts and power outages.
Saving Conditions
* The device automatically saves the counter value to NVM whenever:
** Ignition transitions from ON to OFF.
** A device restart is about to occur.
** The counter value is changed via configuration (e.g., a manual reset or preset adjustment).
=== <u>Valid AVL Ranges</u> ===
* [10216:10235]
* [10298:10347]
'''Example''': If AVL_ID is 10216 and the OPTION for “priority” is 1, then Parameter ID=1,000,000+(10216×100)+1=1,000,000+1,021,600+1=2,021,601
=== <u>MCAN IO Parameter Calculation</u> ===
For ''MCAN'' IO elements (e.g., MCAN0, MCAN1, MCAN2…), each has three specific parameters: '''CAN Type''', '''CAN ID''', and Data Mask. The '''MCAN IO number''' is the index of the MCAN entry (starting at 0, 1, 2, etc.).
'''''Formulas''''':
'''CAN Type'''<br>
Parameter ID=17,000+(10×MCAN IO number)<br>
'''CAN ID'''<br>
Parameter ID=17,001+(10×MCAN IO number)<br>
'''Data Mask'''<br>
Parameter ID=17,002+(10×MCAN IO number)<br>
'''Examples:'''
* '''MCAN0''' (IO number = 0):
** '''CAN Type''': 17000 + (10 × 0) = 17000
** '''CAN ID''': 17001 + (10 × 0) = 17001
** Data Mask: 17002 + (10 × 0) = 17002
* '''MCAN1''' (IO number = 1):
** '''CAN Type''': 17000 + (10 × 1) = 17010
** '''CAN ID:''' 17001 + (10 × 1) = 17011
** Data Mask: 17002 + (10 × 1) = 17012
* '''MCAN69''' (IO number = 69):
** '''CAN Type''': 17000 + (10 × 69) = 17690
** '''CAN ID''': 17001 + (10 × 69) = 17691
** '''Data Mask''': 17002 + (10 × 69) = 17692
=== <u>Putting It All Together</u> ===
'''Check Your AVL ID Range'''
* If your CAN IO element has an AVL ID in [10216–10235] or [10298–10347], use the first formula for Parameter_ID = 1,000,000 + (AVL_ID * 100) + OPTION.
'''Identify Your MCAN IO Number'''
* If you have an MCAN entry (e.g., MCAN0, MCAN1), use the '''second set of formulas''' to find the corresponding '''CAN Type, CAN ID, and Data Mask''' parameter IDs.
'''Plug In the Numbers'''
* Calculate step by step, ensuring you add the correct base offsets and multipliers.
'''Configure Your Device'''
* Once you have the parameter IDs, set or modify them in your configuration tool to match the desired priority, operand, or other CAN-related settings.
==Static navigation==
[[File:FTX Static navigation.png|right|500 px]]
=== <u>Introduction</u> ===
''Static Navigation'' helps eliminate minor “jumps” in GNSS data when the vehicle or device is actually '''stationary'''. Because GNSS signals can fluctuate, your device might appear to move slightly even when it’s not moving at all. With '''Static Navigation''', speed and position changes are filtered out to provide a more accurate representation of a stationary vehicle.
=== <u>How It Works</u> ===
'''Check Movement Status'''
* The device looks at its movement source (e.g., built-in accelerometer, speed reading from GNSS, etc.).
* If this source indicates the device is '''not moving''', the system '''enables Static Navigation''' (assuming you’ve enabled it in the configurator).
'''Filter GNSS Fluctuations'''
* With Static Navigation on, the device '''discards''' small, spurious position changes from the GNSS.
* The internal angle and speed are treated as '''0''' until genuine movement is detected again.
'''GNSS Data vs. Device State'''
* When movement is detected, Static Navigation '''disables itself''', allowing normal GNSS position updates.
* If the device becomes stationary once more, Static Navigation re-enables to filter out jitter.
<!--
==Fall Down Detection==
[[File:FTX Fall Down Detection.png|right|500 px]]
=== <u>Introduction</u> ===
The ''Fall-Down Detectio''n scenario identifies when a vehicle or piece of equipment has fallen over or is tilted beyond a specified angle. It relies on built-in accelerometer data (IMU) along with information about movement, ground speed, and GPS availability. Once enabled, the scenario calculates a “base vector” to represent the normal upright orientation and raises an alert if the device tilts too far for a set amount of time.
=== <u>Prerequisites</u> ===
'''Scenario Priority'''
* Must be greater than 0 (i.e., not 0) for the scenario to be active.
'''Movement Source & Ground Speed'''
* The device monitors whether the vehicle is moving or stationary, including GNSS ground speed readings.
'''GNSS Fix'''
* A valid GNSS fix is required to establish the device’s orientation baseline (the base vector).
'''IMU (Accelerometer) Data'''
* The scenario uses linear vector data from the accelerometer to detect tilt.
=== <u>How It Works</u> ===
'''Waiting for a Baseline'''
* While the vehicle is '''not moving''' (movement is “inactive”), ground speed is 0 m/s, and there is a valid GNSS fix, the device calculates a base vector from the IMU. This vector represents the normal, upright orientation.
'''Monitoring for Tilt'''
* Once the base vector is set, the scenario continuously compares new IMU readings (the current vector) to the base vector.
* If the '''angle''' between these two vectors exceeds the configured '''Activation Angle''' for at least the '''Activation Timeout''', a fall-down event is triggered.
'''Event Generation'''
* If configured to do so (see '''Generate event''' parameter), the device sends a record indicating that a fall-down has been detected. Depending on the '''Priority''' setting, this record may be sent immediately (high priority) or follow regular data acquisition intervals (low priority).
=== <u>Expected Behavior</u> ===
'''Base Vector Setup'''
* When the vehicle/equipment is stationary (movement “off,” speed = 0, GNSS fix valid), the device measures its upright orientation.
'''Tilt Monitoring'''
* As soon as the base vector is established, incoming IMU data is compared against that baseline.
* If the tilt exceeds the '''Activation Angle''' for the entire '''Activation Timeout''' window, the device flags a fall-down event.
'''Event Response'''
* Depending on '''Priority''' and '''Generate Event''' settings, the fall-down event is either sent right away (if high priority) or included with the next scheduled data record (if lower priority).
* If '''Eventual Records''' is enabled, a detailed record is saved for later review.
=== <u>Example Configuration & Outcome</u> ===
* '''Scenario Priority''': 1 (scenario enabled)
* '''Activation Angle''': 45°
* '''Activation Timeout''': 5 seconds
* '''Generate Event''': 1 (immediate)
* '''Eventual Records''': 1 (yes)
'''What Happens?'''
* The device calculates a base vector when the vehicle is parked (no movement, 0 m/s, valid GNSS).
* If the vehicle tilts more than 45° for over 5 seconds, the device immediately generates a fall-down event record, indicating a possible tip-over.
* The fall-down condition remains active until either reset manually or until conditions change (e.g., the vehicle is returned upright, and the device recalibrates).
-->
=Driving behaviour=
==Crash detection==
[[File:FTX crash detection.png|alt=|right|500px]]
=== <u>Introduction</u> ===
The '''Crash Scenarios''' feature detects and logs vehicle crash events using accelerometer data. The device offers two primary crash detection methods:
* '''Basic Crash Detection''' – Monitors the X and Y axes for sudden spikes in acceleration.
* '''Advanced Crash Detection''' – Builds on Basic Crash but also captures additional metrics (e.g., direction, maximum/average acceleration) and uses all three accelerometer axes.
* A '''Crash Trace''' option is also available, which collects high-frequency accelerometer samples and GNSS data before, during, and after a crash, providing detailed insight into the event.
=== <u>Prerequisites</u> ===
'''Onboard IMU/Accelerometer'''
* The device must have a functioning IMU to measure accelerations accurately.
'''Firmware/Configuration Support'''
* Access to parameter configurations (e.g., '''1024700''' for enabling Basic Crash, '''13102''' for Advanced Crash) and the ability to enable '''Crash Trace'''.
'''GNSS Functionality (Optional)'''
* Required if you plan to capture concurrent GNSS data during a crash trace or rely on GNSS-based scenarios.
=== <u>Parameter Description</u> ===
'''Crash Scenario Threshold'''
* '''Basic Crash''' calculates the acceleration magnitude on '''X and Y axes only''' (to avoid triggering on gravity).
* '''Advanced Crash''' (when enabled) calculates magnitude on all '''three axes''', typically resulting in higher measured values.
'''Basic Crash Detection'''
* '''Crash Event AVL ID''': '''247'''
* '''Crash Detection Priority''' (Parameter ID '''1024700'''): Set to '''Low''' or '''High''' to enable/disable the scenario.
'''Threshold & Duration''':
* When the '''accelerometer magnitude''' exceeds the configured threshold for the configured duration, the device flags a crash.
* The crash state continues until the acceleration drops '''30% below''' the threshold (hysteresis) to prevent multiple crash events from small fluctuations.
'''Advanced Crash Detection'''
* '''Enabled''' if '''Basic Crash''' is enabled '''and''' '''Parameter ID 13102''' is set to “enabled.”
* In addition to basic detection, it:
* Calculates '''crash duration''' and '''direction'''.
* Captures '''maximum''' and '''average''' magnitudes, plus '''amplitudes''' on each axis.
* These extended metrics are included in the '''same AVL record''' (ID '''247''') once the crash ends.
'''Crash Trace'''
* When '''Crash Trace''' is enabled, the device collects high-frequency '''accelerometer''' data (~400 samples/second) plus '''GNSS''' data (1 sample/second).
* Upon a crash event (AVL ID '''247''' with value = 1), data continues to be collected for a configured period before and after the crash.
* A second crash record (AVL ID '''247''', “full crash trace” type) is generated once all data is processed, accompanied by '''AVL ID 257''' for accelerometer axis data.
* '''Crash Trace''' timestamps match the actual collection times, providing a detailed timeline of the event.
=== <u>How It Works</u> ===
'''Basic Crash Detection Flow'''
* '''IMU Reading''': Each new acceleration vector is compared against the '''configured threshold'''.
* '''Threshold Exceeded''': If the threshold is met or exceeded for the '''configured duration''', the device flags a crash as “ongoing.”
* '''Hysteresis Check''': The crash continues until acceleration falls '''30% below''' the threshold.
* '''Crash Event''': Once the acceleration returns below threshold, a '''Crash Event''' (AVL ID 247) is generated, and the crash is marked as ended.
'''Advanced Crash Detection Flow'''
* '''Basic Detection as Trigger''': Advanced Crash runs alongside Basic Crash. When Basic Crash sees a threshold exceedance, Advanced Crash also begins data collection on '''all three axes'''.
* '''Extended Metrics''': As long as the device is in a crash state, the algorithm accumulates samples to compute '''maximum''' and '''average''' magnitudes/amplitudes, as well as crash '''direction'''.
* '''Crash End & Record''': When the crash ends (per Basic Crash hysteresis), Advanced Crash finalizes its calculations and outputs a '''single AVL record (ID 247)''' with the extended data fields.
'''Crash Trace'''
* '''Data Collection''': Accelerometer (~400 Hz) and GNSS (1 Hz) data are continuously buffered.
* '''Crash Start''': If a crash is detected, a preliminary '''Crash Event (AVL ID 247, value=1)''' is generated. The device continues collecting data for the specified time window after the crash trigger.
* '''Crash End''': The device finalizes the crash trace data and generates a '''full crash trace record (AVL ID 247)''', which includes:
** '''AVL ID 257''': High-frequency accelerometer data.
** '''GNSS PVT''' data.
**'''Crash trace event type'''.
* '''Logging & Timestamps''': The record’s timestamps correspond to the actual collection times, capturing the event’s progression before, during, and after the crash.
'''Records & Logging'''
* All crash scenarios culminate in event records with '''AVL ID 247'''.
* '''Advanced Crash''' adds extended crash metrics into the '''same''' event record.
* '''Crash Trace''' finalizes with an additional record containing '''AVL ID 257''' for high-frequency accelerometer samples.


== Overspeeding ==
== Overspeeding ==
Line 943: Line 441:
| [[File:FTX overspeeding without dout.png|alt=|right|500px]]   
| [[File:FTX overspeeding without dout.png|alt=|right|500px]]   
}}
}}
=== <u>Introduction</u> ===
The Overspeeding scenario detects when a vehicle exceeds a configured maximum speed and generates a record. Another record is generated when the speed returns to normal.
 
The '''Overspeeding''' scenario detects when a vehicle '''exceeds a configured maximum speed''' and generates a '''record'''. Another '''record''' is generated when the speed '''returns to normal'''.
*'''Purpose:'''
** Promote '''safe and economic driving'''.
** Provide '''real-time alerts''' on speed violations.
** Generate '''automatic reports''' for fleet management.
 
=== <u>How It Works</u> ===


Purpose:
*Promote safe and economic driving.
*Provide real-time alerts on speed violations.
*Generate automatic reports for fleet management.
===How It Works===
'''Speed Monitoring'''
'''Speed Monitoring'''
* The system continuously '''monitors vehicle speed'''.
* The system continuously monitors vehicle speed.
* If the speed '''exceeds the configured max speed''' by an '''allowed tolerance of 2 km/h''', a record is triggered.
* If the speed exceeds the configured max speed by an allowed tolerance, a record is triggered.
'''Event Recording'''
'''Event Recording'''
* A '''record is generated''' when:
* A record is generated when:
** The vehicle '''exceeds''' the max speed + 2 km/h.
** The vehicle exceeds the max speed + 2 km/h.
** The vehicle speed '''returns to normal''' (below max speed - 2 km/h).
** The vehicle speed returns to normal (below max speed - 2 km/h).
'''Customization Options'''
'''Customization Options'''
* '''Max speed limit:''' Default is '''90 km/h''', but it can be customized.
* Max speed limit: Default is 90 km/h, but it can be customized.
* '''Record priority:''' Can be set to '''low or high''' (adjusted in '''Telematics Configuration Tool (TCT)''' under '''Features → Driving Behavior''').
* Record priority: Can be set to low or high (adjusted in Telematics Configuration Tool (TCT) under Features → Driving Behavior).
* '''Feature status:''' '''Disabled by default''', must be manually '''enabled'''.
* Feature status: Disabled by default, must be manually enabled.
 
===Prerequisites===
=== <u>Prerequisites</u> ===
* The device must have active GNSS tracking to monitor speed accurately.
 
To use the '''Over Speeding Scenario''', the following must be met:
 
'''Feature Activation'''
* Enable the feature in '''Telematics Configuration Tool (TCT)''' under '''Driving Behavior'''.
'''Speed Configuration'''
* Configure the '''max speed limit''' and '''record priority''' as per requirements.
'''GNSS & Data Connectivity'''
* The device must have '''active GNSS tracking''' to monitor speed accurately.


==Trip==
==Trip==
[[File:FTX trip.png|alt=|right|500px]]
[[File:FTX trip.png|alt=|right|500px]]
 
The Trip feature allows users to track vehicle journeys from start to finish based on a combination of ignition, movement, and speed parameters. During an active trip, the device maintains a running odometer (Trip Odometer), which is reset once the trip ends.
=== <u>Introduction</u> ===
===Prerequisites===
 
The '''Trip''' feature allows users to track vehicle journeys from start to finish based on a combination of ignition, movement, and speed parameters. During an active trip, the device maintains a running odometer ('''Trip''' Odometer), which is reset once the trip ends.
 
=== <u>Prerequisites</u> ===
 
'''Ignition and Movement Sources'''
* You must have proper '''Ignition''' and '''Movement''' sources configured in the device (e.g., ignition signal, GNSS, accelerometer) so that the device can detect when the vehicle is actually running and moving.
* You must have proper '''Ignition''' and '''Movement''' sources configured in the device (e.g., ignition signal, GNSS, accelerometer) so that the device can detect when the vehicle is actually running and moving.
'''Trip Odometer I/O'''
* The '''I/O Trip Odometer''' must be enabled for the device to log distance traveled during a trip.
* The '''I/O Trip Odometer''' must be enabled for the device to log distance traveled during a trip.
'''GNSS Connectivity'''
===Parameter Description===
* Since Start Speed is tied to '''GPS speed''', a functioning GNSS module is required for accurate speed measurements.
 
=== <u>Parameter Description</u> ===
 
'''Start Speed'''
'''Start Speed'''
* Defines the minimum GPS speed (in km/h) the vehicle must exceed to begin a trip.
* Defines the minimum GPS speed (in km/h) the vehicle must exceed to begin a trip.
Line 1,003: Line 478:
* An internal I/O value that tracks how far the vehicle travels between '''Trip start''' and '''Trip end'''.
* An internal I/O value that tracks how far the vehicle travels between '''Trip start''' and '''Trip end'''.
* Automatically resets to '''0''' when a new trip begins.
* Automatically resets to '''0''' when a new trip begins.
 
===Basic Operation===
=== <u>How It Works</u> ===
 
'''Trip Start'''
'''Trip Start'''
* The device monitors both '''Ignition''' (configured ignition source) and '''Movement''' (configured movement source).
* The device monitors both Ignition (configured ignition source) and Movement (configured movement source).
* Once '''Ignition''' is ''''''ON'''''', '''Movement''' is ''''''ON'''''', and the vehicle’s '''GPS speed''' exceeds the '''Start Speed''' (default: 5 km/h), the trip is marked as “started.”
* Once Ignition is ON, Movement is ON and the vehicle GPS speed exceeds the Start Speed (default: 5 km/h), the trip is marked as “started.”
'''During the Trip'''
'''During the Trip'''
* The '''Trip Odometer''' increments continuously to reflect the total distance traveled.
* The Trip Odometer increments continuously to reflect the total distance traveled.
* Any event triggers, such as data logging or notifications, will note that the vehicle is in an active trip state.
* Any event triggers, such as data logging or notifications, will note that the vehicle is in an active trip state.
'''Trip End'''
'''Trip End'''
* When the '''Ignition''' source turns '''OFF''', the device starts the '''Ignition''' '''OFF''' Timeout countdown (default: 60s).
* When the Ignition source turns OFF, the device starts the Ignition OFF Timeout countdown (default: 60s).
* If the ignition remains '''OFF''' for the entire timeout duration, the trip is ended.
* If the ignition remains OFF for the entire timeout duration, the trip is ended.
* The '''Trip Odometer''' value is stored and then reset to '''0''' before the next trip begins.
* The Trip Odometer value is stored and then reset to 0 before the next trip begins.
'''Record Generation & Logging'''
'''Record Generation & Logging'''
* Depending on the device’s configuration, a record can be generated at '''Trip start''' and '''Trip end''' to facilitate reporting and analytics.
* Depending on the device’s configuration, a record can be generated at Trip start and Trip end to facilitate reporting and analytics.
* Trip distance data is captured in the '''I/O Trip Odometer''' field, which is useful for fleet management or mileage reporting.
* Trip distance data is captured in the I/O Trip Odometer field, which is useful for fleet management or mileage reporting.


 
==Odometer==
== Odometer==
[[File:FTX odometer.png|alt=|right|500px]]
[[File:FTX odometer.png|alt=|right|500px]]
 
The Odometer scenario calculates the total distance traveled by a vehicle using GNSS data. To ensure accuracy and reduce system load, small thresholds are applied to both distance and speed. The device also performs a sanity check to confirm each new distance reading is valid and reasonable.
=== <u>Introduction</u> ===
===Prerequisites===
 
* You must be able to configure odometer parameters (e.g., ID 11807) and potentially format or reset the device’s non-volatile memory (NVM).
The '''Odometer''' scenario calculates the total distance traveled by a vehicle using '''GNSS''' data. To ensure accuracy and reduce system load, small thresholds are applied to both distance and speed. The device also performs a sanity check to confirm each new distance reading is valid and reasonable.
===Parameter Description===
 
=== <u>Prerequisites</u> ===
 
'''GNSS Coverage'''
* A functioning GNSS module with an active fix is required to measure distance traveled.
'''Device Configuration Access'''
* You must be able to configure odometer parameters (e.g., ID '''11807''') and potentially format or reset the device’s non-volatile memory (NVM).
 
=== <u>Parameter Description</u> ===
 
'''Distance and Speed Thresholds'''
'''Distance and Speed Thresholds'''
* '''Minimum distance to update:''' '''2.5 meters'''
* Minimum distance to update: 2.5 meters
* '''Minimum ground speed to update:''' '''0.42 m/s'''
* Minimum ground speed to update: 0.42 m/s
* These thresholds prevent minor fluctuations from inflating the odometer reading.
* These thresholds prevent minor fluctuations from inflating the odometer reading.
'''Sanity Checks'''
'''Sanity Checks'''
* '''Timestamp Validation:''' The current PVT (position, velocity, time) data must be newer than the previous reading.
* Timestamp Validation: The current PVT (position, velocity, time) data must be newer than the previous reading.
* '''Distance Spike Prevention:''' The device discards any reading suggesting a speed greater than '''350 meters/second''', as it indicates erroneous data.
* Distance Spike Prevention:The device discards any reading suggesting a speed greater than 350 meters/second, as it indicates erroneous data.
'''Total Odometer Value (ID 11807)'''
'''Total Odometer Value (ID 11807)'''
* The '''total distance''' traveled is stored internally (in NVM) to preserve the odometer value.
* The total distance traveled is stored internally (in NVM) to preserve the odometer value.
* This value is written to memory '''every kilometer''' to reduce flash wear.
* This value is written to memory every kilometer to reduce flash wear.
* Manually setting or resetting this parameter (via ID '''11807''') allows the odometer to start from a custom value.
* Manually setting or resetting this parameter (via ID 11807 allows the odometer to start from a custom value.
* After formatting or resetting the NVM, the odometer value may be cleared unless reconfigured.
* After formatting or resetting the NVM, the odometer value may be cleared unless reconfigured.
'''Min/Max Values for ID 11807''':
'''Min/Max Values for ID 11807''':
* '''Minimum''': 0
* Minimum: 0
* '''Maximum''': 4,294,967
* Maximum: 4294967
 
===Basic Operation===
=== <u>How It Works</u> ===
 
'''Odometer Updates'''
'''Odometer Updates'''
* As the vehicle travels, the device checks the '''GNSS'''-reported distance in increments. Once the minimum distance (2.5 m) and speed (0.42 m/s) thresholds are exceeded, it updates the '''total odometer'''.
* As the vehicle travels, the device checks the GNSS-reported distance in increments. Once the minimum distance (2.5 m) and speed (0.42 m/s) thresholds are exceeded, it updates the total odometer.
* Every '''1 km''' increment, the new odometer value is saved to '''NVM'''.
* Every 1 km increment, the new odometer value is saved to NVM.
'''Data Validation'''
'''Data Validation'''
* Each new reading is compared against the previous PVT data. If the time is older or the speed exceeds '''350 m/s''', the reading is disregarded.
* Each new reading is compared against the previous PVT data. If the time is older or the speed exceeds 350 m/s, the reading is disregarded.
* This ensures only valid and realistic data points are recorded.
* This ensures only valid and realistic data points are recorded.
'''Odometer Preservation'''
'''Odometer Preservation'''
* The '''total odometer value''' is maintained even if the device reboots or loses power, unless an NVM format or parameter reset occurs.
* The total odometer value is maintained even if the device reboots or loses power, unless an NVM format or parameter reset occurs.
* To continue from a known distance, set the starting odometer value via '''ID 11807'''. The device will then count upward from that point.
* To continue from a known distance, set the starting odometer value via ID 11807. The device will then count upward from that point.


==Eco driving==
==Eco driving==
[[File:FTX eco driving.png|alt=|right|500px]]
[[File:FTX eco driving.png|alt=|right|500px]]
 
The Eco Driving scenario is designed to detect and analyze aggressive driving behaviors such as, Harsh acceleration, Harsh braking, and Harsh cornering. It uses data from either an accelerometer or GNSS to track driving patterns. When a threshold is exceeded for a specific duration, the system generates an eventual record to highlight unsafe driving actions.
=== <u>Introduction</u> ===
===Prerequisites===
 
The '''Eco Driving''' scenario is designed to '''detect and analyze aggressive driving behaviors''' such as:
* '''Harsh acceleration'''
* '''Harsh braking'''
* '''Harsh cornering'''
It uses data from '''either an accelerometer or GNSS''' to track driving patterns. When a threshold is exceeded for a specific duration, the system generates an '''eventual record''' to highlight unsafe driving actions.
 
=== <u>Prerequisites</u> ===
 
'''Scenario Activation'''
'''Scenario Activation'''
* Must be enabled via '''Telematics Configuration Tool (TCT)'''.
* The device needs a stable GNSS fix or properly calibrated accelerometer for accurate event detection.
'''Proper Threshold Configuration'''
===Parameter Description===
* Acceleration limits should be set '''according to driving policies'''.
* '''Priority''' - Defines the importance level of generated Eco Driving events.
'''GNSS & Sensor Calibration'''
* '''Acceleration Source''' - Specifies where the acceleration data is taken from:
* The device needs a '''stable GNSS fix''' or '''properly calibrated accelerometer''' for accurate event detection.
** Accelerometer → Uses data from the device’s built-in accelerometer chip.
 
** GNSS → Uses speed and heading data from GNSS to calculate acceleration vectors.
=== <u>Parameter Description</u> ===
* '''Thresholds (Acceleration Limits in m/s²)''' - Maximum allowed acceleration values before triggering an event:
 
** Acceleration Threshold → Forward acceleration limit.
'''Priority'''
** Braking Threshold → Backward acceleration limit.
*Defines the '''importance level''' of generated Eco Driving events.
** Cornering Threshold → Side (left/right) acceleration limit.
'''Acceleration Source'''
===Basic Operation===
*Specifies where the acceleration data is taken from:
An Eco Driving event is triggered when all of the following conditions are met:
** '''Accelerometer''' → Uses data from the device’s built-in accelerometer chip.
# Scenario is enabled
** '''GNSS''' → Uses speed and heading data from '''GNSS''' to calculate acceleration vectors.
# Ignition is ON
'''Thresholds (Acceleration Limits in m/s²)'''
# GNSS fix is present
*Maximum '''allowed acceleration values''' before triggering an event:
# Vehicle speed is above 10 km/h for the event’s duration
** '''Acceleration Threshold''' → Forward acceleration limit.
# Acceleration exceeds the configured threshold and stays above it for at least 0.5 seconds
** '''Braking Threshold''' → Backward acceleration limit.
# Acceleration drops below the threshold and stays there for 0.5 seconds
** '''Cornering Threshold''' → Side (left/right) acceleration limit.
 
=== <u>How It Works</u> ===
 
An '''Eco Driving event''' is triggered when all of the following conditions are met:
# '''Scenario is enabled'''
# '''Ignition is ON'''
# '''GNSS fix is present'''
# '''Vehicle speed is above 10 km/h''' for the event’s duration
# '''Acceleration exceeds the configured threshold''' and stays above it for at least '''0.5 seconds'''
# Acceleration drops below the threshold and stays there for '''0.5 seconds'''
 
Once an event is detected:
Once an event is detected:
* A '''new record is generated''', identifying the type of Eco Driving event.
* A new record is generated, identifying the type of Eco Driving event.
* The following '''IO parameters''' are updated:
* The following IO parameters are updated:
**'''Eco Driving type (AVL ID 253)''' → Identifies event type:
** Eco Driving type (AVL ID 253) → Identifies event type:
*** 1 = Harsh acceleration
*** 1 = Harsh acceleration
*** 2 = Harsh braking
*** 2 = Harsh braking
*** 3 = Harsh cornering
*** 3 = Harsh cornering
** '''Eco Driving value (AVL ID 254)''' → Records the peak acceleration value (measured in hundredths of g).
** Eco Driving value (AVL ID 254) → Records the peak acceleration value (measured in hundredths of g).
 
===Scenario States===
=== <u>Scenario States</u> ===
The system operates as a state machine with 4 states:
 
# Idle → No event detection (vehicle speed too low, no GNSS fix, ignition off, etc.).
The system operates as a '''state machine''' with 4 states:
# Eco → Normal driving, acceleration remains within safe thresholds.
# '''Idle''' → No event detection (vehicle speed too low, no GNSS fix, ignition off, etc.).
# Harsh → Acceleration exceeds the limit, but event isn't registered yet (prevents false positives).
# '''Eco''' → Normal driving, acceleration remains within safe thresholds.
# Cooldown → Acceleration has dropped back but might spike again; prevents rapid, repeated event logging.
# '''Harsh''' → Acceleration exceeds the limit, but event isn't registered yet (prevents false positives).
If the acceleration remains high beyond the cooldown period, the event is officially recorded.
# '''Cooldown''' → Acceleration has dropped back but might spike again; prevents rapid, repeated event logging.
===Notes & Edge Cases===
If the acceleration remains high '''beyond the cooldown period''', the event is officially recorded.
 
=== <u>Additional Notes & Edge Cases</u> ===
 
'''Repeated Accelerations in the Same Direction'''
'''Repeated Accelerations in the Same Direction'''
* If multiple harsh acceleration spikes occur '''within 0.5 seconds''', they are considered part of the '''same event''' rather than separate ones.
* If multiple harsh acceleration spikes occur within 0.5 seconds, they are considered part of the same event rather than separate ones.
'''Speed Drops Below 10 km/h'''
'''Speed Drops Below 10 km/h'''
* If speed drops below the activation speed '''during an ongoing event''', further acceleration values are ignored '''until speed increases again'''.
* If speed drops below the activation speed during an ongoing event, further acceleration values are ignored until speed increases again.
* This might result in:
* This might result in:
** The '''peak acceleration not being recorded''' accurately.
** The peak acceleration not being recorded accurately.
** '''No event being logged at all''', depending on conditions.
** No event being logged at all, depending on conditions.
'''Directional Independence'''
'''Directional Independence'''
* Each movement direction (forward, backward, left, right) is analyzed separately.
* Each movement direction (forward, backward, left, right) is analyzed separately.
* Example:
* Example: a left-turn event does not interfere with acceleration/braking event detection.
** A '''left-turn event''' does not interfere with acceleration/braking event detection.
 
=== <u>Conclusion</u> ===
 
The '''Eco Driving scenario''' helps businesses '''monitor and reduce aggressive driving behaviors'''<br>
 
By logging '''harsh acceleration, braking, and cornering''', fleet managers can:
* '''Improve driver safety'''
* '''Reduce vehicle wear & tear'''
* '''Lower fuel consumption'''
* ️'''Encourage responsible driving habits'''
 


==Identification scenario==
==Identification scenario==
 
===Parameter Description===
=== <u>Parameter Description</u> ===
 
'''Authorized Devices List'''
'''Authorized Devices List'''
* Maintains a list of devices that have been authenticated and are permitted to connect or be recognized without further checks.
* Maintains a list of devices that have been authenticated and are permitted to connect or be recognized without further checks.
* When a new device is approved, it’s added to this list.
* When a new device is approved, it’s added to this list.
 
'''Scenario functionality can be divided into 5 states:'''
<u>Scenario functionality can be divided into 5 states:</u>
 
* '''Idle'''
* '''Idle'''
** Waits for detection or expiration events.
** Waits for detection or expiration events.
** If a '''device detected''' event occurs, transitions to '''Authorization'''.
** If a device detected event occurs, transitions to Authorization.
** If a '''device expired''' event occurs, transitions to '''Device Expired'''.
** If a device expired event occurs, transitions to Device Expired.
 
* '''Authorization'''
* '''Authorization'''
** Triggered when a '''new device''' is detected.
** Triggered when a new device is detected.
** Checks if the device is authorized:
** Checks if the device is authorized:
*** If '''not authorized''', it returns to '''Idle''' (no record generated).
*** If not authorized, it returns to Idle (no record generated).
*** If '''authorized''' and '''first occurrence''', transitions to '''Device Online'''.
*** If authorized and first occurrence, transitions to Device Online.
*** If '''authorized''' and '''subsequent occurrence''', transitions to '''Device Update'''.
*** If authorized and subsequent occurrence, transitions to Device Update.
 
* '''Device Online'''
* '''Device Online'''
** Generates a '''"Device Online”''' record (e.g., AVL) for an authorized device’s '''first''' recognition.
** Generates a "Device Online" record (e.g., AVL) for an authorized device’s first recognition.
** Moves the device to the “already authorized devices” list.
** Moves the device to the “already authorized devices” list.
** Returns to '''Idle'''.
** Returns to Idle.
 
* '''Device Update'''
* '''Device Update'''
** Reached if the device is '''authorized''' and '''not''' in its first occurrence.
** Reached if the device is authorized and not in its first occurrence.
** Updates the device record to reflect the new detection time or any changes in state.
** Updates the device record to reflect the new detection time or any changes in state.
** Returns to '''Idle'''.
** Returns to Idle.
 
* '''Device Expired'''
* '''Device Expired'''
** Triggered if the device’s authorization has ended (e.g., time limit expired or device removed from the system).
** Triggered if the device’s authorization has ended (e.g., time limit expired or device removed from the system).
** If the device is still in the authorization list, generates a “'''Device Expired'''” record and removes the device from the authorized list.
** If the device is still in the authorization list, generates a “Device Expired” record and removes the device from the authorized list.
** Returns to '''Idle'''.
** Returns to Idle.
 
'''Record Generation'''
'''Record Generation'''
* '''Periodic or Eventual''': Records related to device detection can be configured with different priorities—Low (periodic) or High (immediate).
* Periodic or Eventual: Records related to device detection can be configured with different priorities—Low (periodic) or High (immediate).
* '''Record Types:'''
* Record Types
** '''Device Online'''
** Device Online
** '''Device Update'''
** Device Update
** '''Device Expired'''
** Device Expired
 


==Accelerometer calibration scenario==
==Accelerometer calibration scenario==
 
The Accelerometer Calibration Scenario is used to determine the tracker’s position and orientation within a vehicle and reorient the tracker to the vehicle’s coordinate system. This ensures that acceleration measurements align correctly with the vehicle’s axes:
=== <u>Introduction</u> ===
* X-axis → Forward/Backward
 
* Y-axis → Left/Right
The '''Accelerometer Calibration Scenario''' is used to determine the tracker’s position and orientation within a vehicle and reorient the tracker to the vehicle’s coordinate system. This ensures that acceleration measurements align correctly with the vehicle’s axes:
* Z-axis → Up/Down  
* '''X-axis''' → Forward/Backward
* '''Y-axis''' → Left/Right
* '''Z-axis''' → Up/Down  
By calibrating the accelerometer, the system can accurately interpret vehicle movements, reducing errors caused by varying device installation orientations.
By calibrating the accelerometer, the system can accurately interpret vehicle movements, reducing errors caused by varying device installation orientations.
===Accelerometer Calibration Basic Principles===
The scenario relies on GNSS and accelerometer data. Since most devices do not have a gyroscope, these are the primary sources for orientation detection. The algorithm collects two types of accelerometer data:


=== <u>Accelerometer Calibration Working Principle</u> ===
* '''Movement with Acceleration''' - When the vehicle moves straight while accelerating or decelerating, this data helps determine the front and back direction.
* '''Movement Without Acceleration''' - When the vehicle moves without acceleration, it allows the system to determine the ground vector.


The scenario relies on '''GNSS and accelerometer data'''. Since most devices do not have a gyroscope, these are the primary sources for orientation detection. The algorithm collects two types of accelerometer data:
Because devices can be mounted in various ways, they do not inherently know the directions of the vehicle’s front, back, left, right, up, and down.


'''Movement with Acceleration:'''
The GNSS module helps detect whether the vehicle is moving straight or turning. It provides speed and direction relative to the north. If the vehicle moves straight with an increasing or decreasing speed, the system collects acceleration vectors.
* When the vehicle moves '''straight''' while accelerating or decelerating, this data helps determine the '''front and back direction'''.
 
'''Movement Without Acceleration:'''
* When the vehicle moves '''without acceleration''', it allows the system to determine the '''ground vector'''.
 
Because devices can be mounted in various ways, they do not inherently know the directions of the vehicle’s '''front, back, left, right, up, and down.'''
 
The '''GNSS module''' helps detect whether the vehicle is moving straight or turning. It provides '''speed and direction relative to the north'''. If the vehicle moves straight with an '''increasing or decreasing speed''', the system collects acceleration vectors.


Once a sufficient number of data points are collected:
Once a sufficient number of data points are collected:
Line 1,227: Line 631:
* The device’s orientation in the vehicle coordinate system is established.
* The device’s orientation in the vehicle coordinate system is established.


This allows for the calculation of '''quaternions''', which express the device’s rotation within the vehicle. These quaternions are then applied to '''new accelerometer readings''', ensuring they align with the '''vehicle’s coordinate system'''.
This allows for the calculation of quaternions, which express the device’s rotation within the vehicle. These quaternions are then applied to new accelerometer readings, ensuring they align with the vehicle’s coordinate system. As a result, all future accelerometer data correctly reflect the vehicle’s motion.
 
===Prerequisites===
As a result, all '''future accelerometer data''' correctly reflect the vehicle’s motion:
* A valid GNSS fix.
 
* '''X-axis''' → Forward/Backward
* '''Y-axis''' → Left/Right
* '''Z-axis''' → Up/Down
 
=== <u>Prerequisites</u> ===
 
Before running the '''Accelerometer Calibration Scenario''', ensure the following conditions are met:
 
'''Device Compatibility:'''
* The device must have a '''built-in accelerometer''' and '''GNSS module'''.
* The scenario must be '''enabled in the configuration settings'''.
'''Firmware & Configuration:'''
* The device must be running a '''firmware version''' that supports accelerometer calibration.
* The calibration process should be '''properly configured''' in the device settings.
'''GNSS Requirements:'''
* A '''valid GNSS fix''' is required.
* The GNSS must provide '''speed and direction relative to the north'''.
'''Vehicle Movement Conditions:'''
* The vehicle must move '''in a straight line with acceleration''' to determine the '''front and back direction.'''
* The vehicle must also move '''without acceleration''' to establish the '''ground vector.'''
'''Data Collection:'''
* A '''sufficient number of accelerometer samples''' must be collected for accurate calculations.
* The calibration process relies on '''low-angle change movement''' detected via GNSS.
'''Environmental Considerations:'''
* The device should be '''mounted securely''' in the vehicle to avoid incorrect readings.
* The device should be '''mounted securely''' in the vehicle to avoid incorrect readings.
* External interference affecting GNSS or accelerometer accuracy should be minimized.


==Excessive idling==
==Excessive idling==
Line 1,267: Line 644:
| [[File:FTX excessive idling without dout.png|alt=|right|500px]]
| [[File:FTX excessive idling without dout.png|alt=|right|500px]]
}}
}}
=== <u>Introduction</u> ===
Scenario used to detect when a vehicle is stopped for a long time with a running engine, which is bad for fuel consumption and environmental effects.  
Scenario used to detect when a vehicle is stopped for a long time with a running engine, which is bad for fuel consumption and environmental effects.  
<!-- If model supports DOUT1, then show -->  
<!-- If model supports DOUT1, then show -->  
Line 1,275: Line 649:
Additionally, this scenario can notify the driver by activating DOUT that this event was activated.  
Additionally, this scenario can notify the driver by activating DOUT that this event was activated.  
}}
}}
 
===Prerequisites===
=== <u>Prerequisites</u> ===
 
This scenario uses two global configuration parameters to work:
This scenario uses two global configuration parameters to work:
# '''Ignition source''' – That is used to detect if a vehicle is on or on.
# Ignition source – used to detect if a vehicle is on or off.
# '''Movement source''' – That is used to detect if a vehicle is moving or not.
# Movement source – used to detect if a vehicle is moving or not.


Ignition detection is determined by ignition source in system settings.
Ignition detection is determined by ignition source in system settings. Movement detection is determined by Movement source system settings.
Movement detection is determined by Movement source system settings.


For this scenario ignition is used as is, but there are modifications to the movement parameter. Movement will be also detected when there is GNSS fix and ground speed is more than 5 km/h. This option is not configurable and cannot be turned off.
For this scenario ignition is used as is, but there are modifications to the movement parameter. Movement will be also detected when there is GNSS fix and ground speed is more than 5 km/h. This option is not configurable and cannot be turned off.


Scenario can be in 1 of 2 states:
Scenario can be in 1 of 2 states:
* '''Moving - inactive state.''' Vehicle is moving or stopped, but time to stop timeout has not been reached yet. Will also be forced when ignition is OFF;
* Moving - inactive state. Vehicle is moving or stopped, but time to stop timeout has not been reached yet. Will also be forced when ignition is OFF;
* '''Idle - active state.''' Vehicle is stopped or moving, but time to movement timeout has not been reached yet.
* Idle - active state. Vehicle is stopped or moving, but time to movement timeout has not been reached yet.
 
===Parameter description===
=== <u>Parameter description</u> ===
 
'''Priority:'''
'''Priority:'''
*'''Low''' – Event will be sent together with periodic records according to data acquisition settings.
* Low – Event will be sent together with periodic records according to data acquisition settings.
*'''High''' – Event will be sent immediately not considering for data acquisition settings.
* High – Event will be sent immediately not considering for data acquisition settings.
 
'''Time to stopped''' - The time in seconds for how long vehicle should not move with the ignition ON (by "Ignition source") to enter the excessive idling state.
'''Time to ''''''stopped'''''' (s)''' - The time in seconds for how long vehicle should not move with the ignition ON (by "Ignition source") to enter the excessive idling state.
 
'''Time to moving''' – The time in seconds for how long vehicle should move with the ignition ON (by "Ignition source") to exit the excessive idling state.
'''Time to moving''' – The time in seconds for how long vehicle should move with the ignition ON (by "Ignition source") to exit the excessive idling state.


Line 1,310: Line 677:
}}
}}


=Vehicle protection=
=VEHICLE PROTECTION=
{{#switch: {{{model}}}
| FTC965
| FTC887
| FTM887
| FTC134
| FTM134
| FTC164
| FTM164
| FTM924
| FTM927
| FTC308
| FTM308
| FTC305
| FTM305 = 
 
== Immobilizer ==
== Immobilizer ==
[[File:Immobilizer TCT panel.png|right|500px]]
[[File:Immobilizer TCT panel.png|right|500px]]
Line 1,320: Line 702:
The feature operates based on the vehicle's ignition status. When the ignition is turned on, the system enters a "Waiting authorization" state, activating a digital output to keep the starter blocked. Upon successful presentation of an authorized element, the system transitions to an "Authorized" state, deactivates the output, and allows the engine to run. The authorization is automatically revoked after the ignition has been off for a configurable period.
The feature operates based on the vehicle's ignition status. When the ignition is turned on, the system enters a "Waiting authorization" state, activating a digital output to keep the starter blocked. Upon successful presentation of an authorized element, the system transitions to an "Authorized" state, deactivates the output, and allows the engine to run. The authorization is automatically revoked after the ignition has been off for a configurable period.


=== <u>Prerequisites and Important Settings </u> ===
===Prerequisites and Important Settings===
* The vehicle's ignition status must be monitored by one of the device's digital inputs (DIN).
* The vehicle's ignition status must be monitored by one of the device's digital inputs (DIN).
* A relay must be correctly installed to interrupt the vehicle's starter circuit and connected to one of the device's configurable digital outputs (DOUT).
* A relay must be correctly installed to interrupt the vehicle's starter circuit and connected to one of the device's configurable digital outputs (DOUT).
* An iButton reader or a properly configured BLE sensor is required to detect the authorization element.
* An iButton reader is required to detect the authorization element.
* The unique IDs of all authorized iButtons must be pre-configured in the device's authorization list.


=== <u> Basic Operation </u> ===
===Basic Operation===
The feature's logic is managed through three distinct states:
The feature's logic is managed through three distinct states:<br>
1. '''Not Authorized State:'''
1. '''Not Authorized State:'''
* This is the default, idle state when the vehicle's ignition is OFF. The immobilizer is armed and waiting.
* This is the default, idle state when the vehicle's ignition is OFF. The immobilizer is armed and waiting.
Line 1,339: Line 722:
4. '''De-authorization Process:'''
4. '''De-authorization Process:'''
* When the ignition is turned OFF, a de-authorization timer begins.
* When the ignition is turned OFF, a de-authorization timer begins.
* If the ignition remains off for the entire duration of the configured "Ignition OFF timeout," the system revokes the authorization and returns to the Not Authorized state. If the ignition is turned back on before the timeout expires, the authorization remains active.
* If the ignition remains off for the entire duration of the configured "Authorization persist duration", the system revokes the authorization and returns to the Not Authorized state. If the ignition is turned back on before the timeout expires, the authorization remains active.
5. '''Authorization list management:'''
 
'''1-Wire'''
* If no 1-Wire authorization list is used, any ID can be used for authorization.
* If 1-Wire authorization list is used, device will allow authorization only by specifics IDs. Authorization list management can be done in ('''[[#1-Wire_settings|Accessories]]''') section of the TCT, the user can upload, preview and delete a .csv file with up to 10000 device IDs. ID format will be string of 8 bytes in hex format, e.g: AABBCCDDEEFFAABB. It is also possible to manage 1-Wire authorization list via FOTA using task type: Upload 1-Wire authorization list / Receive 1-Wire authorization list.


'''BLE Sensors'''
* If no BLE device authorization list is used, any ID can be used for authorization.
* If the BLE authorization list is used, the device will only allow authorization from specific BLE devices whose MAC addresses are included in the list.
The authorization list can be accessed in the Immobilizer window, where the user can upload, preview, or delete a .csv file containing up to 200 BLE device entries.
* Each BLE device ID must be provided as a Bluetooth MAC address in the following hexadecimal format:AA:BB:CC:DD:EE:FF
* Any BLE device can be used for authorization — not only Teltonika EYE sensors.
Authorization is performed exclusively by checking the Bluetooth MAC address.


=== <u> Parameters list </u>===  
'''NOTE:'''<br>
It is also possible to manage the Beacon authorization list remotely via FOTA using the following task types:Upload Beacon authorization list and Receive Beacon authorization list.
 
'''NOTE:'''<br>
Example files are provided to illustrate the correct structure for uploading authorization lists. The included [[Media:Ibutton list.zip|ibutton_list.csv]] and [[Media:Bluetooth mac list.zip|bluetooth_mac_list.csv]] files demonstrate the required formatting for 1 Wire and Beacon (BLE) entries.
 
 
===Parameters===  
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<tr>
Line 1,351: Line 753:
</tr>
</tr>
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Immobilizer </td>
<td style="vertical-align: middle; text-align: center;"> Immobilizer </td>
<td style="vertical-align: middle; text-align: center;"> 11700 </td>
<td style="vertical-align: middle; text-align: center;"> 1024800 <br> (248}  </td>
<td style="vertical-align: middle; text-align: center;"> Disables, or enables and sets priority of the event record generated upon successful or failed authorization attempts.Authorization source </td>
<td style="vertical-align: middle; text-align: center;"> Disables, or enables and sets priority of the event record generated upon successful or failed authorization attempts.Authorization source </td>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' Disable scenario. <br>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' Disable scenario. <br>
'''1 =''' Low priority Device makes an additional record with indication of event cause. </td>
'''1 =''' Low priority Device makes an additional record with indication of event cause. <br>
'''2 =''' High priority - module makes additional record with high priority flag and sends event packet immediately to the server by GPRS.
</td>
</tr>  
</tr>  
<tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Authorization mode</td>
<td style="vertical-align: middle; text-align: center;"> Authorization source </td>
<td style="vertical-align: middle; text-align: center;"> 11703 </td>
<td style="vertical-align: middle; text-align: center;"> 11703 </td>
<td style="vertical-align: middle; text-align: center;"> Selects the type of authorization element to be used. </td>
<td style="vertical-align: middle; text-align: center;"> Selects singular or multiple types of authorization elements to be used. </td>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' No authorization selected. <br>  
<td style="vertical-align: middle; text-align: left;"> '''0 =''' No authorization selected. <br>  
'''1 =''' 1-Wire authorization selected.
'''1 =''' 1-Wire authorization selected. Driver is authorized via iButton or RFID tag.<br>
  </td>
  </td>
</tr>  
</tr>  
<tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Authorization persist duration (s)</td>
<td style="vertical-align: middle; text-align: center;"> Ignition OFF timeout (s) </td>
<td style="vertical-align: middle; text-align: center;"> 60068 </td>
<td style="vertical-align: middle; text-align: center;"> 60068 </td>
<td style="vertical-align: middle; text-align: center;"> Sets the time in seconds after the ignition is turned off before the driver's authorization is automatically revoked. </td>
<td style="vertical-align: middle; text-align: center;"> Sets the time in seconds after the ignition is turned off before the driver's authorization is automatically revoked. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 1''' <br>
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 1''' <br>
Maximum value '''= 65535''' </td>
Maximum value '''= 65535''' </td>
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Eventual records </td>
<td style="vertical-align: middle; text-align: center;"> 11701</td>
<td style="vertical-align: middle; text-align: center;"> Enables feature status sending only when the event happens (an eventual record). When disabled, feature status will be sent with both eventual and periodical records. </td>
<td style="vertical-align: middle; text-align: left;"> '''0''' = Disable <br>
'''1''' = Enable </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Bypass authorization </td>
<td style="vertical-align: middle; text-align: center;"> Bypass authorization </td>
<td style="vertical-align: middle; text-align: center;"> 11029</td>
<td style="vertical-align: middle; text-align: center;"> 11029</td>
<td style="vertical-align: middle; text-align: center;"> Allows to bypass authorization when ignition is turned on and a duration expires. </td>
<td style="vertical-align: middle; text-align: center;"> Allows to bypass authorization when ignition is turned on and a set duration expires. </td>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' Disabled
<td style="vertical-align: middle; text-align: left;"> '''0 =''' Disabled <br>
'''0-65535 =''' Enabled </td>
'''0-65535 =''' Enabled <br>
 
Default value = '''0'''  </td>
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Bypass authorization timeout (s) </td>
<td style="vertical-align: middle; text-align: center;"> Bypass authorization timeout (s) </td>
<td style="vertical-align: middle; text-align: center;"> 11029</td>
<td style="vertical-align: middle; text-align: center;"> 11029</td>
Line 1,402: Line 790:
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 1''' <br>
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 1''' <br>
Maximum value '''= 65535''' </td>
Maximum value '''= 65535''' </td>
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Output control </td>
<td style="vertical-align: middle; text-align: center;"> Output control </td>
<td style="vertical-align: middle; text-align: center;"> 65535</td>
<td style="vertical-align: middle; text-align: center;"> 11702</td>
<td style="vertical-align: middle; text-align: center;"> Selects which Digital Output is used to control the immobilizer relay. </td>
<td style="vertical-align: middle; text-align: center;"> Selects which Digital Output is used to control the immobilizer relay. </td>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' None DOUTs are disabled in this scenario. <br>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' None DOUTs are disabled in this scenario. <br>
Line 1,413: Line 799:
'''2 =''' DOUT2 DOUT2 is enabled in this scenario. <br>
'''2 =''' DOUT2 DOUT2 is enabled in this scenario. <br>
'''3 =''' DOUT3 DOUT3 is enabled in this scenario. </td>
'''3 =''' DOUT3 DOUT3 is enabled in this scenario. </td>
</tr>  
</tr>  
</table>
</table>
 
=== Limitations, Edge Cases & Additional Notes===
=== <u> Limitations, Edge Cases & Additional Notes </u> ===
* '''Installation Security:''' The overall effectiveness of the immobilizer is highly dependent on the secure and discreet installation of the control relay. If the wiring is easily accessible, it can be bypassed.
* '''Installation Security:''' The overall effectiveness of the immobilizer is highly dependent on the secure and discreet installation of the control relay. If the wiring is easily accessible, it can be bypassed.
}}


 
==Network Jamming==
== Network Jamming ==
[[File:Network Jamming Extension with DOUT Control TCT panel.png|right|500px]]
[[File:Network Jamming Extension with DOUT Control TCT panel.png|right|500px]]
The Jamming Detection scenario identifies instances of active GSM signal jamming on the device. The modem performs continuous jamming detection and reports any suspicious activity back to the main device.
The Jamming Detection scenario identifies instances of active GSM signal jamming on the device. The modem performs continuous jamming detection and reports any suspicious activity back to the main device.


Line 1,430: Line 813:
When GSM signal jamming is detected, Network Jamming scenario activates. Then it starts  a configurable jamming detection delay before generating jamming event. It is intended to reduce false positives. After the timeout ends, the device generates an event record. SMS notification Additionally, if digital output is configured, it activates already installed measures to inform driver or disrupt thieves  ( like buzzer, LED indication, locking all doors etc. ).   
When GSM signal jamming is detected, Network Jamming scenario activates. Then it starts  a configurable jamming detection delay before generating jamming event. It is intended to reduce false positives. After the timeout ends, the device generates an event record. SMS notification Additionally, if digital output is configured, it activates already installed measures to inform driver or disrupt thieves  ( like buzzer, LED indication, locking all doors etc. ).   


=== <u>Prerequisites and Important Settings </u> ===
===Prerequisites and Important Settings===
* The modem has jamming detection enabled at all times.
* Network Jamming won’t work with Deep Sleep and Power off sleep modes turned ON. Make sure to check information in Power saving settings.   
* Network Jamming won’t work with Deep Sleep and Power off sleep modes turned ON. Make sure to check information in Power saving settings.   


=== <u> Basic operation </u> ===
===Basic Operation===
* The modem continuously always monitors the network, scanning for potential jamming events.
* The modem continuously always monitors the network, scanning for potential jamming events.
* Network Jamming detection scenario activates when GSM signal jamming is detected.  
* Network Jamming detection scenario activates when GSM signal jamming is detected.  
Line 1,442: Line 824:
* Eventual records function lets user choose between sending eventual records of Jamming when enabled. And if disabled – eventual and periodic records are being sent bout Jamming.
* Eventual records function lets user choose between sending eventual records of Jamming when enabled. And if disabled – eventual and periodic records are being sent bout Jamming.
* After jamming event has ended, modem continues monitoring for further jamming events.  
* After jamming event has ended, modem continues monitoring for further jamming events.  
 
===Parameters</u>===  
=== <u> Parameters list </u>===  
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<tr>
Line 1,452: Line 833:
</tr>
</tr>
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Network jamming detection </td>
<td style="vertical-align: middle; text-align: center;"> Network jamming detection </td>
<td style="vertical-align: middle; text-align: center;"> 1024900 <br> (249)</td>
<td style="vertical-align: middle; text-align: center;"> 1024900 <br> (249)</td>
Line 1,461: Line 841:
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Time until jamming reporting (s) </td>
<td style="vertical-align: middle; text-align: center;"> Time until jamming reporting (s) </td>
<td style="vertical-align: middle; text-align: center;"> 11305</td>
<td style="vertical-align: middle; text-align: center;"> 11305</td>
Line 1,467: Line 846:
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br>
Maximum value = '''65535''' <br>Default value = '''60''' </td>
Maximum value = '''65535''' <br>Default value = '''60''' </td>
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Eventual records </td>
<td style="vertical-align: middle; text-align: center;"> Eventual records </td>
<td style="vertical-align: middle; text-align: center;"> 1024904</td>
<td style="vertical-align: middle; text-align: center;"> 1024904</td>
Line 1,476: Line 853:
<td style="vertical-align: middle; text-align: left;"> '''0''' = Disable <br>
<td style="vertical-align: middle; text-align: left;"> '''0''' = Disable <br>
'''1''' = Enable  </td>
'''1''' = Enable  </td>
 
</tr>
</tr>  
{{#if: {{FTX_Pin_Support List|model={{{model}}}|pin=DOUT1}} |
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Output control (ms) </td>
<td style="vertical-align: middle; text-align: center;"> Output control (ms) </td>
<td style="vertical-align: middle; text-align: center;"> 11304</td>
<td style="vertical-align: middle; text-align: center;"> 11304</td>
Line 1,488: Line 864:
'''0''' '''= None''' DOUTs are disabled in this scenario. <br>
'''0''' '''= None''' DOUTs are disabled in this scenario. <br>
'''1 = DOUT1''' DOUT1 is enabled in this scenario. </td>
'''1 = DOUT1''' DOUT1 is enabled in this scenario. </td>
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> DOUT OFF duration (ms) </td>
<td style="vertical-align: middle; text-align: center;"> DOUT OFF duration (ms) </td>
<td style="vertical-align: middle; text-align: center;"> 11302</td>
<td style="vertical-align: middle; text-align: center;"> 11302</td>
Line 1,497: Line 871:
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br>
Maximum value = '''5000''' <br>Default value = '''200''' </td>
Maximum value = '''5000''' <br>Default value = '''200''' </td>
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> DOUT ON duration (ms) </td>
<td style="vertical-align: middle; text-align: center;"> DOUT ON duration (ms) </td>
<td style="vertical-align: middle; text-align: center;"> 11301</td>
<td style="vertical-align: middle; text-align: center;"> 11301</td>
Line 1,506: Line 878:
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0''' (supports zero value)<br>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0''' (supports zero value)<br>
Maximum value = '''5000''' <br>Default value = '''200''' </td>
Maximum value = '''5000''' <br>Default value = '''200''' </td>
</tr>  
</tr>  
 
}}
</table>
</table>


==Unplug detection==
==Unplug detection==
[[File:FTX unplug detection.png|right|500 px]]
[[File:FTX unplug detection.png|right|500 px]]
Unplug Detection is a feature that identifies when a device transitions between being powered by external voltage and running on internal power only. The device generates a record (AVL ID 252) with a configured priority whenever it is plugged in or unplugged.


=== <u>Introduction</u> ===
===Prerequisites & Important Settings===
 
* '''External Power Source''' - The vehicle or external system must provide a stable voltage supply that can be monitored by the device.
'''Unplug Detection''' is a feature that identifies when a device transitions between being powered by external voltage and running on internal power only. The device generates a record (AVL ID '''252''') with a configured priority whenever it is plugged in or unplugged.
 
=== <u>Prerequisites</u> ===
 
'''External Power Source'''
* The vehicle or external system must provide a stable voltage supply that can be monitored by the device.
'''Configuration Access'''
* You need the ability to configure unplug detection parameters to choose between '''Simple''' and '''Advanced''' modes and to set the event priority.
'''Accelerometer (for Advanced Mode)'''
* If '''Advanced''' unplug detection is used, an onboard accelerometer must be present and enabled to combine voltage changes with motion data.
 
=== <u>Parameter Description</u> ===


===Parameter Description===
'''Unplug Detection Mode'''
'''Unplug Detection Mode'''
* '''Simple'''
* Simple - monitors external voltage to determine when the device is plugged or unplugged.
** Monitors '''external voltage''' to determine when the device is plugged or unplugged.
** Recommended for vehicles where power voltage does not depend on ignition status.
** Recommended for vehicles where power voltage does not depend on ignition status.
* '''Advanced'''
* Advanced - monitors both external voltage and accelerometer data.
** Monitors both '''external voltage''' and '''accelerometer''' data.
** Suitable for vehicles where power voltage is disconnected when ignition is off; the accelerometer helps confirm unplug events more reliably.
** Suitable for vehicles where power voltage is disconnected when ignition is off; the accelerometer helps confirm unplug events more reliably.
'''AVL ID 252'''
'''AVL ID 252'''
* The record ID generated when the device is plugged or unplugged.
* The record ID generated when the device is plugged or unplugged.
* The user can configure '''priority''' (Low, High, etc.) to decide how the record is reported and logged.
* The user can configure '''priority''' (Low, High, etc.) to decide how the record is reported and logged.


=== <u>How It Works</u> ===
===Basic Operation===
 
'''Simple Mode'''
'''Simple Mode'''
* The device regularly checks the external power line.
* The device regularly checks the external power line.
* When external voltage is lost (drops below a configured threshold), the device deems itself '''unplugged''' and generates a '''“Power Unplugged”''' record.
* When external voltage is lost (drops below a configured threshold), the device deems itself unplugged and generates a "Power Unplugged" record.
* When external voltage returns (exceeds the threshold), the device deems itself '''plugged''' and generates a '''“Power Plugged”''' record.
* When external voltage returns (exceeds the threshold), the device deems itself plugged and generates a "Power Plugged" record.
'''Advanced Mode'''
'''Advanced Mode'''
* The device monitors both external voltage and the '''accelerometer'''.
* The device monitors both external voltage and the accelerometer.
* If external power is lost but the accelerometer indicates movement or vibration (e.g., ignition turned off in some vehicles), the device can confirm that an '''unplug''' event truly occurred.
* If external power is lost but the accelerometer indicates movement or vibration (e.g., ignition turned off in some vehicles), the device can confirm that an unplug event truly occurred.
* When power is restored along with the lack of movement, or once the system stabilizes, a '''plugged''' event is generated.
* When power is restored along with the lack of movement, or once the system stabilizes, a plugged event is generated.
'''Record Generation & Logging'''
'''Record Generation & Logging'''
* Whenever a change in power source state is detected (plugged or unplugged), an '''AVL ID 252''' record is created with the configured priority.
* Whenever a change in power source state is detected (plugged or unplugged), an AVL ID 252 record is created with the configured priority.
* Depending on the priority level, the device may send the record immediately (High priority) or with the next scheduled data batch (Low priority).
* Depending on the priority level, the device may send the record immediately (High priority) or with the next scheduled data batch (Low priority).


== Auto Geofence ==
Geofencing is a location-based technology that creates a software-defined boundary (geofence) around a geographic area (geozone).


==Auto geofence==
Two geofencing features are available with Teltonika Telematics devices:
== Auto Geofence ==
* '''Auto Geofence (described in this section)''' – allows automatically creating a circular geozone around the device’s last known location after it has been stationary for a specified period, then capture related events.
* Manual Geofence – see [[#Manual Geofence|here]].
[[File:Auto Geofence TCT panel with DIN.png|right|500px]]
[[File:Auto Geofence TCT panel with DIN.png|right|500px]]


Line 1,566: Line 927:
The feature operates in two main states. In its "Wait State," it monitors for the vehicle to become stationary with a valid GNSS fix. Once this condition is met for a configured timeout, it creates the geofence and enters the "Active State." In the Active State, it monitors for breaches. The feature can be deactivated and returned to the Wait State by various configurable triggers, such as a change in voltage, a digital input, or the presentation of an authorized iButton.
The feature operates in two main states. In its "Wait State," it monitors for the vehicle to become stationary with a valid GNSS fix. Once this condition is met for a configured timeout, it creates the geofence and enters the "Active State." In the Active State, it monitors for breaches. The feature can be deactivated and returned to the Wait State by various configurable triggers, such as a change in voltage, a digital input, or the presentation of an authorized iButton.


=== <u>Prerequisites and Important Settings </u> ===
===Prerequisites and Important Settings===
* The device must have a reliable GNSS signal and be able to detect its movement status for the feature to arm correctly.
* The device must have a reliable GNSS signal and be able to detect its movement status for the feature to arm correctly.
* If using a deactivation source such as a Digital Input (DIN) or iButton, the corresponding hardware (e.g., ignition connection, iButton reader) must be properly installed and configured.
* If using a deactivation source such as a Digital Input (DIN) or iButton, the corresponding hardware (e.g., ignition connection, iButton reader) must be properly installed and configured.


=== <u> Basic Operation </u> ===
===Basic Operation===
The feature's logic is divided into two distinct operational states: Wait State and Active State.
The feature's logic is divided into two distinct operational states: Wait State and Active State.
* '''Entering the Wait State (Arming Process)''':
* '''Entering the Wait State (Arming Process)''':
Line 1,584: Line 945:
* '''Deactivation:'''
* '''Deactivation:'''
** The armed geofence can be deactivated, returning the system to the Wait State without generating an alarm. This is achieved when a configured "Deactivate by" source is triggered (e.g., Digital Input 1 becomes active).
** The armed geofence can be deactivated, returning the system to the Wait State without generating an alarm. This is achieved when a configured "Deactivate by" source is triggered (e.g., Digital Input 1 becomes active).
 
===Parameter list===  
 
=== <u> Parameters list </u>===  
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<tr>
Line 1,595: Line 954:
</tr>
</tr>
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Auto geofence </td>
<td style="vertical-align: middle; text-align: center;"> Auto geofence </td>
<td style="vertical-align: middle; text-align: center;"> 1017500 </td>
<td style="vertical-align: middle; text-align: center;"> 1017500 </td>
Line 1,602: Line 960:
'''1 = Low priority''' Device makes an additional record with indication of event cause.
'''1 = Low priority''' Device makes an additional record with indication of event cause.
'''2 = High priority''' Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS. </td>
'''2 = High priority''' Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS. </td>
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Generate event </td>
<td style="vertical-align: middle; text-align: center;"> Generate event </td>
<td style="vertical-align: middle; text-align: center;"> 20001 </td>
<td style="vertical-align: middle; text-align: center;"> 20001 </td>
Line 1,611: Line 967:
<td style="vertical-align: middle; text-align: left;"> '''0 =''' On exit <br>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' On exit <br>
'''1 =''' On enter <br>
'''1 =''' On enter <br>
'''2 =''' On both <br>
'''2 =''' On both</td>
</td>
 
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Activation timeout (s) </td>
<td style="vertical-align: middle; text-align: center;"> Activation timeout (s) </td>
<td style="vertical-align: middle; text-align: center;"> 20002 </td>
<td style="vertical-align: middle; text-align: center;"> 20002 </td>
Line 1,625: Line 978:
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 0''' <br>
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 0''' <br>
Maximum value '''= 65535''' </td>
Maximum value '''= 65535''' </td>
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Radius (m) </td>
<td style="vertical-align: middle; text-align: center;"> Radius (m) </td>
<td style="vertical-align: middle; text-align: center;"> 20003 </td>
<td style="vertical-align: middle; text-align: center;"> 20003 </td>
Line 1,634: Line 985:
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 0''' <br>
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 0''' <br>
Maximum value '''= 1000000''' </td>
Maximum value '''= 1000000''' </td>
</tr>  
</tr>  
{{#if: {{FTX_Pin_Support List|model={{{model}}}|pin=DIN1}} | 
<tr>
<tr>


Line 1,649: Line 1,000:


</tr>  
</tr>  
}}
</table>
</table>
 
===Limitations, Edge Cases & Additional Notes===
=== <u> Limitations, Edge Cases & Additional Notes </u> ===
* '''Stuck in Wait State:''' The feature will never arm if the conditions are not met. This can happen if the vehicle is constantly moving or if it is parked in a location with no GNSS signal (e.g., an underground garage).
* '''Stuck in Wait State:''' The feature will never arm if the conditions are not met. This can happen if the vehicle is constantly moving or if it is parked in a location with no GNSS signal (e.g., an underground garage).
* '''Movement without GNSS:''' A key capability of this feature is generating an "On Exit" alarm if the vehicle moves for a sustained period without a GNSS fix. This is a critical security measure against signal jamming or loss.
* '''Movement without GNSS:''' A key capability of this feature is generating an "On Exit" alarm if the vehicle moves for a sustained period without a GNSS fix. This is a critical security measure against signal jamming or loss.
* '''Deactivation Source:''' The chosen deactivation source is the only way to disarm the feature without triggering an alarm (aside from staying within the geofence). Ensure the source aligns with the intended use case (e.g., using a Digital Input connected to the ignition).
* '''Deactivation Source:''' The chosen deactivation source is the only way to disarm the feature without triggering an alarm (aside from staying within the geofence). Ensure the source aligns with the intended use case (e.g., using a Digital Input connected to the ignition).


== Manual Geofence ==
==Manual Geofence==
Geofencing is a location-based technology that creates a software-defined boundary (geofence) around a geographic area (geozone).
 
Two geofencing features are available with Teltonika Telematics devices:
* Auto Geofence – see [[#Auto Geofence|here]].
* '''Manual Geofence (described in this section)''' – allows the user to manually create geozones of various shapes, then capture events related these geozones, with multiple options.
 
[[File:Manual Geofence - menu.png|right|500px]]
[[File:Manual Geofence - menu.png|right|500px]]
<!---
Unneeded images, may delete later, or keep if needed
[[File:Manual Geofence - zone circle.png|right|150px]]
[[File:Manual Geofence - zone circle.png|right|150px]]
[[File:Manual Geofence - zone square.png|right|150px]]
[[File:Manual Geofence - zone square.png|right|150px]]
--->
Manual Geofence is a feature that allows the device to monitor predefined geographic zones and generate events when the device enters, exits, or exceeds a configured speed limit within those zones. A geozone is defined on a map using geometric shapes (circle, rectangle, polygon).


Manual geofence is a feature that monitors the location of the vehicle and triggers an event when the vehicle enters or exits any geofence zone, manually created on a map in the TCT.
Manual Geofence is used in fleet management, vehicle protection, and operational monitoring scenarios where location-based events are required. Typical use cases include detecting entry into restricted areas, monitoring vehicle departures from operational zones, enforcing speed limits in defined locations, or triggering device actions such as digital output control.


Manual geofences are useful to get notified when the tracker enters or leaves a certain area, or exceeds a speed limit in such an area. This can help ensure driver compliance with predefined routes and speed limits.
The device continuously compares its GNSS position with configured geozone boundaries. Each scenario independently tracks whether the device is inside or outside the zone and whether the configured speed limit threshold is exceeded. When these states change, the device generates an event record containing geofence-related identifiers and event information, and can control digital outputs.


When the vehicle crosses a geofence boundary (enters, exits, or in both cases), or exceeds the pre-defined speed limit, the device generates a record. There can be up to 50 geofence zones. Geofences can be circles or squares, defined by coordinates and border widths.
In TCT, the user can create geozones by drawing them on the map. Three shapes are available:
* Circle - defined by Radius and one pair of latitude/longitude (center coordinates of the circle).
* Rectangle - defined by two pairs of latitude/longitude (most northwestern and southeastern corners of the rectangle).
* Polygon - defined by 3-10 pairs of latitude/longitude (vertices of the polygon).
Each manual geozone has various associated options. They are discussed below.


=== <u>Prerequisites and Important Settings </u> ===
===Manual geofence global settings===
* In Manual Geofence square and circle shapes can be used for creating a geofence and have their own different parameters.
In the upper right corner of the main Manual geofence window, the „Geofence settings“ button allows configuring global settings for digital output (DOUT) and timezone control accross all manual geozones.
[[File:Manual geofence global settings.png|right|300px]]
For each separate DOUT, the user can set up Output control settings for individual geofences. The number of DOUTs depends on device hardware.


=== <u> Basic Operation </u> ===
Disabling a DOUT here will disable output control configuration in all zones which use that particular DOUT.
Each configured Manual Geofence scenario runs every second and checks if its conditions are met. The geozone tracks two main states:
 
* In-Zone: Indicates whether the device is inside the geozone.
Settings here (see table below) will affect what can be configured in the „Output control“ section of a particular geozone.
* Speeding: Indicates whether the device is exceeding the speed limit while inside the geozone.
 
When a state change occurs (entering/exiting the geozone or starting/stopping speeding), an event is recorded. The frame border prevents false exit detections.
====Parameters in global settings====
AVL IDs:
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:15%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:15%; vertical-align: middle; text-align: center;">PARAMETER ID</th>
<th style="width:50%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<th style="width:20%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Control mode</td>
<td style="vertical-align: middle; text-align: center;">DOUT1= 899900<br>DOUT2=899910<br>DOUT3=899920</td>
<td style="vertical-align: middle; text-align: left;">Select Control mode for digital output.<br><br>In Persistent mode, DOUT is controlled according to global DOUT parameters while the device is Inside/Outside of all geozones.<br><br>In Event mode, DOUT is controlled according to individual scenario parameters when a configured event occurs (Inside/Outside/Both) in the specific geozone.</td>
<td style="vertical-align: middle; text-align: left;">0=None (DOUT control disabled)<br>1=Persistent<br>2=Event</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Activation timing</td>
<td style="vertical-align: middle; text-align: center;">DOUT1= 899901<br>DOUT2=899911<br>DOUT3=899921</td>
<td style="vertical-align: middle; text-align: left;">Select Activation timing when the event will be triggered.<br><br>Control mode - Persistent:<br>
* Outside activation timing, selected DOUT will start being controlled while the device is outside of the geozone and will stop being controlled while the device is inside of the geozone. If the device is outside of multiple geozones, selected DOUT will continue being controlled until the device enters one of the geozones.
* Inside activation timing, selected DOUT will start being controlled while the device is inside the geozone and will stop being controlled while the device is outside of the geozone. If Output control according to speed limit is set, selected DOUT will start being controlled while the device is exceeding the speed limit inside the geozone. If the device is inside multiple geozones, selected DOUT will continue being controlled until the device is outside of all geozones (or stops exceeding the speed limit, if configured).
Control mode - Event:<br>
* Outside activation timing, selected DOUT will be triggered once you exit the configured geozone.
* Inside activation timing, selected DOUT will be triggered once you enter the configured geozone.</td>
<td style="vertical-align: middle; text-align: left;">1=Outside<br>2=Inside</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">DOUT activation</td>
<td style="vertical-align: middle; text-align: center;">DOUT1= 899904<br>DOUT2=899914<br>DOUT3=899924</td>
<td style="vertical-align: middle; text-align: left;">Select DOUT activation for how long digital output will be active.<br><br>With Timed DOUT activation, DOUT is controlled according to global DOUT ON/OFF duration parameters while all conditions are being met. When control mode is Event, only Timed DOUT activation can be configured.<br><br>With Permanent activation, DOUT is simply set to ON state while all conditions are being met. When control mode is Persistent, both Timed and Permanent can be configured globally.</td>
<td style="vertical-align: middle; text-align: left;">0=Timed<br>1=Permanent</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Output ON duration (ms)</td>
<td style="vertical-align: middle; text-align: center;">DOUT1= 899902<br>DOUT2=899912<br>DOUT3=899922</td>
<td style="vertical-align: middle; text-align: left;">Value in milliseconds, for how long DOUT should be active.</td>
<td style="vertical-align: middle; text-align: left;">Min = 100<br>Max = 5000<br>Default = "200"</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Output OFF duration (ms)</td>
<td style="vertical-align: middle; text-align: center;">DOUT1= 899930<br>DOUT2=899913<br>DOUT3=899923</td>
<td style="vertical-align: middle; text-align: left;">A value in milliseconds, for how long DOUT should be inactive.</td>
<td style="vertical-align: middle; text-align: left;">Min = 1<br>Max = 5000<br>Default = "200"</td>
</tr>
</table>
 
===Basic Operation===
Because multiple Manual Geofence scenarios can be configured, all scenarios are stored in a list and run every second.
 
The device constantly tracks the current state related to the geozone:
* In zone – whether the device is currently inside the geozone (changes as the device enters/exits the geozone).
* Speeding – whether the device is currently exceeding the speed limit configured for the geozone (changes as device starts/stops speeding inside the geozone (on geozone exit, speeding state is set to ‘stop’)).
When any of these states change, and if the device is configured to capture them, appropriate events are recorded.
 
Manual geofence records consist of the following AVL IDs:
* 155 - used to identify the specific manual geofence scenario, which generated the event:
* 155 - used to identify the specific manual geofence scenario, which generated the event:
* 156 - In-zone event. Is added to the record if an in-zone event was captured. Possible values:
** Value = (<scenario_id> - 1); eg. scenario 10 generates AVL ID 155 with value 9;
* 156 - In-zone event. Is added to the record if an in-zone event was captured;
** 0 - Exit event;
** 0 - Exit event;
** 1 - Enter event.
** 1 - Enter event.
* 157 - Speeding event. Is added to the record if a speeding event was captured. Possible values:
* 157 - Speeding event. Is added to the record if a speeding event was captured.
** 0 - Speeding stop event;
** 0 - Speeding stop event;
** 1 - Speeding start event.
** 1 - Speeding start event.
===Parameters===
NOTE! Parameters are given for Geozone 1. See [[#Geozone Parameter ID Calculation]] for more information.
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:15%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:15%; vertical-align: middle; text-align: center;">PARAMETER ID</th>
<th style="width:50%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<th style="width:20%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr><td colspan="4">'''Geozone settings'''</td></tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Priority</td>
<td style="vertical-align: middle; text-align: center;">900000</td>
<td style="vertical-align: middle; text-align: left;">Priority of how events are being sent to a server. Events with low priority are added to the periodical record, and events with high priority are sent immediately after they occur.<br>Value „0“ disables the geozone.</td>
<td style="vertical-align: middle; text-align: left;">0=Disable<br>1=Low priority<br>2=High priority</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Event type</td>
<td style="vertical-align: middle; text-align: center;">900002</td>
<td style="vertical-align: middle; text-align: left;">Defines which geozone events should be captured.</td>
<td style="vertical-align: middle; text-align: left;">0=No event<br>1=On Exit<br>2=On Entrance<br>3=On Both</td>
</tr>
<tr><td colspan="4">'''Output control'''</td></tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Output source</td>
<td style="vertical-align: middle; text-align: center;">900008</td>
<td style="vertical-align: middle; text-align: left;">Select the digital output that will be controlled by this geozone.</td>
<td style="vertical-align: middle; text-align: left;">List of available DOUTs (e.g. DOUT1, etc.)</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Control mode</td>
<td style="vertical-align: middle; text-align: center;">899900</td>
<td style="vertical-align: middle; text-align: left;">Select Control mode for digital output.<br><br>In Persistent mode, DOUT is controlled according to global DOUT parameters while the device is Inside/Outside of all geozones.<br><br>In Event mode, DOUT is controlled according to individual scenario parameters when a configured event occurs (Inside/Outside/Both) in the specific geozone.</td>
<td style="vertical-align: middle; text-align: left;">0=None<br>1=Persistent<br>2=Event</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">DOUT activation</td>
<td style="vertical-align: middle; text-align: center;">899904</td>
<td style="vertical-align: middle; text-align: left;">Select DOUT activation for how long digital output will be active.<br><br>With Timed DOUT activation, DOUT is controlled according to global DOUT ON/OFF duration parameters while all conditions are being met. When control mode is Event, only Timed DOUT activation can be configured.<br><br>With Permanent activation, DOUT is simply set to ON state while all conditions are being met. When control mode is Persistent, both Timed and Permanent can be configured globally.</td>
<td style="vertical-align: middle; text-align: left;">0=Timed<br>1=Permanent</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Activation timing</td>
<td style="vertical-align: middle; text-align: center;">900009</td>
<td style="vertical-align: middle; text-align: left;">Select Activation timing when the event will be triggered.<br><br>
Control mode - Persistent:
* Outside activation timing, selected DOUT will start being controlled while the device is outside of the geozone and will stop being controlled while the device is inside of the geozone. If the device is outside of multiple geozones, selected DOUT will continue being controlled until the device enters one of the geozones.
* Inside activation timing, selected DOUT will start being controlled while the device is inside the geozone and will stop being controlled while the device is outside of the geozone. If Output control according to speed limit is set, selected DOUT will start being controlled while the device is exceeding the speed limit inside the geozone. If the device is inside multiple geozones, selected DOUT will continue being controlled until the device is outside of all geozones (or stops exceeding the speed limit, if configured).
<br>
Control mode - Event:
* Outside activation timing, selected DOUT will be triggered once you exit the configured geozone.
* Inside activation timing, selected DOUT will be triggered once you enter the configured geozone.
* With Outside and Inside activation timing, both described logics will be applied.</td>
<td style="vertical-align: middle; text-align: left;">1=Outside<br>2=Inside<br>3=Outside and inside</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Output ON duration (ms)</td>
<td style="vertical-align: middle; text-align: center;">900010</td>
<td style="vertical-align: middle; text-align: left;">A value in milliseconds, for how long DOUT should be active.</td>
<td style="vertical-align: middle; text-align: left;">Min = 100<br>Max = 5000<br>Default = "200"</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Output OFF duration (ms)</td>
<td style="vertical-align: middle; text-align: center;">900011</td>
<td style="vertical-align: middle; text-align: left;">A value in milliseconds, for how long DOUT should be inactive.</td>
<td style="vertical-align: middle; text-align: left;">Min = 1<br>Max = 5000<br>Default = "200"</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Output repeat count</td>
<td style="vertical-align: middle; text-align: center;">900012</td>
<td style="vertical-align: middle; text-align: left;">A value for how many times DOUT activation should be repeated.</td>
<td style="vertical-align: middle; text-align: left;">Min = 1<br>Max = 500<br>Default = "1"</td>
</tr>
<tr><td colspan="4">'''Output control according to speed limit'''</td></tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Output control according to speed limit</td>
<td style="vertical-align: middle; text-align: center;">900006</td>
<td style="vertical-align: middle; text-align: left;">Toggles setting up speed limit threshold that will have an effect on selected output activation and deactivation.</td>
<td style="vertical-align: middle; text-align: left;">0=Disable<br>1=Enable</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Speed limit</td>
<td style="vertical-align: middle; text-align: center;">900007</td>
<td style="vertical-align: middle; text-align: left;">Speed threshold which determines when to generate speeding start/stop events.</td>
<td style="vertical-align: middle; text-align: left;">Min = 0<br>Max = 1000<br>Default = "0"</td>
</tr>
</table>
====Parameters for coordinates====
Parameter sets for coordinates depend on the shape of geozone:
*All shapes have „Frame Border“.
*Circle - defined by Radius and one pair of latitude/longitude (center coordinates of the circle).
*Rectangle - defined by two pairs of latitude/longitude (most northwestern and southeastern corners of the rectangle).
*Polygon - defined by 3-10 pairs of latitude/longitude (vertices of the polygon).
For polygon, click „See all points“ at the bottom of the list to view or edit all entered coordinates.
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:15%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:15%; vertical-align: middle; text-align: center;">PARAMETER ID</th>
<th style="width:50%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<th style="width:20%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Frame Border (m)</td>
<td style="vertical-align: middle; text-align: center;">900003</td>
<td style="vertical-align: middle; text-align: left;">Border size of geozone.</td>
<td style="vertical-align: middle; text-align: left;">Min = 0<br>Max = 1000000<br>Default = "0"</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Frame Border (m)</td>
<td style="vertical-align: middle; text-align: center;">900003</td>
<td style="vertical-align: middle; text-align: left;">Border size of geozone.</td>
<td style="vertical-align: middle; text-align: left;">Min = 0<br>Max = 1000000<br>Default = "0"</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Radius (m)</td>
<td style="vertical-align: middle; text-align: center;">900005</td>
<td style="vertical-align: middle; text-align: left;">The radius of circle geozone.</td>
<td style="vertical-align: middle; text-align: left;">Min = 5<br>Max = 1000000<br>Default = "5"</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Latitude (X)</td>
<td style="vertical-align: middle; text-align: center;"></td>
<td style="vertical-align: middle; text-align: left;">Latitude of:
* circle center
* one of the rectangle corners
* one of the polygon vertices</td>
<td style="vertical-align: middle; text-align: left;"></td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">Longitude (Y)</td>
<td style="vertical-align: middle; text-align: center;"></td>
<td style="vertical-align: middle; text-align: left;">Longitude of:
* circle center
* one of the rectangle corners
* one of the polygon vertices</td>
<td style="vertical-align: middle; text-align: left;"></td>
</tr>
</table>


===Geozone Parameter ID Calculation===
There are two types of parameter IDs used in the Manual Geofence scenario:
* Global parameter IDs - used to configure global parameters, which can affect all scenarios;
* Scenario-specific parameter IDs - used to configure scenario-specific parameters, which only affect the specific scenario.
Offsets are used in order to find out any specific Parameter ID for either a global or scenario-specific parameter.
====Global parameter IDs====
Global parameter IDs start from 899,900.


=== <u> Parameters list </u>===
The formula for calculating a global parameter ID is:
'''NOTE:''' parameter IDs in the table below are given for Geozone 1, as an example. I.e., here some parameter IDs are identical for both circle and rectangle shapes, since geozeone parameter IDs are calculated using formulas, based on the number of a geozone. See below [link] for geofence parameter ID calculation.


''Will be added soon''.
''parameter_id = 899,900 + offset''
====Scenario-specific parameter IDs====
Scenario-specific parameter IDs start from 900,000.


=== <u> Geozone Parameter ID Calculation </u>===
Each individual scenario reserves 100 parameter IDs. This means that scenario 1 parameter ID range is 900000 - 900099, scenario 2 is 900100 - 900199, etc.
Geozone-specific parameter IDs start from 900000. Each geozone has 100 reserved parameter IDs, e.g. Geozone 1 parameter ID range is 900000-900099, Geozone 2 – 900100-900199, etc.
Parameter IDs have a reserved offset that is used for ID calculation:


''Will be added soon''.  
First 50 parameter IDs are reserved for various scenario parameters, while the latter 50 are reserved for geozone coordinates (up to 25 points).


The formula for a parameter ID is:
The formula for calcuating a scenario-specific parameter ID is:
parameter_id = 900000 + (geozone_number – 1)*100 + id_offset
''scenario_offset = (scenario_number - 1) * 100''


Examples:
''parameter_id = 900,000 + scenario_offset + id_offset''
* Priority of Geozone 1:
===Limitations, Edge Cases & Additional Notes===
900000 + (1 - 1) * 100 + 0 = 900000
* With [[#Private / Business mode]] Private mode active and GNSS masking enabled (Param :11813), geozone events are not recorded because GNSS data is masked(GNSS data is 0 (invalid) or last known position).
* Speed limit threshold of Geozone 2:
900000 + (2 – 1) * 100 + 7 = 900107


==Towing detection==
==Towing detection==
Line 1,713: Line 1,275:
| [[File:FTX towing detection without dout.png|right|500 px]]  
| [[File:FTX towing detection without dout.png|right|500 px]]  
}}
}}
=== <u>Introduction</u> ===
This scenario detects when a vehicle is being towed, whether it is lifted at an angle or as a whole. The detection is based on accelerometer data and external triggers such as ignition and movement
 
===Basic Operation===
This scenario detects when a vehicle is being towed, whether it is lifted at an angle or as a whole. The detection is based on '''accelerometer data''' and '''external triggers''' such as '''ignition and movement.'''
* The scenario activates when the ignition is OFF and stops if the ignition turns ON.
 
* It monitors the accelerometer data for sudden angle changes or movements that indicate towing.
=== <u>Prerequisites</u> ===
* If the vehicle remains in a towed state for a configured duration, an event is recorded
 
<!-- If model supports DOUT1, then show -->
To ensure proper operation, the following conditions must be met:
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}} | and a '''digital output (DOUT)''' can be triggered.}}
# '''Ignition Source''' – Used to detect whether the vehicle is turned ON or OFF.
* Once the towing stops, the scenario '''logs an event'''
# '''Movement Source''' – Used to determine if the vehicle is moving or stationary.
<!-- If model supports DOUT1, then show -->
# '''Accelerometer Data''' – The device must have a working accelerometer to detect changes in orientation and movement.
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}} | and cancels the DOUT before resetting.}}
 
===Scenario States===
=== <u>How It Works</u> ===
 
* The scenario '''activates when the ignition is OFF''' and stops if the ignition turns ON.
* It monitors the accelerometer data for sudden '''angle changes or movements''' that indicate towing.
* If the vehicle remains in a towed state for a configured duration, an '''event is recorded''' <!-- If model supports DOUT1, then show --> {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}} | and a '''digital output (DOUT)''' can be triggered.}}
* Once the towing stops, the scenario '''logs an event''' <!-- If model supports DOUT1, then show --> {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}} | and cancels the DOUT before resetting.}}
 
=== <u>Scenario States</u> ===
 
'''Waiting for Activation:'''
'''Waiting for Activation:'''
* The scenario starts when '''ignition is OFF.'''
* The scenario starts when ignition is OFF.
* It waits for a '''configured activation delay''' before monitoring accelerometer data.
* It waits for a configured activation delay before monitoring accelerometer data.
'''Monitoring for Towing:'''
'''Monitoring for Towing:'''
* When the first valid accelerometer reading is received, the device sets a '''reference vector''' (baseline position).
* When the first valid accelerometer reading is received, the device sets a reference vector (baseline position).
* It continuously checks if an '''angle or movement threshold''' is exceeded.
* It continuously checks if an angle or movement threshold is exceeded.
'''Towing Detection:'''
'''Towing Detection:'''
* If the threshold is exceeded for the '''configured duration''', the scenario moves to the '''active towing state''' and logs an event.
* If the threshold is exceeded for the configured duration, the scenario moves to the active towing state and logs an event.
<!-- If model supports DOUT1, then show -->  
<!-- If model supports DOUT1, then show -->
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}} |
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}} |
* '''DOUT can be activated''' to trigger an alert or external system. }}
* DOUT can be activated to trigger an alert or external system. }}
'''Towing Active State:'''
'''Towing Active State:'''
* The device waits for '''movement to stop''' before resetting.
* The device waits for movement to stop before resetting.
* If movement resumes, the '''timer resets''', extending the active state.
* If movement resumes, the timer resets, extending the active state.
* If no movement is detected for the configured '''Movement Stop Delay''', the scenario logs a '''towing end event''' <!-- If model supports DOUT1, then show --> {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}} | and cancels the DOUT before resetting.}}
* If no movement is detected for the configured Movement Stop Delay, the scenario logs a towing end event
<!-- If model supports DOUT1, then show -->
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}} | and cancels the DOUT before resetting.}}
'''Reset & Restart:'''
'''Reset & Restart:'''
* After detecting the end of towing, the scenario resets and returns to the '''waiting for activation''' state.
* After detecting the end of towing, the scenario resets and returns to the waiting for activation state.


=Other features=
=OTHER FEATURES=
== Fall Down Detection ==
== Fall Down Detection ==
[[File:Fall down detection - menu.png|right|500px]]
[[File:Fall down detection - menu.png|right|500px]]
Line 1,760: Line 1,315:
This is achieved by the device acquiring a base vector, which will serve as a reference point for when the two-wheeler is upright. This vector is acquired by measuring the accelerometer readings when the GNSS fix is available, GNSS ground speed is 0 and no movement is detected.  Once the base vector is acquired, the device will constantly monitor the readings of the accelerometer to calculate the current vector. If the difference in angle between the base vector and the current vector exceed the configured values, a fall down event will be generated and sent to the server.
This is achieved by the device acquiring a base vector, which will serve as a reference point for when the two-wheeler is upright. This vector is acquired by measuring the accelerometer readings when the GNSS fix is available, GNSS ground speed is 0 and no movement is detected.  Once the base vector is acquired, the device will constantly monitor the readings of the accelerometer to calculate the current vector. If the difference in angle between the base vector and the current vector exceed the configured values, a fall down event will be generated and sent to the server.


=== <u>Prerequisites and Important Settings </u> ===
===Prerequisites and Important Settings===


* All accelerometer-related features, including fall down detection depend on secure device mounting to function properly. See “Mounting recommendations” [link].
* All accelerometer-related features, including fall down detection depend on secure device mounting to function properly.
* Movement source settings are vital for proper functioning of the feature, since base vector will only be calculated when movement, according to movement source is not detected.  
* Movement source settings are vital for proper functioning of the feature, since base vector will only be calculated when movement, according to movement source is not detected.  
* It is important to note, that a valid GNSS fix is also neccessery for proper base vector acquiring. Due to this reason, it is not possible for the device to acquire a base vector indoors, for example, inside a garage.
* It is important to note, that a valid GNSS fix is also necessary for proper base vector acquiring. Due to this reason, it is not possible for the device to acquire a base vector indoors, for example, inside a garage.
* If the device is remounted to another vehicle, the base vector will have to be recalculated. Base vector recalculation can be initiated via the SMS/GPRS command '''fall_down_reset'''.
* If the device is remounted to another vehicle, the base vector will have to be recalculated. Base vector recalculation can be initiated via the [[SMS/GPRS command - fall_down_reset]].
 
===Basic Operation===
=== <u> Basic Operation </u> ===
 
* Once the feature is enabled, the device waits until the conditions for base vector calculation are met.
* Once the feature is enabled, the device waits until the conditions for base vector calculation are met.
* Once a valid GNSS fix is available, ground speed is 0 m/s and no movement, according to the configured movement source is detected, the device initiates base vector calculation.
* Once a valid GNSS fix is available, ground speed is 0 m/s and no movement, according to the configured movement source is detected, the device initiates base vector calculation.
Line 1,777: Line 1,330:
* Once the base vector is established, the device will continuously read the current vector and compare it to the base vector.
* Once the base vector is established, the device will continuously read the current vector and compare it to the base vector.
Once the angle difference returns to a value below the configured Activation Angle, the fall down event is considered over. The device returns to the monitoring state.
Once the angle difference returns to a value below the configured Activation Angle, the fall down event is considered over. The device returns to the monitoring state.
 
===Parameters===  
=== <u> Parameters list </u>===  
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<tr>
Line 1,787: Line 1,339:
</tr>
</tr>
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> XXX </td>
<td style="vertical-align: middle; text-align: center;"> XXX </td>
<td style="vertical-align: middle; text-align: center;"> XXX</td>
<td style="vertical-align: middle; text-align: center;"> XXX</td>
<td style="vertical-align: middle; text-align: center;"> XXX </td>
<td style="vertical-align: middle; text-align: center;"> XXX </td>
<td style="vertical-align: middle; text-align: left;"> XXX </td>
<td style="vertical-align: middle; text-align: left;"> XXX </td>
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Eventual Records </td>
<td style="vertical-align: middle; text-align: center;"> Eventual Records </td>
<td style="vertical-align: middle; text-align: center;"> 1024400 </td>
<td style="vertical-align: middle; text-align: center;"> 1024400 </td>
<td style="vertical-align: middle; text-align: center;"> Defines whether eventual records are generated (Disable) or whether the status of the fall down event is sent with each periodic record </td>
<td style="vertical-align: middle; text-align: center;"> Defines whether eventual records are generated (Disable) or whether the status of the fall down event is sent with each periodic record </td>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' Disable <br>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' Disable <br>'''1 =''' Enable  </td>
'''1 =''' Enable  </td>
 
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Activation angle (deg) </td>
<td style="vertical-align: middle; text-align: center;"> Activation angle (deg) </td>
<td style="vertical-align: middle; text-align: center;"> 12102</td>
<td style="vertical-align: middle; text-align: center;"> 12102</td>
Line 1,810: Line 1,356:
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''30'''<br>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''30'''<br>
Maximum value = '''180''' <br>Default value = '''30''' </td>
Maximum value = '''180''' <br>Default value = '''30''' </td>
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Activation timeout </td>
<td style="vertical-align: middle; text-align: center;"> Activation timeout </td>
<td style="vertical-align: middle; text-align: center;"> 12103 </td>
<td style="vertical-align: middle; text-align: center;"> 12103 </td>
Line 1,819: Line 1,363:
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br>
Maximum value = '''3600''' <br>Default value = '''3''' </td>
Maximum value = '''3600''' <br>Default value = '''3''' </td>
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Generate event </td>
<td style="vertical-align: middle; text-align: center;"> Generate event </td>
<td style="vertical-align: middle; text-align: center;"> 12110 </td>
<td style="vertical-align: middle; text-align: center;"> 12110 </td>
Line 1,829: Line 1,371:
'''1 = On enter''' Fall down event will be generated once the fall down event begins. <br>
'''1 = On enter''' Fall down event will be generated once the fall down event begins. <br>
'''2 = On both''' Fall down events will be generated once the event begins and when it ends. <br> </td>
'''2 = On both''' Fall down events will be generated once the event begins and when it ends. <br> </td>
</tr>  
</tr>  
</table>
</table>


==Static navigation==
==Static navigation==
 
Static Navigation helps eliminate minor “jumps” in GNSS data when the vehicle or device is actually stationary. Because GNSS signals can fluctuate, your device might appear to move slightly even when it’s not moving at all. With Static Navigation, speed and position changes are filtered out to provide a more accurate representation of a stationary vehicle.
=== <u>Introduction</u> ===
===Basic Operation===
 
''Static Navigation'' helps eliminate minor “jumps” in GNSS data when the vehicle or device is actually '''stationary'''. Because GNSS signals can fluctuate, your device might appear to move slightly even when it’s not moving at all. With '''Static Navigation''', speed and position changes are filtered out to provide a more accurate representation of a stationary vehicle.
 
=== <u>How It Works</u> ===
 
'''Check Movement Status'''
'''Check Movement Status'''
* The device looks at its movement source (e.g., built-in accelerometer, speed reading from GNSS, etc.).
* The device looks at its movement source (e.g., built-in accelerometer, speed reading from GNSS, etc.).
* If this source indicates the device is '''not moving''', the system '''enables Static Navigation''' (assuming you’ve enabled it in the configurator).
* If this source indicates the device is not moving, the system enables Static Navigation (assuming you’ve enabled it in the configurator).
'''Filter GNSS Fluctuations'''
'''Filter GNSS Fluctuations'''
* With Static Navigation on, the device '''discards''' small, spurious position changes from the GNSS.
* With Static Navigation on, the device discards small, spurious position changes from the GNSS.
* The internal angle and speed are treated as '''0''' until genuine movement is detected again.
* The internal angle and speed are treated as "0" until genuine movement is detected again.
'''GNSS Data vs. Device State'''
'''GNSS Data vs. Device State'''
* When movement is detected, Static Navigation '''disables itself''', allowing normal GNSS position updates.
* When movement is detected, Static Navigation disables itself, allowing normal GNSS position updates.
* If the device becomes stationary once more, Static Navigation re-enables to filter out jitter.
* If the device becomes stationary once more, Static Navigation re-enables to filter out jitter.


== Ignition ON counter ==  
== Ignition ON counter ==  
[[File:Ignition ON counter TCT Main panel.png|right|500px]]
[[File:Ignition ON counter TCT Main panel.png|right|500px]]
Ignition ON Counter feature continuously tracks how long a vehicle has spent with the active ignition.  
Ignition ON Counter feature continuously tracks how long a vehicle has spent with the active ignition.  


Line 1,863: Line 1,397:
Once Ignition source state changes to OFF, it saves the last value to Ignition on counter value field and  will start counting from this exact saved value if Ignition source changes again.   
Once Ignition source state changes to OFF, it saves the last value to Ignition on counter value field and  will start counting from this exact saved value if Ignition source changes again.   


 
===Prerequisites and Important Settings===
=== <u>Prerequisites and Important Settings </u> ===
* For the functionality to work properly and to achieve the desired results, it's recommended to check the Ignition settings Source section in configurator.
* For the functionality to work properly and to achieve the desired results, it's recommended to check the '''Ignition settings Source''' section in configurator.
* To ensure proper and desired notification of functionality status changes, check if it's enabled and configured in the configurator's '''SMS / call settings''' and '''Input / output (I/O)''' sections.
* To ensure proper and desired notification of functionality status changes, check if it's '''enabled and configured''' in the configurator's '''SMS / call settings and Input / output (I/O)''' sections.
* To avoid incorrect value calculations, always check the set value in the configurator's '''Ignition on counter value (s)'''.
* To avoid incorrect value calculations, always check the set value in the configurator's '''Ignition on counter value (s)'''.
 
===Basic Operation===
=== <u> Basic Operation </u> ===
* Ignition ON counter scenario starts, when it is enabled in configurator’s Features section.  
* Ignition ON counter scenario starts, when it is enabled in configurator’s Features section.  
* It monitors the state of ignition source.  
* It monitors the state of ignition source.  
Line 1,879: Line 1,411:
Also, counter value is saved before device restarts and when counter value is changed in configurator.  
Also, counter value is saved before device restarts and when counter value is changed in configurator.  
* After the ignition is turned OFF and later turned ON again, "Ignition on counter" value will continue counting from the last saved value.
* After the ignition is turned OFF and later turned ON again, "Ignition on counter" value will continue counting from the last saved value.
 
===Parameters</u>===  
 
=== <u> Parameters list </u>===  
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<tr>
Line 1,890: Line 1,420:
</tr>
</tr>
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Ignition ON counter </td>
<td style="vertical-align: middle; text-align: center;"> Ignition ON counter </td>
<td style="vertical-align: middle; text-align: center;"> 1044900 <br> (449)</td>
<td style="vertical-align: middle; text-align: center;"> 1044900 <br> (449)</td>
Line 1,899: Line 1,428:
'''1''' = Low priority Device makes an additional record with indication of event cause.
'''1''' = Low priority Device makes an additional record with indication of event cause.
'''2''' = High priority Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS. </td>
'''2''' = High priority Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS. </td>
</tr>  
</tr>  
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Ignition on counter value (s) </td>
<td style="vertical-align: middle; text-align: center;"> Ignition on counter value (s) </td>
<td style="vertical-align: middle; text-align: center;"> 13501</td>
<td style="vertical-align: middle; text-align: center;"> 13501</td>
Line 1,909: Line 1,436:
Maximum value = '''4294967295''' <br> Default value = '''0'''
Maximum value = '''4294967295''' <br> Default value = '''0'''
  </td>
  </td>
</tr>  
</tr>  
</table>
</table>
 
===Limitations, Edge Cases & Additional Notes===
=== <u> Limitations, Edge Cases & Additional Notes </u> ===
* When manually setting a new counter value via the TCT configurator, the counter increment parameter may override the new value. This can cause the update to be ignored. This issue only occurs when the value is set manually.
* When manually setting a new counter value via the '''TCT configurator''', the '''counter increment parameter''' may override the new value. This can cause the update to be ignored. This issue only occurs when the value is set manually.
* On rare occasions the counter value may not be saved to the device's flash memory due to a sudden software crash or a power cut.
* On rare occasions the counter value may not be saved to the device's flash memory due to a sudden software crash or a power cut.


==Custom scenarios==
==GNSS Fuel Counter==
[[File:FTX Customscenarios.png|alt=|right|500px]]  
[[File:FTX GNSS fuel counter.png|right|500px]]
The Fuel Counter GNSS scenario provides fuel consumption estimation using GNSS-derived distance and user-configured fuel rate. It calculates the amount of fuel used by multiplying traveled distance by the average fuel rate and converting it to appropriate units. It is a software-based alternative when fuel flow sensors are not available.
===Basic Operation===
The scenario monitors GNSS data and updates fuel usage whenever valid  GNSS PVT(Position, Velocity, Time) messages are received and movement is detected. It also supports runtime reconfiguration to keep fuel usage parameters in sync with user changes.


=== <u>Introduction</u> ===
On device startup, the scenario:
* Checks for a retained value of previously used fuel.
* If found, it restores this value and updates the corresponding I/O element.
* If no retained value is found, the system uses the current configuration parameter (user-defined or default), stores it in retained RAM for future startups, and updates the I/O element.


The ''Custom Scenarios'' feature empowers you to define custom rules (conditions) using existing IO parameters. When those rules are met, the device can generate an event record and/or toggle a digital output (DOUT). Think of it as a flexible, user-configurable “if-this-then-that” system on your tracking device.
When GNSS messages are received, the scenario determines whether they represent a GNSS source event or position data, and, if valid movement is detected, updates both distance traveled and fuel consumption.


'''Use Cases'''
If the scenario is enabled and the user modifies the average fuel usage parameter, it automatically detects any deviation between the configuration and the current I/O value and synchronizes them.
===Parameters===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
<th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Scenario priority </td>
<td style="vertical-align: middle; text-align: center;"> 1001200<br>(12)</td>
<td style="vertical-align: middle; text-align: center;">Priority of how events are being sent to a server. For example, events with low priority are added to the periodical record, and events with high priority are sent immediately after they occur.</td>
<td style="vertical-align: middle; text-align: left;"> Disable = '''0''' <br> Low priority = '''1''' <br> High priority = '''2''' </td>
</tr> 
<tr>
<td style="vertical-align: middle; text-align: center;"> Average consumption </td>
<td style="vertical-align: middle; text-align: center;"> 11902 </td>
<td style="vertical-align: middle; text-align: center;">Average consumption presented in the technical documentation of the vehicle.</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0.0'''<br> Maximum value = '''50.0''' <br> Default value = '''0.0''' </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">
Fuel counter value</td>
<td style="vertical-align: middle; text-align: center;"> 11910 </td>
<td style="vertical-align: middle; text-align: center;">The initial fuel counter value in liters. Can be used to set the starting value or reset the current one.</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0.0'''<br> Maximum value = '''4294967.2''' <br> Default value = '''0.0''' </td>
</tr>
</table>


* '''Immobilizer-Style Control''' – Turn on a vehicle’s starter if certain conditions are met.
==Custom scenarios==
* '''Immobilizer-Style Control''' – Turn off a vehicle’s starter if certain conditions are met.
[[File:FTX Customscenarios.png|alt=|right|500px]]
* '''iButton Authorization''' – Generate a record when an authorized driver inserts an iButton, or beep a buzzer if unauthorized.
The Custom Scenarios feature empowers you to define custom rules (conditions) using existing IO parameters. When those rules are met, the device can generate an event record and/or toggle a digital output (DOUT). Think of it as a flexible, user-configurable “if-this-then-that” system on your tracking device.
 
=== <u>Key Features</u> ===


Use Cases:
* Immobilizer-Style Control – Turn on/off a vehicle’s starter if certain conditions are met.
* iButton Authorization – Generate a record when an authorized driver inserts an iButton, or beep a buzzer if unauthorized.
===Key Features===
'''Record Generation'''
'''Record Generation'''
* Generate records when a scenario '''activates''' (goes from inactive to active) and '''deactivates''' (goes from active to inactive).
* Generate records when a scenario activates (goes from inactive to active) and deactivates (goes from active to inactive).
* You can set the priority of these records so they either send immediately (high priority) or follow normal data acquisition intervals (low priority).
* You can set the priority of these records so they either send immediately (high priority) or follow normal data acquisition intervals (low priority).
'''Flexible IO Conditions'''
'''Flexible IO Conditions'''
* Each custom scenario can use '''up to three IO elements''' (“sources”) to build an activation condition.
* Each custom scenario can use up to three IO elements (“sources”) to build an activation condition.
* You define thresholds and how the data is evaluated: “OnEnter,” “OnExit,” “Is,” etc.
* You define thresholds and how the data is evaluated: “OnEnter,” “OnExit,” “Is,” etc.
* '''Activation Delay''' can replace older “averaging” logic—this ensures the condition remains valid for a set time before it triggers.
* Activation Delay can replace older “averaging” logic—this ensures the condition remains valid for a set time before it triggers.
'''DOUT Control'''
'''DOUT Control'''
* A scenario can switch a device’s DOUT '''on and off''' in a timed pattern.
* A scenario can switch a device’s DOUT on and off in a timed pattern.
* Infinite Mode: Repeat ON/OFF until the scenario becomes inactive.
* Infinite Mode: Repeat ON/OFF until the scenario becomes inactive.
* Finite Mode: Repeat ON/OFF for a configured number of cycles, then stop.
* Finite Mode: Repeat ON/OFF for a configured number of cycles, then stop.
'''DOUT Deactivation'''
'''DOUT Deactivation'''
* You can specify an '''extra IO element''' to forcibly '''turn off''' the active DOUT.
* You can specify an extra IO element to forcibly turn off the active DOUT.
* Useful when you want a driver or operator to silence a buzzer (via, for example, pressing a button linked to a digital input).
* Useful when you want a driver or operator to silence a buzzer (via, for example, pressing a button linked to a digital input).
'''Logic Operands & Activation'''
'''Logic Operands & Activation'''
* When using multiple sources, you can combine them with ''AND/OR'' logic.
* When using multiple sources, you can combine them with ''AND/OR'' logic.
* For example, “Source 2 AND Source 3” must both be active, or “Source 2 OR Source 3” can trigger a condition.
* For example, “Source 2 AND Source 3” must both be active, or “Source 2 OR Source 3” can trigger a condition.
 
===Basic Operation===
=== <u>How It Works: Flow Overview</u> ===
 
'''Enable the Scenario'''
'''Enable the Scenario'''
* Set the '''Scenario Priority''' to a value '''greater than 0''' (1 = low priority, 2 = high priority). Zero disables the scenario.<br>
* Set the Scenario Priority to a value greater than 0 (1 = low priority, 2 = high priority). Zero disables the scenario.
'''Define Up to Three Sources'''
'''Define Up to Three Sources'''
* '''Source 1''' is always evaluated.
* Source 1 is always evaluated.
* '''Source 2''' and '''Source 3''' can be turned on/off and combined via AND/OR logic with the previous source.
* Source 2 and Source 3 can be turned on/off and combined via AND/OR logic with the previous source.
* Each source has:
* Each source has:
** '''IO Element (AVL ID)'''
** IO Element (AVL ID)
** '''Operand''' (OnEnter, OnExit, Is, etc.)
** Operand (OnEnter, OnExit, Is, etc.)
** '''Low/High Threshold'''
** Low/High Threshold
** '''Activation Delay''' (seconds)
** Activation Delay (seconds)
'''Scenario Activation'''
'''Scenario Activation'''
* The scenario becomes active if '''all selected sources''' meet their conditions simultaneously (based on the chosen logic AND/OR).
* The scenario becomes active if '''all selected sources''' meet their conditions simultaneously (based on the chosen logic AND/OR).
* A '''record''' is generated if the scenario transitions from inactive → active, unless the operand is “Is” (which remains constantly active while the condition is true).
* A record is generated if the scenario transitions from inactive → active, unless the operand is “Is” (which remains constantly active while the condition is true).
'''DOUT Behavior'''
'''DOUT Behavior'''
* If configured, the device '''toggles DOUT ON/OFF''' according to:
* If configured, the device toggles DOUT ON/OFF according to:
** '''DOUT ON Duration (ms)'''
** DOUT ON Duration (ms)
** '''DOUT OFF Duration (ms)'''
** DOUT OFF Duration (ms)
** DOUT Repeat Count'''Bold text''' (0 for infinite).
** DOUT Repeat Count (0 for infinite).
'''DOUT Deactivation'''
'''DOUT Deactivation'''
* If a '''deactivation source''' is set, that IO can forcibly '''turn off''' the DOUT even if the scenario is still active.
* If a deactivation source is set, that IO can forcibly turn off the DOUT even if the scenario is still active.
* The DOUT will remain off until the scenario becomes inactive (or conditions change).
* The DOUT will remain off until the scenario becomes inactive (or conditions change).
'''Scenario Deactivation'''
'''Scenario Deactivation'''
* If any source condition fails (e.g., threshold not met), the scenario goes back to inactive and a '''record''' is generated indicating this change (unless using “Is,” which ends immediately when condition fails).
* If any source condition fails (e.g., threshold not met), the scenario goes back to inactive and a record is generated indicating this change (unless using “Is,” which ends immediately when condition fails).
 
===Parameters===
=== <u>Configuration Parameters</u> ===
 
'''Scenario & Priority'''
'''Scenario & Priority'''
* '''Scenario AVL IDs:'''
* '''Scenario AVL IDs:'''
Line 1,985: Line 1,542:


* '''Priority Values & Meaning'''
* '''Priority Values & Meaning'''
 
<table class="nd-othertables_2" style="width:35%; margin-bottom: 30px;">
<table class="nd-othertables_2" style="width:80%; margin-bottom: 30px;">
    <tr>
        <th style="width:5%; text-align: left;">'''Value'''</th>
        <th style="width:5%; text-align: left;">'''AVL Priority'''</th>
        <th style="width:10%; text-align: left;">'''Scenario Enabled?'''</th>
    </tr>
     <tr>
     <tr>
         <th style="width:10%; text-align: left;">'''Value'''</th>
         <td style="width:5%; text-align: left;">0</td>
         <th style="width:10%; text-align: left;">'''AVL Priority'''</th>
         <td style="width:5%; text-align: left;">None</td>
         <th style="width:20%; text-align: left;">'''Scenario Enabled?'''</th>
         <td style="width:5%; text-align: left;">No</td>
        <th rowspan="13" style="width:30%; text-align: center; vertical-align: middle;">
        </th>
 
<tr>
        <td style="text-align: left;">0</td>
        <td style="text-align: left;">None</td>
        <td style="text-align: left;">No</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td style="text-align: left;">1</td>
         <td style="width:5%; text-align: left;">1</td>
         <td style="text-align: left;">Low</td>
         <td style="width:5%; text-align: left;">Low</td>
         <td style="text-align: left;">Yes</td>
         <td style="width:5%; text-align: left;">Yes</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td style="text-align: left;">2</td>
         <td style="width:10%; text-align: left;">2</td>
         <td style="text-align: left;">High</td>
         <td style="width:10%; text-align: left;">High</td>
         <td style="text-align: left;">Yes</td>
         <td style="width:10%; text-align: left;">Yes</td>
     </tr>
     </tr>
</table>
</table>


'''Source Configuration'''
'''Source Configuration'''
* '''Source (AVL ID)''' – Which IO to monitor (e.g., digital input, sensor reading).
* Source (AVL ID) – Which IO to monitor (e.g., digital input, sensor reading).
* '''Operand''' – “OnEnter,” “OnExit,” “Is,” etc.
* Operand – “OnEnter,” “OnExit,” “Is,” etc.
* '''Low/High Level''' – Numeric threshold range for the IO value.
* Low/High Level – Numeric threshold range for the IO value.
* '''Delay''' – Time in seconds the condition must stay valid (for “Is,” “OnEnter,” “OnExit”).
* Delay – Time in seconds the condition must stay valid (for “Is,” “OnEnter,” “OnExit”).
* '''Active''' – For Source 2 and 3, whether to include them in the logic.
* Active – For Source 2 and 3, whether to include them in the logic.
* '''Logic''' – How Source 2 or 3 combines with the previous source: AND (0) or OR (1).
* Logic – How Source 2 or 3 combines with the previous source: AND (0) or OR (1).


'''DOUT Configuration'''
'''DOUT Configuration'''
* '''DOUT Control''' – Which DOUT to activate (0 = none).
* DOUT Control – Which DOUT to activate (0 = none).
* '''DOUT ON Duration (ms)''' – How long DOUT stays ON each cycle (0 or 100–5000 ms).
* DOUT ON Duration (ms) – How long DOUT stays ON each cycle (0 or 100–5000 ms).
* '''DOUT OFF Duration (ms)''' – How long DOUT stays OFF each cycle (0 or 100–5000 ms).
* DOUT OFF Duration (ms) – How long DOUT stays OFF each cycle (0 or 100–5000 ms).
* '''DOUT Repeat''' – Number of ON/OFF cycles (0 = infinite).
* DOUT Repeat – Number of ON/OFF cycles (0 = infinite).


'''DOUT Deactivation'''  
'''DOUT Deactivation'''  
* '''Source (AVL ID)''' – Which IO can force DOUT off.
* Source (AVL ID) – Which IO can force DOUT off.
* '''Operand''' – Condition on that IO (similar to source operand).
** Set the source to 0 to disable DOUT deactivation.
* '''Low/High Level''' – Thresholds for that IO.
* Operand – Condition on that IO (similar to source operand).
* Set the source to '''0''' to disable DOUT deactivation.
* Low/High Level – Thresholds for that IO.
 
=== <u>Expected Behavior: Simple Example</u> ===


===Example===
'''Scenario Setup'''
'''Scenario Setup'''
* '''Priority''': 2 (High, scenario enabled)
* Priority: 2 (High, scenario enabled)
* '''Source 1 (AVL ID = 21, e.g., Speed)''':
* Source 1 (AVL ID = 21, e.g., Speed):
** Operand: OnEnter
** Operand: OnEnter
** Low: 0, High: 5 (speed range)
** Low: 0, High: 5 (speed range)
** Delay: 3 s
** Delay: 3 s
* '''DOUT Control''':
* DOUT Control:
** DOUT = 1
** DOUT = 1
** ON Duration = 500 ms, OFF Duration = 500 ms, Repeat = 0 (infinite)
** ON Duration = 500 ms, OFF Duration = 500 ms, Repeat = 0 (infinite)
'''Activation'''
'''Activation'''
* If the vehicle’s speed stays between 0 and 5 km/h for at least 3 seconds, the scenario becomes active.
* If the vehicle’s speed stays between 0 and 5 km/h for at least 3 seconds, the scenario becomes active.
* The device generates an “active” event record.
* The device generates an “active” event record.
* DOUT 1 starts toggling: ON for 500 ms, OFF for 500 ms.
* OUT 1 starts toggling: ON for 500 ms, OFF for 500 ms.
'''Deactivation'''
'''Deactivation'''
* If speed goes above 5 km/h or drops below 0 for even a moment, the scenario becomes inactive.
* If speed goes above 5 km/h or drops below 0 for even a moment, the scenario becomes inactive.
* A “deactivated” event record is generated, and DOUT stops toggling.
* A “deactivated” event record is generated, and DOUT stops toggling.
'''Optional DOUT Deactivation'''
'''Optional DOUT Deactivation'''
* If configured, an extra input (e.g., driver-pressed button) could turn DOUT off instantly, even while the scenario remains active.
* If configured, an extra input (e.g., driver-pressed button) could turn DOUT off instantly, even while the scenario remains active.
=== <u>Conclusion</u> ===
The ''Custom Scenarios'' feature offers '''unparalleled flexibility''' for creating user-defined logic based on any available IO parameters. By mixing thresholds, delays, operands (“OnEnter,” “OnExit,” “Is”), and logic (AND/OR), you can tailor the device’s behavior to your exact operational needs—'''all without extra firmware modules'''.<br>
Whether you need a simple record when a door opens or a complex multi-condition alert that flashes lights and logs data, Custom Scenarios gives you the tools to build it.


<!-- TBD
<!-- TBD

Latest revision as of 17:05, 19 March 2026

DRIVING BEHAVIOR

Crash detection

The Crash detection feature detects and logs vehicle crash events using accelerometer data. The device offers two primary crash detection methods:

  • Basic Crash Detection – Monitors the X and Y axes for sudden spikes in acceleration.
  • Advanced Crash Detection – Builds on Basic Crash but also captures additional metrics (e.g., direction, maximum/average acceleration) and uses all three accelerometer axes.
  • A Crash Trace option is also available, which collects high-frequency accelerometer samples and GNSS data before, during, and after a crash, providing detailed insight into the event.

Prerequisites

  • GNSS (Optional) is required if you plan to capture concurrent GNSS data during a crash trace or rely on GNSS-based scenarios.

Parameter Description

Crash Scenario Threshold

  • Basic Crash calculates the acceleration magnitude on X and Y axes only (to avoid triggering on gravity).
  • Advanced Crash (when enabled) calculates magnitude on all three axes typically resulting in higher measured values.

Basic Crash Detection

  • Crash Event AVL ID: 247
  • Crash Detection Priority (Parameter ID 1024700): Set to Low or High to enable/disable the scenario.

Threshold & Duration

  • When the accelerometer magnitude exceeds the configured threshold for the configured duration, the device flags a crash.
  • The crash state continues until the acceleration drops 30% below the threshold (hysteresis) to prevent multiple crash events from small fluctuations.

Advanced Crash Detection

  • Enabled if Basic Crash is enabled and Parameter ID 13102 is set to “enabled.”
  • In addition to basic detection, it:
    • Calculates crash duration and direction
    • Captures maximum and average magnitudes, plus amplitudes on each axis.
  • These extended metrics are included in the same AVL record (ID 247) once the crash ends.

Crash Trace

  • When Crash Trace is enabled, the device collects high-frequency accelerometer data (~400 samples/second) plus GNSS data (1 sample/second).
  • Upon a crash event (AVL ID 247 with value = 1), data continues to be collected for a configured period before and after the crash.
  • A second crash record (AVL ID 247, “full crash trace” type) is generated once all data is processed, accompanied by AVL ID 257 for accelerometer axis data.
  • Crash Trace timestamps match the actual collection times, providing a detailed timeline of the event.

Basic Operation

Basic Crash Detection

  • IMU Reading: Each new acceleration vector is compared against the configured threshold.
  • Threshold Exceeded: If the threshold is met or exceeded for the configured duration, the device flags a crash as “ongoing.”
  • Hysteresis Check: The crash continues until acceleration falls 30% below the threshold.
  • Crash Event: Once the acceleration returns below threshold, a Crash Event (AVL ID 247) is generated, and the crash is marked as ended.

Advanced Crash Detection

  • Basic Detection as Trigger: Advanced Crash runs alongside Basic Crash. When Basic Crash sees a threshold exceedance, Advanced Crash also begins data collection on all three axes.
  • Extended Metrics: As long as the device is in a crash state, the algorithm accumulates samples to compute maximum and average magnitudes/amplitudes, as well as crash direction.
  • Crash End & Record: When the crash ends (per Basic Crash hysteresis), Advanced Crash finalizes its calculations and outputs a single AVL record (ID 247) with the extended data fields.

Crash Trace

  • Data Collection: Accelerometer (~400 Hz) and GNSS (1 Hz) data are continuously buffered.
  • Crash Start: If a crash is detected, a preliminary Crash Event (AVL ID 247, value=1) is generated. The device continues collecting data for the specified time window after the crash trigger.
  • Crash End: The device finalizes the crash trace data and generates a full crash trace record (AVL ID 247 which includes:
    • AVL ID 257: High-frequency accelerometer data.
    • GNSS PVT data.
    • Crash trace event type.
  • Logging & Timestamps: The record’s timestamps correspond to the actual collection times, capturing the event’s progression before, during, and after the crash.

Records & Logging

  • All crash scenarios culminate in event records with AVL ID 247.
  • Advanced Crash adds extended crash metrics into the same event record.
  • Crash Trace finalizes with an additional record containing AVL ID 257 for high-frequency accelerometer samples.

Private / Business mode

This feature enables employees to use company vehicles for personal purposes while maintaining compliance with EU General Data Protection Regulation requirements. When Private mode is active, the device masks location data and other sensitive information to prevent unauthorized tracking. Business mode restores full data visibility for standard fleet operations.

Private/Business Mode is used in fleet operations where employees may drive company vehicles for both work and personal needs. It helps ensure privacy during personal use by disabling location reporting, while still providing full tracking and operational data during business use.

In the TCT Features section, the Private / Business Mode allows the user to configure when the private mode should activate and deactivate by selecting one of the available feature triggers: a weekly scheduler or an external trigger type. Additionally, the user can define how the system should handle GNSS and odometer data while private mode is active. The feature also supports automatic deactivation of private mode when specific events are detected, such as Unplug, Towing, and other configured triggers.

Prerequisites and Important Settings

  • After exiting any sleep mode, DOUT and Private/Business state will automatically return to the values they had before entering the sleep mode.

Basic Operation

  • In the Private/Business window, the user can set the priority level used for sending messages (HIGH or LOW priority).
  • The DOUT control function allows indicating the state of Private Mode.When Private Mode is detected as ON, the configured DOUT output will also be switched ON.

DOUT State in Sleep mode

In different sleep modes, DOUT behavior and Private/Business states are:

MODE DOUT STATE PRIVATE/BUSINESS MODE STATE
Online Sleep Last state before entering sleep Last state before entering sleep
Deep Sleep Last state before entering sleep Last state before entering Deep Sleep
Power Off Sleep DOUT is OFF Last state before entering Power Off Sleep

After exiting any sleep mode, DOUT and Private/Business state return to the state they were in before entering the sleep mode.

GNSS Data Masking defines how the device will handle location information (GNSS data) while in Private Mode:

  • No masking – GNSS information is not hidden.
  • GNSS data is sent as zero – In every record sent to the server, the GNSS fields (latitude, longitude, altitude, angle, and number of satellites) are set to "0". Additionally, GSM Cell ID and GSM Area Code information will not be sent.
  • GNSS data is sent as last known good position – The last valid GNSS data (latitude, longitude, altitude) recorded before entering Private Mode is sent in every record.

The following I/O elements are sent as "0":

  • GSM Cell ID (AVL ID 205)
  • GSM Area Code (AVL ID 206)
  • Private Mode Odometer Stop - when enabled, the device does not accumulate odometer data while Private Mode is active.
  • Private Business Deactivation – enables the system to automatically deactivate Private Mode based on selected scenarios.

Available scenarios include: Towing, Unplug, Crash and Autogeofence. The user can select one, several, or all scenarios from the dropdown menu.

NOTE! If Trigger type is set to External, the user must press the button or switch again to re enable Private Mode. If Trigger type is set to Weekly Schedule, the user must wait until the next scheduled activation time for Private Mode to be enabled again.

Feature Triggers

This section allows the user to configure the trigger logic that switches the feature between Private Mode and Business Mode.

Trigger Types

1. External

External triggers can be configured using Digital Inputs (DINs). When External is selected, the user can choose a specific DIN for the trigger logic.

DIN Mode Options:

  • Button Mode. The selected DIN operates as a button. Private Mode is activated or deactivated when the DIN status changes (triggered on the status transition).
  • Switch Mode. The selected DIN operates as a switch. Private Mode is controlled based on the current DIN value:
    • DIN = HIGH → Private Mode enabled
    • DIN = LOW → Private Mode disabled

2. Weekly Schedule

A weekly schedule can be configured to automatically enable Private Mode at specific times based on the user defined schedule.

Enables automatic switching between Private Mode and Business Mode based on configured time, date, daylight saving rules and time zones.

PARAMETER NAME PARAMETER ID (RELATED AVL ID) DESCRIPTION VALUES
Private/Business mode 391 Private/Business mode where:

0 - Private mode OFF (Business mode ON);

1 - Private mode ON (Business mode OFF);		 Min: 0
Default: 0
Max: 1
Private/Business mode triggers 11811 Private/Business mode triggers. When a trigger is activated it activates the private mode. When the trigger goes low the private mode is turned OFF and device works in a business mode. Implemented using bit mask so that multiple choices could be selected where:
0 - no trigger;
1 - DIN1;
2 - DIN2;
3 - DIN3;
4 - DIN4;		 Min: 0
Default: 0
Max: 15
Private/Business DOUT control 11812 Private/Business DOUT. When the private mode is active the selected DOUT is turned ON, when the private mode is OFF DOUT needs to go low also. Parameter values:
0 - DOUT control disabled;
1 - DOUT1;
2 - DOUT2;
3 - DOUT3;
4 - DOUT4;		 Min: 0
Default: 0
Max: 4
GPS data masking 11813 GPS data masking describes how the GPS data is being masked when the device is in private mode. The parameter values are:
0 - No masking;
1 - GNSS data is sent as zero;
2 - GNSS data is sent as last good known position		 Min: 0
Default: 1
Max: 2
Private mode odometer stop 11815 If enabled stops odometer calculation for Odometer and Trip scenarios in Private mode:
0 - Disabled;
1 - Enabled;		 Min: 0
Default: 0
Max: 1
Private mode deactivation triggers 11816 Private mode deactivation triggers. When a trigger is activated it deactivates the private mode. Implemented using bit mask so that multiple choices could be selected where:

0 - no trigger;
1 - Towing detected;
2 - Unplug detected;
3 - Towing or Unplug detected;
4 - Crash detected;
5 - Towing or Crash detected;
6 - Unplug or Crash detected;
7 - Towing, Unplug or Crash detected;
8 - Autogeofence triggered;
9 - Towing or Autogeofence triggered;
10 - Unplug or Autogeofence triggered;
11 - Towing, Unplug or Autogeofence triggered;
12 - Crash or Autogeofence triggered;
13 - Towing, Crash or Autogeofence triggered;
14 - Unplug, Crash or Autogeofence triggered;

15 - Towing, Unplug, Crash or Autogeofence triggered		 Min: 0
Default: 15
Max: 15
Private/Business mode Weekly Schedule Monday Enable 11818 If enabled automatically disables private mode on Monday during configured time:

0 - Disabled;

1 - Enabled		 Min: 0
Default: 1
Max: 1
Private/Business mode Weekly Schedule start time of a Business mode on Monday 11819 Starting from a configured time until end time disables Private mode and enables Business mode on Monday Min: 0
Default: 0
Max: 1440
Private/Business mode Weekly Schedule end time of a Business mode on Monday 11820 Starting from a configured time until end time disables Private mode and enables Business mode on Monday Min: 0
Default: 0
Max: 1440
Private/Business mode Weekly Schedule Tuesday Enable 11821 If enabled automatically disables private mode on Tuesday during configured time:

0 - Disabled;

1 - Enabled		 Min: 0
Default: 1
Max: 1
Private/Business mode Weekly Schedule start time of a Business mode on Tuesday 11822 Starting from a configured time until end time disables Private mode and enables Business mode on Tuesday Min: 0
Default: 0
Max: 1440
Private/Business mode Weekly Schedule end time of a Business mode on Tuesday 11823 Starting from a configured time until end time disables Private mode and enables Business mode on Tuesday Min: 0
Default: 0
Max: 1440
Private/Business mode Weekly Schedule Wednesday Enable 11824 If enabled automatically disables private mode on Wednesday during configured time:

0 - Disabled;

1 - Enabled		 Min: 0
Default: 1
Max: 1
Private/Business mode Weekly Schedule start time of a Business mode on Wednesday 11825 Starting from a configured time until end time disables Private mode and enables Business mode on Wednesday Min: 0
Default: 0
Max: 1440
Private/Business mode Weekly Schedule end time of a Business mode on Wednesday 11826 Starting from a configured time until end time disables Private mode and enables Business mode on Wednesday Min: 0
Default: 0
Max: 1440
Private/Business mode Weekly Schedule Thursday Enable 11827 If enabled automatically disables private mode on Thursday during configured time:

0 - Disabled;

1 - Enabled		 Min: 0
Default: 1
Max: 1
Private/Business mode Weekly Schedule start time of a Business mode on Thursday 11828 Starting from a configured time until end time disables Private mode and enables Business mode on Thursday Min: 0
Default: 0
Max: 1440
Private/Business mode Weekly Schedule end time of a Business mode on Thursday 11829 Starting from a configured time until end time disables Private mode and enables Business mode on Thursday Min: 0
Default: 0
Max: 1440
Private/Business mode Weekly Schedule Friday Enable 11830 If enabled automatically disables private mode on Friday during configured time:

0 - Disabled;

1 - Enabled		 Min: 0
Default: 1
Max: 1
Private/Business mode Weekly Schedule start time of a Business mode on Friday 11831 Starting from a configured time until end time disables Private mode and enables Business mode on Friday Min: 0
Default: 0
Max: 1440
Private/Business mode Weekly Schedule end time of a Business mode on Friday 11832 Starting from a configured time until end time disables Private mode and enables Business mode on Friday Min: 0
Default: 0
Max: 1440
Private/Business mode Weekly Schedule Saturday Enable 11833 If enabled automatically disables private mode on Saturday during configured time:

0 - Disabled;

1 - Enabled;		 Min: 0
Default: 1
Max: 1
Private/Business mode Weekly Schedule start time of a Business mode on Saturday 11834 Starting from a configured time until end time disables Private mode and enables Business mode on Saturday Min: 0
Default: 0
Max: 1440
Private/Business mode Weekly Schedule end time of a Business mode on Saturday 11835 Starting from a configured time until end time disables Private mode and enables Business mode on Saturday Min: 0
Default: 0
Max: 1440
Private/Business mode Weekly Schedule Sunday Enable 11836 If enabled automatically disables private mode on Sunday during configured time:

0 - Disabled;

1 - Enabled		 Min: 0
Default: 1
Max: 1
Private/Business mode Weekly Schedule start time of a Business mode on Sunday 11837 Starting from a configured time until end time disables Private mode and enables Business mode on Sunday Min: 0
Default: 0
Max: 1440
Private/Business mode Weekly Schedule end time of a Business mode on Sunday 11838 Starting from a configured time until end time disables Private mode and enables Business mode on Sunday Min: 0
Default: 0
Max: 1440
Private/Business Weekly Schedule Time zone 11839 Time in minutes from GMT +00:00. Example: GMT +02:00 is 120 Min: -720
Default: 0
Max: 1440
Private/Business Weekly Schedule Daylight saving enable 11840 If enabled automatically adjusts the time for daylight saving;

0 - Disabled;

1 - Enabled		 Min: 0
Default: 0
Max: 1
Private/Business Weekly Schedule Daylight saving start week 11841 Sets the week when daylight saving starts:

1 - First week of a month;
2 - Second week of a month;
3 - Third week of a month;
4 - Fourth week of a month;

5 - Last week of a month		 Min: 0
Default: 0
Max: 4
Private/Business Weekly Schedule Daylight saving start month 11842 Sets the month when daylight saving starts. A month is represented by a number from 1 to 12 Min: 1
Default: 1
Max: 12
Private/Business Weekly Schedule Daylight saving start weekday 11843 Sets the weekday when daylight saving starts:

1 - Monday;
2 - Tuesday;
3 - Wednesday;
4 - Thursday;
5 - Friday;
6 - Saturday;

7 - Sunday		 Min: 0
Default: 0
Max: 6
Private/Business Weekly Schedule Daylight saving start time 11844 Sets the time in minutes when daylight saving starts. A start time is represented by a number from 0 to 1440, where the number represents the minutes from midnight Min: 0
Default: 0
Max: 1440
Private/Business Weekly Schedule Daylight saving end week 11845 Sets the week when daylight saving ends:

1 - First week of a month;
2 - Second week of a month;
3 - Third week of a month;
4 - Fourth week of a month;

5 - Last week of a month		 Min: 0
Default: 0
Max: 4
Private/Business Weekly Schedule Daylight saving end month 11846 Sets the month when daylight saving ends. A month is represented by a number from 1 to 12 Min: 1
Default: 1
Max: 12
Private/Business Weekly Schedule Daylight saving end weekday 11847 Sets the weekday when daylight saving ends:

1 - Monday;
2 - Tuesday;
3 - Wednesday;
4 - Thursday;
5 - Friday;
6 - Saturday;

7 - Sunday		 Min: 0
Default: 0
Max: 6
Private/Business Weekly Schedule Daylight saving end time 11848 Sets the time in minutes when daylight saving ends. An end time is represented by a number from 0 to 1440, where the number represents the minutes from midnight Min: 0
Default: 0
Max: 1440
Private/Business trigger type 11849 Sets Private/Business trigger type:

0 - External trigger such as DIN;

1 - Weekly schedule		 Min: 0
Default: 0
Max: 1
Private/Business DIN mode 11851 Sets Private/Business DIN mode:

0 - Button: triggers on state change Low -> High;

1 - Switch: triggers on state change Low -> High and High -> Low		 Min: 0
Default: 0
Max: 1

Overspeeding

The Overspeeding scenario detects when a vehicle exceeds a configured maximum speed and generates a record. Another record is generated when the speed returns to normal.

Purpose:

  • Promote safe and economic driving.
  • Provide real-time alerts on speed violations.
  • Generate automatic reports for fleet management.

How It Works

Speed Monitoring

  • The system continuously monitors vehicle speed.
  • If the speed exceeds the configured max speed by an allowed tolerance, a record is triggered.

Event Recording

  • A record is generated when:
    • The vehicle exceeds the max speed + 2 km/h.
    • The vehicle speed returns to normal (below max speed - 2 km/h).

Customization Options

  • Max speed limit: Default is 90 km/h, but it can be customized.
  • Record priority: Can be set to low or high (adjusted in Telematics Configuration Tool (TCT) under Features → Driving Behavior).
  • Feature status: Disabled by default, must be manually enabled.

Prerequisites

  • The device must have active GNSS tracking to monitor speed accurately.

Trip

The Trip feature allows users to track vehicle journeys from start to finish based on a combination of ignition, movement, and speed parameters. During an active trip, the device maintains a running odometer (Trip Odometer), which is reset once the trip ends.

Prerequisites

  • You must have proper Ignition and Movement sources configured in the device (e.g., ignition signal, GNSS, accelerometer) so that the device can detect when the vehicle is actually running and moving.
  • The I/O Trip Odometer must be enabled for the device to log distance traveled during a trip.

Parameter Description

Start Speed

  • Defines the minimum GPS speed (in km/h) the vehicle must exceed to begin a trip.
  • Default: 5 km/h

Ignition OFF Timeout

  • Sets the time (in seconds) the system waits after the ignition source turns OFF before officially ending the trip.
  • Default: 60 seconds

Trip Odometer

  • An internal I/O value that tracks how far the vehicle travels between Trip start and Trip end.
  • Automatically resets to 0 when a new trip begins.

Basic Operation

Trip Start

  • The device monitors both Ignition (configured ignition source) and Movement (configured movement source).
  • Once Ignition is ON, Movement is ON and the vehicle GPS speed exceeds the Start Speed (default: 5 km/h), the trip is marked as “started.”

During the Trip

  • The Trip Odometer increments continuously to reflect the total distance traveled.
  • Any event triggers, such as data logging or notifications, will note that the vehicle is in an active trip state.

Trip End

  • When the Ignition source turns OFF, the device starts the Ignition OFF Timeout countdown (default: 60s).
  • If the ignition remains OFF for the entire timeout duration, the trip is ended.
  • The Trip Odometer value is stored and then reset to 0 before the next trip begins.

Record Generation & Logging

  • Depending on the device’s configuration, a record can be generated at Trip start and Trip end to facilitate reporting and analytics.
  • Trip distance data is captured in the I/O Trip Odometer field, which is useful for fleet management or mileage reporting.

Odometer

The Odometer scenario calculates the total distance traveled by a vehicle using GNSS data. To ensure accuracy and reduce system load, small thresholds are applied to both distance and speed. The device also performs a sanity check to confirm each new distance reading is valid and reasonable.

Prerequisites

  • You must be able to configure odometer parameters (e.g., ID 11807) and potentially format or reset the device’s non-volatile memory (NVM).

Parameter Description

Distance and Speed Thresholds

  • Minimum distance to update: 2.5 meters
  • Minimum ground speed to update: 0.42 m/s
  • These thresholds prevent minor fluctuations from inflating the odometer reading.

Sanity Checks

  • Timestamp Validation: The current PVT (position, velocity, time) data must be newer than the previous reading.
  • Distance Spike Prevention:The device discards any reading suggesting a speed greater than 350 meters/second, as it indicates erroneous data.

Total Odometer Value (ID 11807)

  • The total distance traveled is stored internally (in NVM) to preserve the odometer value.
  • This value is written to memory every kilometer to reduce flash wear.
  • Manually setting or resetting this parameter (via ID 11807 allows the odometer to start from a custom value.
  • After formatting or resetting the NVM, the odometer value may be cleared unless reconfigured.

Min/Max Values for ID 11807:

  • Minimum: 0
  • Maximum: 4294967

Basic Operation

Odometer Updates

  • As the vehicle travels, the device checks the GNSS-reported distance in increments. Once the minimum distance (2.5 m) and speed (0.42 m/s) thresholds are exceeded, it updates the total odometer.
  • Every 1 km increment, the new odometer value is saved to NVM.

Data Validation

  • Each new reading is compared against the previous PVT data. If the time is older or the speed exceeds 350 m/s, the reading is disregarded.
  • This ensures only valid and realistic data points are recorded.

Odometer Preservation

  • The total odometer value is maintained even if the device reboots or loses power, unless an NVM format or parameter reset occurs.
  • To continue from a known distance, set the starting odometer value via ID 11807. The device will then count upward from that point.

Eco driving

The Eco Driving scenario is designed to detect and analyze aggressive driving behaviors such as, Harsh acceleration, Harsh braking, and Harsh cornering. It uses data from either an accelerometer or GNSS to track driving patterns. When a threshold is exceeded for a specific duration, the system generates an eventual record to highlight unsafe driving actions.

Prerequisites

Scenario Activation

  • The device needs a stable GNSS fix or properly calibrated accelerometer for accurate event detection.

Parameter Description

  • Priority - Defines the importance level of generated Eco Driving events.
  • Acceleration Source - Specifies where the acceleration data is taken from:
    • Accelerometer → Uses data from the device’s built-in accelerometer chip.
    • GNSS → Uses speed and heading data from GNSS to calculate acceleration vectors.
  • Thresholds (Acceleration Limits in m/s²) - Maximum allowed acceleration values before triggering an event:
    • Acceleration Threshold → Forward acceleration limit.
    • Braking Threshold → Backward acceleration limit.
    • Cornering Threshold → Side (left/right) acceleration limit.

Basic Operation

An Eco Driving event is triggered when all of the following conditions are met:

  1. Scenario is enabled
  2. Ignition is ON
  3. GNSS fix is present
  4. Vehicle speed is above 10 km/h for the event’s duration
  5. Acceleration exceeds the configured threshold and stays above it for at least 0.5 seconds
  6. Acceleration drops below the threshold and stays there for 0.5 seconds

Once an event is detected:

  • A new record is generated, identifying the type of Eco Driving event.
  • The following IO parameters are updated:
    • Eco Driving type (AVL ID 253) → Identifies event type:
      • 1 = Harsh acceleration
      • 2 = Harsh braking
      • 3 = Harsh cornering
    • Eco Driving value (AVL ID 254) → Records the peak acceleration value (measured in hundredths of g).

Scenario States

The system operates as a state machine with 4 states:

  1. Idle → No event detection (vehicle speed too low, no GNSS fix, ignition off, etc.).
  2. Eco → Normal driving, acceleration remains within safe thresholds.
  3. Harsh → Acceleration exceeds the limit, but event isn't registered yet (prevents false positives).
  4. Cooldown → Acceleration has dropped back but might spike again; prevents rapid, repeated event logging.

If the acceleration remains high beyond the cooldown period, the event is officially recorded.

Notes & Edge Cases

Repeated Accelerations in the Same Direction

  • If multiple harsh acceleration spikes occur within 0.5 seconds, they are considered part of the same event rather than separate ones.

Speed Drops Below 10 km/h

  • If speed drops below the activation speed during an ongoing event, further acceleration values are ignored until speed increases again.
  • This might result in:
    • The peak acceleration not being recorded accurately.
    • No event being logged at all, depending on conditions.

Directional Independence

  • Each movement direction (forward, backward, left, right) is analyzed separately.
  • Example: a left-turn event does not interfere with acceleration/braking event detection.

Identification scenario

Parameter Description

Authorized Devices List

  • Maintains a list of devices that have been authenticated and are permitted to connect or be recognized without further checks.
  • When a new device is approved, it’s added to this list.

Scenario functionality can be divided into 5 states:

  • Idle
    • Waits for detection or expiration events.
    • If a device detected event occurs, transitions to Authorization.
    • If a device expired event occurs, transitions to Device Expired.
  • Authorization
    • Triggered when a new device is detected.
    • Checks if the device is authorized:
      • If not authorized, it returns to Idle (no record generated).
      • If authorized and first occurrence, transitions to Device Online.
      • If authorized and subsequent occurrence, transitions to Device Update.
  • Device Online
    • Generates a "Device Online" record (e.g., AVL) for an authorized device’s first recognition.
    • Moves the device to the “already authorized devices” list.
    • Returns to Idle.
  • Device Update
    • Reached if the device is authorized and not in its first occurrence.
    • Updates the device record to reflect the new detection time or any changes in state.
    • Returns to Idle.
  • Device Expired
    • Triggered if the device’s authorization has ended (e.g., time limit expired or device removed from the system).
    • If the device is still in the authorization list, generates a “Device Expired” record and removes the device from the authorized list.
    • Returns to Idle.

Record Generation

  • Periodic or Eventual: Records related to device detection can be configured with different priorities—Low (periodic) or High (immediate).
  • Record Types
    • Device Online
    • Device Update
    • Device Expired

Accelerometer calibration scenario

The Accelerometer Calibration Scenario is used to determine the tracker’s position and orientation within a vehicle and reorient the tracker to the vehicle’s coordinate system. This ensures that acceleration measurements align correctly with the vehicle’s axes:

  • X-axis → Forward/Backward
  • Y-axis → Left/Right
  • Z-axis → Up/Down

By calibrating the accelerometer, the system can accurately interpret vehicle movements, reducing errors caused by varying device installation orientations.

Accelerometer Calibration Basic Principles

The scenario relies on GNSS and accelerometer data. Since most devices do not have a gyroscope, these are the primary sources for orientation detection. The algorithm collects two types of accelerometer data:

  • Movement with Acceleration - When the vehicle moves straight while accelerating or decelerating, this data helps determine the front and back direction.
  • Movement Without Acceleration - When the vehicle moves without acceleration, it allows the system to determine the ground vector.

Because devices can be mounted in various ways, they do not inherently know the directions of the vehicle’s front, back, left, right, up, and down.

The GNSS module helps detect whether the vehicle is moving straight or turning. It provides speed and direction relative to the north. If the vehicle moves straight with an increasing or decreasing speed, the system collects acceleration vectors.

Once a sufficient number of data points are collected:

  • The forward vector is calculated.
  • The ground vector is determined.
  • The device’s orientation in the vehicle coordinate system is established.

This allows for the calculation of quaternions, which express the device’s rotation within the vehicle. These quaternions are then applied to new accelerometer readings, ensuring they align with the vehicle’s coordinate system. As a result, all future accelerometer data correctly reflect the vehicle’s motion.

Prerequisites

  • A valid GNSS fix.
  • The device should be mounted securely in the vehicle to avoid incorrect readings.

Excessive idling

Scenario used to detect when a vehicle is stopped for a long time with a running engine, which is bad for fuel consumption and environmental effects.

Prerequisites

This scenario uses two global configuration parameters to work:

  1. Ignition source – used to detect if a vehicle is on or off.
  2. Movement source – used to detect if a vehicle is moving or not.

Ignition detection is determined by ignition source in system settings. Movement detection is determined by Movement source system settings.

For this scenario ignition is used as is, but there are modifications to the movement parameter. Movement will be also detected when there is GNSS fix and ground speed is more than 5 km/h. This option is not configurable and cannot be turned off.

Scenario can be in 1 of 2 states:

  • Moving - inactive state. Vehicle is moving or stopped, but time to stop timeout has not been reached yet. Will also be forced when ignition is OFF;
  • Idle - active state. Vehicle is stopped or moving, but time to movement timeout has not been reached yet.

Parameter description

Priority:

  • Low – Event will be sent together with periodic records according to data acquisition settings.
  • High – Event will be sent immediately not considering for data acquisition settings.

Time to stopped - The time in seconds for how long vehicle should not move with the ignition ON (by "Ignition source") to enter the excessive idling state. Time to moving – The time in seconds for how long vehicle should move with the ignition ON (by "Ignition source") to exit the excessive idling state.


VEHICLE PROTECTION

Network Jamming

The Jamming Detection scenario identifies instances of active GSM signal jamming on the device. The modem performs continuous jamming detection and reports any suspicious activity back to the main device.

Network jamming detection serves as a useful tool, which provides the crucial benefits of preventing cargo or vehicle theft, ensuring driver safety, and maintaining uninterrupted data flow.

When GSM signal jamming is detected, Network Jamming scenario activates. Then it starts a configurable jamming detection delay before generating jamming event. It is intended to reduce false positives. After the timeout ends, the device generates an event record. SMS notification Additionally, if digital output is configured, it activates already installed measures to inform driver or disrupt thieves ( like buzzer, LED indication, locking all doors etc. ).

Prerequisites and Important Settings

  • Network Jamming won’t work with Deep Sleep and Power off sleep modes turned ON. Make sure to check information in Power saving settings.

Basic Operation

  • The modem continuously always monitors the network, scanning for potential jamming events.
  • Network Jamming detection scenario activates when GSM signal jamming is detected.
  • When GSM signal Jamming is detected, Time until jamming reporting (s) counter starts. It can be configured by user. It is intended to reduce false positives of jamming events.
  • If detected jamming event lasts after entire delay period, device creates a High or Low priority record labeled “Jamming started”. Additionally, if output control is configured, it will activates already installed measures to inform driver or disrupt thieves (like buzzers, LED indication, locking all doors etc.).
  • As soon as jamming stops (after a “Jamming started” record was generated), the device creates a “Jamming ended” record. It is sent immediately if priority level is set to High.
  • Eventual records function lets user choose between sending eventual records of Jamming when enabled. And if disabled – eventual and periodic records are being sent bout Jamming.
  • After jamming event has ended, modem continues monitoring for further jamming events.

Parameters

PARAMETER NAME PARAMETER ID (RELATED AVL ID) DESCRIPTION VALUES
Network jamming detection 1024900
(249)		 The feature detects GSM jamming, initiates actions using an output, and helps to prevent vehicle theft when jamming devices are used. A low signal level is not equal to GSM jamming, the device recognizes these events. 0 = Disable Disable scenario.

1 = Low priority Device makes an additional record with indication of event cause.

2 = High priority Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS.
Time until jamming reporting (s) 11305 Jamming - network signal disruption. Time until jamming reporting is the time between jamming being detected and the record creation. Value in seconds. Minimum value = 0
Maximum value = 65535
Default value = 60
Eventual records 1024904 Enables feature status sending only when the event happens (an eventual record). When disabled, feature status will be sent with both eventual and periodical records. 0 = Disable
1 = Enable

Unplug detection

Unplug Detection is a feature that identifies when a device transitions between being powered by external voltage and running on internal power only. The device generates a record (AVL ID 252) with a configured priority whenever it is plugged in or unplugged.

Prerequisites & Important Settings

  • External Power Source - The vehicle or external system must provide a stable voltage supply that can be monitored by the device.

Parameter Description

Unplug Detection Mode

  • Simple - monitors external voltage to determine when the device is plugged or unplugged.
    • Recommended for vehicles where power voltage does not depend on ignition status.
  • Advanced - monitors both external voltage and accelerometer data.
    • Suitable for vehicles where power voltage is disconnected when ignition is off; the accelerometer helps confirm unplug events more reliably.

AVL ID 252

  • The record ID generated when the device is plugged or unplugged.
  • The user can configure priority (Low, High, etc.) to decide how the record is reported and logged.

Basic Operation

Simple Mode

  • The device regularly checks the external power line.
  • When external voltage is lost (drops below a configured threshold), the device deems itself unplugged and generates a "Power Unplugged" record.
  • When external voltage returns (exceeds the threshold), the device deems itself plugged and generates a "Power Plugged" record.

Advanced Mode

  • The device monitors both external voltage and the accelerometer.
  • If external power is lost but the accelerometer indicates movement or vibration (e.g., ignition turned off in some vehicles), the device can confirm that an unplug event truly occurred.
  • When power is restored along with the lack of movement, or once the system stabilizes, a plugged event is generated.

Record Generation & Logging

  • Whenever a change in power source state is detected (plugged or unplugged), an AVL ID 252 record is created with the configured priority.
  • Depending on the priority level, the device may send the record immediately (High priority) or with the next scheduled data batch (Low priority).

Auto Geofence

Geofencing is a location-based technology that creates a software-defined boundary (geofence) around a geographic area (geozone).

Two geofencing features are available with Teltonika Telematics devices:

  • Auto Geofence (described in this section) – allows automatically creating a circular geozone around the device’s last known location after it has been stationary for a specified period, then capture related events.
  • Manual Geofence – see here.

The Auto Geofence feature automatically creates a circular geofence zone around a vehicle's last known location after it has been stationary for a specified period. The system then generates alarm events if the vehicle moves outside this zone, or if it moves for a sustained period without a valid GNSS signal.

This functionality offers a dynamic layer of security against theft, particularly unauthorized towing, as it arms itself automatically based on vehicle behavior rather than ignition status. It is highly valuable for asset protection where vehicles make frequent, unscheduled stops. The ability to trigger an alarm even without a GNSS fix provides a crucial advantage in scenarios where a signal might be intentionally jammed or lost.

The feature operates in two main states. In its "Wait State," it monitors for the vehicle to become stationary with a valid GNSS fix. Once this condition is met for a configured timeout, it creates the geofence and enters the "Active State." In the Active State, it monitors for breaches. The feature can be deactivated and returned to the Wait State by various configurable triggers, such as a change in voltage, a digital input, or the presentation of an authorized iButton.

Prerequisites and Important Settings

  • The device must have a reliable GNSS signal and be able to detect its movement status for the feature to arm correctly.
  • If using a deactivation source such as a Digital Input (DIN) or iButton, the corresponding hardware (e.g., ignition connection, iButton reader) must be properly installed and configured.

Basic Operation

The feature's logic is divided into two distinct operational states: Wait State and Active State.

  • Entering the Wait State (Arming Process):
    • The system starts in the Wait State. It continuously checks for two conditions to be met simultaneously: the device must have a valid GNSS fix, and the vehicle must be stationary.
    • Once both conditions are met, an "Activation timeout" timer begins. If the vehicle moves or loses its GNSS fix at any point, the timer resets.
    • When the timer successfully completes, the device creates a circular geofence of a configured "Radius" centered on its current location.
    • Depending on the configuration, an "On Enter" event record can be generated at this point. The system then transitions to the Active State.
  • Active State (Monitoring and Alarm Trigger):
    • While in the Active State, the geofence is armed. The system monitors for two primary breach conditions:
      • Condition A: The device has a valid GNSS fix, and its current position is outside the created geofence.
      • Condition B: The device does not have a GNSS fix, but it detects continuous movement for the duration of the "Activation timeout".
    • If either of these conditions is met, an "On Exit" event record is generated (if configured), and the system returns to the Wait State.
  • Deactivation:
    • The armed geofence can be deactivated, returning the system to the Wait State without generating an alarm. This is achieved when a configured "Deactivate by" source is triggered (e.g., Digital Input 1 becomes active).

Parameter list

PARAMETER NAME PARAMETER ID (RELATED AVL ID) DESCRIPTION VALUES
Auto geofence 1017500 Disables, or enables and sets priority for record generation. 0 = Disable scenario.

1 = Low priority Device makes an additional record with indication of event cause.

2 = High priority Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS.
Generate event 20001 Defines when the event will be generated 0 = On exit

1 = On enter

2 = On both
Activation timeout (s) 20002 Sets the duration in seconds for two conditions:

1. In Wait State: how long the vehicle must be stationary with a GNSS fix before the geofence is armed.
2. In Active State: how long the vehicle must be moving without a GNSS fix to trigger an alarm.

Minimum value = 0
Maximum value = 65535
Radius (m) 20003 Sets the radius of the circular geofence in meters, measured from the vehicle's position when armed. Minimum value = 0
Maximum value = 1000000

Limitations, Edge Cases & Additional Notes

  • Stuck in Wait State: The feature will never arm if the conditions are not met. This can happen if the vehicle is constantly moving or if it is parked in a location with no GNSS signal (e.g., an underground garage).
  • Movement without GNSS: A key capability of this feature is generating an "On Exit" alarm if the vehicle moves for a sustained period without a GNSS fix. This is a critical security measure against signal jamming or loss.
  • Deactivation Source: The chosen deactivation source is the only way to disarm the feature without triggering an alarm (aside from staying within the geofence). Ensure the source aligns with the intended use case (e.g., using a Digital Input connected to the ignition).

Manual Geofence

Geofencing is a location-based technology that creates a software-defined boundary (geofence) around a geographic area (geozone).

Two geofencing features are available with Teltonika Telematics devices:

  • Auto Geofence – see here.
  • Manual Geofence (described in this section) – allows the user to manually create geozones of various shapes, then capture events related these geozones, with multiple options.

Manual Geofence is a feature that allows the device to monitor predefined geographic zones and generate events when the device enters, exits, or exceeds a configured speed limit within those zones. A geozone is defined on a map using geometric shapes (circle, rectangle, polygon).

Manual Geofence is used in fleet management, vehicle protection, and operational monitoring scenarios where location-based events are required. Typical use cases include detecting entry into restricted areas, monitoring vehicle departures from operational zones, enforcing speed limits in defined locations, or triggering device actions such as digital output control.

The device continuously compares its GNSS position with configured geozone boundaries. Each scenario independently tracks whether the device is inside or outside the zone and whether the configured speed limit threshold is exceeded. When these states change, the device generates an event record containing geofence-related identifiers and event information, and can control digital outputs.

In TCT, the user can create geozones by drawing them on the map. Three shapes are available:

  • Circle - defined by Radius and one pair of latitude/longitude (center coordinates of the circle).
  • Rectangle - defined by two pairs of latitude/longitude (most northwestern and southeastern corners of the rectangle).
  • Polygon - defined by 3-10 pairs of latitude/longitude (vertices of the polygon).

Each manual geozone has various associated options. They are discussed below.

Manual geofence global settings

In the upper right corner of the main Manual geofence window, the „Geofence settings“ button allows configuring global settings for digital output (DOUT) and timezone control accross all manual geozones.

For each separate DOUT, the user can set up Output control settings for individual geofences. The number of DOUTs depends on device hardware.

Disabling a DOUT here will disable output control configuration in all zones which use that particular DOUT.

Settings here (see table below) will affect what can be configured in the „Output control“ section of a particular geozone.

Parameters in global settings

PARAMETER NAME PARAMETER ID DESCRIPTION VALUES
Control mode DOUT1= 899900
DOUT2=899910
DOUT3=899920		 Select Control mode for digital output.

In Persistent mode, DOUT is controlled according to global DOUT parameters while the device is Inside/Outside of all geozones.

In Event mode, DOUT is controlled according to individual scenario parameters when a configured event occurs (Inside/Outside/Both) in the specific geozone.		 0=None (DOUT control disabled)
1=Persistent
2=Event
Activation timing DOUT1= 899901
DOUT2=899911
DOUT3=899921		 Select Activation timing when the event will be triggered.

Control mode - Persistent:
  • Outside activation timing, selected DOUT will start being controlled while the device is outside of the geozone and will stop being controlled while the device is inside of the geozone. If the device is outside of multiple geozones, selected DOUT will continue being controlled until the device enters one of the geozones.
  • Inside activation timing, selected DOUT will start being controlled while the device is inside the geozone and will stop being controlled while the device is outside of the geozone. If Output control according to speed limit is set, selected DOUT will start being controlled while the device is exceeding the speed limit inside the geozone. If the device is inside multiple geozones, selected DOUT will continue being controlled until the device is outside of all geozones (or stops exceeding the speed limit, if configured).

Control mode - Event:

  • Outside activation timing, selected DOUT will be triggered once you exit the configured geozone.
  • Inside activation timing, selected DOUT will be triggered once you enter the configured geozone.
 1=Outside
2=Inside
DOUT activation DOUT1= 899904
DOUT2=899914
DOUT3=899924		 Select DOUT activation for how long digital output will be active.

With Timed DOUT activation, DOUT is controlled according to global DOUT ON/OFF duration parameters while all conditions are being met. When control mode is Event, only Timed DOUT activation can be configured.

With Permanent activation, DOUT is simply set to ON state while all conditions are being met. When control mode is Persistent, both Timed and Permanent can be configured globally.		 0=Timed
1=Permanent
Output ON duration (ms) DOUT1= 899902
DOUT2=899912
DOUT3=899922		 Value in milliseconds, for how long DOUT should be active. Min = 100
Max = 5000
Default = "200"
Output OFF duration (ms) DOUT1= 899930
DOUT2=899913
DOUT3=899923		 A value in milliseconds, for how long DOUT should be inactive. Min = 1
Max = 5000
Default = "200"

Basic Operation

Because multiple Manual Geofence scenarios can be configured, all scenarios are stored in a list and run every second.

The device constantly tracks the current state related to the geozone:

  • In zone – whether the device is currently inside the geozone (changes as the device enters/exits the geozone).
  • Speeding – whether the device is currently exceeding the speed limit configured for the geozone (changes as device starts/stops speeding inside the geozone (on geozone exit, speeding state is set to ‘stop’)).

When any of these states change, and if the device is configured to capture them, appropriate events are recorded.

Manual geofence records consist of the following AVL IDs:

  • 155 - used to identify the specific manual geofence scenario, which generated the event:
    • Value = (<scenario_id> - 1); eg. scenario 10 generates AVL ID 155 with value 9;
  • 156 - In-zone event. Is added to the record if an in-zone event was captured;
    • 0 - Exit event;
    • 1 - Enter event.
  • 157 - Speeding event. Is added to the record if a speeding event was captured.
    • 0 - Speeding stop event;
    • 1 - Speeding start event.

Parameters

NOTE! Parameters are given for Geozone 1. See #Geozone Parameter ID Calculation for more information.

PARAMETER NAME PARAMETER ID DESCRIPTION VALUES
Geozone settings
Priority 900000 Priority of how events are being sent to a server. Events with low priority are added to the periodical record, and events with high priority are sent immediately after they occur.
Value „0“ disables the geozone.		 0=Disable
1=Low priority
2=High priority
Event type 900002 Defines which geozone events should be captured. 0=No event
1=On Exit
2=On Entrance
3=On Both
Output control
Output source 900008 Select the digital output that will be controlled by this geozone. List of available DOUTs (e.g. DOUT1, etc.)
Control mode 899900 Select Control mode for digital output.

In Persistent mode, DOUT is controlled according to global DOUT parameters while the device is Inside/Outside of all geozones.

In Event mode, DOUT is controlled according to individual scenario parameters when a configured event occurs (Inside/Outside/Both) in the specific geozone.		 0=None
1=Persistent
2=Event
DOUT activation 899904 Select DOUT activation for how long digital output will be active.

With Timed DOUT activation, DOUT is controlled according to global DOUT ON/OFF duration parameters while all conditions are being met. When control mode is Event, only Timed DOUT activation can be configured.

With Permanent activation, DOUT is simply set to ON state while all conditions are being met. When control mode is Persistent, both Timed and Permanent can be configured globally.		 0=Timed
1=Permanent
Activation timing 900009 Select Activation timing when the event will be triggered.

Control mode - Persistent:

  • Outside activation timing, selected DOUT will start being controlled while the device is outside of the geozone and will stop being controlled while the device is inside of the geozone. If the device is outside of multiple geozones, selected DOUT will continue being controlled until the device enters one of the geozones.
  • Inside activation timing, selected DOUT will start being controlled while the device is inside the geozone and will stop being controlled while the device is outside of the geozone. If Output control according to speed limit is set, selected DOUT will start being controlled while the device is exceeding the speed limit inside the geozone. If the device is inside multiple geozones, selected DOUT will continue being controlled until the device is outside of all geozones (or stops exceeding the speed limit, if configured).


Control mode - Event:

  • Outside activation timing, selected DOUT will be triggered once you exit the configured geozone.
  • Inside activation timing, selected DOUT will be triggered once you enter the configured geozone.
  • With Outside and Inside activation timing, both described logics will be applied.
 1=Outside
2=Inside
3=Outside and inside
Output ON duration (ms) 900010 A value in milliseconds, for how long DOUT should be active. Min = 100
Max = 5000
Default = "200"
Output OFF duration (ms) 900011 A value in milliseconds, for how long DOUT should be inactive. Min = 1
Max = 5000
Default = "200"
Output repeat count 900012 A value for how many times DOUT activation should be repeated. Min = 1
Max = 500
Default = "1"
Output control according to speed limit
Output control according to speed limit 900006 Toggles setting up speed limit threshold that will have an effect on selected output activation and deactivation. 0=Disable
1=Enable
Speed limit 900007 Speed threshold which determines when to generate speeding start/stop events. Min = 0
Max = 1000
Default = "0"

Parameters for coordinates

Parameter sets for coordinates depend on the shape of geozone:

  • All shapes have „Frame Border“.
  • Circle - defined by Radius and one pair of latitude/longitude (center coordinates of the circle).
  • Rectangle - defined by two pairs of latitude/longitude (most northwestern and southeastern corners of the rectangle).
  • Polygon - defined by 3-10 pairs of latitude/longitude (vertices of the polygon).

For polygon, click „See all points“ at the bottom of the list to view or edit all entered coordinates.

PARAMETER NAME PARAMETER ID DESCRIPTION VALUES
Frame Border (m) 900003 Border size of geozone. Min = 0
Max = 1000000
Default = "0"
Frame Border (m) 900003 Border size of geozone. Min = 0
Max = 1000000
Default = "0"
Radius (m) 900005 The radius of circle geozone. Min = 5
Max = 1000000
Default = "5"
Latitude (X) Latitude of:
  • circle center
  • one of the rectangle corners
  • one of the polygon vertices
Longitude (Y) Longitude of:
  • circle center
  • one of the rectangle corners
  • one of the polygon vertices

Geozone Parameter ID Calculation

There are two types of parameter IDs used in the Manual Geofence scenario:

  • Global parameter IDs - used to configure global parameters, which can affect all scenarios;
  • Scenario-specific parameter IDs - used to configure scenario-specific parameters, which only affect the specific scenario.

Offsets are used in order to find out any specific Parameter ID for either a global or scenario-specific parameter.

Global parameter IDs

Global parameter IDs start from 899,900.

The formula for calculating a global parameter ID is:

parameter_id = 899,900 + offset

Scenario-specific parameter IDs

Scenario-specific parameter IDs start from 900,000.

Each individual scenario reserves 100 parameter IDs. This means that scenario 1 parameter ID range is 900000 - 900099, scenario 2 is 900100 - 900199, etc.

First 50 parameter IDs are reserved for various scenario parameters, while the latter 50 are reserved for geozone coordinates (up to 25 points).

The formula for calcuating a scenario-specific parameter ID is: scenario_offset = (scenario_number - 1) * 100

parameter_id = 900,000 + scenario_offset + id_offset

Limitations, Edge Cases & Additional Notes

  • With #Private / Business mode Private mode active and GNSS masking enabled (Param :11813), geozone events are not recorded because GNSS data is masked(GNSS data is 0 (invalid) or last known position).

Towing detection

This scenario detects when a vehicle is being towed, whether it is lifted at an angle or as a whole. The detection is based on accelerometer data and external triggers such as ignition and movement

Basic Operation

  • The scenario activates when the ignition is OFF and stops if the ignition turns ON.
  • It monitors the accelerometer data for sudden angle changes or movements that indicate towing.
  • If the vehicle remains in a towed state for a configured duration, an event is recorded
  • Once the towing stops, the scenario logs an event

Scenario States

Waiting for Activation:

  • The scenario starts when ignition is OFF.
  • It waits for a configured activation delay before monitoring accelerometer data.

Monitoring for Towing:

  • When the first valid accelerometer reading is received, the device sets a reference vector (baseline position).
  • It continuously checks if an angle or movement threshold is exceeded.

Towing Detection:

  • If the threshold is exceeded for the configured duration, the scenario moves to the active towing state and logs an event.

Towing Active State:

  • The device waits for movement to stop before resetting.
  • If movement resumes, the timer resets, extending the active state.
  • If no movement is detected for the configured Movement Stop Delay, the scenario logs a towing end event

Reset & Restart:

  • After detecting the end of towing, the scenario resets and returns to the waiting for activation state.

OTHER FEATURES

Fall Down Detection

Fall down detection is a feature which is used to detect when a two-wheeler vehicle has fallen over. The scenario uses a combination of accelerometer sensor and GNSS data to determine whether the physical orientation of the vehicle changed in such a way, that would indicate a fall down event.

The feature allows to improve safety of the end user, by sending events to the fleet tracking platform indicating that the equipment has fallen over. It can help business meet safety regulations while also helping to keep riders and their equipment safe.

This is achieved by the device acquiring a base vector, which will serve as a reference point for when the two-wheeler is upright. This vector is acquired by measuring the accelerometer readings when the GNSS fix is available, GNSS ground speed is 0 and no movement is detected. Once the base vector is acquired, the device will constantly monitor the readings of the accelerometer to calculate the current vector. If the difference in angle between the base vector and the current vector exceed the configured values, a fall down event will be generated and sent to the server.

Prerequisites and Important Settings

  • All accelerometer-related features, including fall down detection depend on secure device mounting to function properly.
  • Movement source settings are vital for proper functioning of the feature, since base vector will only be calculated when movement, according to movement source is not detected.
  • It is important to note, that a valid GNSS fix is also necessary for proper base vector acquiring. Due to this reason, it is not possible for the device to acquire a base vector indoors, for example, inside a garage.
  • If the device is remounted to another vehicle, the base vector will have to be recalculated. Base vector recalculation can be initiated via the SMS/GPRS command - fall_down_reset.

Basic Operation

  • Once the feature is enabled, the device waits until the conditions for base vector calculation are met.
  • Once a valid GNSS fix is available, ground speed is 0 m/s and no movement, according to the configured movement source is detected, the device initiates base vector calculation.
  • The device continuously reads IMU acceleration vectors, until a sufficient number of measurements have been taken.
  • Once the base vector is established, the device will continuously read the current vector and compare it to the base vector.
  • Once the base vector is established, the device will continuously read the current vector and compare it to the base vector.

If a the angle difference is greater than the configured Activation Angle for more seconds than the configured Activation Timeout, a fall down event will be generated.

  • Once the base vector is established, the device will continuously read the current vector and compare it to the base vector.

Once the angle difference returns to a value below the configured Activation Angle, the fall down event is considered over. The device returns to the monitoring state.

Parameters

PARAMETER NAME PARAMETER ID (RELATED AVL ID) DESCRIPTION VALUES
XXX XXX XXX XXX
Eventual Records 1024400 Defines whether eventual records are generated (Disable) or whether the status of the fall down event is sent with each periodic record 0 = Disable
1 = Enable
Activation angle (deg) 12102 Sets the angle difference, which should be detected between the base vector and the current vector in order to generate a fall down event. Minimum value = 30
Maximum value = 180
Default value = 30
Activation timeout 12103 Sets the timeout, for how many seconds the difference in angle between the base and current vector should be exceeded before generating a fall down event. Minimum value = 0
Maximum value = 3600
Default value = 3
Generate event 12110 The parameter defines under what condition (operand) the event will be generated. 0 = On exit Fall down event will be generated once the fall down event ends.

1 = On enter Fall down event will be generated once the fall down event begins.

2 = On both Fall down events will be generated once the event begins and when it ends.

Static navigation

Static Navigation helps eliminate minor “jumps” in GNSS data when the vehicle or device is actually stationary. Because GNSS signals can fluctuate, your device might appear to move slightly even when it’s not moving at all. With Static Navigation, speed and position changes are filtered out to provide a more accurate representation of a stationary vehicle.

Basic Operation

Check Movement Status

  • The device looks at its movement source (e.g., built-in accelerometer, speed reading from GNSS, etc.).
  • If this source indicates the device is not moving, the system enables Static Navigation (assuming you’ve enabled it in the configurator).

Filter GNSS Fluctuations

  • With Static Navigation on, the device discards small, spurious position changes from the GNSS.
  • The internal angle and speed are treated as "0" until genuine movement is detected again.

GNSS Data vs. Device State

  • When movement is detected, Static Navigation disables itself, allowing normal GNSS position updates.
  • If the device becomes stationary once more, Static Navigation re-enables to filter out jitter.

Ignition ON counter

Ignition ON Counter feature continuously tracks how long a vehicle has spent with the active ignition.

It serves as an useful tool for maintenance schedules, driver oversight, and any application where total engine running time matters.

When Ignition ON counter feature is enabled, it starts to monitor the ignition source. The moment ignition value changes to ON, it starts to count the actvie ingnition time (in seconds). SMS nofications about the event status will be sent to predefined number, if it was configured in Input/output and SMS/call settings. Additionally, Ignition ON counter default value can be set to specific number, other than zero. In that way, when ignition value changes to ON, counting adds the active ignition time to the already predefiend value. Once Ignition source state changes to OFF, it saves the last value to Ignition on counter value field and will start counting from this exact saved value if Ignition source changes again.

Prerequisites and Important Settings

  • For the functionality to work properly and to achieve the desired results, it's recommended to check the Ignition settings Source section in configurator.
  • To ensure proper and desired notification of functionality status changes, check if it's enabled and configured in the configurator's SMS / call settings and Input / output (I/O) sections.
  • To avoid incorrect value calculations, always check the set value in the configurator's Ignition on counter value (s).

Basic Operation

  • Ignition ON counter scenario starts, when it is enabled in configurator’s Features section.
  • It monitors the state of ignition source.

Suitable Ignition source can be set in System settings section, under Ignition settings.

  • When ignition source state changes to ON, counting of active ignition time starts (in seconds). It increments counter every 500ms.

SMS notifications about scenario state changes are sent, according to configured settings. Notification settings can be set in SMS/call settings section under SMS events and in Input /output (I/O) settings under Permanent I/O.

  • When ignition source state changes to OFF, counter value is saved to device’s memory.

Also, counter value is saved before device restarts and when counter value is changed in configurator.

  • After the ignition is turned OFF and later turned ON again, "Ignition on counter" value will continue counting from the last saved value.

Parameters

PARAMETER NAME PARAMETER ID (RELATED AVL ID) DESCRIPTION VALUES
Ignition ON counter 1044900
(449)

The feature counts the time spent with the active ignition and the counter value can be set according to your needs. After the ignition is turned OFF and later turned ON again, "Ignition on counter" value will continue counting (from the last saved value).

0 = Disable Disable scenario.

1 = Low priority Device makes an additional record with indication of event cause.

2 = High priority Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS.
Ignition on counter value (s) 13501 Ignition on counter value to be used initially. Minimum value = 0

Maximum value = 4294967295
Default value = 0

Limitations, Edge Cases & Additional Notes

  • When manually setting a new counter value via the TCT configurator, the counter increment parameter may override the new value. This can cause the update to be ignored. This issue only occurs when the value is set manually.
  • On rare occasions the counter value may not be saved to the device's flash memory due to a sudden software crash or a power cut.

GNSS Fuel Counter

The Fuel Counter GNSS scenario provides fuel consumption estimation using GNSS-derived distance and user-configured fuel rate. It calculates the amount of fuel used by multiplying traveled distance by the average fuel rate and converting it to appropriate units. It is a software-based alternative when fuel flow sensors are not available.

Basic Operation

The scenario monitors GNSS data and updates fuel usage whenever valid GNSS PVT(Position, Velocity, Time) messages are received and movement is detected. It also supports runtime reconfiguration to keep fuel usage parameters in sync with user changes.

On device startup, the scenario:

  • Checks for a retained value of previously used fuel.
  • If found, it restores this value and updates the corresponding I/O element.
  • If no retained value is found, the system uses the current configuration parameter (user-defined or default), stores it in retained RAM for future startups, and updates the I/O element.

When GNSS messages are received, the scenario determines whether they represent a GNSS source event or position data, and, if valid movement is detected, updates both distance traveled and fuel consumption.

If the scenario is enabled and the user modifies the average fuel usage parameter, it automatically detects any deviation between the configuration and the current I/O value and synchronizes them.

Parameters

PARAMETER NAME PARAMETER ID (RELATED AVL ID) DESCRIPTION VALUES
Scenario priority 1001200
(12)		 Priority of how events are being sent to a server. For example, events with low priority are added to the periodical record, and events with high priority are sent immediately after they occur. Disable = 0
Low priority = 1
High priority = 2
Average consumption 11902 Average consumption presented in the technical documentation of the vehicle. Minimum value = 0.0
Maximum value = 50.0
Default value = 0.0
Fuel counter value 11910 The initial fuel counter value in liters. Can be used to set the starting value or reset the current one. Minimum value = 0.0
Maximum value = 4294967.2
Default value = 0.0

Custom scenarios

The Custom Scenarios feature empowers you to define custom rules (conditions) using existing IO parameters. When those rules are met, the device can generate an event record and/or toggle a digital output (DOUT). Think of it as a flexible, user-configurable “if-this-then-that” system on your tracking device.

Use Cases:

  • Immobilizer-Style Control – Turn on/off a vehicle’s starter if certain conditions are met.
  • iButton Authorization – Generate a record when an authorized driver inserts an iButton, or beep a buzzer if unauthorized.

Key Features

Record Generation

  • Generate records when a scenario activates (goes from inactive to active) and deactivates (goes from active to inactive).
  • You can set the priority of these records so they either send immediately (high priority) or follow normal data acquisition intervals (low priority).

Flexible IO Conditions

  • Each custom scenario can use up to three IO elements (“sources”) to build an activation condition.
  • You define thresholds and how the data is evaluated: “OnEnter,” “OnExit,” “Is,” etc.
  • Activation Delay can replace older “averaging” logic—this ensures the condition remains valid for a set time before it triggers.

DOUT Control

  • A scenario can switch a device’s DOUT on and off in a timed pattern.
  • Infinite Mode: Repeat ON/OFF until the scenario becomes inactive.
  • Finite Mode: Repeat ON/OFF for a configured number of cycles, then stop.

DOUT Deactivation

  • You can specify an extra IO element to forcibly turn off the active DOUT.
  • Useful when you want a driver or operator to silence a buzzer (via, for example, pressing a button linked to a digital input).

Logic Operands & Activation

  • When using multiple sources, you can combine them with AND/OR logic.
  • For example, “Source 2 AND Source 3” must both be active, or “Source 2 OR Source 3” can trigger a condition.

Basic Operation

Enable the Scenario

  • Set the Scenario Priority to a value greater than 0 (1 = low priority, 2 = high priority). Zero disables the scenario.

Define Up to Three Sources

  • Source 1 is always evaluated.
  • Source 2 and Source 3 can be turned on/off and combined via AND/OR logic with the previous source.
  • Each source has:
    • IO Element (AVL ID)
    • Operand (OnEnter, OnExit, Is, etc.)
    • Low/High Threshold
    • Activation Delay (seconds)

Scenario Activation

  • The scenario becomes active if all selected sources meet their conditions simultaneously (based on the chosen logic AND/OR).
  • A record is generated if the scenario transitions from inactive → active, unless the operand is “Is” (which remains constantly active while the condition is true).

DOUT Behavior

  • If configured, the device toggles DOUT ON/OFF according to:
    • DOUT ON Duration (ms)
    • DOUT OFF Duration (ms)
    • DOUT Repeat Count (0 for infinite).

DOUT Deactivation

  • If a deactivation source is set, that IO can forcibly turn off the DOUT even if the scenario is still active.
  • The DOUT will remain off until the scenario becomes inactive (or conditions change).

Scenario Deactivation

  • If any source condition fails (e.g., threshold not met), the scenario goes back to inactive and a record is generated indicating this change (unless using “Is,” which ends immediately when condition fails).

Parameters

Scenario & Priority

  • Scenario AVL IDs:
    • Scenario 1 → AVL ID 358 (Priority config: 1035800)
    • Scenario 2 → AVL ID 359 (Priority config: 1035900)
    • Scenario 3 → AVL ID 360 (Priority config: 1036000)
  • Priority Values & Meaning
Value AVL Priority Scenario Enabled?
0 None No
1 Low Yes
2 High Yes

Source Configuration

  • Source (AVL ID) – Which IO to monitor (e.g., digital input, sensor reading).
  • Operand – “OnEnter,” “OnExit,” “Is,” etc.
  • Low/High Level – Numeric threshold range for the IO value.
  • Delay – Time in seconds the condition must stay valid (for “Is,” “OnEnter,” “OnExit”).
  • Active – For Source 2 and 3, whether to include them in the logic.
  • Logic – How Source 2 or 3 combines with the previous source: AND (0) or OR (1).

DOUT Configuration

  • DOUT Control – Which DOUT to activate (0 = none).
  • DOUT ON Duration (ms) – How long DOUT stays ON each cycle (0 or 100–5000 ms).
  • DOUT OFF Duration (ms) – How long DOUT stays OFF each cycle (0 or 100–5000 ms).
  • DOUT Repeat – Number of ON/OFF cycles (0 = infinite).

DOUT Deactivation

  • Source (AVL ID) – Which IO can force DOUT off.
    • Set the source to 0 to disable DOUT deactivation.
  • Operand – Condition on that IO (similar to source operand).
  • Low/High Level – Thresholds for that IO.

Example

Scenario Setup

  • Priority: 2 (High, scenario enabled)
  • Source 1 (AVL ID = 21, e.g., Speed):
    • Operand: OnEnter
    • Low: 0, High: 5 (speed range)
    • Delay: 3 s
  • DOUT Control:
    • DOUT = 1
    • ON Duration = 500 ms, OFF Duration = 500 ms, Repeat = 0 (infinite)

Activation

  • If the vehicle’s speed stays between 0 and 5 km/h for at least 3 seconds, the scenario becomes active.
  • The device generates an “active” event record.
  • OUT 1 starts toggling: ON for 500 ms, OFF for 500 ms.

Deactivation

  • If speed goes above 5 km/h or drops below 0 for even a moment, the scenario becomes inactive.
  • A “deactivated” event record is generated, and DOUT stops toggling.

Optional DOUT Deactivation

  • If configured, an extra input (e.g., driver-pressed button) could turn DOUT off instantly, even while the scenario remains active.


[[Category:{{{model}}} Configuration]]

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Template:FTX_Features&oldid=112017"