Jump to content
  • EN

Test-AC: Difference between revisions

From Teltonika Telematics Wiki
← Older editNewer edit →
VisualWikitext
GTPGTM-11768 - draft
No edit summary
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Introduction==
https://wiki.teltonika-gps.com/view/Template:FTX_Features
=SECO Scenario=


With a professional device lineup, telltale information (dashboard indicators) from heavy-duty vehicles can be read remotely to identify a variety of issues. New feature of Diagnostic Trouble Code (DTC) reading will help to narrow down the specific faults happening in vehicles.  
===<u>Introduction</u>===
[[File:FTX SECO.png|right|500px]]


With {{{model}}} you can read 2 types of DTC messages based on J1939 protocol:
'''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.


*DM1 – Communicates currently present faults
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.
*DM2 – Reports stored faults


{{{model}}} is able to read DM codes and pass them to the server in IO element. When active DM1 or DM2 messages appear on CAN line it is broadcasted very often – {{{model}}} device saves the codes into the internal memory and does not flood the server with irrelevant information – only new DTC codes are sent to the server.
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.


==Functionality Description==
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.


This functionality is available from Firmware version '''03.01.02.rev.06''' or higher.
DOUT control remains active until the <code>secoff</code> command is received.


For proper functionality, the device requires ignition to be active. Source of ignition and voltage level can be selected from '''System''' tab.
===<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.


Ignition has to be active for at least 14 sec to start generating the DTC list. If ignition is turned off, the device will clean all DM1 and DM2 codes and functionality will not be working.


[[File:DTC_Ignition.png]]
===<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.


After the device is connected to the Configurator, there will be '''DM1 / DM2''' tab made available. There is a configurable DM1 / DM2 Data source parameter. This parameter selects the CAN source based on which device will parse DM data from. Based on selected data source, device will also call a request for DTCs.
====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


'''Note:''' The functionality is completely separated from the FMS source.
Once these conditions are met, the device begins toggling the configured DOUT according to the DOUT ON duration and DOUT OFF duration settings.


[[File:DTC Data source selection.png]]
If the vehicle speed increases above the configured Speed pulse scenario threshold, the Speed check period timer is reset.


*NONE – Device will not use any CAN as data source
====Safe Stop Threshold====
*CAN1 – Device will use CAN1 as data source
The '''Speed (km/h)''' parameter defines the speed at which the system switches from pulsed control to '''permanent DOUT activation'''.
*CAN2 – Device will use CAN2 as data source
*BOTH – Device will use CAN1 and CAN2 as data source


Bellow '''Data source''' parameters there is a list of configurable IOs
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.


[[File:DTC Configurable IOs.png]]
====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)'''


„DTC DM1“ and “DTC DM2“ shows the last DTC that has been detected. „Active DM1 List“ and „Active DM2 List“ provides a list of all active DTCs for a given source.
====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.


Example of generating DM1 / DM2 list: To register DM1 code, it is required to send a command using (pgn 0xFEFA). Device will first check if such DTC code exist in the system (MCUID and CAN Source has to be unique for each DTC). Otherwise, DTC will be rejected.
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.


[[File:DTC Configurator outputs.png]]
This ensures that the fuel supply is not interrupted while the vehicle might still be moving at high speed.


<span style="color:green;">9D000301:<span style="color:blue;">01:<span style="color:red;">01
=== <u> Parameters list </u>===
*<span style="color:green;">9D000301</span> – DTC in hexadecimal format
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
*<span style="color:blue;">01</span> – MCU source that reported the DTC
<tr>
*<span style="color:red;">01</span> – Device CAN source used (00 - CAN1, 01 - CAN2)
<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>


<span style="color:green;">9D000302:<span style="color:blue;">02:<span style="color:red;">01
<td style="vertical-align: middle; text-align: center;"> SECO DOUT status </td>
*<span style="color:green;">9D000302</span> – DTC in hexadecimal format
<td style="vertical-align: middle; text-align: center;"> 396</td>
*<span style="color:blue;">02</span> – MCU source that reported the DTC
<td style="vertical-align: middle; text-align: center;"> SECO DOUT status. </td>
*<span style="color:red;">01</span> – Device CAN source used (00 - CAN1, 01 - CAN2)
<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>


Based on configured „Priority“, „Event Only“ and „Operand“ device will add this parameter to record.
</tr>
<tr>


[[File:DTC Terminal logs.png]]
<td style="vertical-align: middle; text-align: center;"> Priority </td>
<td style="vertical-align: middle; text-align: center;"> 1039600 </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;"> '''0''' = SECO  scenario is '''disabled''' <br> '''1''' = SECO scenario is '''low''' <br> '''2''' = SECO scenario is '''high''' <br>
</td>


To remove one of the DTC from DM1 list, DM2 code (pgn 0xFEFB) is required. Device will check if the sent DTC code exists in the system (MCUID and CAN Source has to be unique for each DTC). If sent DTC does not exist in the system, it will be rejected.
</tr>
<tr>


Based on previous example, sending DTC 9D000301 with MCUID 01 on CAN2, device remove this DTC from the system, as the result, this DTC is removed from „Active DM1 List“ and added to the „Active DM2 List“.
<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>


[[File:DTC Configurator outputs 2.png]]
</tr>
<tr>


Log example:
<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>


[[File:DTC Terminal logs 2.png]]
</tr>
<tr>


That DTCs will be added to record and would be accessible on server. Data on server need to be converted from HEX to ASCII.
<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>


[[File:DTC Outputs from server.png]]
</tr>
<tr>


'''39443030303330323A30323A30313B''' -> (after conversion from hex to ANSCII) '''9D000302:02:01''';
<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>


'''39443030303330313A30313A30313B''' -> (after conversion from hex to ANSCII) '''9D000301:01:01''';
</tr>
<tr>


==Functionality Block Diagram==
<td style="vertical-align: middle; text-align: center;">Eventual records</td>
Graphic representation of '''DM1''' and '''DM2''' functionality:
<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>


[[File:DTC Functionality blok diagram.png]]
</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>


==DM1 Lamp Status and Flash Signals==
</tr>
<tr>


The '''DM1 (Diagnostic Message 1)''' in the '''J1939''' protocol reports active '''Diagnostic Trouble Codes (DTCs)''' and controls vehicle warning indicators. It defines the behavior of the '''Malfunction Indicator Lamp (MIL)''' and other warning lamps, which can be off, on solid, or flashing, depending on the severity and priority of detected faults. Flashing typically signals a more urgent or severe condition, while a solid light indicates an active but less critical issue.
<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>


The first byte represents the status of four indicator lamps:
</tr>
<tr>


*'''PL (Protect Lamp)''' - DTC's indicate non-electronic subsystem issue.
<td style="vertical-align: middle; text-align: center;">
*'''AWL(Amber Warning Light)''' - DTC's indicate a non-critical issue that does not warrant stopping the vehicle.
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>


*'''RSL(Red Stop Lamp)''' -  DTC's indicate a critical issue that warrants stopping the vehicle immediately.
</tr>
<tr>


*'''MIL(Malfunction Indicator Lamp)''' - At least one DTC indicates emissions related issue.
<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>


Each lamp is encoded using 2 bits, allowing four possible states: '''off, on, slow flash, and fast flash'''. This compact encoding means all lamp states are conveyed within a single byte, with each pair of bits mapped to a specific lamp in a fixed order. These lamp states directly inform the operator about the severity and urgency of active faults.
</tr>
</table>


DM1 encodes warning lamp information in its first 2 bytes, combining both lamp status  and flash behavior. Each lamp is represented by two 2-bit fields—one in byte 1 (status) and one in byte 2 (flash).
<!---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}}
To decode, split each byte into 2-bit segments and map each pair to its corresponding lamp. The final behavior is determined by combining status and flash (e.g., ON + fast flash = rapidly blinking warning).
|
 
===SECO Commands===
==Global and Manufacturer SPN Codes==
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
 
<tr>
===Global-Level SPN codes===
<th style="width:20%; vertical-align: middle; text-align: left;">COMMAND</th>
 
<th style="width:45%; vertical-align: middle; text-align: left;">DESCRIPTION</th>
Standard codes are defined by the SAE J1939 standards and are recognized across all compliant vehicles and equipment. The SPNs for these codes fall within the range of '''1 to 24,324''' representing widely used parameters such as engine speed, coolant temperature, or oil pressure. FMI values are standardized, describing specific failure patterns such as high voltage, circuit open, or out-of-range conditions.
<th style="width:35%; vertical-align: middle; text-align: left;">SYNTAX EXAMPLE</th>
 
</tr>
Because they are standardized, these codes are universally interpretable by any compliant diagnostic tool without requiring manufacturer-specific references.
<tr>
 
<td style="vertical-align: middle; text-align: left;">[[SMS/GPRS command - secooff|secooff]]</td>
===Manufacturer-Level SPN codes===
<td style="vertical-align: middle; text-align: left;">Deactivate SECO scenario.</td>
 
<td style="vertical-align: middle; text-align: left;"><code>secooff</code></td>
Manufacturer-level or proprietary codes are reserved for OEM-specific faults that are not defined in the J1939 standard. These allow manufacturers to monitor unique components, systems, or operational conditions that are specific to their equipment.
</tr>
 
<tr>
The SPNs for proprietary codes typically occupy the high end of the 19-bit field, ranging from '''516,096 to 524,287'''. FMI values may be standard or custom, but the meaning of the SPN is defined by the manufacturer. Accurate interpretation requires access to OEM documentation, as these codes are not universally defined or interpretable.
<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>
==DM1/DM2 Message Structure==
<td style="vertical-align: middle; text-align: left;"><code>secoon</code></td>
 
</tr>
Each DM1/DM2 message is transmitted using the J1939 transport protocol when needed (multi-packet if the data exceeds 8 bytes), but can also fit within a single CAN frame when only one DTC is present. The message begins with a lamp status byte, followed by zero or more DTC entries, each occupying exactly 4 bytes.
</table>
 
}}
 
 
Following the lamp status byte, the message contains one or more Diagnostic Trouble Codes (DTCs). Each DTC is encoded in a 4-byte structure that combines several fields into a compact binary format. The first 19 bits represent the Suspect Parameter Number (SPN), which identifies the specific parameter or component that is faulty. This value is split across the first three bytes in a non-linear way, requiring bit-level extraction rather than simple byte parsing.
 
The next 5 bits define the Failure Mode Identifier (FMI), which describes how the failure manifests (for example, data out of range, voltage too high, or signal erratic). Together, the SPN and FMI uniquely describe the nature of the fault.
 
After the FMI, a single bit is used for the SPN Conversion Method (CM). In modern systems, this bit is almost always set to 0, indicating the standard encoding method is used. A value of 1 indicates an alternative legacy encoding, which is rarely encountered but must still be handled correctly in robust implementations.
 
The final 7 bits of the 4-byte DTC structure represent the Occurrence Count (OC). This value indicates how many times the fault has been detected. It is typically capped at 127 and provides useful insight into whether a fault is intermittent or persistent.
 
When multiple DTCs are present, they are simply appended sequentially after the lamp status byte, each occupying 4 bytes. There is no explicit delimiter between DTCs; instead, the total message length determines how many are included. In multi-packet transmissions, this sequence continues seamlessly across transport protocol frames.
 
Practical Interpretation and DM1 vs DM2 Context
 
From an implementation perspective, decoding DM1 and DM2 messages requires careful bit extraction and reconstruction of the SPN, FMI, CM, and OC fields from each 4-byte DTC block. The lamp status byte must be interpreted separately before processing the DTC list.
 
The practical difference between DM1 and DM2 lies not in structure but in semantics. DM1 messages are typically broadcast periodically (for example, once per second) whenever active faults exist, making them essential for real-time monitoring and dashboards. In contrast, DM2 messages are only transmitted upon request and provide access to historical fault data that is no longer active but still stored in the ECU memory.
 
An important implementation detail is that DM1 messages may contain no DTCs, in which case only the lamp status byte is transmitted. This indicates that no active faults are present, and all lamps are typically off. However, the system must still correctly interpret this as a valid message rather than an error condition.
 
Another subtle but important aspect is that multiple ECUs on the same network can transmit their own DM1 messages independently. Each message is identified by its source address, meaning a complete diagnostic picture requires aggregating DM1 data across all nodes on the network.
 
In summary, the DM1/DM2 message structure is compact but highly information-dense. A single byte conveys overall system warning states, while each 4-byte DTC block encodes a complete fault description including what failed, how it failed, and how often it has occurred. Proper decoding requires precise bit-level handling, but once implemented, it provides a standardized and scalable way to monitor and diagnose vehicle systems across the entire J1939 network.

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


Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Test-AC&oldid=112021"