Jump to content
  • EN

Template:FTX Features: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
No edit summary
 
(57 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<!--
==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:
* Generate a record every '''1 minute''' when '''Home''' and '''Moving'''
* Generate a record every '''10 minutes''' when '''Roaming''' and '''Moving'''
=== <u>Prerequisites</u> ===
'''Connectivity'''
* The device must support GPRS (or cellular) connectivity to send data to a remote server. <br>
'''Network Mode Awareness'''
* The device should correctly identify whether it is in '''Home''' or '''Roaming''' mode.
'''Movement Detection'''
* 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> ===
'''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:
* '''Min Saved Records'''
**  The minimum number of coordinates (records) that must be accumulated before the device attempts to send data to the server.
* '''Send Period'''
**  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>
'''Note''': The device internally uses GMT+0 without daylight saving.<br>
'''Data Collection Methods'''
The device can collect records using one or more of the following methods '''simultaneously''':
'''Time-Based Data Acquisition (Min Period)'''
* Acquires a record each time a specified interval of time passes.
* Setting this to zero '''disables''' time-based acquisition.
'''Distance-Based Data Acquisition (Min Distance)'''
* Acquires a record when the device’s traveled distance (from the last recorded coordinate) exceeds a specified value (in meters).
* Setting this to zero '''disables''' distance-based acquisition.
'''Angle-Based Data Acquisition (Min Angle)'''
* Acquires a record when the angle difference between the last recorded coordinate and the current heading exceeds a defined threshold (in degrees).
* Setting this to zero disables angle-based acquisition.
'''Speed-Based Data Acquisition (Min Speed Delta)'''
* 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).
* Setting this to zero '''disables''' speed-based acquisition.
=== <u>Expected Behavior</u> ===
'''Record Collection'''
* The device continuously checks for any of the enabled conditions (time, distance, angle, speed).
* If any threshold is met (e.g., Min Period elapsed, Min Distance exceeded), a new record is stored in internal memory.
'''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==
==Private/Business Scenario==
=== <u>Overview</u> ===
=== <u>Overview</u> ===
Line 7: Line 114:


=== <u>Functionality</u> ===
=== <u>Functionality</u> ===
The Private/Business Mode works as follows:
The '''Private/Business Mode''' works as follows:
'''Mode Selection''':
'''Mode Selection''':
* When Private Mode is ON, the vehicle's location is not shared, and optionally, odometer tracking can be disabled.
* When '''Private Mode is ON''', the vehicle's location is '''not shared''', and optionally, odometer tracking can be '''disabled'''.
* When Private Mode is OFF (Business Mode ON), the device works as usual, sending all data to the server.
* When P'''rivate Mode is OFF''' (Business Mode ON), the device works as usual, sending all data to the server.
'''Triggering Mechanisms''':
'''Triggering Mechanisms''':
* Digital Inputs (DINs): A set of configurable digital inputs can trigger Private Mode when activated.
* '''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.
* '''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.
* '''Special Conditions''': Private Mode can also be activated/deactivated by events like '''towing, unplug detection, crash detection, or auto-geofencing'''.
'''GNSS Data Masking''':
'''GNSS Data Masking''':
* The system can mask GPS data in different ways when Private Mode is active:
* The system can '''mask GPS data''' in different ways when Private Mode is active:
** Option 1: No masking (data is still visible).
** '''Option 1''': No masking (data is still visible).
** Option 2: GNSS data is replaced with zeros.
** '''Option 2''': GNSS data is replaced with '''zeros'''.
** Option 3: GNSS data remains at the last known good position before Private Mode was enabled.
** '''Option 3''': GNSS data remains at the '''last known good position''' before Private Mode was enabled.
'''Odometer Control''':
'''Odometer Control''':
* When Private Mode is ON, odometer tracking can be disabled to prevent distance accumulation during personal use.
* When Private Mode is ON, odometer tracking can be '''disabled''' to prevent distance accumulation during personal use.
'''DOUT Control''':
'''DOUT Control''':
* The device can trigger an external output (DOUT) when switching modes (e.g., to activate an indicator light showing the current mode).
* 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''':
'''Daylight Saving Adjustments''':
* The system supports automatic daylight saving time adjustments, ensuring that the schedule remains accurate throughout the year.
* The system supports '''automatic daylight saving time adjustments''', ensuring that the schedule remains accurate throughout the year.


=== <u>Prerequisites</u> ===
=== <u>Prerequisites</u> ===
To ensure proper operation of the Private/Business Mode, the following conditions must be met:
To ensure proper operation of the '''Private/Business Mode''', the following conditions must be met:
1. Device Compatibility:
'''Device Compatibility''':
a. The tracking device must support Private/Business Mode functionality.
* The tracking device must support '''Private/Business Mode functionality'''.
b. The device should have digital inputs (DINs) or schedule configuration options enabled.
* The device should have '''digital inputs (DINs)''' or s'''chedule configuration options enabled'''.
2. Firmware & Configuration:
'''Firmware & Configuration''':
a. The device must run a firmware version that supports Private/Business Mode.
* The device must run a firmware version that supports '''Private/Business Mode'''.
b. The mode-switching triggers (DINs, schedule, or special conditions) must be properly configured in the device settings.
* The mode-switching triggers (DINs, schedule, or special conditions) must be '''properly configured''' in the device settings.
3. GNSS & IO Elements Setup:
'''GNSS & IO Elements Setup''':
a. If using GPS masking, ensure the appropriate masking option is selected.
* If using '''GPS masking''', ensure the appropriate masking option is selected.
b. If using odometer stop, confirm that it is enabled in the configuration.
* If using '''odometer stop''', confirm that it is '''enabled''' in the configuration.
4. Power & Connectivity:
'''Power & Connectivity''':
a. The device should be powered on and connected to receive trigger signals.
* The device should be '''powered on''' and '''connected''' to receive trigger signals.
b. If using a weekly schedule, ensure the system's time zone and daylight saving settings are correctly configured.
* If using a '''weekly schedule''', ensure the system's '''time zone and daylight saving settings''' are correctly configured.
5. Trigger Setup:
'''Trigger Setup''':
a. If using digital inputs (DINs) to switch modes, ensure the correct DINs are assigned in the configuration.
* If using '''digital inputs (DINs)''' to switch modes, ensure the correct DINs are assigned in the configuration.
b. If using a weekly schedule, configure the start and end times for business mode on each required day.
* If using a '''weekly schedule''', configure the start and end times for business mode on each required day.
 




Line 143: Line 249:
'''Incorrect Mounting''':
'''Incorrect Mounting''':
* '''IOAVL 1452 > 0''' → False mounting detected.
* '''IOAVL 1452 > 0''' → False mounting detected.
==Eye-Sensor activity monitoring scenario==
=== <u>Introduction</u> ===
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.
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.
=== <u>Functionality</u> ===
The '''Activity Monitoring Scenario''' operates as follows:
'''Detecting BLE Advertisements:'''
* The scenario listens for BLE advertisement signals from EYE Sensor devices.
* If a device is detected, it is added to the active monitoring list.
'''Monitoring Device Presence:'''
* The system continuously checks for '''appear/disappear events.'''
* If a device stops sending signals (disappears), the scenario updates the monitored device list accordingly.
'''Updating IO Elements:'''
* When a device is active, the scenario updates '''all IO elements''' provided by the EYE Sensor.
* Periodic records are generated to ensure real-time status updates.
'''Scenario Enable/Disable Option:'''
* While the scenario is part of the '''global configuration''', users have the option to '''enable or disable it manually.'''
* By default, the '''Activity Monitoring Scenario is always enabled.'''
=== <u>Prerequisites</u> ===
To ensure proper operation of the '''Activity Monitoring Scenario''', the following conditions must be met:
'''Device Compatibility:'''
* The scenario requires a '''Teltonika Telematics EYE Sensor''' with BLE functionality.
* The tracking device must support '''BLE scanning and advertisement processing.'''
'''Firmware & Configuration:'''
* The device must run a firmware version that supports '''Activity Monitoring'''.
* The scenario must be '''enabled in the device’s configuration settings''' (if not using the default setting).
'''BLE Signal Conditions:'''
* The EYE Sensor must be '''within range''' of the tracking device’s BLE receiver.
* BLE signal interference should be minimized to ensure '''consistent detection'''.
'''Power & Connectivity:'''
* The tracking device should be '''powered on''' and capable of processing BLE advertisements.
* A '''stable power supply''' is required to maintain continuous monitoring.
'''Data Collection & Logging:'''
* The device must be configured to '''log periodic records''' for accurate activity tracking.
* Ensure the system has sufficient '''storage capacity''' for storing sensor data.


==Eye-Sensor magnet detection scenario==
==Eye-Sensor magnet detection scenario==
Line 175: Line 323:
'''User-Controlled Activation''':
'''User-Controlled Activation''':
* The scenario is '''enabled by default''', but users can '''manually enable or disable''' it as needed.
* The scenario is '''enabled by default''', but users can '''manually enable or disable''' it as needed.


==Eye-Sensor Temperature/Humidity monitoring scenario==
==Eye-Sensor Temperature/Humidity monitoring scenario==
Line 185: Line 331:
To ensure the scenario functions correctly, the following conditions must be met:<br>
To ensure the scenario functions correctly, the following conditions must be met:<br>


'''BLE Support''' – The device must support BLE scanning to detect temperature and humidity sensors.<br>
'''BLE Support''' – The device must support '''BLE scanning''' to detect temperature and humidity sensors.<br>


'''Compatible BLE Sensors''' – The scenario works with BLE temperature and humidity sensors that broadcast their data.<br>
'''Compatible BLE Sensors''' – The scenario works with '''BLE temperature and humidity sensors''' that broadcast their data.<br>


'''BLE Event Handling''' – The device must process the following '''BLE events''':
'''BLE Event Handling''' – The device must process the following '''BLE events''':
Line 202: Line 348:
'''Device Detection''':
'''Device Detection''':
* When a BLE sensor is detected (ble.device_detected), the scenario adds it to the active monitoring list.
* When a BLE sensor is detected (ble.device_detected), the scenario adds it to the active monitoring list.
* It differentiates between newly detected sensors and those that are '''already being tracked'''.
* It differentiates between '''newly detected sensors''' and those that are '''already being tracked'''.
'''Data Monitoring & Logging''':
'''Data Monitoring & Logging''':
* The scenario continuously monitors temperature and humidity values.
* The scenario continuously monitors temperature and humidity values.
Line 232: Line 378:


Each Manual Geofence scenario includes the following settings:<br>
Each Manual Geofence scenario includes the following settings:<br>
'''Priority''': Enables or disables the scenario.<br>
'''Priority''': Enables or disables the scenario.<br>
'''Shape Type''':<br>
'''Shape Type''':<br>
* '''Circle''' – Requires center coordinates and radius.
* '''Circle''' – Requires center coordinates and radius.
Line 429: Line 577:


'''Instant Movement''':
'''Instant Movement''':
* Processes every IMU reading and updates an IO (ID = 303) whenever the movement state changes.
* 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.
* Relies on internal noise-level estimation to decide if the vehicle is truly moving or idle.
'''Delayed Movement''':
'''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.
* 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.
* Generates movement or idle events that can be used as ignition or movement sources.


Line 440: Line 588:
* The device must be equipped with an IMU module that is fully functional.
* The device must be equipped with an IMU module that is fully functional.
'''Firmware / Configuration Access'''
'''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).
* 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'''
'''Device Firmware Compatibility'''
* Ensure the firmware supports IMU-based movement detection. Always refer to release notes for any hardware or firmware requirements.
* Ensure the firmware supports IMU-based movement detection. Always refer to release notes for any hardware or firmware requirements.
Line 480: Line 628:


'''Example Configuration Screenshots'''
'''Example Configuration Screenshots'''
* '''Movement Source Selection''': accel-as-movement-source.png
* '''Movement Source Selection''':
* '''Delays Configuration''': accel-as-movement-params.png
[[File:FTX-accel-as-movement-source.png|600px]]
 
* '''Delays Configuration''':
[[File:FTX-accel-as-movement-params.png|800px]]


=== <u>Expected Behavior</u> ===
=== <u>Expected Behavior</u> ===


'''Instant Movement Scenario'''
'''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.
* 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.
* A noise threshold helps filter out minor vibrations, ensuring only genuine movement causes a state change.
'''Delayed Movement Scenario'''
'''Delayed Movement Scenario'''
* Relies on the IO (ID = 303) from the Instant 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.
* 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.
* 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'''
'''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.
* 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.
* 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'''
'''Record Generation & Logging'''
Line 517: Line 668:
* If output control is enabled, the device sets the output pin to '''high''', blocking the starter.
* 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).
* 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'''.
* 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'''
'''Authorized'''
* The vehicle starter is '''unblocked''', allowing the driver to start the vehicle.
* The vehicle starter is '''unblocked''', allowing the driver to start the vehicle.
Line 579: Line 730:


==Ignition ON counter==
==Ignition ON counter==
[[File:FTX Ignition ON counter.png|alt=|right|500px]]


=== <u>Introduction</u> ===
=== <u>Introduction</u> ===
Line 595: Line 747:
** A device restart is about to occur.
** A device restart is about to occur.
** The counter value is changed via configuration (e.g., a manual reset or preset adjustment).
** The counter value is changed via configuration (e.g., a manual reset or preset adjustment).
=== <u>Manual CAN</u> ===
When configuring CAN IO elements, each parameter (like priority, operand, CAN type, CAN ID, etc.) requires a unique '''configuration ID'''. These IDs follow specific formulas to ensure no overlap with other parameters in the system. This guide explains how to calculate them.
'''''Formula''':''<br>
Parameter_ID = 1,000,000 + (AVL_ID * 100) + OPTION Parameter_ID = 1,000,000 + (AVL_ID * 100) + OPTION
* '''1,000,000:''' Base offset for CAN-related parameters.
* '''AVL_ID:''' The CAN AVL IO element identifier (within certain allowed ranges).
* '''OPTION:''' A small integer offset indicating which setting is being adjusted (e.g., priority or operand).


=== <u>Valid AVL Ranges</u> ===
=== <u>Valid AVL Ranges</u> ===
Line 648: Line 788:
* 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.
* 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'''
'''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.
* 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'''
'''Plug In the Numbers'''
* Calculate step by step, ensuring you add the correct base offsets and multipliers.
* Calculate step by step, ensuring you add the correct base offsets and multipliers.
'''Configure Your Device'''  
'''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.
* 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.
==Custom scenarios==
=== <u>Introduction</u> ===
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 off a vehicle’s starter if certain conditions are met.
* '''Immobilizer-Style Control''' – Turn 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.
=== <u>Key Features</u> ===
'''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.
=== <u>How It Works: Flow Overview</u> ===
'''Enable the Scenario'''
* Set the '''Scenario Priority''' to a value '''greater than 0''' (1 = low priority, 2 = high priority). Zero disables the scenario.<br>
'''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'''Bold text''' (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).
=== <u>Configuration Parameters</u> ===
'''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'''
<table class="nd-othertables_2" style="width:80%; margin-bottom: 30px;">
    <tr>
        <th style="width:10%; text-align: left;">'''Value'''</th>
        <th style="width:10%; text-align: left;">'''AVL Priority'''</th>
        <th style="width:20%; text-align: left;">'''Scenario Enabled?'''</th>
        <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>
        <td style="text-align: left;">1</td>
        <td style="text-align: left;">Low</td>
        <td style="text-align: left;">Yes</td>
    </tr>
    <tr>
        <td style="text-align: left;">2</td>
        <td style="text-align: left;">High</td>
        <td style="text-align: left;">Yes</td>
    </tr>
</table>
'''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.
* '''Operand''' – Condition on that IO (similar to source operand).
* '''Low/High Level''' – Thresholds for that IO.
* Set the source to '''0''' to disable DOUT deactivation.
=== <u>Expected Behavior: Simple Example</u> ===
'''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.
* DOUT 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.
=== <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.


==Static navigation==
==Static navigation==
[[File:FTX Static navigation.png|right|500 px]]


=== <u>Introduction</u> ===
=== <u>Introduction</u> ===
Line 812: Line 812:
* 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.
 
<!--
==Fall Down Detection==
==Fall Down Detection==
[[File:FTX Fall Down Detection.png|right|500 px]]


=== <u>Introduction</u> ===
=== <u>Introduction</u> ===
Line 863: Line 864:
* 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.
* 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).
* 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==
==Crash detection==
Line 930: Line 934:
* '''Crash Trace''' finalizes with an additional record containing '''AVL ID 257''' for high-frequency accelerometer samples.
* '''Crash Trace''' finalizes with an additional record containing '''AVL ID 257''' for high-frequency accelerometer samples.


=Driving behaviour scenarios=


== Overspeeding ==
== Overspeeding ==
Line 1,148: Line 1,151:
* '''Lower fuel consumption'''
* '''Lower fuel consumption'''
* ️'''Encourage responsible driving habits'''
* ️'''Encourage responsible driving habits'''
==Identification scenario==
=== <u>Parameter Description</u> ===
'''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.
<u>Scenario functionality can be divided into 5 states:</u>
* '''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==
=== <u>Introduction</u> ===
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.
=== <u>Accelerometer Calibration Working Principle</u> ===
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:
* '''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.
* External interference affecting GNSS or accelerometer accuracy should be minimized.




Line 1,202: Line 1,311:


=Vehicle protection=
=Vehicle protection=
==Network jamming detection==
{{#if: {{FTX_Pin_Support List|model={{{model}}}|pin=1-Wire}} |
<!-- If model supports DOUT1, show picture with output control -->
== Immobilizer ==
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}}
[[File:Immobilizer TCT panel.png|right|500px]]
<!-- Model supports DOUT1 --> 
 
| [[File:FTX network jamming detection.png|alt=|right|500px]]
The Immobilizer feature provides an additional layer of vehicle security by requiring driver authorization after the ignition is turned on. It is designed to block the vehicle's starter circuit, preventing the engine from being started until an authorized identification element is presented.
<!-- Model doesn't support DOUT1 -->
 
| [[File:FTX network jamming detection without dout.png|alt=|right|500px]]
This functionality is essential for preventing vehicle theft and ensuring that only permitted individuals can operate a vehicle. By linking vehicle operation to a physical token, it significantly enhances security for fleet management, rental services, and any application where control over vehicle access is a priority.
 
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> ===
* 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).
* An iButton reader or a properly configured BLE sensor is required to detect the authorization element.
 
=== <u> Basic Operation </u> ===
The feature's logic is managed through three distinct states:
1. '''Not Authorized State:'''
* This is the default, idle state when the vehicle's ignition is OFF. The immobilizer is armed and waiting.
2. '''Waiting Authorization State:'''
* When the ignition is turned ON, the system transitions to this state.
* If a Digital Output is configured, it is immediately activated to control the relay and block the starter circuit.
* The device actively waits for an authorization element to be presented.
3. '''Authorized State:'''
* Once an ID is detected and confirmed to be authorized, the system transitions to the Authorized state.
* The configured Digital Output is deactivated, which unblocks the starter circuit and allows the vehicle to be started and driven.
* The driver remains authorized as long as the ignition stays ON.
4. '''De-authorization Process:'''
* 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.
 
 
=== <u> Parameters list </u>===
<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;"> Immobilizer </td>
<td style="vertical-align: middle; text-align: center;"> 11700 </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>
'''1 =''' Low priority Device makes an additional record with indication of event cause. </td>
</tr>
<tr>
 
<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;"> Selects the type of authorization element to be used. </td>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' No authorization selected. <br>
'''1 =''' 1-Wire authorization selected.
</td>
 
</tr>
<tr>
 
<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;"> 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>
Maximum value '''= 65535''' </td>
 
</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;"> 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: left;"> '''0 =''' Disabled
'''0-65535 =''' Enabled  </td>
 
</tr>
<tr>
 
<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;"> Sets duration which starts when ignition is turned on. When duration expires immobilizer is turned off, even if the user was not authenticated. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 1''' <br>
Maximum value '''= 65535''' </td>
 
</tr>
<tr>
 
<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;"> 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>
'''1 = DOUT1''' DOUT1 is enabled in this scenario. <br>
'''2 = DOUT2''' DOUT2 is enabled in this scenario. <br>
'''3 = DOUT3''' DOUT3 is enabled in this scenario. </td>
 
</tr>
 
</table>
 
=== <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.
}}
}}
=== <u>Introduction</u> ===


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. This feature is enabled by default in modems that support it.
== Network Jamming ==
[[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.
 
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. ). 
 
=== <u>Prerequisites and Important Settings </u> ===
* 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. 
 
=== <u> Basic operation </u> ===
* 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.
 
=== <u> Parameters list </u>===
<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;"> Network jamming detection </td>
<td style="vertical-align: middle; text-align: center;"> 1024900 <br> (249)</td>
<td style="vertical-align: middle; text-align: center;"> 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. </td>
<td style="vertical-align: middle; text-align: left;"> '''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. </td>
</tr>
<tr>
 
<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;"> Jamming - network signal disruption. Time until jamming reporting is the time between jamming being detected and the record creation. Value in seconds. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br>
Maximum value = '''65535''' <br>Default value = '''60''' </td>
 
</tr>
<tr>
 
<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;"> 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>
{{#if: {{FTX_Pin_Support List|model={{{model}}}|pin=DOUT1}} |
<tr>
 
<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;"> This Digital Output activation can be used to trigger measures to disrupt potential thieves using GSM signal jamming to steal your vehicle.<br>
Source of digital output (DOUT) for feature activation/deactivation.
</td>
<td style="vertical-align: middle; text-align: left;">
'''0''' '''= None''' DOUTs are disabled in this scenario. <br>
'''1 = DOUT1''' DOUT1 is enabled in this scenario. </td>


=== <u>Prerequisites</u> ===
</tr>  
<tr>


'''Modem Compatibility'''
<td style="vertical-align: middle; text-align: center;"> DOUT OFF duration (ms) </td>
* The jamming detection feature operates only with certain modems and firmware versions. Known compatible models include:
<td style="vertical-align: middle; text-align: center;"> 11302</td>
** '''EG915U-EU''' (from EG915UEUABR03A01M08_01.002.01.001)
<td style="vertical-align: middle; text-align: center;"> Duration for how long DOUT should be '''inactive'''. </td>
** '''EG915-LA''' (from EG915ULAABR03A01M08_01.001.01.001)
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br>
'''Scenario Enablement'''
Maximum value = '''5000''' <br>Default value = '''200''' </td>
* The modem has jamming detection enabled at all times.
* The device must be configured to create records upon detecting a jamming event.


=== <u>How It Works</u> ===
</tr>  
<tr>


'''Initial Jamming Detection'''
<td style="vertical-align: middle; text-align: center;"> DOUT ON duration (ms) </td>
* The modem continuously monitors the network. If jamming is detected, the timer for '''Jamming Detection Delay''' (e.g., 60 seconds) starts.
<td style="vertical-align: middle; text-align: center;"> 11301</td>
'''Jamming Started'''
<td style="vertical-align: middle; text-align: center;"> Duration for how long DOUT should be '''active'''. </td>
* If the detected jamming lasts for the entire delay period (e.g., 60 seconds), the device creates a '''High''' or '''Low''' priority record (depending on 1024900 setting) labeled '''“Jamming started.”'''
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0''' (supports zero value)<br>
* If configured for immediate reporting, the record is sent right away, bypassing periodic data acquisition intervals.
Maximum value = '''5000''' <br>Default value = '''200''' </td>
'''Jamming Ended'''
* As soon as jamming stops (after a “Jamming started” record was generated), the device creates a '''“Jamming ended”''' record.
* This record is typically sent immediately if the scenario’s priority level is set to '''High'''.
'''Monitoring Resumes'''
* The modem continues monitoring for further jamming events. If another jamming incident occurs, the same process repeats (steps 1–3).


</tr>
}}
</table>


==Unplug detection==
==Unplug detection==
Line 1,283: Line 1,559:




==Auto geofence==
== Auto Geofence ==
[[File:Auto Geofence TCT panel with DIN.png|right|500px]]
 
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.


[[File:FTX auto geofence.png|right|500 px]]
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.


=== <u>Introduction</u> ===
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> ===
* 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.
 
=== <u> Basic Operation </u> ===
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).
 
 
=== <u> Parameters list </u>===
<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;"> Auto geofence </td>
<td style="vertical-align: middle; text-align: center;"> 1017500 </td>
<td style="vertical-align: middle; text-align: center;"> Disables, or enables and sets priority for record generation. </td>
<td style="vertical-align: middle; text-align: left;"> '''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. </td>
 
</tr>
<tr>
 
<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;"> Defines when the event will be generated </td>
<td style="vertical-align: middle; text-align: left;"> '''0 =''' On exit <br>
'''1 =''' On enter <br>
'''2 =''' On both <br>
</td>
 
</tr>
<tr>
 
<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;"> Sets the duration in seconds for two conditions: <br>
1. '''In Wait State:''' how long the vehicle must be stationary with a GNSS fix before the geofence is armed. <br>
2. '''In Active State:''' how long the vehicle must be moving without a GNSS fix to trigger an alarm.
</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 0''' <br>
Maximum value '''= 65535''' </td>
 
</tr>
<tr>
 
<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;"> Sets the radius of the circular geofence in meters, measured from the vehicle's position when armed. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 0''' <br>
Maximum value '''= 1000000''' </td>
 
</tr>
{{#if: {{FTX_Pin_Support List|model={{{model}}}|pin=DIN1}} | 
<tr>


This scenario automatically creates a geozone around a vehicle’s last known location when certain conditions are met. It also detects when a vehicle is moving without a GNSS fix for a configured amount of time and records this as an event.
<td style="vertical-align: middle; text-align: center;"> Deactivate by </td>
<td style="vertical-align: middle; text-align: center;"> 20004 </td>
<td style="vertical-align: middle; text-align: center;"> Selects the source that will deactivate an armed geofence and return the system to the Wait State. </td>
<td style="vertical-align: middle; text-align: left;"> '''0 = Power Voltage:''' Deactivates if external voltage exceeds a predefined threshold.
'''1 = Digital Input 1:''' Deactivates if DIN1 becomes active. <br>
'''2 = Digital Input 2:''' Deactivates if DIN2 becomes active. <br>
'''3 = Digital Input 3:''' Deactivates if DIN3 becomes active. <br>
'''4 = iButton:''' Deactivates if an authorized iButton is presented.  
</td>


=== <u>Prerequisites</u> ===
</tr>  
}}
</table>


This scenario relies on several key parameters to function properly:
=== <u> Limitations, Edge Cases & Additional Notes  </u> ===
# '''Activation Timeout (s):''' Determines how long specific conditions must be met before creating a geozone. It depends on the current state:
* '''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).
# '''Wait State:''' The duration required to capture the vehicle’s last known location.
* '''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.
# '''Active State:''' The duration the vehicle must be moving without a GNSS fix before triggering an “On Exit” event.
* '''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).
# '''Geozone Radius (m):''' Defines the size of the geozone created after the activation timeout. The center of the geozone is based on the vehicle’s last known location.
# '''Deactivation Source:''' Specifies how the Auto Geofence scenario can be deactivated. Available options:
# '''Power Voltage:''' If external voltage exceeds 5250 mV. <!-- If model supports DIN1, then show --> {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN1}} |
# '''Digital Input:''' If configured digital input becomes active. }}
# '''iButton:''' If an authorized iButton is attached.


=== <u>How It Works</u> ===
== Manual Geofence ==
[[File:Manual Geofence - menu.png|right|500px]]
[[File:Manual Geofence - zone circle.png|right|150px]]
[[File:Manual Geofence - zone square.png|right|150px]]


According to configuration settings device will:
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.
# Detect when a vehicle is stationary with a valid GNSS fix and create a geozone at the last known location.
# Monitor movement without a GNSS fix and generate an exit event if the vehicle moves outside the geozone or moves for too long without GNSS.
# Automatically reset when a configured '''deactivation source''' (e.g., power voltage, digital input, or iButton) is activated.


=== <u>Scenario States</u> ===
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 Auto Geofence scenario operates in 2 states:
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.


==== 1. <u>Wait State</u> ====
=== <u>Prerequisites and Important Settings </u> ===
* In Manual Geofence square and circle shapes can be used for creating a geofence and have their own different parameters.


In this state, the scenario waits for specific conditions to be met before creating a geozone and moving to the Active State.
=== <u> Basic Operation </u> ===
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. (If "Event type" is configured On Exit|On Entrance|On Both)
* Speeding: Indicates whether the device is exceeding the speed limit while inside the geozone. (If "Speed limit" is configured)
When a state change occurs (entering/exiting the geozone or starting/stopping speeding), an event is recorded. The frame border prevents false exit detections.
Eventual record will contain these AVL IDs:
* 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:
** 0 - Exit event;
** 1 - Enter event.
* 157 - Speeding event. Is added to the record if a speeding event was captured. Possible values:
** 0 - Speeding stop event;
** 1 - Speeding start event.


'''Conditions for activation:'''
* GNSS fix is valid.
* Vehicle is not moving.


Once these conditions are met, the scenario starts the '''Activation Timeout''' countdown. If any condition is broken (e.g., movement is detected), the countdown resets.
=== <u> Parameters list </u>===
'''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.


'''After the timeout:'''
''Will be added soon''.
* A geozone is created at the vehicle’s last known location.
* If configured, an “On Enter” event is generated.
* The scenario transitions to '''Active State'''.


==== 2. <u>Active State</u> ====
=== <u> Geozone Parameter ID Calculation </u>===  
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:


Once in Active State, the scenario monitors for movement without a GNSS fix or movement outside the geozone.
''Will be added soon''.  


'''Exit conditions:'''
The formula for a parameter ID is:
* The configured '''deactivation source''' is triggered.
parameter_id = 900000 + (geozone_number – 1)*100 + id_offset
* The vehicle moves without a GNSS fix for the '''Active State timeout'''.
* The vehicle moves outside the geozone with a valid GNSS fix.


'''When an exit event is triggered:'''
Examples:
* If configured, an '''“On Exit” event''' is generated.
* Priority of Geozone 1:
* The scenario returns to '''Wait State'''.
900000 + (1 - 1) * 100 + 0 = 900000
* Speed limit threshold of Geozone 2:
900000 + (2 – 1) * 100 + 7 = 900107


==Towing detection==
==Towing detection==
Line 1,387: Line 1,754:
'''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=
== Fall Down Detection ==
[[File:Fall down detection - menu.png|right|500px]]
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.
=== <u>Prerequisites and Important Settings </u> ===
* All accelerometer-related features, including fall down detection depend on secure device mounting to function properly. See “Mounting recommendations” [link].
* 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.
* 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'''.
=== <u> Basic Operation </u> ===
* 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.
=== <u> Parameters list </u>===
<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;"> 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>
</tr>
<tr>
<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;"> 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>
'''1 =''' Enable  </td>
</tr>
<tr>
<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;"> Sets the angle difference, which should be detected between the base vector and the current vector in order to generate a fall down event. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''30'''<br>
Maximum value = '''180''' <br>Default value = '''30''' </td>
</tr>
<tr>
<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;"> 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. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br>
Maximum value = '''3600''' <br>Default value = '''3''' </td>
</tr>
<tr>
<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;"> The parameter defines under what condition (operand) the event will be generated. </td>
<td style="vertical-align: middle; text-align: left;"> '''0 = On exit''' Fall down event will be generated once the fall down event ends. <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>
</tr>
</table>
==Static navigation==
=== <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.
== Ignition ON counter ==
[[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.
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. 
=== <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.
* 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)'''.
=== <u> Basic Operation </u> ===
* 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.
=== <u> Parameters list </u>===
<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;"> Ignition ON counter </td>
<td style="vertical-align: middle; text-align: center;"> 1044900 <br> (449)</td>
<td style="vertical-align: middle; text-align: center;">
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).
</td>
<td style="vertical-align: middle; text-align: left;"> '''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. </td>
</tr>
<tr>
<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;"> Ignition on counter value to be used initially. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0''' <br>
Maximum value = '''4294967295''' <br> Default value = '''0'''
</td>
</tr>
</table>
=== <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.
* 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==
[[File:FTX Customscenarios.png|alt=|right|500px]]
=== <u>Introduction</u> ===
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 a vehicle’s starter if certain conditions are met.
* '''Immobilizer-Style Control''' – Turn 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.
=== <u>Key Features</u> ===
'''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.
=== <u>How It Works: Flow Overview</u> ===
'''Enable the Scenario'''
* Set the '''Scenario Priority''' to a value '''greater than 0''' (1 = low priority, 2 = high priority). Zero disables the scenario.<br>
'''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'''Bold text''' (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).
=== <u>Configuration Parameters</u> ===
'''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'''
<table class="nd-othertables_2" style="width:80%; margin-bottom: 30px;">
    <tr>
        <th style="width:10%; text-align: left;">'''Value'''</th>
        <th style="width:10%; text-align: left;">'''AVL Priority'''</th>
        <th style="width:20%; text-align: left;">'''Scenario Enabled?'''</th>
        <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>
        <td style="text-align: left;">1</td>
        <td style="text-align: left;">Low</td>
        <td style="text-align: left;">Yes</td>
    </tr>
    <tr>
        <td style="text-align: left;">2</td>
        <td style="text-align: left;">High</td>
        <td style="text-align: left;">Yes</td>
    </tr>
</table>
'''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.
* '''Operand''' – Condition on that IO (similar to source operand).
* '''Low/High Level''' – Thresholds for that IO.
* Set the source to '''0''' to disable DOUT deactivation.
=== <u>Expected Behavior: Simple Example</u> ===
'''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.
* DOUT 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.
=== <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
=Other features=
=Other features=

Latest revision as of 09:16, 19 November 2025


Driving behaviour

Crash detection

Introduction

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.

Prerequisites

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.

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.

How It Works

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

Introduction

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 of 2 km/h, 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

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

Introduction

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

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.

Trip Odometer I/O

  • The I/O Trip Odometer must be enabled for the device to log distance traveled during a trip.

GNSS Connectivity

  • Since Start Speed is tied to GPS speed, a functioning GNSS module is required for accurate speed measurements.

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.

How It Works

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’s 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

Introduction

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

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).

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: 4,294,967

How It Works

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

Introduction

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.

Prerequisites

Scenario Activation

  • Must be enabled via Telematics Configuration Tool (TCT).

Proper Threshold Configuration

  • Acceleration limits should be set according to driving policies.

GNSS & Sensor Calibration

  • 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.

How It Works

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.

Additional 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.

Conclusion

The Eco Driving scenario helps businesses monitor and reduce aggressive driving behaviors

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

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

Introduction

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 Working Principle

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:

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

Prerequisites

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.
  • External interference affecting GNSS or accelerometer accuracy should be minimized.


Excessive idling

Introduction

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 – That is used to detect if a vehicle is on or on.
  2. Movement source – That is 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' (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.


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

  • 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.

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 list

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

Introduction

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

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.

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.

How It Works

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

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).


Parameters 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

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 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.

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.

Prerequisites and Important Settings

  • In Manual Geofence square and circle shapes can be used for creating a geofence and have their own different parameters.

Basic Operation

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. (If "Event type" is configured On Exit|On Entrance|On Both)
  • Speeding: Indicates whether the device is exceeding the speed limit while inside the geozone. (If "Speed limit" is configured)

When a state change occurs (entering/exiting the geozone or starting/stopping speeding), an event is recorded. The frame border prevents false exit detections. Eventual record will contain these AVL IDs:

  • 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:
    • 0 - Exit event;
    • 1 - Enter event.
  • 157 - Speeding event. Is added to the record if a speeding event was captured. Possible values:
    • 0 - Speeding stop event;
    • 1 - Speeding start event.


Parameters list

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.

Geozone Parameter ID Calculation

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.

The formula for a parameter ID is: parameter_id = 900000 + (geozone_number – 1)*100 + id_offset

Examples:

  • Priority of Geozone 1:

900000 + (1 - 1) * 100 + 0 = 900000

  • Speed limit threshold of Geozone 2:

900000 + (2 – 1) * 100 + 7 = 900107

Towing detection

Introduction

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.

Prerequisites

To ensure proper operation, the following conditions must be met:

  1. Ignition Source – Used to detect whether the vehicle is turned ON or OFF.
  2. Movement Source – Used to determine if the vehicle is moving or stationary.
  3. Accelerometer Data – The device must have a working accelerometer to detect changes in orientation and movement.

How It Works

  • 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. See “Mounting recommendations” [link].
  • 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.
  • 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 list

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

Introduction

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.

How It Works

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 list

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.

Custom scenarios

Introduction

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 a vehicle’s starter if certain conditions are met.
  • Immobilizer-Style Control – Turn 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.

How It Works: Flow Overview

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 CountBold text (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).

Configuration 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.
  • Operand – Condition on that IO (similar to source operand).
  • Low/High Level – Thresholds for that IO.
  • Set the source to 0 to disable DOUT deactivation.

Expected Behavior: Simple 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.
  • DOUT 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.

Conclusion

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.

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.


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

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