Line 1: |
Line 1: |
| ==Introduction to Custom Scenarios functionality== | | ==Introduction to Custom Scenarios functionality== |
| | | |
− | Given that different clients have unique needs and are always expanding their options and solutions, we continually look for ways to meet various expectations in a timely manner.To achieve this, we developed a solution that allows users to customize a set of parameters as conditions in order generate an event or control the device's digital outputs. When connected to different types of peripherals such as alarms, buzzers or relays, this feature can inform the driver or complete specific functions.
| + | 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. |
| | | |
− | Since the device operates independently under different conditions, it eliminates the need to monitor device status on the platform and implement complex backend functions. Using the custom scenarios functionality any type of data readable by the specific device model can impact how and when the digital output is controlled.
| + | 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== | | ==Custom Scenarios functionality logic== |
| [[File:Custom Scenarios Topology.png|right|thumb|800px|Figure 1. “Custom Scenarios” functionality logic]] | | [[File:Custom Scenarios Topology.png|right|thumb|800px|Figure 1. “Custom Scenarios” functionality logic]] |
− | “Smart Ignition Detection”– detects ignition “on” and “off” automatically by monitoring last “Smart Ignition Duration” seconds of external voltage and comparing it to current external voltage value. If current external voltage value is higher by “Smart Ignition Delta” than external voltage “Smart Ignition Duration” seconds ago, Ignition “on” event is detected. If current external voltage value is lower by “Smart Ignition Delta” than “Smart Ignition Duration” seconds ago Ignition “off” event is detected.
| + | 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, or 1-Wire/Bluetooth sensor temperature. Each trigger is configured with specific logic operands (e.g., "On Entrance," "On Exit"), threshold values (low and high), 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 enabled) 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. |
| | | |
| | | |
Line 28: |
Line 34: |
| | | |
| | | |
− | ==Smart Ignition Detection configuration== | + | |
| + | |
| + | ==Custom Scenarios functionality logic== |
| | | |
| New configurable parameters were added under “Ignition Settings” (Figure 2): | | New configurable parameters were added under “Ignition Settings” (Figure 2): |