Template:FMM640 iButton Read Notification - Revision history

AugustasP: /* iButton Read Notification */

2022-09-19T13:05:35Z

iButton Read Notification

← Older revision		Revision as of 16:05, 19 September 2022
Line 1:		Line 1:
	==iButton Read Notification==		==iButton Read Notification==

	~~{{{pic_ibutton\|~~[[Image:~~I button~~.~~JPG~~\|~~300px~~\|right]]~~}}}~~		[[Image:IButton_Read_Notification .png\|{{{general\|size}}}\|\|right]]
			Output control parameter lets the user choose which DOUT will iButton blink. After connecting iButton, DOUT will blink for a period of time, which is configured in DOUT ON Duration parameter. The iButton List checking parameter configures whether the device reads the iButton ID from iButton list or not. For example if configured as Enabled, device will not blink DOUT unless the iButton is in the iButton list.
			If Depend on Ignition parameter is enabled, then Output will be triggered only if ignition is off (in addition to being in a list if iButton List Checking is also enabled).
			Output control examples when iButton is detected (if None is selected in Output Control – all of the following steps will be skipped):

	* 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 both iButton List Checking and Depend on Ignition are disabled – Output is triggered.
	* 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 iButton List Checking is enabled and Depend on Ignition is disabled – Output is triggered only if iButton is in the list.
	* ~~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 iButton List Checking is disabled but Depend on Ignition is enabled – Output is triggered only if ignition is off.
	~~IButton’s event generation works as a standard IO event generation~~		*If both iButton List Checking and Depend on Ignition are enabled – Output will trigger if iButton is in the list and ignition is off.

			iButton Read Notification parameters:

			*Output control – available scenario settings for module Digital output activation/deactivation
			*DOUT ON duration – a value in seconds, for how long {{{text_dout\|DOUT1/DOUT2/DOUT3}}} should be active.
			*iButton List checking - parameter configures that device reads the iButton ID from list or not.
			*Depend on Ignition - Output will be triggered only if ignition is off
	<br/><br/>		<br/><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/>~~

Sandra.Gasyte at 22:00, 20 April 2020

2020-04-20T22:00:48Z

← Older revision		Revision as of 01:00, 21 April 2020
Line 1:		Line 1:
	==iButton Read Notification==		==iButton Read Notification==

	{{{~~pic_jamming~~\|[[Image:I button.JPG\|300px\|right]]}}}		{{{pic_ibutton\|[[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/><br/>~~<br/><br/>~~<br/><br/><br/>		<br/><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/>

Irmantas.Tydikas: Created page with "==iButton Read Notification== {{{pic_jamming|right}}} * If scenario is enabled, when iButton is attached and is successfully read, configured DO..."

2019-08-22T11:36:07Z

Created page with "==iButton Read Notification== {{{pic_jamming|300px|right}}} * If scenario is enabled, when iButton is attached and is successfully read, configured DO..."

New page

==iButton Read Notification==

{{{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). 
* If DOUT ON and DOUT OFF durations are both set to 0, DOUT will be ON until iButton will be removed from the reader. 
* 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.
IButton’s event generation works as a standard IO event generation