Changes

In order to distinguish driver and passenger iButtons while both iButton readers are on the same 1-wire line, special logic applied: if there is no voltage on configured Passenger iButton source DINX then it is taken that Passenger iButton is attached. The value of reading Passenger iButton ID is saved to Passenger iButton IO element. This functionality works with an immobilizer scenario only.

In order to distinguish driver and passenger iButtons while both iButton readers are on the same 1-wire line, special logic applied: if there is no voltage on configured Passenger iButton source DINX then it is taken that Passenger iButton is attached. The value of reading Passenger iButton ID is saved to Passenger iButton IO element. This functionality works with an immobilizer scenario only.

-->

-->

 

{{{txt_br|<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>}}}

<br/>{{{txt_br|<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>}}}

==iButton Read Notification==

==iButton Read Notification==

'''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.

 

==Short burst data settings==

==Short burst data settings==