3,261
edits
Changes
Template:FMB640 Features settings (view source)
Revision as of 07:22, 21 October 2019
, 07:22, 21 October 2019→iButton Read Notification
{{{pic_jamming|[[Image:I button.JPG|300px|right]]}}}
{{{pic_jamming|[[Image:I button.JPG|300px|right]]}}}
* If scenario is enabled, when iButton is attached and is successfully read, configured DOUT goes ON for configurable amount of time (min: 0.00 s; max: 5.00 s; default: 0.2 s). <br>
* If the scenario is enabled, when iButton is attached and is successfully read, configured DOUT goes ON for configurable amount of time (min: 0.00 s; max: 5.00 s; default: 0.2 s). <br>
* If DOUT ON and DOUT OFF durations are both set to 0, DOUT will be ON until iButton will be removed from the reader. <br>
* If DOUT ON and DOUT OFF durations are both set to 0, DOUT will be ON until iButton will be removed from the reader. <br>
* If 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/>
'''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.
<br/><br/><br/><br/><br/><br/><br/>
<br/><br/><br/><br/><br/><br/><br/>