DOUT controls: Difference between revisions
No edit summary |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
'''DOUT ON''' Duration parameter shows for how long DOUT is set on after the scenario is activated and the '''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 the scenario turns off. DOUT ON and DOUT OFF duration parameters must be configured in ms. | '''DOUT ON''' Duration parameter shows for how long DOUT is set on after the scenario is activated and the '''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 the scenario turns off. DOUT ON and DOUT OFF duration parameters must be configured in ms. | ||
[[image:DOUT ctrl]] | In the example below, when any of the configured scenarios is activated, DOUT will switch ON --> OFF every 200ms until the scenario is no longer active. | ||
[[image:DOUT ctrl.png]] | |||
For example, when Towing is detected, DOUT will switch ON for 200ms, then will switch OFF for 200ms, switch ON for 200ms, etc, until Towing is no longer detected. | |||
==DOUT control depending on functionality priority== | ==DOUT control depending on functionality priority== | ||
| Line 16: | Line 20: | ||
* DOUT control via SMS (lowest priority)<br/> | * 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. | ||
'''Important Note:''' Immobilizer cannot be used with any other feature with same DOUT as it takes full control of the DOUT. | |||