Template:Magnetic Card Functionality - Revision history

Gediminas.suminas: /* Authorization for immobilizer scenario */

2021-04-21T11:14:46Z

Authorization for immobilizer scenario

← Older revision		Revision as of 14:14, 21 April 2021
Line 21:		Line 21:

	==Authorization for immobilizer scenario==		==Authorization for immobilizer scenario==
			====Type of card parameter====

			Introduced from firmware version '''FMB.Ver.03.27.01.Rev.163+'''.

			This parameter determines if the vehicle can be started based on card type. If the card type matches the configured parameter and the vehicle can be started based on user configuration, then the scenario allows entering the registered state. Also, if the vehicle is authorized to start (the device is in a registered state), then the card which is not allowed will cause deregistration if swiped.

	Based on parameters '''Vehicle type''', '''Vehicle use type''','''Vehicle additional information''', ''Table 1''		Based on parameters '''Vehicle type''', '''Vehicle use type''','''Vehicle additional information''', ''Table 1''

Gediminas.suminas: /* Type of card parameter */

2021-04-21T11:14:38Z

Type of card parameter

← Older revision		Revision as of 14:14, 21 April 2021
Line 19:		Line 19:
	• Integrated uses built-in buzzer in tracking device<br>		• Integrated uses built-in buzzer in tracking device<br>
	• Reader uses built-in buzzer in the magnetic card reader (if supports buzzer control command)<br>		• Reader uses built-in buzzer in the magnetic card reader (if supports buzzer control command)<br>

	~~====Type of card parameter====~~

	~~Introduced from firmware version '''FMB.Ver.03.27.01.Rev.163+'''.~~

	This parameter determines if the vehicle can be started based on card type. If the card type matches the configured parameter and the vehicle can be started based on user configuration, then the scenario allows entering the registered state. Also, if the vehicle is authorized to start (the device is in a registered state), then the card which is not allowed will cause deregistration if swiped.

	==Authorization for immobilizer scenario==		==Authorization for immobilizer scenario==

Gediminas.suminas: /* Magnetic card functionality */

2021-04-21T11:13:09Z

Magnetic card functionality

← Older revision		Revision as of 14:13, 21 April 2021
Line 19:		Line 19:
	• Integrated uses built-in buzzer in tracking device<br>		• Integrated uses built-in buzzer in tracking device<br>
	• Reader uses built-in buzzer in the magnetic card reader (if supports buzzer control command)<br>		• Reader uses built-in buzzer in the magnetic card reader (if supports buzzer control command)<br>

			====Type of card parameter====

			Introduced from firmware version '''FMB.Ver.03.27.01.Rev.163+'''.

			This parameter determines if the vehicle can be started based on card type. If the card type matches the configured parameter and the vehicle can be started based on user configuration, then the scenario allows entering the registered state. Also, if the vehicle is authorized to start (the device is in a registered state), then the card which is not allowed will cause deregistration if swiped.

	==Authorization for immobilizer scenario==		==Authorization for immobilizer scenario==

Gediminas.suminas: /* Type of card parameter */

2021-04-21T11:12:21Z

Type of card parameter

← Older revision		Revision as of 14:12, 21 April 2021
Line 19:		Line 19:
	• Integrated uses built-in buzzer in tracking device<br>		• Integrated uses built-in buzzer in tracking device<br>
	• Reader uses built-in buzzer in the magnetic card reader (if supports buzzer control command)<br>		• Reader uses built-in buzzer in the magnetic card reader (if supports buzzer control command)<br>

	~~==Type of card parameter==~~

	~~Introduced from firmware version '''FMB.Ver.03.27.01.Rev.163+'''.~~

	This parameter determines if the vehicle can be started based on card type. If the card type matches the configured parameter and the vehicle can be started based on user configuration, then the scenario allows entering the registered state. Also, if the vehicle is authorized to start (the device is in a registered state), then the card which is not allowed will cause deregistration if swiped.

	==Authorization for immobilizer scenario==		==Authorization for immobilizer scenario==

Gediminas.suminas: /* Magnetic card functionality */

2021-04-21T11:11:52Z

Magnetic card functionality

← Older revision		Revision as of 14:11, 21 April 2021
Line 8:		Line 8:
	====Vehicle use type====		====Vehicle use type====
	On initial configuration, the parameters '''Vehicle type''' and '''Vehicle use type''' are set to '''None'''. This		On initial configuration, the parameters '''Vehicle type''' and '''Vehicle use type''' are set to '''None'''. This
	allows the vehicle to be started via immobilizer scenario with any license type (if immobilizer is enabled) enabled). If		allows the vehicle to be started via immobilizer scenario with any license type (if the immobilizer is enabled) enabled). If
	any other options are used for '''Vehicle type''' and '''Vehicle use type''', ''Table 1'' is used to lookup authorization		any other options are used for ''' Vehicle type''' and '''Vehicle use type''', ''Table 1'' is used to lookup authorization
	with regards to driver's license type.		with regards to driver's license type.

	====Buzzer Control====		====Buzzer Control====
	Different buzzers can be controlled when unauthorized cards are swiped see chapter Driver state		Different buzzers can be controlled when unauthorized cards are swiped see chapter Driver state
	logic for a specific or infinite amount of time:		the logic for a specific or infinite amount of time:
	<br>		<br>
	• DOUT1 or DOUT2 are simply turned on for the amount of time configured<br>		• DOUT1 or DOUT2 are simply turned on for the amount of time configured<br>
	• Integrated uses built in buzzer in tracking device<br>		• Integrated uses built-in buzzer in tracking device<br>
	• Reader uses built in buzzer in the magnetic card reader (if supports buzzer control command)<br>		• Reader uses built-in buzzer in the magnetic card reader (if supports buzzer control command)<br>

			==Type of card parameter==

			Introduced from firmware version '''FMB.Ver.03.27.01.Rev.163+'''.

			This parameter determines if the vehicle can be started based on card type. If the card type matches the configured parameter and the vehicle can be started based on user configuration, then the scenario allows entering the registered state. Also, if the vehicle is authorized to start (the device is in a registered state), then the card which is not allowed will cause deregistration if swiped.

	==Authorization for immobilizer scenario==		==Authorization for immobilizer scenario==

Gediminas.suminas: /* Authorization for immobilizer scenario */

2021-04-20T12:06:34Z

Authorization for immobilizer scenario

← Older revision		Revision as of 15:06, 20 April 2021
Line 28:		Line 28:
	{\| class="wikitable mw-collapsible"		{\| class="wikitable mw-collapsible"
	\|+Table 1 Authorization to start vehicle depending on license and vehicle type		\|+Table 1 Authorization to start vehicle depending on license and vehicle type
	! colspan="2" \|Vehicle type		! style="background: #0054A6; color:white"; colspan="2" \|Vehicle type
	!B.1		!style="background: #0054A6; color:white" \| B.1
	!B.2		!style="background: #0054A6; color:white" \| B.2
	!B.3		!style="background: #0054A6; color:white" \| B.3
	!B.4		!style="background: #0054A6; color:white" \| B.4
	!T.1		!style="background: #0054A6; color:white" \| T.1
	!T.2		!style="background: #0054A6; color:white" \| T.2
	!T.3		!style="background: #0054A6; color:white" \| T.3
	!T.4		!style="background: #0054A6; color:white" \| T.4
	\|-		\|-
	! rowspan="2" \|Special Airconditioned Bus		! rowspan="2" \|Special Airconditioned Bus

Aurimas.vanagas: /* Authorization for immobilizer scenario */

2020-04-02T13:56:54Z

Authorization for immobilizer scenario

← Older revision		Revision as of 16:56, 2 April 2020
Line 305:		Line 305:
	<br>		<br>

	If the '''Vehicle type''' is configured as '''Other''', then the decision of whether the vehicle can be started or not is made by using the table located in ~~'''~~Custom ~~vehicle types'''~~ tab.		If the '''Vehicle type''' is configured as '''Other''', then the decision of whether the vehicle can be started or not is made by using the table located in [[Custom_Vehicle_Types\|Custom Vehicle Types]] tab.

	==Driver State Logic==		==Driver State Logic==

Aurimas.vanagas: /* Magnetic card functionality */

2020-04-02T13:56:04Z

Magnetic card functionality

← Older revision		Revision as of 16:56, 2 April 2020
Line 4:		Line 4:
	Magnetic card functionality parameter appearance is shown in ''Figure 1.'' The Other vehicle type ID		Magnetic card functionality parameter appearance is shown in ''Figure 1.'' The Other vehicle type ID
	is displayed only if '''Vehicle type''' is selected as '''Other''' This field allows configuring custom vehicle types		is displayed only if '''Vehicle type''' is selected as '''Other''' This field allows configuring custom vehicle types
	see chapter [[~~'''FMU126_Custom_Vehicle_Types#Custom_vehicle_types~~\|Custom Vehicle Types~~'''~~]].		see chapter [[Custom_Vehicle_Types\|Custom Vehicle Types]].
	<br>		<br>
	====Vehicle use type====		====Vehicle use type====

Aurimas.vanagas at 10:01, 2 April 2020

2020-04-02T10:01:11Z

← Older revision		Revision as of 13:01, 2 April 2020
Line 4:		Line 4:
	Magnetic card functionality parameter appearance is shown in ''Figure 1.'' The Other vehicle type ID		Magnetic card functionality parameter appearance is shown in ''Figure 1.'' The Other vehicle type ID
	is displayed only if '''Vehicle type''' is selected as '''Other''' This field allows configuring custom vehicle types		is displayed only if '''Vehicle type''' is selected as '''Other''' This field allows configuring custom vehicle types
	see chapter '''Custom ~~vehicle types~~'''.		see chapter [['''FMU126_Custom_Vehicle_Types#Custom_vehicle_types\|Custom Vehicle Types''']].
	<br>		<br>
	====Vehicle use type====		====Vehicle use type====

Aurimas.vanagas at 09:26, 2 April 2020

2020-04-02T09:26:58Z

← Older revision		Revision as of 12:26, 2 April 2020
Line 9:		Line 9:
	On initial configuration, the parameters '''Vehicle type''' and '''Vehicle use type''' are set to '''None'''. This		On initial configuration, the parameters '''Vehicle type''' and '''Vehicle use type''' are set to '''None'''. This
	allows the vehicle to be started via immobilizer scenario with any license type (if immobilizer is enabled) enabled). If		allows the vehicle to be started via immobilizer scenario with any license type (if immobilizer is enabled) enabled). If
	any other options are used for '''Vehicle type''' and '''Vehicle use type''', ''Table 2'' is used to lookup authorization		any other options are used for '''Vehicle type''' and '''Vehicle use type''', ''Table 1'' is used to lookup authorization
	with regards to driver's license type.		with regards to driver's license type.

Line 22:		Line 22:
	==Authorization for immobilizer scenario==		==Authorization for immobilizer scenario==

	Based on parameters '''Vehicle type''', '''Vehicle use type''','''Vehicle additional information''', ''Table 2''		Based on parameters '''Vehicle type''', '''Vehicle use type''','''Vehicle additional information''', ''Table 1''
	data that is shown below and the license type obtained from the magnetic card via reader , the functionality		data that is shown below and the license type obtained from the magnetic card via reader , the functionality
	decides whether or not the vehicle can be started (immobilizer scenario) The immobilizer must have priority to be set and output control configured in order for it to function.		decides whether or not the vehicle can be started (immobilizer scenario) The immobilizer must have priority to be set and output control configured in order for it to function.
	<br />		<br />
	{\| class="wikitable mw-collapsible"		{\| class="wikitable mw-collapsible"
	\|+Table 2 Authorization to start vehicle depending on license and vehicle type		\|+Table 1 Authorization to start vehicle depending on license and vehicle type
	! colspan="2" \|Vehicle type		! colspan="2" \|Vehicle type
	!B.1		!B.1
Line 306:		Line 306:

	If the '''Vehicle type''' is configured as '''Other''', then the decision of whether the vehicle can be started or not is made by using the table located in '''Custom vehicle types''' tab.		If the '''Vehicle type''' is configured as '''Other''', then the decision of whether the vehicle can be started or not is made by using the table located in '''Custom vehicle types''' tab.

			==Driver State Logic==
			[[File:Driver State Logic.png\|400px\|center\|thumb\|Figure 2 Driver State Logic]]

			The main driver registration, deregistration and swapping logic is shown in '''Figure 2'''.

			Once deregistration event is generated, the start of the car is disallowed immediatelly (ignition off timer is not taken into consideration).