Test-AC

https://wiki.teltonika-gps.com/view/Template:FTX_Features

SECO Scenario

Introduction

The purpose of Secure Engine Cut Off (SECO) is to bring a vehicle to a stop, in order to prevent unauthorized use. SECO disables the fuel pump, which would prevent the engine from continuing to run and stop the vehicle from being driven. For safety reasons, the system is designed to slow the vehicle down gradually in a controlled manner, ensuring that security measures do not compromise the driver’s or passengers’ safety. It is typically triggered by remote commands (SMS or GPRS) and is used for security or immobilization purposes.

Prerequisites

• At least one DOUT is available.
• SECO functionality should have DOUT control priority higher than Immobilizer scenario.

How It Works

Firstly, in order to safely slow down vehicle the systems toggles the relay, which is connected to fuel pump (GNSS Available). Secondly, at a safe speed, the system tuns on DOUT permanently in order to stop the vehicle (Speed Pulse). Last mode is activated in case no GNSS fix is available (GNSS Unavailable).

Speed Pulse

DOUT control starts when the vehicle speed goes below a configured speed threshold and remains below this threshold for a specified speed check period. As soon as that happens DOUT is activated.

The timer will be reset if the vehicle speed increases above the configured speed threshold.

GNSS Available

This mode requires a GNSS fix to be present before DOUT control begins.

DOUT pulsing starts when the vehicle speed drops below a configured speed pulse threshold and the speed remains below this threshold for a specified speed check period.

GNSS Unavailable

This mode is used when a GNSS fix is not available.

In this mode, the system initiates DOUT control only if the vehicle is stationary, location data is unavailable, and the movement timeout condition is met.

Note: If there is no GNSS fix available and “secoon” command is sent, the system waits for the movement timeout to be reached before activating the configured DOUT. This approach ensures that the vehicle is stationary prior to disabling the fuel supply.

Parameters list

PARAMETER NAME	PARAMETER ID (RELATED AVL ID)	DESCRIPTION	VALUES
SECO DOUT status	396	SECO DOUT status.	0 = SECO DOUT is OFF 1 = SECO DOUT is pulsing 2 = SECO DOUT is ON
Priority	1039600	Priority of how events are being sent to a server. For example, events with low priority are added to the periodical record, and events with high priority are sent immediately after they occur.	0 = SECO scenario is disabled 1 = SECO scenario is low 2 = SECO scenario is high
Speed	12254	Speed threshold at which the configured digital output (DOUT) will be activated.	Minimum value = 0 Maximum value = 255 Default value = 10
Speed pulse scenario	12259	Speed threshold at which the configured digital output (DOUT) will be toggled.	Minimum value = 0 Maximum value = 255 Default value = 10
Speed check period	12255	Time span during which speed must be lower than configured for output to activate (GNSS on).	Minimum value = 0 Maximum value = 65535 Default value = 10
Movement timeout	12256	Duration after which the DOUT will be activated if no movement is detected and GNSS is off.	Minimum value = 0 Maximum value = 65535 Default value = 30
Eventual records	1039604	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 = SECO status will be sent with both eventual and periodical records. 1 = SECO status will be sent only when the event happens (an eventual record).
Output control	12252	Digital output used for connection to fuel pump to gradually stop the vehicle.	0 = DOUT control is disabled 1 = DOUT1 is controlled 2 = DOUT2 is controlled 3 = DOUT3 is controlled 4 = DOUT4 is controlled
Output pulse	12253	Pulse functionality adds additional output control which helps to slow down vehicle before fully disabling fuel pump.	0 = Disabled 1 = Enabled
DOUT on duration	12257	Duration for how long DOUT should be active.	Minimum value = 10 Maximum value = 5000 Default value = 1000
DOUT off duration	12258	A value in milliseconds, for how long DOUT should be inactive.	Minimum value = 10 Maximum value = 5000 Default value = 1000

---

https://wiki.teltonika-gps.com/index.php?title=Template:FTX_Mobile_network

Server settings

Primary server settings

Domain

• Server or Domain address, either IP address or Domain can be written.

Port

• Server Port.

Data protocol

• TCP (Transmission control protocol) or UDP (User datagram protocol). Changing this parameter will alter how the device communicates. From the device side, TCP and UDP work almost the same, the only difference is that UDP doesn't need additional confirmation from the server side, that the data packet was received. TCP has that and uses more network data for the confirmation. The desired data transfer protocol can be selected through the configurator. For more information on the protocol differences of Teltonika devices, refer here [1]

---

New description added
Encryption

• TLS/DTLS are security protocols that protect information sent over a network by encrypting the data so only the intended recipient can read it. These Protocols help authenticate devices communicating with the server and ensure data integrity during transmission. TLS/DTLS encryption creates a secure, private connection so sensitive data can travel safely across networks.

• In order to utilize TLS/DTLS encryption, server certificates must be uploaded via Teltonika Configurator Tool (TCT) or FOTA Web using Upload user TLS certificate task. For more information please reference [[{{{model}}} Device status]].

• Note: Currently Encryption is supported only if TCP/UDP data protocol is used. MQTT + TLS is not supported in Firmware version 3.7.0 at this time.

---

Secondary server settings

Mode

• Backup - Records are sent to second server while main server is not available.
• Duplicate - records are sent to both servers (main and second), records are deleted from Flash storage only if both servers confirmed that the records were received from device.

Secondary server parameters

Parameter	Parameter ID	Values
Second server type	2010	0 - Disable, 1 - Backup, 2 - Duplicate
Secondary server IP or DNS address	2007	String
Secondary server port	2008	Integer
Secondary server protocol	2009	0 - TCP, 1 - UDP

https://wiki.teltonika-gps.com/view/Template:FTX_Features

GNSS Fuel Counter

Introduction

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

How It Works

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

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

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

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

Parameters list

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