Jump to content

Test-AC: Difference between revisions

From Teltonika Telematics Wiki
Tag: Manual revert
No edit summary
Line 5: Line 5:
[[File:FTX SECO.png|right|500px]]
[[File:FTX SECO.png|right|500px]]


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.
'''Secure Engine Cut Off (SECO)''' is a functionality that safely disables a vehicle’s engine based on predefined speed or movement conditions. It is typically activated remotely and used for security, immobilization, or theft prevention purposes.


===<u>Prerequisites</u>===
SECO enhances vehicle security by allowing the engine to be disabled under controlled conditions. It helps prevent theft by stopping unauthorized movement, supports fleet security through remote immobilization when suspicious activity occurs, and limits unauthorized usage by shutting down the engine when vehicles operate outside permitted times or areas.
*At least one '''DOUT''' is available.
*'''SECO functionality''' should have DOUT control priority higher than '''Immobilizer''' scenario.


===<u>How It Works</u>===
To safely slow down a vehicle after receiving the <code>secoon</code> command, the device waits for the vehicle speed to drop below the configured '''Speed pulse scenario (km/h)''' threshold. Once the speed remains below this threshold for the configured '''Speed check period''', the device starts pulsing the configured '''DOUT''' to toggle the relay connected to the fuel pump. This intermittently interrupts the fuel supply and gradually slows down the vehicle.
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'''
When the vehicle speed further decreases and reaches the configured '''Speed (km/h)''' threshold, the system activates the configured '''DOUT permanently''', fully interrupting the fuel supply and bringing the vehicle to a complete stop.


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.
DOUT control remains active until the <code>secoff</code> command is received.


The timer will be reset if the vehicle speed increases above the configured speed threshold.
===<u>Prerequisites and Important Settings</u>===
*The device must have at least one free DOUT that can be assigned to SECO functionality.
*For SECO functionality to work, DOUT must be selected. SECO has DOUT control priority higher than immobilizer scenario.
*'''IMOPORTANT:''' If the pulse parameter is disabled while pulsing is active, the DOUT will activate instantly.
*'''IMPORTANT:''' The SECO scenario must be controlled using SMS and GPRS commands, enabling remote activation and deactivation of the engine cut off functionality.


'''GNSS Available'''


This mode requires a GNSS fix to be present before DOUT control begins.  
===<u>Basic Operation</u>===
The SECO scenario supports the following engine cut off modes, each using different logic for controlling a digital output (DOUT) based on speed, movement, and data availability.


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.
====Speed Pulse====
The Speed pulse scenario (km/h) parameter defines the speed threshold at which pulsed DOUT control begins.
DOUT pulsing starts when:
*Vehicle speed drops below Speed pulse scenario (km/h)
*Speed remains below this threshold for the configured Speed check period


'''GNSS Unavailable'''
Once these conditions are met, the device begins toggling the configured DOUT according to the DOUT ON duration and DOUT OFF duration settings.


This mode is used when a GNSS fix is not available.
If the vehicle speed increases above the configured Speed pulse scenario threshold, the Speed check period timer is reset.


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.
====Safe Stop Threshold====
The '''Speed (km/h)''' parameter defines the speed at which the system switches from pulsed control to '''permanent DOUT activation'''.


'''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.
When the vehicle speed reaches or falls below this value, the configured '''DOUT''' is activated continuously, completely disabling the fuel pump and stopping the vehicle.
 
====GNSS Available====
 
When a GNSS fix is available, vehicle speed is determined using GNSS data and the SECO process follows the normal flow:
#Wait until speed drops below '''Speed pulse scenario (km/h)'''
#Start pulsing DOUT after the '''Speed check period'''
#Activate '''DOUT permanently''' when speed reaches '''Speed (km/h)'''
 
====GNSS Unavailable====
If a ''''GNSS fix''' is not available, vehicle speed cannot be reliably determined. In this case, the system uses a safety fallback mechanism.
 
After receiving the secoon command, the device waits until:
*No movement is detected
*The configured Movement timeout is reached
Once these conditions are met, the configured '''DOUT''' is activated.
 
This ensures that the fuel supply is not interrupted while the vehicle might still be moving at high speed.


=== <u> Parameters list </u>===  
=== <u> Parameters list </u>===  
Line 160: Line 183:
</table>
</table>
}}
}}
----
https://wiki.teltonika-gps.com/index.php?title=Template:FTX_Mobile_network
==Server settings== 
[[File:FTX server settings.png|right|500x800px]]
===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 [https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols]
----
'''New description added''' <br>
<span style="color:#00FF00;">'''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.</span>
*Tp use 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, refer to [[{{{model}}} Device status]].
*'''Note:''' Encryption is supported only for TCP/UDP data protocols. MQTT over TLS is not supported in the current implementation.
----
===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.
{| class="wikitable"
|+ 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=
[[File:FTX GNSS fuel counter.png|right|500px]]
===<u>Introduction</u>===
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.
===<u>How It Works</u>===
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.
=== <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;"> Scenario priority </td>
<td style="vertical-align: middle; text-align: center;"> 1001200<br>(12)</td>
<td style="vertical-align: middle; text-align: center;">Priority of how events are being sent to a server. For example, events with low priority are added to the periodical record, and events with high priority are sent immediately after they occur.</td>
<td style="vertical-align: middle; text-align: left;"> Disable = '''0''' <br> Low priority = '''1''' <br> High priority = '''2''' </td>
</tr> 
<tr>
<td style="vertical-align: middle; text-align: center;"> Average consumption </td>
<td style="vertical-align: middle; text-align: center;"> 11902 </td>
<td style="vertical-align: middle; text-align: center;">Average consumption presented in the technical documentation of the vehicle.</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0.0'''<br> Maximum value = '''50.0''' <br> Default value = '''0.0''' </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">
Fuel counter value</td>
<td style="vertical-align: middle; text-align: center;"> 11910 </td>
<td style="vertical-align: middle; text-align: center;">The initial fuel counter value in liters. Can be used to set the starting value or reset the current one.</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0.0'''<br> Maximum value = '''4294967.2''' <br> Default value = '''0.0''' </td>
</tr>
</table>

Revision as of 08:28, 20 March 2026

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

SECO Scenario

Introduction

Secure Engine Cut Off (SECO) is a functionality that safely disables a vehicle’s engine based on predefined speed or movement conditions. It is typically activated remotely and used for security, immobilization, or theft prevention purposes.

SECO enhances vehicle security by allowing the engine to be disabled under controlled conditions. It helps prevent theft by stopping unauthorized movement, supports fleet security through remote immobilization when suspicious activity occurs, and limits unauthorized usage by shutting down the engine when vehicles operate outside permitted times or areas.

To safely slow down a vehicle after receiving the secoon command, the device waits for the vehicle speed to drop below the configured Speed pulse scenario (km/h) threshold. Once the speed remains below this threshold for the configured Speed check period, the device starts pulsing the configured DOUT to toggle the relay connected to the fuel pump. This intermittently interrupts the fuel supply and gradually slows down the vehicle.

When the vehicle speed further decreases and reaches the configured Speed (km/h) threshold, the system activates the configured DOUT permanently, fully interrupting the fuel supply and bringing the vehicle to a complete stop.

DOUT control remains active until the secoff command is received.

Prerequisites and Important Settings

  • The device must have at least one free DOUT that can be assigned to SECO functionality.
  • For SECO functionality to work, DOUT must be selected. SECO has DOUT control priority higher than immobilizer scenario.
  • IMOPORTANT: If the pulse parameter is disabled while pulsing is active, the DOUT will activate instantly.
  • IMPORTANT: The SECO scenario must be controlled using SMS and GPRS commands, enabling remote activation and deactivation of the engine cut off functionality.


Basic Operation

The SECO scenario supports the following engine cut off modes, each using different logic for controlling a digital output (DOUT) based on speed, movement, and data availability.

Speed Pulse

The Speed pulse scenario (km/h) parameter defines the speed threshold at which pulsed DOUT control begins. DOUT pulsing starts when:

  • Vehicle speed drops below Speed pulse scenario (km/h)
  • Speed remains below this threshold for the configured Speed check period

Once these conditions are met, the device begins toggling the configured DOUT according to the DOUT ON duration and DOUT OFF duration settings.

If the vehicle speed increases above the configured Speed pulse scenario threshold, the Speed check period timer is reset.

Safe Stop Threshold

The Speed (km/h) parameter defines the speed at which the system switches from pulsed control to permanent DOUT activation.

When the vehicle speed reaches or falls below this value, the configured DOUT is activated continuously, completely disabling the fuel pump and stopping the vehicle.

GNSS Available

When a GNSS fix is available, vehicle speed is determined using GNSS data and the SECO process follows the normal flow:

  1. Wait until speed drops below Speed pulse scenario (km/h)
  2. Start pulsing DOUT after the Speed check period
  3. Activate DOUT permanently when speed reaches Speed (km/h)

GNSS Unavailable

If a 'GNSS fix is not available, vehicle speed cannot be reliably determined. In this case, the system uses a safety fallback mechanism.

After receiving the secoon command, the device waits until:

  • No movement is detected
  • The configured Movement timeout is reached

Once these conditions are met, the configured DOUT is activated.

This ensures that the fuel supply is not interrupted while the vehicle might still be moving at high speed.

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