FMB930 Features settings - Revision history

Justinas.strelciunas at 07:59, 17 August 2023

2023-08-17T07:59:47Z

← Older revision		Revision as of 10:59, 17 August 2023
Line 112:		Line 112:
	[[File:Immobilizer1.png\|{{{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~~/>		From the firmware version '''[https://wiki.teltonika-gps.com/view/{{{model\|FMB1YX}}}_firmware_errata 03.25.14]''' Beacon authentication was introduced. Beacon authentication works in the same way as iButton authentication. To use authorized Beacons, the Beacon list should be filled in the device configurator. Instructions how to list Beacons in FMB devices can be found '''[https://wiki.teltonika-gps.com/view/{{{model\|FMB1YX}}}_Beacon_List here]'''.
	~~<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~~.

			By using Beacon authorization, the immobilizer feature can be used with devices that don't have a 1-wire data connection available.

	~~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]'''~~.		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 Beacon ID is attached, {{{text_dout\|DOUT1/DOUT2}}} turns OFF. After Beacon 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 '' List Check for Authorization'' parameter is enabled, the authorization will be successful only if the attached Beacon is specified in the Beacon list.<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 make an idenfication with the Beacon again.

	~~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>

Justinas.strelciunas at 07:44, 17 August 2023

2023-08-17T07:44:06Z

← Older revision		Revision as of 10:44, 17 August 2023
Line 123:		Line 123:


	~~{{{gnss_fuel\|~~
	==GNSS Fuel Counter==		==GNSS Fuel Counter==

Line 135:		Line 134:

	''Fuel Consumption on Idling'' is used to calculate fuel consumption when the ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with a minimum and maximum of accordingly 0 and 5 l/h. This parameter is less than 1.0 l/h for almost all diesel cars and is equal to about 1.5 – 2.0 l/h for gasoline cars.		''Fuel Consumption on Idling'' is used to calculate fuel consumption when the ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with a minimum and maximum of accordingly 0 and 5 l/h. This parameter is less than 1.0 l/h for almost all diesel cars and is equal to about 1.5 – 2.0 l/h for gasoline cars.
	~~}}}~~

	==DOUT Control Via Ignition==		==DOUT Control Via Ignition==

Justinas.strelciunas: /* DOUT Control Via Call */

2023-08-17T07:43:18Z

DOUT Control Via Call

← Older revision		Revision as of 10:43, 17 August 2023
Line 108:		Line 108:
	* {{{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.		* {{{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==

	[[File:Immobilizer1.png\|{{{general\|size}}}\|right]]		[[File:Immobilizer1.png\|{{{general\|size}}}\|right]]
Line 120:		Line 120:

	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>

Justinas.strelciunas at 07:31, 17 August 2023

2023-08-17T07:31:35Z

← Older revision		Revision as of 10:31, 17 August 2023
Line 122:		Line 122:
	<br/><br/><youtube>gjuiJjAejWU</youtube>}}}		<br/><br/><youtube>gjuiJjAejWU</youtube>}}}

	~~{{{ibutton_feature\|==iButton Read Notification==~~
	~~[[Image:IButton_Read_Notification.gif\|{{{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 both iButton List Checking and Depend on Ignition are disabled – Output is triggered.
	*If iButton List Checking is enabled and Depend on Ignition is disabled – Output is triggered only if iButton is in the list.
	*If iButton List Checking is disabled but Depend on Ignition is enabled – Output is triggered only if ignition is off.
	*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}}} 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/>}}}~~

	{{{gnss_fuel\|		{{{gnss_fuel\|

Justinas.strelciunas: /* Network Jamming */

2023-08-17T07:04:51Z

Network Jamming

← Older revision		Revision as of 10:04, 17 August 2023
Line 83:		Line 83:

	==Network Jamming==		==Network Jamming==
	~~<br>~~
	[[File:Network Jamming.png\|{{{general\|size}}}\|right]]		[[File:Network Jamming.png\|{{{general\|size}}}\|right]]

Justinas.strelciunas: /* Network Jamming */

2023-08-17T07:04:20Z

Network Jamming

← Older revision		Revision as of 10:04, 17 August 2023
Line 83:		Line 83:

	==Network Jamming==		==Network Jamming==
			<br>
	[[File:Network Jamming.png\|{{{general\|size}}}\|right]]		[[File:Network Jamming.png\|{{{general\|size}}}\|right]]

Justinas.strelciunas: /* Over Speeding */

2023-08-17T07:03:58Z

Over Speeding

← Older revision		Revision as of 10:03, 17 August 2023
Line 79:		Line 79:
	*SMS text – SMS text.		*SMS text – SMS text.
	<br />		<br />
			<br>
			<br>

	==Network Jamming==		==Network Jamming==

Justinas.strelciunas: /* Eco/Green Driving */

2023-08-17T07:03:11Z

Eco/Green Driving

← Older revision		Revision as of 10:03, 17 August 2023
Line 67:		Line 67:
	Calibration is saved to internal flash memory, which means it will stay after a reset.		Calibration is saved to internal flash memory, which means it will stay after a reset.
	To check auto-calibration status send a following short text message to the {{{model_2\|FMB}}} device: ''"auto_calibrate:get"''.		To check auto-calibration status send a following short text message to the {{{model_2\|FMB}}} device: ''"auto_calibrate:get"''.
			<br>

	==Over Speeding==		==Over Speeding==

Justinas.strelciunas: /* Network Jamming */

2023-08-17T07:02:37Z

Network Jamming

← Older revision		Revision as of 10:02, 17 August 2023
Line 89:		Line 89:

	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]'''
			<br>
	<br>		<br>
	<br>		<br>

Justinas.strelciunas: /* Network Jamming */

2023-08-17T07:02:01Z

Network Jamming

← Older revision		Revision as of 10:02, 17 August 2023
Line 89:		Line 89:

	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]'''
			<br>
			<br>
	<br>		<br>
	<br>		<br>