Test-AC: Difference between revisions
Appearance
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
===<u> Introduction </u>=== | ===<u> Introduction </u>=== | ||
[[File:FTX SECO.png|right|500px]] | |||
The SECO scenario (Secure Engine Cut Off) is a static scenario module responsible for controlling a digital output (DOUT) to cut off the engine based on configurable speed and movement conditions. It is typically triggered by remote commands (SMS or GPRS) and is used for security or immobilization purposes. | The SECO scenario (Secure Engine Cut Off) is a static scenario module responsible for controlling a digital output (DOUT) to cut off the engine based on configurable speed and movement conditions. It is typically triggered by remote commands (SMS or GPRS) and is used for security or immobilization purposes. | ||
===<u>Prerequisites</u>=== | ===<u>Prerequisites</u>=== | ||
*At least one DOUT is available. | *At least one '''DOUT''' is available. | ||
*SECO functionality should have DOUT control priority higher than Immobilizer scenario | *'''SECO functionality''' should have DOUT control priority higher than '''Immobilizer''' scenario. | ||
===<u>How It Works</u>=== | ===<u>How It Works</u>=== | ||
Revision as of 14:05, 23 February 2026
SECO Scenario
Introduction

The SECO scenario (Secure Engine Cut Off) is a static scenario module responsible for controlling a digital output (DOUT) to cut off the engine based on configurable speed and movement conditions. 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
The SECO scenario supports three distinct engine cut-off modes, each designed for different operational requirements.
First Mode
- In the first mode, DOUT control starts when the vehicle speed goes below a configured speed threshold and remains below this threshold for a specified speed check period.
- In this configuration, the DOUT is activated instantly when the speed condition is met.
- If the speed check period timer is running and the vehicle speed increases above the configured speed threshold before the timer expires, the timer will be reset.
- Example:
- Speed threshold: 70 km/h
- Speed check period: 10 second
Second Mode
- The second mode requires a GNSS fix to be present before DOUT control begins.
- In this mode, 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.
- While pulsing is ongoing, when the vehicle speed drops below a configured speed threshold, the system switches from pulsing to steady DOUT control.
- If the speed check period timer is running and the vehicle speed increases above the configured speed pulse threshold before the timer expires, the timer will be reset.
- Example:
- Speed pulse threshold: 70 km/h
- Speed threshold: 40 km/h
- Speed check period: 10 seconds
- Pulsing enabled: Yes
Third Mode
- The third mode is used when a GNSS fix is not available, no vehicle movement is detected anymore, and the configured movement timeout has passed.
- 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, providing an additional layer of security.
- If the movement timeout has not been reached and movement is detected, the DOUT will not be activated, and the movement timeout will be reset.
- Example:
- Movement timeout: 20 seconds
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 | SECO scenario priority. | 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 | Eventual 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 | SECO output control. | 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 |