Changes

no edit summary
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:center; width:100%;"
+
{| class="wikitable" style="text-align:left; width:100%;"
! Parameter ID !! Parameter Name !! Value Range !! Default Value !! Description
+
! Parameter ID !! Parameter Name !! Min Value !! Max Value !! Default Value !! Description
 
|-
 
|-
| 19100, 19130, 19160 || Output Control || 0–3 || 0 || Determines which DOUT is controlled:
+
| 19100, 19130, 19160 || Output Control || 0 || 3 || 0 || Specifies the DOUT controlled by the scenario:
 
* 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 priority level:
+
| 19101, 19131, 19161 || Priority || 0 || 3 || 0 || Sets the scenario priority:
 
* 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 || Keeps the DOUT ON while the scenario is active, ignoring ON/OFF durations.
+
| 19124, 19154, 19184 || Permanent Output Control || 0 || 1 || 0 || Enables continuous DOUT control as long as conditions are met.
 
|-
 
|-
| 19102, 19132, 19162 || DOUT ON Duration || 100–65,000,000 ms || 200 ms || Defines the duration DOUT remains ON when activated.
+
| 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.
 
|-
 
|-
| 19103, 19133, 19163 || DOUT OFF Duration || 0–65,000,000 ms || 200 ms || Defines the duration DOUT remains OFF for blinking behavior.
+
| 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.
 
|-
 
|-
| 19105, 19135, 19165 || Source || I/O Element ID || N/A || Specifies the I/O source to monitor (e.g., fuel level, ignition).
+
| 19105, 19135, 19165 || Source #1 || Device-specific || Device-specific || IO element ID || The primary I/O source for the trigger. Cannot be ignored.
 
|-
 
|-
| 19106, 19136, 19166 || Operand || 0–6 || 0 || Determines the evaluation logic for source values:
+
| 19110, 19140, 19170 || Source #2 || Device-specific || Device-specific || Ignored || The secondary I/O source. Can be ignored.
 +
|-
 +
| 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 56: Line 60:  
* 6 – Is
 
* 6 – Is
 
|-
 
|-
| 19107, 19137, 19167 || Low Level || Dynamic || 0 || Sets the lower threshold for source trigger activation.
+
| 19107, 19137, 19167 || Low Level || Dynamic || Dynamic || 0 || Sets the lower threshold value for the source trigger.
 
|-
 
|-
| 19108, 19138, 19168 || High Level || Dynamic || 0 || Sets the upper threshold for source trigger activation.
+
| 19108, 19138, 19168 || High Level || Dynamic || Dynamic || 0 || Sets the upper threshold value for the source trigger.
 
|-
 
|-
| 19109, 19139, 19169 || Activation Delay Timer || 0–65,535 s || 0 || Time the condition must be true before the trigger activates.
+
| 19109, 19139, 19169 || Activation Delay Timer || 0 s || 65,535 s || 0 || Time (in seconds) the condition must remain true for activation.
 
|-
 
|-
| 19115, 19145, 19175 || Logic || 0–1 || 1 || Determines how triggers are evaluated:
+
| 19115, 19145, 19175 || Logic || 0 || 1 || 1 || Determines trigger evaluation logic:
 
* 0 – OR (any trigger activates the scenario)
 
* 0 – OR (any trigger activates the scenario)
* 1 – AND (all triggers must be true to activate)
+
* 1 – AND (all triggers must be true to activate the scenario)
 
|}
 
|}
   −
=== Configuration Steps ===
+
=== Configuration Process ===
1. **Define Output Control**:  
+
 
   - Select the DOUT to be controlled when the scenario is active.
+
1. **Define Output Control**:
2. **Set Triggers**:
+
   - Assign the DOUT (DOUT1, DOUT2, or DOUT3) to be controlled by the scenario.
   - Configure up to three sources, each with unique thresholds, operands, and delay timers.
+
 
   - Sources must differ for each scenario.
+
2. **Configure Triggers**:
3. **Configure Timing**:
+
   - Select up to three I/O sources (e.g., ignition, fuel level, temperature).
   - Set DOUT ON and OFF durations or enable Permanent Output Control for continuous activation.
+
  - Define operands to specify logic (e.g., "On Entrance," "Is").
4. **Save Settings**:
+
  - Set Low and High threshold values for each source.
   - Verify the configuration and save. The device evaluates all scenarios every second.
+
   - Adjust the Activation Delay Timer for precise control.
 +
 
 +
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.
   −
=== Operational Details ===
+
=== Example Use Cases ===
- 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 ===
+
- **Scenario 1**: Control a relay when fuel level drops below 10%.
- Activating an alarm if RPM exceeds a threshold while the ignition is on.
+
- **Scenario 2**: Trigger a buzzer if RPM exceeds 3000 while ignition is ON.
- Triggering a relay when the fuel level drops below a critical point.
+
- **Scenario 3**: Activate an alarm when GSM signal strength drops below 20%.
- Enabling a buzzer for temperature out-of-range conditions.