Secure vehicle disabling: Difference between revisions
No edit summary |
No edit summary |
||
| (18 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
==Introduction== | ==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. | |||
==Solution Description== | |||
SECO feature is available from firmware version '''03.28.02'''. | |||
Secure Engine Cut Off 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. | |||
==Solution | ==Solution Requirements== | ||
*The secure vehicle disabling solution is supported by '''any Teltonika FMB series tracker (excluding FMX6 series trackers) that has''' one or more '''digital output''' (DOUT) which in this scenario is used to control fuel pump of the car. | |||
*SIM card for data transmition to your server. | |||
*[[Automotive_Relay|Automotive Relay]] to cut off the fuel pump. | |||
*SECO functionality is only available with Teltonika FMB series GPS trackers starting with the firmware version '''03.28.02'''. | |||
*FOTA WEB for remote configuration of the device. | |||
==Installation== | |||
It is important to position the tracker so it would not be easy to locate. | |||
Additionally, please refer to [[FMB130_First_Start#Mounting_recommendations mounting recommendations|Mounting Recommendations]] for recommended mounting instructions. | |||
[[File:Wiring scheme.png|alt=|right|frameless|357x357px]] | |||
Although devices have high gain antennas it is important to mount devices with stickers on top and in metal-free space. The device should be firmly fixed to the surface or cables. Please make sure, that device is not fixed to heat emitting or moving parts. | |||
During installation please follow recommendations in order to avoid damaging device and vehicle: | During installation please follow recommendations in order to avoid damaging device and vehicle: | ||
*Wires should be connected while the module is not plugged in. | *Wires should be connected while the module is not plugged in. | ||
*Be sure that after the car computer falls asleep, power is still available on the chosen wire. Depending on the car, this may happen | *Be sure that after the car computer falls asleep, power is still available on the chosen wire. Depending on the car, this may happen within 5 to 30. | ||
*When the module is connected, be sure to measure the voltage again if it did not decrease. | *When the module is connected, be sure to measure the voltage again to see if it did not decrease. | ||
*The ground wire is connected to the vehicle frame or metal parts that are fixed to the frame. | *The ground wire is connected to the vehicle frame or metal parts that are fixed to the frame. | ||
| Line 68: | Line 69: | ||
*<span style="background:#05CC6F">102</span> – Sleep settings (0 – Disable, 1 – Gps sleep, 2 – Deep sleep, 3 – Online Deep sleep, 4 – Ultra sleep) | *<span style="background:#05CC6F">102</span> – Sleep settings (0 – Disable, 1 – Gps sleep, 2 – Deep sleep, 3 – Online Deep sleep, 4 – Ultra sleep) | ||
<br> | <br> | ||
<br> | <br> | ||
<br> | <br> | ||
| Line 81: | Line 80: | ||
<br> | <br> | ||
*<span style="background:#E18DE7">12250</span> – Scenario priority (0 - Disable, 1 - Low, 2 - High, 3 - Panic). | *<span style="background:#E18DE7">12250</span> – Scenario priority (0 - Disable, 1 - Low, 2 - High, 3 - Panic). | ||
*12251 – Eventual settings (0 – Disable, 1 – Enable), if disabled - scenario status value will be | *12251 – Eventual settings (0 – Disable, 1 – Enable), if disabled - scenario status value will be added at the end of each AVL record. | ||
*<span style="background:#24FFD4">12252</span> – Output Control (0 – None, 1 – DOUT1, 2 – DOUT2, 3 – DOUT3) | *<span style="background:#24FFD4">12252</span> – Output Control (0 – None, 1 – DOUT1, 2 – DOUT2, 3 – DOUT3) | ||
* 12254 - Speed (km/h). Digital output will be activated if vehicle speed consistently lower than configured during | * 12254 - Speed (km/h). Digital output will be activated if vehicle speed is consistently lower than configured during "Speed check period". | ||
* 12259 - Speed Pulse Scenario (km/h). Valid if "Output Pulse" feature enabled. Scenario will be activated if vehicle speed consistently lower than configured during | * 12259 - Speed Pulse Scenario (km/h). Valid if "Output Pulse" feature enabled. Scenario will be activated if vehicle speed is consistently lower than configured during "Speed check period". After activation digital output will be activated and disabled continuously until speed will be lower then configured in "Speed" field and longer then "Speed check period". | ||
*12255 - Speed check period (s). Time span during which vehicle speed must be lower than configured for output to activate. | *12255 - Speed check period (s). Time span during which vehicle speed must be lower than configured for output to activate. | ||
*12256 - Movement timeout (s). Accelerometer's instant movement timeout after which output will be | *12256 - Movement timeout (s). Accelerometer's instant movement timeout after which output will be activated (GNSS OFF). | ||
*12253 - Output Pulse (0 – Disable, 1 – Enable). Pulse scenario adds additional output control which helps to slow down vehicle before fully disabling fuel pump. | *12253 - Output Pulse (0 – Disable, 1 – Enable). Pulse scenario adds additional output control which helps to slow down vehicle before fully disabling fuel pump. | ||
*12257 – DOUT ON Duration (ms) | *12257 – DOUT ON Duration (ms) | ||
* 12258 – DOUT OFF Duration (ms) | * 12258 – DOUT OFF Duration (ms) | ||
*7377 | *7377 – Send SMS To | ||
*8377 – SMS text<br> | *8377 – SMS text<br> | ||
<br> | <br> | ||
| Line 107: | Line 100: | ||
==SECO SMS Commands== | ==SECO SMS Commands== | ||
Secure engine cut-off (SECO) functionality is available for device with at least one DOUT. For SECO functionality to work, DOUT must to be selected. SECO has DOUT control priority higher than immobilizer scenario. | Secure engine cut-off (SECO) functionality is available for device with at least one DOUT. For SECO functionality to work, DOUT must to be selected. SECO has DOUT control priority higher than immobilizer scenario. | ||
SECO scenario can only be enabled or disabled by SMS commands: | SECO scenario can only be enabled or disabled by SMS commands: | ||
*"secoon" - to activate | *"[[SMS/GPRS command - secoon|secoon]]" - to activate SECO functionality. | ||
*"[[SMS/GPRS command - secooff|secooff]]" - to disable SECO functionality. | |||
The structure of sending SMS commands: [[FMB130 SMS/GPRS Commands]] | The structure of sending SMS commands: [[FMB130 SMS/GPRS Commands]] | ||
| Line 123: | Line 113: | ||
=== 1. SMS responses=== | === 1. SMS responses=== | ||
To SMS command <code>secooff</code> device will give response: „Seco off received. DOUTX off“. | |||
To SMS command | To SMS command <code>secoon</code> response: | ||
#„Seco on received. Waiting for conditions“. | |||
#„Seco on received. DOUTX pulsing“. | |||
#„Seco on received. DOUTX on“. | |||
When response is not 3 all later SMS will be received | When response is not 3 all later SMS will be received. | ||
'''Example:''' SMS 1 received and pulse configured, then SMS 2 will be received when speed is lower than configured and SMS 3 will be received when speed reaches 0 km/h. | |||
'''Note:''' Sending commands to the device without DOUT will give response "SECO not available for this device". When DOUT is not selected in configuration response will be: "Error. no DOUT configured". | '''Note:''' Sending commands to the device without DOUT will give response "SECO not available for this device". When DOUT is not selected in configuration response will be: "Error. no DOUT configured". | ||
| Line 141: | Line 129: | ||
===2. SECO Pulse functionality=== | ===2. SECO Pulse functionality=== | ||
In case '''SECO pulse (12253)''' is enabled device will not activate DOUT immediately. | |||
'''GNSS fix present''': when speed is lower than the configured '''Speed Pulse Scenario (12259)''' for the configured amount of '''time (12255)''', the device will pulse DOUT until GNSS speed reaches configured '''speed (12254)''' then DOUT will stop pulsing and stay active (ON) until „secooff“ SMS is received. | |||
'''GNSS fix present''': when speed is lower than configured Speed Pulse Scenario (12259) for configured amount of time (12255), device will pulse DOUT until GNSS speed reaches configured speed (12254) then DOUT will stop pulsing and stay active (ON) until „secooff“ SMS is received. | |||
'''GNSS fix unavailable:''' wait until movement timeout (12256) is reached then DOUT will stay active until | '''GNSS fix unavailable:''' wait until '''movement timeout (12256)''' is reached then DOUT will stay active until <code>secooff</code> SMS is received. | ||
In case SECO pulse is disabled while pulsing, device will activate DOUT. | In case SECO pulse is disabled while pulsing, device will activate DOUT. | ||
| Line 153: | Line 139: | ||
===3. GNSS fix available=== | ===3. GNSS fix available=== | ||
After <code>secoon</code | |||
After | > SMS is received, command will be saved to the device memory and check vehicle speed. When '''speed (12254)''' is lower than configured for the configured amount of '''time (12255)''', device will activate configured '''DOUT'''. | ||
===4. GNSS fix unavailable=== | ===4. GNSS fix unavailable=== | ||
After <code>secoon</code> SMS is received, command will be saved to device memory and movement timeout. When movement '''timeout (12256)''' is reached, device will activate configured DOUT. | |||
After | |||
==Parsing information== | ==Parsing information== | ||
| Line 344: | Line 329: | ||
==Demonstration in platform== | ==Demonstration in platform== | ||
TAVL | ===TAVL=== | ||
Open '''TAVL''' → select '''client''' → select '''Street Map''' → select '''device''' → choose the '''date''' range → select '''advanced''' → select '''show''' → information will appear in the '''bottom left''' corner. | |||
[[File:Tavl Seco 1.png|alt=|frameless|1153x1153px]] | [[File:Tavl Seco 1.png|alt=|frameless|1153x1153px]] | ||
[[File:Tavl Seco 2.png|alt=|frameless|1153x1153px]] | [[File:Tavl Seco 2.png|alt=|frameless|1153x1153px]] | ||
===WIALON=== | |||
Open '''WIALON''' → select '''messages''' → select '''unit''' (select your device) → choose the '''date range''' → select '''message''' (data messages) → select '''execute'''. | |||
[[File:Wialon Seco 1.png|alt=|frameless|1153x1153px]] | [[File:Wialon Seco 1.png|alt=|frameless|1153x1153px]] | ||
| Line 361: | Line 344: | ||
<br> | <br> | ||
<br> | <br> | ||
[[Category: Usage scenarios]] | |||