Difference between revisions of "DOUT controls"
Danielekrau (talk | contribs) m (Protected "DOUT controls" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))) |
|||
| Line 2: | Line 2: | ||
In all scenarios that control Digital Output, Digital Output can be controlled independent from scenario.<br/>DOUT ON Duration parameter shows for how long DOUT is set on after scenario is activated and DOUT OFF Duration parameter shows how long DOUT is set off after DOUT ON duration ends. After DOUT OFF duration ends, DOUT ON duration will be counted again. This period continues until scenario turns off. DOUT ON and DOUT OFF duration parameters must be configured in ms. | In all scenarios that control Digital Output, Digital Output can be controlled independent from scenario.<br/>DOUT ON Duration parameter shows for how long DOUT is set on after scenario is activated and DOUT OFF Duration parameter shows how long DOUT is set off after DOUT ON duration ends. After DOUT OFF duration ends, DOUT ON duration will be counted again. This period continues until scenario turns off. DOUT ON and DOUT OFF duration parameters must be configured in ms. | ||
==DOUT control depending on functionality priority== | ==DOUT control depending on functionality priority== | ||
| − | All DOUT control functionalities now have their own priority (non-configurable). Depending on priority DOUT control may be overtaken by higher priority functionality without finishing previous scenario.<br/>DOUT control scenarios and functionalities by priority: | + | All DOUT control functionalities now have their own priority (non-configurable). Depending on priority DOUT control may be overtaken by higher priority functionality without finishing the previous scenario.<br/>DOUT control scenarios and functionalities by priority: |
| − | * Immobilizer (highest priority) | + | * Immobilizer (highest priority) |
| − | * DOUT control via call | + | * DOUT control via call |
| − | * Green Driving | + | * Green Driving |
| − | * Jamming | + | * Jamming |
| − | * Overspeeding | + | * Overspeeding |
| − | * Idling | + | * Towing |
| − | * DOUT control via SMS (lowest priority) | + | * Idling |
| + | * DOUT control via SMS (lowest priority)<br/> | ||
For example, if jamming will be detected during Overspeeding, then Jamming functionality will control DOUT. | For example, if jamming will be detected during Overspeeding, then Jamming functionality will control DOUT. | ||
Revision as of 07:43, 15 September 2020
DOUT ON/OFF Duration
In all scenarios that control Digital Output, Digital Output can be controlled independent from scenario.
DOUT ON Duration parameter shows for how long DOUT is set on after scenario is activated and DOUT OFF Duration parameter shows how long DOUT is set off after DOUT ON duration ends. After DOUT OFF duration ends, DOUT ON duration will be counted again. This period continues until scenario turns off. DOUT ON and DOUT OFF duration parameters must be configured in ms.
DOUT control depending on functionality priority
All DOUT control functionalities now have their own priority (non-configurable). Depending on priority DOUT control may be overtaken by higher priority functionality without finishing the previous scenario.
DOUT control scenarios and functionalities by priority:
- Immobilizer (highest priority)
- DOUT control via call
- Green Driving
- Jamming
- Overspeeding
- Towing
- Idling
- DOUT control via SMS (lowest priority)
For example, if jamming will be detected during Overspeeding, then Jamming functionality will control DOUT.
