Changes

Template:FMB Features settings (view source)

Revision as of 12:48, 17 June 2021

17 bytes removed , 12:48, 17 June 2021

m

no edit summary

Line 1: Line 1:

==Eco/Green Driving==

−

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

+

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

−

When vehicle parameters exceed the values of ''Max Acceleration'', ''Max Braking'' or ''Max Cornering'' parameters, the scenario is activated: a record is generated, and digital output status is changed to 1 when configured. You can configure all three parameters in m/s2 units. The scenario is activated until the current Acceleration, Braking, or Cornering value decreases below the set parameter value. Parameters used with ''Eco/Green Driving'' functionality are given in a table below.

+

When vehicle parameters exceed the values of ''Max Acceleration'', ''Max Braking'' or ''Max Cornering'' parameters, the scenario is activated: a record is generated, and the digital output status is changed to 1 when configured. You can configure all three parameters in m/s2 units. The scenario is activated until the current Acceleration, Braking, or Cornering value decreases below the set parameter value. Parameters used with ''Eco/Green Driving'' functionality are given in a table below.

Line 61: Line 61:

{{{FMT100_eco|==Advanced Eco Driving==

+

From 03.25.14.Rev.03 base firmware version new '''[[FMB120_Parameter_list|parameter]]''' has been added (Eco Driving Maximum and Eco Driving Average) to '''[[FMT100]]''' device. This parameter is '''enabled''' by default.

Line 77: Line 78:

<td style="width: 8%; text-align:left;">If Eco/Green driving is enabled and accelerometer is selected as the data source, enabling Eco Driving Maximum will cause records with Eco Driving event Maximum value to be saved and send to the server.</td>

</tr>

−

</table>

+

</table>}}}

−

}}}

+

−

~~ ~~

===Data output===

----

Line 98: Line 98:

==Over Speeding==

−

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}}}. Scenario is active until detected speed decreases below the set parameter value.

Line 106: Line 105:

−

~~ ~~

+

{{{jamming1|

==Jamming==

Line 130: Line 129:

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 ~~which~~ is on the authorized numbers list.

+

The scenario is activated and digital output is ON when a call is received from a number that is on the authorized numbers list.

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

Line 146: Line 143:

[[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, 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.

+

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.

−

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

Line 159: Line 156:

This functionality allows users to see when iButton is read. {{{text_dout|DOUT1/DOUT2}}} turns on for a configured duration and after DOUT ON duration ends {{{text_dout|DOUT1/DOUT2}}} does not turn on even if iButton is left attached.

−

[[Image:IButton_Read_Notification.gif|{{{general|size}}}|left]]~~ ~~ }}}

+

[[Image:IButton_Read_Notification.gif|{{{general|size}}}|left]] }}}

+

{{{gnss_fuel|

==GNSS Fuel Counter==

Sandra.Gasyte

Administrators

2,556

edits