482
edits
Changes
Template:FMB Features settings (view source)
Revision as of 09:08, 15 September 2022
, 09:08, 15 September 2022→Over Speeding
==Eco/Green Driving==
==Eco/Green Driving==
[[Image:EcoGreen_Driving.gif|{{{general|size}}}|right]]<br>
[[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/s<sup>2</sup> units. The scenario is activated until the current Acceleration, Braking, or Cornering value decreases below the set parameter value.<br />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/s<sup>2</sup> units. The scenario is activated until the current Acceleration, Braking, or Cornering value decreases below the set parameter value.<br />Parameters used with ''Eco/Green Driving'' functionality are given in a table below.
<table class="nd-othertables" style="width: 68%;">
<table class="nd-othertables" style="width: 68%;">
{{{FMT100_eco|==Advanced Eco Driving==
{{{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.
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.
<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>
<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>
</tr>
</table>
</table>}}}
}}}
===Data output===
===Data output===
----
----
===Auto calibration===
===Auto calibration===
----
----
The auto-calibration process is following:
The auto-calibration process is as follows:
#The vehicle is stopped.
#The vehicle is stopped.
==Over Speeding==
==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}}}.<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.
[[Image:OverSpeeding.gif|{{{general|size}}}|right]]
[[Image:Over_Speeding.gif|{{{general|size}}}|left]] <br /><br /><br /><br />
<br />
*Scenario settings – defines the priority of over speeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.
*Max speed – it is the maximum 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.
*SMS text – SMS text.
<br />
{{{jamming1|
{{{jamming1|
==Jamming==
==Jamming==
[[Image:Jamming.gif|{{{general|size}}}|right]]
[[Image:Jamming.gif|{{{general|size}}}|right]]
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==
{{{dout_control_via_call_feature|==DOUT Control Via Call==
[[Image:DOUT_Control_Via_Call.gif|{{{general|size}}}|right]]
[[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.<br/>
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:
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.
* 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}}} 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==
{{{immobilizer_feature|==Immobilizer==
[[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, 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.
{{{ibutton_feature|==iButton Read Notification==
{{{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/OFF duration – a value in seconds, for how long {{{text_dout|DOUT1/DOUT2}}} should be active or inactive.
*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|
==GNSS Fuel Counter==
==GNSS Fuel Counter==
[[Image:GNSS_Fuel_Counter.gif|{{{general|size}}}|right]]
[[Image:GNSS_Fuel_Counter.gif|{{{general|size}}}|right]]
To configure ''Fuel Counter'' parameters use fuel consumption norms which are presented in the technical documentation of the vehicle. By default speeds for these fuel consumption norms are: City – 30 km/h, Average - 60 km/h, Highway - 90 km/h. These values can be changed.
When speed is higher than the highway fuel consumption speed, x% of highway fuel consumption is added every extra y km/h, by default [[{{{model|FMB1YX}}}]] adds 20% every 50 km/h of extra speed. For example, the fuel consumption is (1.2 * (Highway Fuel Consumption)) at 140 km/h and (1.4 * (Highway Fuel Consumption)) at 190 km/h.
''Correction coefficient'' is used to correct every value of fuel consumption which is sent to the server through an expression of ((Used Fuel) * ''Correction coefficient''). By default, it is 1, with minimum and maximum values of accordingly 0.01 and 2. For example, when the correction coefficient is 1 and [[{{{model|FMB1YX}}}]] calculates that the amount of used fuel over 35 m distance is 20 ml, the value of 20 ml will be sent to the server, and if correction coefficient is 1.2, the value of 20 * 1.2 = 24 ml will be sent to the server.
''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_feature|==DOUT Control Via Ignition==
{{{dout_control_via_ignition_feature|==DOUT Control Via Ignition==
==Ignition ON Counter==
==Ignition ON Counter==
[[File:Ignition on.gif|right]]
'''Ignition ON Counter''' scenario counts the time spent with the ignition in the resolution of seconds. <br>
'''Ignition ON Counter''' scenario counts the time spent with the ignition in the resolution of seconds. <br>
It is possible to configure a starting value of the counter. Maximum value: '''2147483647''' seconds or 596523.235 hours
It is possible to configure a starting value of the counter. Maximum value: '''2147483647''' seconds or 596523.235 hours
'''NOTE THAT''', when entering a starting value, the value must be in seconds!
'''NOTE THAT''', when entering a starting value, the value must be in seconds!
Example of Ignition On Counter '''I/O''' element:
Example of Ignition On Counter '''I/O''' element:
[[File:Ingintion On counter.gif|left]]
<br></br>
{{{dout_type|
==DOUT 1 Output Type==
[[File:Dout1 output type.gif|right]] '''DOUT 1 Output Type''' functionality sets the initial ''DOUT1'' state. If functionality is configured in ''Normal'' mode digital output inactive state is low and when it is controlled by any scenario digital output is set to high state. Whenever functionality is configured in ''Inverted'' mode digital output inactive state is high and when it is controlled by any scenario digital output is set to low state.<br></br>
[[image:IgnitionOnCounter.gif]]
DOUT1 in '''Normal''' state:
[[File:DoutNormal.jpg|thumb|left|500px]]
<br></br><br></br><br></br><br></br></br>
DOUT1 in '''Inverted''' state:
[[File:InvertedDout.png|thumb|left|500px]]
<br></br><br></br><br></br>
*'''<u>Notice!</u>''' Digital output type control functionality will not affect SMS/GPRS command '''setdigout''' execution. <br></br>
[[File:Alert.png|50px]] <b>Available from Firmware version: [[ {{{model|}}}_firmware_errata|03.27.07.Rev.00]] </b>
}}}
