Difference between revisions of "Custom Scenarios"

From Wiki Knowledge Base | Teltonika GPS
(Undo revision 101241 by Airidas.S (talk))
Tag: Undo
(2 intermediate revisions by the same user not shown)
Line 24: Line 24:
 
Below is a detailed explanation of configurable parameters for each scenario.
 
Below is a detailed explanation of configurable parameters for each scenario.
  
−
{| class="wikitable" style="text-align:left; width:100%;"
+
{| class="wikitable" style="text-align:center; width:100%;"
−
! Parameter ID !! Parameter Name !! Min Value !! Max Value !! Default Value !! Description
+
! Parameter ID !! Parameter Name !! Value Range !! Default Value !! Description
 
|-
 
|-
−
| 19100, 19130, 19160 || Output Control || 0 || 3 || 0 || Specifies the DOUT controlled by the scenario:
+
| 19100, 19130, 19160 || Output Control || 0–3 || 0 || Determines which DOUT is controlled:
 
* 0 – None
 
* 0 – None
 
* 1 – DOUT1
 
* 1 – DOUT1
Line 33: Line 33:
 
* 3 – DOUT3
 
* 3 – DOUT3
 
|-
 
|-
−
| 19101, 19131, 19161 || Priority || 0 || 3 || 0 || Sets the scenario priority:
+
| 19101, 19131, 19161 || Priority || 0–3 || 0 || Sets the priority level:
 
* 0 – None
 
* 0 – None
 
* 1 – Low
 
* 1 – Low
Line 39: Line 39:
 
* 3 – Panic
 
* 3 – Panic
 
|-
 
|-
−
| 19124, 19154, 19184 || Permanent Output Control || 0 || 1 || 0 || Enables continuous DOUT control as long as conditions are met.
+
| 19124, 19154, 19184 || Permanent Output Control || 0–1 || 0 || Keeps the DOUT ON while the scenario is active, ignoring ON/OFF durations.
 
|-
 
|-
−
| 19102, 19132, 19162 || DOUT ON Duration || 100 ms || 65,000,000 ms || 200 ms || Duration for which DOUT remains ON when the scenario is active.
+
| 19102, 19132, 19162 || DOUT ON Duration || 100–65,000,000 ms || 200 ms || Defines the duration DOUT remains ON when activated.
 
|-
 
|-
−
| 19103, 19133, 19163 || DOUT OFF Duration || 0 || 65,000,000 ms || 200 ms || Duration for which DOUT remains OFF. A value of 0 means the DOUT stays ON continuously.
+
| 19103, 19133, 19163 || DOUT OFF Duration || 0–65,000,000 ms || 200 ms || Defines the duration DOUT remains OFF for blinking behavior.
 
|-
 
|-
−
| 19105, 19135, 19165 || Source #1 || Device-specific || Device-specific || IO element ID || The primary I/O source for the trigger. Cannot be ignored.
+
| 19105, 19135, 19165 || Source || I/O Element ID || N/A || Specifies the I/O source to monitor (e.g., fuel level, ignition).
 
|-
 
|-
−
| 19110, 19140, 19170 || Source #2 || Device-specific || Device-specific || Ignored || The secondary I/O source. Can be ignored.
+
| 19106, 19136, 19166 || Operand || 0–6 || 0 || Determines the evaluation logic for source values:
−
|-
 
−
| 19116, 19146, 19176 || Source #3 || Device-specific || Device-specific || Ignored || The tertiary I/O source. Can be ignored.
 
−
|-
 
−
| 19106, 19136, 19166 || Operand || 0 || 6 || 0 || Defines the condition logic for the trigger:
 
 
* 0 – On Exit
 
* 0 – On Exit
 
* 1 – On Entrance
 
* 1 – On Entrance
Line 60: Line 56:
 
* 6 – Is
 
* 6 – Is
 
|-
 
|-
−
| 19107, 19137, 19167 || Low Level || Dynamic || Dynamic || 0 || Sets the lower threshold value for the source trigger.
+
| 19107, 19137, 19167 || Low Level || Dynamic || 0 || Sets the lower threshold for source trigger activation.
 
|-
 
|-
−
| 19108, 19138, 19168 || High Level || Dynamic || Dynamic || 0 || Sets the upper threshold value for the source trigger.
+
| 19108, 19138, 19168 || High Level || Dynamic || 0 || Sets the upper threshold for source trigger activation.
 
|-
 
|-
−
| 19109, 19139, 19169 || Activation Delay Timer || 0 s || 65,535 s || 0 || Time (in seconds) the condition must remain true for activation.
+
| 19109, 19139, 19169 || Activation Delay Timer || 0–65,535 s || 0 || Time the condition must be true before the trigger activates.
 
|-
 
|-
−
| 19115, 19145, 19175 || Logic || 0 || 1 || 1 || Determines trigger evaluation logic:
+
| 19115, 19145, 19175 || Logic || 0–1 || 1 || Determines how triggers are evaluated:
 
* 0 – OR (any trigger activates the scenario)
 
* 0 – OR (any trigger activates the scenario)
−
* 1 – AND (all triggers must be true to activate the scenario)
+
* 1 – AND (all triggers must be true to activate)
 
|}
 
|}
  
−
=== Configuration Process ===
+
=== Configuration Steps ===
−
 
+
1. **Define Output Control**:  
−
1. **Define Output Control**:
+
   - Select the DOUT to be controlled when the scenario is active.
−
   - Assign the DOUT (DOUT1, DOUT2, or DOUT3) to be controlled by the scenario.
+
2. **Set Triggers**:
−
 
+
   - Configure up to three sources, each with unique thresholds, operands, and delay timers.
−
2. **Configure Triggers**:
+
   - Sources must differ for each scenario.
−
   - Select up to three I/O sources (e.g., ignition, fuel level, temperature).
+
3. **Configure Timing**:
−
  - Define operands to specify logic (e.g., "On Entrance," "Is").
+
   - Set DOUT ON and OFF durations or enable Permanent Output Control for continuous activation.
−
   - Set Low and High threshold values for each source.
+
4. **Save Settings**:
−
  - Adjust the Activation Delay Timer for precise control.
+
   - Verify the configuration and save. The device evaluates all scenarios every second.
−
 
 
−
3. **Set Priority**:
 
−
   - Choose the priority level for the scenario. Higher-priority scenarios override lower-priority ones for the same DOUT.
 
−
 
 
−
4. **Adjust DOUT Control Settings**:
 
−
  - Configure DOUT ON/OFF durations or enable Permanent Output Control for continuous activation.
 
−
 
 
−
5. **Save Configuration**:
 
−
   - Verify all parameters and save the configuration. The device evaluates scenario conditions every second.
 
  
−
=== Example Use Cases ===
+
=== Operational Details ===
 +
- Scenarios are evaluated every second. When all triggers are true:
 +
  - The scenario activates, toggling the DOUT and optionally creating a record.
 +
- Deep sleep compatibility: Scenarios operate in low-power modes if sources support it.
 +
- Priority management ensures higher-priority scenarios override lower-priority ones for DOUT control.
  
−
- **Scenario 1**: Control a relay when fuel level drops below 10%.
+
=== Example Applications ===
−
- **Scenario 2**: Trigger a buzzer if RPM exceeds 3000 while ignition is ON.
+
- Activating an alarm if RPM exceeds a threshold while the ignition is on.
−
- **Scenario 3**: Activate an alarm when GSM signal strength drops below 20%.
+
- Triggering a relay when the fuel level drops below a critical point.
 +
- Enabling a buzzer for temperature out-of-range conditions.

Revision as of 16:40, 18 November 2024

Introduction to Custom Scenarios functionality

To meet the diverse and evolving needs of our clients, we have developed the Custom Scenarios feature. This solution allows users to define specific conditions using customizable parameters to trigger events or control a device’s digital outputs. By connecting the device to peripherals like alarms, buzzers, or relays, this functionality can notify drivers or perform targeted actions seamlessly.

The feature enables the device to operate autonomously based on predefined conditions, eliminating the need for constant monitoring of device status or complex backend integrations. With Custom Scenarios, any data the device can read becomes a potential input for controlling digital outputs, providing flexibility and efficiency.


Custom Scenarios functionality logic

Figure 1. “Custom Scenarios” functionality logic

The Custom Scenarios functionality enables configuration of up to three independent scenarios, each with up to three unique triggers. Triggers are defined using data from various I/O elements, such as: Fuel Level, Engine RPM, Seatbelt Status, DTC Faults, Movement Status, Ignition State, GSM Signal Level, 1-Wire/Bluetooth sensor temperature and etc. Each trigger is configured with specific logic operands (e.g., "On Entrance," "On Exit"), threshold values (Low and High levels), and an activation delay timer, which specifies how long a value must remain within the defined range before the trigger is activated.

When all triggers of a scenario evaluate as true, the scenario becomes active. This can generate a record (if configured) and control the digital output (DOUT) by toggling it on or off based on the active conditions. Additionally, if configured for continuous operation, the DOUT remains active as long as the conditions are met.

Key features include:

  • Support for dynamic trigger logic based on selected operands and conditions.
  • Autonomous device operation, even in low-power or deep-sleep modes, provided compatible I/O sources are used.
  • Adjustable ON/OFF durations or permanent output control, enabling versatile device behaviors such as blinking or continuous activation.
  • Custom Scenarios operate independently from the I/O menu, with priority management ensuring that higher-priority scenarios take precedence in controlling the DOUT when multiple scenarios are configured.


Custom Scenarios functionality configuration

Below is a detailed explanation of configurable parameters for each scenario.

Parameter ID Parameter Name Value Range Default Value Description
19100, 19130, 19160 Output Control 0–3 0 Determines which DOUT is controlled:
  • 0 – None
  • 1 – DOUT1
  • 2 – DOUT2
  • 3 – DOUT3
19101, 19131, 19161 Priority 0–3 0 Sets the priority level:
  • 0 – None
  • 1 – Low
  • 2 – High
  • 3 – Panic
19124, 19154, 19184 Permanent Output Control 0–1 0 Keeps the DOUT ON while the scenario is active, ignoring ON/OFF durations.
19102, 19132, 19162 DOUT ON Duration 100–65,000,000 ms 200 ms Defines the duration DOUT remains ON when activated.
19103, 19133, 19163 DOUT OFF Duration 0–65,000,000 ms 200 ms Defines the duration DOUT remains OFF for blinking behavior.
19105, 19135, 19165 Source I/O Element ID N/A Specifies the I/O source to monitor (e.g., fuel level, ignition).
19106, 19136, 19166 Operand 0–6 0 Determines the evaluation logic for source values:
  • 0 – On Exit
  • 1 – On Entrance
  • 2 – On Both
  • 3 – On Hysteresis
  • 4 – On Change
  • 5 – On Delta Change
  • 6 – Is
19107, 19137, 19167 Low Level Dynamic 0 Sets the lower threshold for source trigger activation.
19108, 19138, 19168 High Level Dynamic 0 Sets the upper threshold for source trigger activation.
19109, 19139, 19169 Activation Delay Timer 0–65,535 s 0 Time the condition must be true before the trigger activates.
19115, 19145, 19175 Logic 0–1 1 Determines how triggers are evaluated:
  • 0 – OR (any trigger activates the scenario)
  • 1 – AND (all triggers must be true to activate)

Configuration Steps

1. **Define Output Control**: 

  - Select the DOUT to be controlled when the scenario is active.

2. **Set Triggers**: 

  - Configure up to three sources, each with unique thresholds, operands, and delay timers.
  - Sources must differ for each scenario.

3. **Configure Timing**: 

  - Set DOUT ON and OFF durations or enable Permanent Output Control for continuous activation.

4. **Save Settings**: 

  - Verify the configuration and save. The device evaluates all scenarios every second.

Operational Details

- Scenarios are evaluated every second. When all triggers are true: 

 - The scenario activates, toggling the DOUT and optionally creating a record.

- Deep sleep compatibility: Scenarios operate in low-power modes if sources support it. - Priority management ensures higher-priority scenarios override lower-priority ones for DOUT control.

Example Applications

- Activating an alarm if RPM exceeds a threshold while the ignition is on. - Triggering a relay when the fuel level drops below a critical point. - Enabling a buzzer for temperature out-of-range conditions.

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Custom_Scenarios&oldid=101239"