Template:FMM Features settings - Revision history

Donatas.Mazonas at 13:15, 30 January 2026

2026-01-30T13:15:19Z

← Older revision		Revision as of 16:15, 30 January 2026
Line 155:		Line 155:
	<br/><br/><youtube>gjuiJjAejWU</youtube>}}}		<br/><br/><youtube>gjuiJjAejWU</youtube>}}}

	From firmware version '''04.00.00.Rev.13 and above''', the "Authorization ID List Checking" option “None” was removed as part of a security improvement. Devices now require selecting 1-Wire, RFID (for RS232-capable devices), or Beacons. If the list is empty, the behavior is equivalent to the previous “None” option - any iButton, RFID card, or Beacon disables the Immobilizer.		From firmware version '''04.00.00.Rev.13 and above''', the "Authorization ID List Checking" option “None” was removed as part of a security improvement. Devices now require selecting 1-Wire, RFID (for RS232-capable devices), or Beacons. If the Authorization ID list is empty, the behavior is equivalent to the previous “None” option - any iButton, RFID card, or Beacon disables the Immobilizer.

	{{{ibutton_feature\|==iButton Read Notification==		{{{ibutton_feature\|==iButton Read Notification==

Donatas.Mazonas: Replaced immobilizer image. Added text about immobilizer changes. [GTPGTM-11057]

2026-01-30T13:07:00Z

Replaced immobilizer image. Added text about immobilizer changes. [GTPGTM-11057]

← Older revision		Revision as of 16:07, 30 January 2026
Line 143:		Line 143:
	{{{immobilizer_feature\|==Immobilizer==		{{{immobilizer_feature\|==Immobilizer==

	[[~~Image~~:~~Immobilizer~~.~~gif~~\|{{{general\|size}}}\|right]]		[[File:Immobilizer1.png\|{{{general\|size}}}\|right]]

	If ''DOUT Control'' is disabled, the scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout\|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID (or RFID card) is attached, {{{text_dout\|DOUT1/DOUT2}}} turns OFF. After iButton identification configured ''Ignition Source'' can be turned OFF (''Ignition Source'' is configured to 0) for no longer than 30 seconds, otherwise, the immobilizer must be repeated. If the ''iButton List Check'' parameter is enabled, the authorization will be successful only if the attached iButton is specified in the iButton list.<br/>		If ''DOUT Control'' is disabled, the scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout\|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID (or RFID card) is attached, {{{text_dout\|DOUT1/DOUT2}}} turns OFF. After iButton identification configured ''Ignition Source'' can be turned OFF (''Ignition Source'' is configured to 0) for no longer than 30 seconds, otherwise, the immobilizer must be repeated. If the ''iButton List Check'' parameter is enabled, the authorization will be successful only if the attached iButton is specified in the iButton list.<br/>
Line 154:		Line 154:
	By using iBeacon authorization, the immobilizer feature can be used with devices that don't have a 1-wire data connection available.		By using iBeacon authorization, the immobilizer feature can be used with devices that don't have a 1-wire data connection available.
	<br/><br/><youtube>gjuiJjAejWU</youtube>}}}		<br/><br/><youtube>gjuiJjAejWU</youtube>}}}

			From firmware version '''04.00.00.Rev.13 and above''', the "Authorization ID List Checking" option “None” was removed as part of a security improvement. Devices now require selecting 1-Wire, RFID (for RS232-capable devices), or Beacons. If the list is empty, the behavior is equivalent to the previous “None” option - any iButton, RFID card, or Beacon disables the Immobilizer.

	{{{ibutton_feature\|==iButton Read Notification==		{{{ibutton_feature\|==iButton Read Notification==

Justinas.strelciunas: Undo revision 101586 by Justinas.strelciunas (talk)

2024-12-11T08:43:29Z

Undo revision 101586 by Justinas.strelciunas (talk)

← Older revision		Revision as of 11:43, 11 December 2024
Line 131:		Line 131:
	For a more visual explanation, take a look at the video made by Teltonika explaining the use-case of Jamming Detection: '''[https://www.youtube.com/watch?v=otQd34WqL54 Teltonika Jamming Detection scenario]'''		For a more visual explanation, take a look at the video made by Teltonika explaining the use-case of Jamming Detection: '''[https://www.youtube.com/watch?v=otQd34WqL54 Teltonika Jamming Detection scenario]'''
	}}}		}}}
			{{{dout_control_via_call_feature\|==DOUT Control Via Call==

			[[Image:DOUT_Control_Via_Call.gif\|{{{general\|size}}}\|right]]

			The scenario is activated and digital output is ON when a call is received from a number that is on the authorized numbers list.<br/>
			Call control functionality is the following:
			* When [[{{{model\|FMB1YX}}}]] is configured to control {{{text_dout\|DOUT1/DOUT2}}} the device waits for an incoming call from a configured secure number. If a call is received [[{{{model\|FMB1YX}}}]] turns on {{{text_dout\|DOUT1/DOUT2}}} for a user defined ''Duration Timeout''. If duration timeout set to "0" {{{text_dout\|DOUT1/DOUT2}}} will be OFF.
			* {{{text_dout\|DOUT1/DOUT2}}} can be turned off by ''Duration Timeout'' or by {{{text_din\|digital input 1, digital input 2 or digital input 3}}}.
			* {{{text_dout\|DOUT1/DOUT2}}} will always be ON if, for example, DOUT deactivation is set to DIN1, but DIN1 will be never turned ON, or when duration timeout is set to the maximum value (2147483647) which is about 68 years.}}}

	{{{immobilizer_feature\|==Immobilizer==		{{{immobilizer_feature\|==Immobilizer==

Justinas.strelciunas: /* Over Speeding */

2024-12-11T08:37:41Z

Over Speeding

← Older revision		Revision as of 11:37, 11 December 2024
Line 131:		Line 131:
	For a more visual explanation, take a look at the video made by Teltonika explaining the use-case of Jamming Detection: '''[https://www.youtube.com/watch?v=otQd34WqL54 Teltonika Jamming Detection scenario]'''		For a more visual explanation, take a look at the video made by Teltonika explaining the use-case of Jamming Detection: '''[https://www.youtube.com/watch?v=otQd34WqL54 Teltonika Jamming Detection scenario]'''
	}}}		}}}
	~~{{{dout_control_via_call_feature\|==DOUT Control Via Call==~~

	~~[[Image:DOUT_Control_Via_Call.gif\|{{{general\|size}}}\|right]]~~

	~~The scenario is activated and digital output is ON when a call is received from a number that is on the authorized numbers list.<br/>~~
	~~Call control functionality is the following:~~
	* When [[{{{model\|FMB1YX}}}]] is configured to control {{{text_dout\|DOUT1/DOUT2}}} the device waits for an incoming call from a configured secure number. If a call is received [[{{{model\|FMB1YX}}}]] turns on {{{text_dout\|DOUT1/DOUT2}}} for a user defined ''Duration Timeout''. If duration timeout set to "0" {{{text_dout\|DOUT1/DOUT2}}} will be OFF.
	* {{{text_dout\|DOUT1/DOUT2}}} can be turned off by ''Duration Timeout'' or by {{{text_din\|digital input 1, digital input 2 or digital input 3}}}.
	* {{{text_dout\|DOUT1/DOUT2}}} will always be ON if, for example, DOUT deactivation is set to DIN1, but DIN1 will be never turned ON, or when duration timeout is set to the maximum value (2147483647) which is about 68 years.}}}

	{{{immobilizer_feature\|==Immobilizer==		{{{immobilizer_feature\|==Immobilizer==

Donatas.Kondratokas: /* Over Speeding */

2023-01-30T08:23:29Z

Over Speeding

← Older revision		Revision as of 11:23, 30 January 2023
Line 100:		Line 100:

	When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout\| and digital output status is changed to 1 when configured}}}.<br />Scenario is active until detected speed decreases below the set parameter value. Configurable parameters:		When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout\| and digital output status is changed to 1 when configured}}}.<br />Scenario is active until detected speed decreases below the set parameter value. Configurable parameters:
	[[Image:Over_Speeding.~~gif~~\|{{{general\|size}}}\|right]]		[[Image:Over_Speeding.PNG\|{{{general\|size}}}\|right]]
	<br />		<br />
	*Scenario settings – defines priority of over speeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.		*Scenario settings – defines priority of over speeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.

Donatas.Kondratokas: /* Over Speeding */

2023-01-27T12:47:44Z

Over Speeding

← Older revision		Revision as of 15:47, 27 January 2023
Line 104:		Line 104:
	*Scenario settings – defines priority of over speeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.		*Scenario settings – defines priority of over speeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.
	*Max speed – it is max allowed speed which can be reached. If speed exceeded configured value, then event will occur.		*Max speed – it is max allowed speed which can be reached. If speed exceeded configured value, then event will occur.
	*Output control – available scenario settings for module Digital output activation/deactivation
	*DOUT ON/OFF duration – a value in seconds, for how long {{{text_dout\|DOUT1/DOUT2}}} should be active or inactive.
	*Send SMS to – GSM number to which SMS event will be sent.		*Send SMS to – GSM number to which SMS event will be sent.
	*SMS text – SMS text.		*SMS text – SMS text.

Marius Bakas at 13:11, 6 October 2022

2022-10-06T13:11:16Z

← Older revision		Revision as of 16:11, 6 October 2022
Line 250:		Line 250:

	}}}		}}}
			{{{SECO\|{{Template:Secure_vehicle_disabling}}}}}

Arnas.Zeb at 12:46, 20 October 2021

2021-10-20T12:46:40Z

← Older revision		Revision as of 15:46, 20 October 2021
Line 147:		Line 147:
	[[Image:Immobilizer.gif\|{{{general\|size}}}\|right]]		[[Image:Immobilizer.gif\|{{{general\|size}}}\|right]]

	If ''DOUT Control'' is disabled, the scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout\|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID is attached, {{{text_dout\|DOUT1/DOUT2}}} turns OFF. After iButton identification configured ''Ignition Source'' can be turned OFF (''Ignition Source'' is configured to 0) for no longer than 30 seconds, otherwise, the immobilizer must be repeated. If the ''iButton List Check'' parameter is enabled, the authorization will be successful only if the attached iButton is specified in the iButton list.<br/>		If ''DOUT Control'' is disabled, the scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout\|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID (or RFID card) is attached, {{{text_dout\|DOUT1/DOUT2}}} turns OFF. After iButton identification configured ''Ignition Source'' can be turned OFF (''Ignition Source'' is configured to 0) for no longer than 30 seconds, otherwise, the immobilizer must be repeated. If the ''iButton List Check'' parameter is enabled, the authorization will be successful only if the attached iButton is specified in the iButton list.<br/>
	<br/><br/>		<br/><br/>
	The ignition off timeout parameter is used to set the duration after which authorization is activated when the ignition is turned off. For example, if the Ignition off timeout is set to 30 seconds when the driver turns the ignition off, he has 30 seconds until the immobilizer security check turns on again. In other words, if the driver turns off the ignition and turns it back on in less than 30 seconds, then he will not have to attach the iButton to the reader again.		The ignition off timeout parameter is used to set the duration after which authorization is activated when the ignition is turned off. For example, if the Ignition off timeout is set to 30 seconds when the driver turns the ignition off, he has 30 seconds until the immobilizer security check turns on again. In other words, if the driver turns off the ignition and turns it back on in less than 30 seconds, then he will not have to attach the iButton to the reader again.

Mantas.Kraujelis at 12:20, 19 August 2021

2021-08-19T12:20:56Z

Show changes

Raul.andrade at 16:22, 4 March 2021

2021-03-04T16:22:59Z

← Older revision		Revision as of 19:22, 4 March 2021
Line 76:		Line 76:
	==Over Speeding==		==Over Speeding==

	[[Image:~~FMB120_Over_Speeding~~.~~png~~\|~~300px~~\|size\|right]]		[[Image:Over_Speeding.gif\|{{{general\|size}}}\|right]]

	When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout\| and digital output status is changed to 1 when configured}}}.<br/>Scenario is active until detected speed decreases below the set parameter value.<br/>{{{over_speeding_dout\|info}}}		When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout\| and digital output status is changed to 1 when configured}}}.<br/>Scenario is active until detected speed decreases below the set parameter value.<br/>{{{over_speeding_dout\|info}}}
Line 86:		Line 86:
	{{{dout_control_via_call_feature\|== DOUT Control Via Call==		{{{dout_control_via_call_feature\|== DOUT Control Via Call==

	[[Image:~~FMB120_DOUT_Control_Via_Call~~.~~png~~\|~~295px~~\|size\|right]]		[[Image:DOUT_Control_Via_Call.gif\|{{{general\|size}}}\|right]]

	Scenario is activated and digital output is ON when call is received from a number which is on the authorized numbers list.<br/>		Scenario is activated and digital output is ON when call is received from a number which is on the authorized numbers list.<br/>
Line 99:		Line 99:
	{{{immobilizer_feature\|==Immobilizer==		{{{immobilizer_feature\|==Immobilizer==

	[[Image:~~FMB120_Immobilizer~~.~~png~~\|~~300px~~\|size\|right]]		[[Image:Immobilizer.gif\|{{{general\|size}}}\|right]]

	If ''DOUT Control'' is disabled, scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout\|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID is attached, {{{text_dout\|DOUT1/DOUT2}}} turns OFF. After iButton identification configured ''Ignition Source'' can be turned OFF (''Ignition Source'' is configured to 0) for no longer than 30 seconds, otherwise immobilizer must be repeated. If ''iButton List Check'' parameter is enabled, authorization will be successful only if the attached iButton is specified in iButton list.<br/>{{{immobilizer_dout\|info}}}		If ''DOUT Control'' is disabled, scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout\|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID is attached, {{{text_dout\|DOUT1/DOUT2}}} turns OFF. After iButton identification configured ''Ignition Source'' can be turned OFF (''Ignition Source'' is configured to 0) for no longer than 30 seconds, otherwise immobilizer must be repeated. If ''iButton List Check'' parameter is enabled, authorization will be successful only if the attached iButton is specified in iButton list.<br/>{{{immobilizer_dout\|info}}}

← Older revision		Revision as of 19:22, 4 March 2021
Line 76:		Line 76:
	==Over Speeding==		==Over Speeding==

	[[Image:~~FMB120_Over_Speeding~~.~~png~~\|~~300px~~\|size\|right]]		[[Image:Over_Speeding.gif\|{{{general\|size}}}\|right]]

	When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout\| and digital output status is changed to 1 when configured}}}.<br/>Scenario is active until detected speed decreases below the set parameter value.<br/>{{{over_speeding_dout\|info}}}		When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout\| and digital output status is changed to 1 when configured}}}.<br/>Scenario is active until detected speed decreases below the set parameter value.<br/>{{{over_speeding_dout\|info}}}
Line 86:		Line 86:
	{{{dout_control_via_call_feature\|== DOUT Control Via Call==		{{{dout_control_via_call_feature\|== DOUT Control Via Call==

	[[Image:~~FMB120_DOUT_Control_Via_Call~~.~~png~~\|~~295px~~\|size\|right]]		[[Image:DOUT_Control_Via_Call.gif\|{{{general\|size}}}\|right]]

	Scenario is activated and digital output is ON when call is received from a number which is on the authorized numbers list.<br/>		Scenario is activated and digital output is ON when call is received from a number which is on the authorized numbers list.<br/>
Line 99:		Line 99:
	{{{immobilizer_feature\|==Immobilizer==		{{{immobilizer_feature\|==Immobilizer==

	[[Image:~~FMB120_Immobilizer~~.~~png~~\|~~300px~~\|size\|right]]		[[Image:Immobilizer.gif\|{{{general\|size}}}\|right]]

	If ''DOUT Control'' is disabled, scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout\|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID is attached, {{{text_dout\|DOUT1/DOUT2}}} turns OFF. After iButton identification configured ''Ignition Source'' can be turned OFF (''Ignition Source'' is configured to 0) for no longer than 30 seconds, otherwise immobilizer must be repeated. If ''iButton List Check'' parameter is enabled, authorization will be successful only if the attached iButton is specified in iButton list.<br/>{{{immobilizer_dout\|info}}}		If ''DOUT Control'' is disabled, scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout\|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID is attached, {{{text_dout\|DOUT1/DOUT2}}} turns OFF. After iButton identification configured ''Ignition Source'' can be turned OFF (''Ignition Source'' is configured to 0) for no longer than 30 seconds, otherwise immobilizer must be repeated. If ''iButton List Check'' parameter is enabled, authorization will be successful only if the attached iButton is specified in iButton list.<br/>{{{immobilizer_dout\|info}}}