Jump to content

Test-AC: Difference between revisions

From Teltonika Telematics Wiki
No edit summary
No edit summary
(14 intermediate revisions by the same user not shown)
Line 1: Line 1:
===Firmware versions===
https://wiki.teltonika-gps.com/view/Template:FTX_Features
=SECO Scenario=


===<u>Introduction</u>===
[[File:FTX SECO.png|right|500px]]
'''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 <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.
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 <code>secoff</code> command is received.
===<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.
===<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.
====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:
#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>===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<tr>
<th style="width:20%; vertical-align: middle; text-align: center;"> '''FIRMWARE VERSION''' </th>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:20%; vertical-align: middle; text-align: center;"> '''RELEASE DATE''' </th>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
<th style="width:60%; vertical-align: middle; text-align: center;"> '''CHANGES''' </th>
<th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<tr style="text-align: center; vertical-align: middle;">
<th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
<td style="vertical-align: middle">''' 03.01.01.rev.15'''</td>
</tr>
<td style="vertical-align: middle">2026.03.23</td>
<tr>
<td style="text-align: left; vertical-align: top">
 
'''General Stability / Functionality'''
<td style="vertical-align: middle; text-align: center;"> SECO DOUT status </td>
*Improved internal device watchdog mechanisms to ensure more stable long-term operation. 
<td style="vertical-align: middle; text-align: center;"> 396</td>
*Fixed inconsistent generation of periodic records so they are now created according  to configuration. 
<td style="vertical-align: middle; text-align: center;"> SECO DOUT status. </td>
*Fixed the record counter IO so that it increments correctly when new records are created and does not reset unexpectedly in specific configurations.
<td style="vertical-align: middle; text-align: left;">'''0''' = SECO DOUT is '''OFF''' <br> '''1''' = SECO DOUT is '''pulsing''' <br> '''2''' = SECO DOUT is '''ON''' </td>
*Fixed unnecessary daily activation of a specific event IO. The IO now triggers only on real events instead of once per day. 
 
*Improved GNSS calculation algorithms for more stable, precise and faster coordinate updates. 
</tr>
*Fixed issues where idling events were not recorded even when idling detection was configured. 
<tr>
*Improved movement detection algorithms for more precise event recording. 
 
*Fixed duplicate or missing “Trip End” status records. 
<td style="vertical-align: middle; text-align: center;"> Priority </td>
*Fixed DOUT1 behaviour in Geofence scenarios where a non-zero speed was required even when configuration did not require it. 
<td style="vertical-align: middle; text-align: center;"> 1039600 </td>
*Fixed unnecessary immobilizer status change records. 
<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>
*Fixed an issue where the immobilizer scenario could be bypassed under certain conditions and where immobilizer events were generated without values. 
<td style="vertical-align: middle; text-align: left;"> '''0''' = SECO scenario is '''disabled''' <br> '''1''' = SECO scenario is '''low''' <br> '''2''' = SECO scenario is '''high''' <br>
*Fixed incorrect behaviour where the immobilizer scenario was not enforced when no authorization list was configured. 
*Improved logic for DOUT control in immobilizer scenarios so DOUT states are handled consistently, including across sleep/wake transitions. 
*Fixed mismatches between the device-calculated odometer and tachograph  odometer. 
*Fixed issues where fuel data from certain liquid level sensors could be lost, causing incomplete fuel history. 
*Improved total distance and trip distance counting for more accurate mileage  tracking. 
*Included multiple minor internal stability and bug-fix improvements that collectively improve overall system robustness, logging, and performance. 
*Fixed an issue where the device did not enter Deep Sleep mode properly.
'''Connectivity & Server Communication'''
*Fixed an issue where the device did not establish a data connection if the APN field was left blank. 
*Improved modem and network handling, including better operator selection and reconnection behaviour, reducing unexpected data link issues. 
*Fixed behaviour where the device continuously contacted the NTP server when GNSS fix was unavailable. 
*Fixed an issue where incorrect NTP responses could lead to timestamps being set in the future. 
*Fixed a problem where the device could receive future timestamps when NITZ was used as the time synchronisation source. 
*Fixed an issue where the device did not send records to the configured duplicate server correctly. 
*Fixed failures to send records to the duplicate server in some TCP/UDP scenarios. 
*Fixed an issue where records were bundled into a single packet rather than being sent individually as expected. 
*Fixed delays in record transmission over UDP. 
*Fixed issues where the device could disconnect from the server after executing certain GPRS or configuration commands. 
*Fixed internal log download issues via over-the-air tools. 
*Fixed a situation where over-the-air firmware update tasks could remain stuck in “Pending” or “Executing” state.
*Fixed occasional failures of firmware updates performed via the configuration tool, reducing the chance of interrupted or failed local updates. 
*Fixed an issue where the device was not generating Iridium SBD records. 
*Improved RS232 data sending to the Iridium module to ensure that SBD payloads are delivered reliably and without truncation.  
'''Bluetooth / BLE'''
*Fixed cases where the device generated unnecessary beacon records in stop mode.  
*Fixed issues where advanced beacon packet length information was not generated correctly in advanced beacon mode.
*Fixed incorrect reading of custom BLE parameter values when the data size was less than three bytes.
'''MQTT'''
* Fixed incorrect packing of MQTT packets containing multiple JSON objects when sending to cloud platforms. 
* Fixed an issue where the device did not send data via MQTT to custom cloud endpoints in some configurations. 
* Fixed behaviour where long RS232 messages were not sent correctly via MQTT, which could cause truncation or loss when transmitted as JSON. 
* Improved long-term stability of MQTT JSON operation, increasing reliability for continuous cloud integrations and complex payloads. 
'''Tachograph, K-Line & Driver/Company Data'''
* Implemented separate internal instance IDs for tachograph IO elements and DDD file  downloading to avoid interference between live data and file download. 
* Fixed a problem where tachograph auto address selection did not work correctly. 
* Fixed an issue where the working tachograph address could change unexpectedly after firmware updates, causing DDD download failures. 
* Fixed errors where remote tachograph file download sessions could be interrupted or not start at all in certain conditions. 
* Fixed behaviour where the tachograph company card number continued to be reported even after the card was removed. 
* Fixed an issue where the tachograph Driver Name field was missing or incomplete in driver information data. 
* Improved character encoding for tachograph Driver Name, including extended and Nordic letters. 
* Fixed an issue where no data was received over K-Line, preventing tachograph and diagnostic data reception. 
* Improved K-Line detection and privacy mode handling, including explicit privacy status reporting where applicable. 
* Enhanced tachograph-related logging and error handling to make diagnostics clearer.
* Fixed transmission of vehicle and driver identification values (such as VIN, VRN and driver identification) so that accurate identification data is always sent.
'''FMS / Manual CAN / CAN / Eco Driving & Vehicle Data'''
* Fixed missing or incorrect reading of specific FMS parameters, including version-specific parameter sets. 
* Fixed fluctuating fuel levels when using FMS or CAN sources, improving fuel accuracy for both standard and EV FMS use cases. 
* Fixed issues where FMS-based speed was not being used correctly as the selected speed source. 
* Improved overall CAN stability so that tachograph CAN and FMS information is not lost due to CAN bus overflow. 
* Fixed incomplete or malformed responses to commands that start or stop Manual CAN (MCAN) transmissions, ensuring clear responses and reliable remote control. 
* Ensured that Manual CAN requests and commands are no longer executed when ignition is OFF. 
'''New Features'''
* NEW! Added support for storing and sending records from [[FMC650 System settings#Records Saving/Sending Without TS|RAM memory]]. recommended for rapid data sending i.e. data saving every second etc.
* NEW! Implemented a new feature called the “[[FMC650 LVCAN I/O,FMS IO and Tachograph data elements#Driver Working State Filters|one minute rule]]” for tachograph driving state, reducing unnecessary state toggling and improving driving/rest detection accuracy.
* NEW! [[FMC650 Thermograph#Apach|Apache Thermograph]].
* NEW! [[FMC650 TrailerCAN|Trailer CAN]] functionality. 
* NEW! Implemented [[FMB scanevfms|“scanevfms“]] command for diagnosing electric trucks, providing targeted EV CAN diagnostics. 
* NEW! Implemented “[[FMB can_info|can_info]]“ command that returns details of the CAN bus (baud rates, modes and other key parameters), aiding diagnostics.
* NEW! Updated the “[[FMB tachocheck|tachocheck“]] command to show more detailed information.
'''Configuration, Parameters & Tools'''
* Fixed an issue where a single setparam command could not change multiple parameters at once. 
* Fixed behaviour where the odometer command always returned a GNSS-based odometer value regardless of the configured odometer source. 
* Fixed cases where the device disconnected unnecessarily from the configurator. 
* Fixed an issue where the SIM PIN was not remembered after soft or hard reset.
</td>
</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Speed </td>
<td style="vertical-align: middle; text-align: center;"> 12254 </td>
<td style="vertical-align: middle; text-align: center;"> Speed threshold at which the configured digital output (DOUT) will be activated. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br> Maximum value = '''255''' <br> Default value = '''10''' </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;"> Speed pulse scenario </td>
<td style="vertical-align: middle; text-align: center;"> 12259 </td>
<td style="vertical-align: middle; text-align: center;">
Speed threshold at which the configured digital output (DOUT) will be toggled. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br> Maximum value = '''255''' <br>Default value = '''10''' </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">
Speed check period </td>
<td style="vertical-align: middle; text-align: center;"> 12255 </td>
<td style="vertical-align: middle; text-align: center;"> Time span during which speed must be lower than configured for output to activate (GNSS on). </td>
<td style="vertical-align: middle; text-align: left;">  Minimum value = '''0'''<br> Maximum value = '''65535''' <br>Default value = '''10''' </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">
Movement timeout</td>
<td style="vertical-align: middle; text-align: center;"> 12256 </td>
<td style="vertical-align: middle; text-align: center;"> Duration after which the DOUT will be activated if no movement is detected and GNSS is off. </td>
<td style="vertical-align: middle; text-align: left;">  Minimum value = '''0'''<br> Maximum value = '''65535''' <br>Default value = '''30''' </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">Eventual records</td>
<td style="vertical-align: middle; text-align: center;"> 1039604</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''' = SECO status will be sent with both eventual and periodical records. <br> '''1''' = SECO status will be sent only when the event happens (an eventual record).</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">Output control</td>
<td style="vertical-align: middle; text-align: center;">12252</td>
<td style="vertical-align: middle; text-align: center;">
Digital output used for connection to fuel pump to gradually stop the vehicle. </td>
<td style="vertical-align: middle; text-align: left;"> '''0''' = DOUT control is disabled <br> '''1''' = DOUT1 is controlled <br> '''2''' = DOUT2 is controlled <br> '''3''' = DOUT3 is controlled <br> '''4''' = DOUT4 is controlled</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">Output pulse</td>
<td style="vertical-align: middle; text-align: center;">12253</td>
<td style="vertical-align: middle; text-align: center;">Pulse functionality adds additional output control which helps to slow down vehicle before fully disabling fuel pump.</td>
<td style="vertical-align: middle; text-align: left;"> '''0''' = Disabled <br> '''1''' = Enabled </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">
DOUT on duration</td>
<td style="vertical-align: middle; text-align: center;">12257</td>
<td style="vertical-align: middle; text-align: center;"> Duration for how long DOUT should be active.</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''10'''<br> Maximum value = '''5000''' <br>Default value = '''1000''' </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">DOUT off duration</td>
<td style="vertical-align: middle; text-align: center;">12258</td>
<td style="vertical-align: middle; text-align: center;"> A value in milliseconds, for how long DOUT should be inactive. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''10'''<br> Maximum value = '''5000''' <br>Default value = '''1000''' </td>
</tr>
</table>
<!---For Template:FTX SMS/GPRS Commands--->
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}}{{FTX Pin Support List|model={{{model}}}|pin=DOUT2}}{{FTX Pin Support List|model={{{model}}}|pin=DOUT3}}
|
===SECO Commands===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:20%; vertical-align: middle; text-align: left;">COMMAND</th>
<th style="width:45%; vertical-align: middle; text-align: left;">DESCRIPTION</th>
<th style="width:35%; vertical-align: middle; text-align: left;">SYNTAX EXAMPLE</th>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">[[SMS/GPRS command - secooff|secooff]]</td>
<td style="vertical-align: middle; text-align: left;">Deactivate SECO scenario.</td>
<td style="vertical-align: middle; text-align: left;"><code>secooff</code></td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">[[SMS/GPRS command - secoon|secoon]]</td>
<td style="vertical-align: middle; text-align: left;">Activate SECO scenario.</td>
<td style="vertical-align: middle; text-align: left;"><code>secoon</code></td>
</tr>
</tr>
</table>
}}

Revision as of 09:29, 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