Custom Scenarios
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
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 and parameters
Below is an UI example of configurable parameters:
Below is a detailed explanation of configurable parameters for each scenario:
| Parameter Name | Parameter ID | Value Range | Default Value | Value | Value Definition | Description | |||
|---|---|---|---|---|---|---|---|---|---|
| Custom Scenario 1 ID | Custom Scenario 2 ID | Custom Scenario 3 ID | Min | Max | |||||
| Priority | 19101 | 19131 | 19161 | 0 | 3 | 0 | 0 | None | No priority is set for the scenario. Eventual records are not generated. |
| 1 | Low | Low priority is set for the scenario. | |||||||
| 2 | High | High priority is set for the scenario. | |||||||
| 3 | Panic | Panic priority is set for the scenario. | |||||||
| Output Control | 19100 | 19130 | 19160 | 0 | 3 | 0 | 0 | None | Specifies that no DOUT is controlled by the scenario. |
| 1 | DOUT1 | Specifies that DOUT1 is controlled by the scenario. | |||||||
| 2 | DOUT2 | Specifies that DOUT2 is controlled by the scenario. | |||||||
| 3 | DOUT3 | Specifies that DOUT3 is controlled by the scenario. | |||||||
| Permanent Output Control | 19124 | 19154 | 19184 | 0 | 1 | 0 | 0 | Disabled | Continuous DOUT control is disabled. |
| 1 | Enabled | Continuous DOUT control is enabled as long as conditions are met. | |||||||
| DOUT ON Duration | 19102 | 19132 | 19162 | 100 | 65000000 | 200 | - | milliseconds | Duration for which DOUT remains ON when the scenario is active. |
| DOUT OFF Duration | 19103 | 19133 | 19163 | 0 | 65000000 | 200 | - | milliseconds | Duration for which DOUT remains OFF. A value of 0 means the DOUT stays ON continuously. |
| Trigger #1 | 19105 | 19135 | 19165 | Min IO ID | Max IO ID | Device-specific | - | - | Primary trigger for the scenario. This trigger cannot be ignored. |
| Trigger #2 | 19110 | 19140 | 19170 | Min IO ID | Max IO ID | Device-specific | - | - | Secondary trigger for the scenario. This trigger can be ignored. |
| Trigger #3 | 19116 | 19146 | 19176 | Min IO ID | Max IO ID | Device-specific | - | - | Tertiary trigger for the scenario. This trigger can be ignored. |
| Operand | 19106 | 19136 | 19166 | 0 | 6 | 0 | 0 | On Exit | Trigger activates on exit of the defined condition. |
| 1 | On Entrance | Trigger activates on entrance of the defined condition. | |||||||
| 2 | On Both | Trigger activates on both entrance and exit of the condition. | |||||||
| 3 | On Hysteresis | Trigger activates on hysteresis of the condition. | |||||||
| 4 | On Change | Trigger activates on any change in the condition. | |||||||
| 5 | On Delta Change | Trigger activates on a specified delta change. | |||||||
| 6 | Is | Trigger activates if the condition is true. | |||||||
| Low Level | 19107 | 19137 | 19167 | Dynamic | Dynamic | 0 | - | - | Sets the lower threshold value for the trigger. |
| High Level | 19108 | 19138 | 19168 | Dynamic | Dynamic | 0 | - | - | Sets the upper threshold value for the trigger. |
| Activation Delay Timer | 19109 | 19139 | 19169 | 0 | 65535 | 0 | - | seconds | Time (in seconds) the condition must remain true for activation. |
| Ignore | 19114 | 19144 | 19174 | 0 | 1 | 1 | 0 | No | The trigger will not be ignored and is actively checked. |
| 1 | Yes | The trigger will be ignored and will not affect scenario activation. | |||||||
| Logic | 19115 | 19145 | 19175 | 0 | 1 | 1 | 0 | OR | Trigger evaluation logic: any trigger activates the scenario. |
| 1 | AND | Trigger evaluation logic: all triggers must be true to activate the scenario. | |||||||
Configuration Process
1. **Define Output Control**:
- Assign the DOUT (DOUT1, DOUT2, or DOUT3) to be controlled by the scenario.
2. **Configure Triggers**:
- Select up to three I/O sources (e.g., ignition, fuel level, temperature). - Define operands to specify logic (e.g., "On Entrance," "Is"). - Set Low and High threshold values for each source. - 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.
Example Use Cases
- **Scenario 1**: Control a relay when fuel level drops below 10%. - **Scenario 2**: Trigger a buzzer if RPM exceeds 3000 while ignition is ON. - **Scenario 3**: Activate an alarm when GSM signal strength drops below 20%.