Template:FMC Features settings - Revision history

Arijus.C at 11:15, 30 March 2026

2026-03-30T11:15:40Z

← Older revision		Revision as of 14:15, 30 March 2026
Line 197:		Line 197:
	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.		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.

			{{#switch: {{{model}}}
			\|FMC130\|FMC125\|FMC230\|FMC225\|FMC13A\|FMC234 =
	{{{seco_feature\|==SECO==		{{{seco_feature\|==SECO==
	[[Image:SECO.png\|right]]		[[Image:SECO.png\|right]]
Line 289:		Line 291:

	'''SECO functionality is also supported by the {{{model\|FMB1YX}}} device.'''		'''SECO functionality is also supported by the {{{model\|FMB1YX}}} device.'''

			\|#default =
			}}

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

Donatas.Mazonas at 13:15, 30 January 2026

2026-01-30T13:15:04Z

← Older revision		Revision as of 16:15, 30 January 2026
Line 195:		Line 195:
	'''Immobilizer scenario is also supported by the {{{model\|FMB1YX}}} device.'''		'''Immobilizer scenario is also supported by the {{{model\|FMB1YX}}} device.'''

	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.

	{{{seco_feature\|==SECO==		{{{seco_feature\|==SECO==

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

2026-01-30T13:07:07Z

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

← Older revision		Revision as of 16:07, 30 January 2026
Line 179:		Line 179:
	{{{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 194:		Line 194:

	'''Immobilizer scenario is also supported by the {{{model\|FMB1YX}}} device.'''		'''Immobilizer scenario is also supported by the {{{model\|FMB1YX}}} device.'''

			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.

	{{{seco_feature\|==SECO==		{{{seco_feature\|==SECO==

Mantas.Kraujelis at 08:13, 6 February 2025

2025-02-06T08:13:06Z

← Older revision		Revision as of 11:13, 6 February 2025
Line 372:		Line 372:
	{{{dout_type\|		{{{dout_type\|
	==DOUT 1 Output Type==		==DOUT 1 Output Type==
	[[File:Dout1 output type.gif\|right]] {{{model\|FMB1YX}}}'''DOUT 1 Output Type''' functionality sets the initial ''DOUT1'' state. If the functionality is configured in ''Normal'' mode, the digital output inactive state is low, and when it is controlled by any scenario the digital output is set to high state. Whenever the functionality is configured in ''Inverted'' mode, the digital output inactive state is high, and when it is controlled by any scenario the digital output is set to low state.<br></br>		[[File:Dout1 output type.gif\|right]] {{{model\|FMB1YX}}} '''DOUT 1 Output Type''' functionality sets the initial ''DOUT1'' state. If the functionality is configured in ''Normal'' mode, the digital output inactive state is low, and when it is controlled by any scenario the digital output is set to high state. Whenever the functionality is configured in ''Inverted'' mode, the digital output inactive state is high, and when it is controlled by any scenario the digital output is set to low state.<br></br>

	DOUT1 in '''Normal''' state:		DOUT1 in '''Normal''' state:
Line 386:		Line 386:
	[[File:Alert.png\|50px]] <b>Available from Firmware version: [[ {{{model\|}}}_firmware_errata\|3.27.07.Rev.00]] </b>		[[File:Alert.png\|50px]] <b>Available from Firmware version: [[ {{{model\|}}}_firmware_errata\|3.27.07.Rev.00]] </b>
	}}}		}}}

	~~'''DOUT 1 Output Type feature is also supported by the {{{model\|FMB1YX}}} device.'''~~

Mantas.Kraujelis at 08:05, 6 February 2025

2025-02-06T08:05:33Z

Show changes

Mantas.Kraujelis at 08:03, 6 February 2025

2025-02-06T08:03:07Z

Show changes

Aurimas.vanagas at 15:04, 12 December 2024

2024-12-12T15:04:57Z

← Older revision		Revision as of 18:04, 12 December 2024
Line 145:		Line 145:
	Alternatively, the Digital output can also be connected to an LED visible to the driver to inform the driver when Jamming occurs.		Alternatively, the Digital output can also be connected to an LED visible to the driver to inform the driver when Jamming occurs.

	'''Note that this scenario will not work with [[{{{model\|FMB1YX}}}_Sleep_modes#Deep_Sleep_mode\|Deep Sleep]], [[{{{model\|FMB1YX}}}_Sleep_modes#Ultra_Deep_Sleep_mode\|Ultra Deep Sleep]] (since they disable the device's GSM module to save power) and [[{{{model\|FMB1YX}}}_Sleep_modes#Online_Deep_Sleep_mode\|Online Deep Sleep]] modes'''		'''Note that this scenario will not work with [[{{{model\|FMB1YX}}}_Sleep_modes#Deep_Sleep_mode\|Deep Sleep]], [[{{{model\|FMB1YX}}}_Sleep_modes#Ultra_Deep_Sleep_mode\|Ultra Deep Sleep]] (since they disable the device's GSM module to save power) and [[{{{model\|FMB1YX}}}_Sleep_modes#Online_Deep_Sleep_mode\|Online Deep Sleep]] modes.'''

	''Eventual Records'' parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise, it will be appended only to eventual records.		''Eventual Records'' parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise, it will be appended only to eventual records.

Aurimas.vanagas at 15:03, 12 December 2024

2024-12-12T15:03:19Z

← Older revision		Revision as of 18:03, 12 December 2024
Line 145:		Line 145:
	Alternatively, the Digital output can also be connected to an LED visible to the driver to inform the driver when Jamming occurs.		Alternatively, the Digital output can also be connected to an LED visible to the driver to inform the driver when Jamming occurs.

	'''Note that this scenario will not work with [[{{{model\|FMB1YX}}}_Sleep_modes#Deep_Sleep_mode\|Deep Sleep]], [[{{{model\|FMB1YX}}}_Sleep_modes#Ultra_Deep_Sleep_mode\|Ultra Deep Sleep]] ~~modes,~~ since they disable the device's GSM module to save power.'''		'''Note that this scenario will not work with [[{{{model\|FMB1YX}}}_Sleep_modes#Deep_Sleep_mode\|Deep Sleep]], [[{{{model\|FMB1YX}}}_Sleep_modes#Ultra_Deep_Sleep_mode\|Ultra Deep Sleep]] (since they disable the device's GSM module to save power) and [[{{{model\|FMB1YX}}}_Sleep_modes#Online_Deep_Sleep_mode\|Online Deep Sleep]] modes'''

	''Eventual Records'' parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise, it will be appended only to eventual records.		''Eventual Records'' parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise, it will be appended only to eventual records.

Aurimas.vanagas at 14:57, 12 December 2024

2024-12-12T14:57:05Z

← Older revision		Revision as of 17:57, 12 December 2024
Line 145:		Line 145:
	Alternatively, the Digital output can also be connected to an LED visible to the driver to inform the driver when Jamming occurs.		Alternatively, the Digital output can also be connected to an LED visible to the driver to inform the driver when Jamming occurs.

	'''Note that this scenario will not work with [[{{{model\|FMB1YX}}}_Sleep_modes#Deep_Sleep_mode\|Deep Sleep]], [[{{{model\|FMB1YX}}}_Sleep_modes#Ultra_Deep_Sleep_mode\|Ultra ~~Deep Sleep]] and [[{{{model\|FMB1YX}}}_Sleep_modes#Online_Deep_Sleep_mode\|Online~~ Deep Sleep]] modes, since they disable the device's GSM module to save power.'''		'''Note that this scenario will not work with [[{{{model\|FMB1YX}}}_Sleep_modes#Deep_Sleep_mode\|Deep Sleep]], [[{{{model\|FMB1YX}}}_Sleep_modes#Ultra_Deep_Sleep_mode\|Ultra Deep Sleep]] modes, since they disable the device's GSM module to save power.'''

	''Eventual Records'' parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise, it will be appended only to eventual records.		''Eventual Records'' parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise, it will be appended only to eventual records.

Paulius.peciulis at 09:27, 26 March 2024

2024-03-26T09:27:18Z

← Older revision		Revision as of 12:27, 26 March 2024
Line 167:		Line 167:
	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/>
	<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.


	From the firmware version '''[https://wiki.teltonika-gps.com/view/{{{model\|FMB1YX}}}_firmware_errata 03.25.14]''' iBeacon authentication was introduced. iBeacon authentication works in the same way as iButton authentication. To use authorized iBeacons, the iBeacon list should be filled in the device configurator. Instructions how to list iBeacons in FMB devices can be found '''[https://wiki.teltonika-gps.com/view/{{{model\|FMB1YX}}}_Beacon_List here]'''.		From the firmware version '''[https://wiki.teltonika-gps.com/view/{{{model\|FMB1YX}}}_firmware_errata 03.25.14]''' iBeacon authentication was introduced. iBeacon authentication works in the same way as iButton authentication. To use authorized iBeacons, the iBeacon list should be filled in the device configurator. Instructions how to list iBeacons in FMB devices can be found '''[https://wiki.teltonika-gps.com/view/{{{model\|FMB1YX}}}_Beacon_List here]'''.
Line 174:		Line 172:
	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>}}}

			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 "No Authentification Timeout" is used as a backup option in order to turn on the vehicle. For example if you set the "No Authentification Timeout" to 60 seconds, then you need to turn on the ignition and keep it active for 60 seconds, then the authorization will be successful (it will bypass the iBeacon or iButton authorization) and user will be able to turn on the vehicle on.

	{{{seco_feature\|==SECO==		{{{seco_feature\|==SECO==

← Older revision		Revision as of 16:07, 30 January 2026
Line 179:		Line 179:
	{{{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 194:		Line 194:

	'''Immobilizer scenario is also supported by the {{{model\|FMB1YX}}} device.'''		'''Immobilizer scenario is also supported by the {{{model\|FMB1YX}}} device.'''

			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.

	{{{seco_feature\|==SECO==		{{{seco_feature\|==SECO==