3,229
edits
Changes
Template:FMB640 Features settings (view source)
Revision as of 08:22, 21 October 2019
, 08:22, 21 October 2019→iButton Read Notification
* If the Immobilizer scenario is enabled and iButton’s indication scenario is enabled and the same DOUT controls are chosen then in case iButton is attached DOUT is not affected.
* If the Immobilizer scenario is enabled and iButton’s indication scenario is enabled and the same DOUT controls are chosen then in case iButton is attached DOUT is not affected.
IButton’s event generation works as a standard IO event generation
IButton’s event generation works as a standard IO event generation
<br/>
<br/><br/>
'''Confirmation about successful iButton identification with configured DOUT ON indication'''
'''Confirmation about successful iButton identification with configured DOUT ON indication'''
If DOUTX iButton read notification parameter is configured to control DOUTX and DOUTX is ON, then when new iButton is successfully read, DOUTX is turned OFF for 0,5 seconds and then turned back ON. By “new iButton” it is meant that the value read by (let’s say Driver’s) iButton reader is either different compared to what was read before or it’s the first time this iButton is read.
If DOUTX iButton read notification parameter is configured to control DOUTX and DOUTX is ON, then when new iButton is successfully read, DOUTX is turned OFF for 0,5 seconds and then turned back ON. By “new iButton” it is meant that the value read by (let’s say Driver’s) iButton reader is either different compared to what was read before or it’s the first time this iButton is read.
