Changes

         <td style="width: 8%; text-align:left">Which source (GPS or accelerometer) data will be collected from.</td>

         <td style="width: 8%; text-align:left">Which source (GPS or accelerometer) data will be collected from.</td>

     </tr>

     </tr>

</table>

</table>

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.  

When this parameter is enabled device uses advanced Eco Driving algorithm and send different IO (maximum, average) elements instead of IO to server. When enabled, device does not send Green Driving value IO element '''[[FMB120_AVL_ID|254]]'''.

When this parameter is enabled device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to server. When enabled, device does not send Green Driving value IO element '''[[FMB120_AVL_ID|254]]'''.

<br /><br />'''Eco Driving Average -''' If Eco/Green driving is enabled and accelerometer is selected as the data source, enabling Eco Driving Average will cause records with Eco Driving event Average value to be saved and send to server.

<br /><br />'''Eco Driving Average -''' If Eco/Green driving is enabled and accelerometer is selected as the data source, enabling Eco Driving Average will cause records with Eco Driving event Average value to be saved and send to the server.

'''Eco Driving Maximum -''' 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 server.

'''Eco Driving Maximum -''' 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.

===Data output===

===Data output===

----

----

Data from accelerometer/GPS are continiously monitored and processed and are used to decide whether a harsh event has occured. If either of three cases is satisfied, an event is generated and a record is saved and sent to the server ({{{model|FMB1YX}}} must be properly configured in order to send the record). Event value is multiplied by 100 before sending/saving record to get more precision when displaying data.{{{text_dout|<br/>{{{dout|info}}}}}}

Data from accelerometer/GPS are continuously monitored and processed and are used to decide whether a harsh event has occurred. If either of three cases is satisfied, an event is generated and a record is saved and sent to the server ({{{model|FMB1YX}}} must be properly configured in order to send the record). Event value is multiplied by 100 before sending/saving record to get more precision when displaying data.{{{text_dout|<br/>{{{dout|info}}}}}}

===Auto calibration===

===Auto calibration===

'''Note that this scenario will not work with Deep Sleep, Ultra Deep Sleep and Online Deep Sleep modes, since they disable the device's GSM module to save power.'''

'''Note that this scenario will not work with Deep Sleep, Ultra Deep Sleep and Online 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.  

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

[[Image:{{{model|FMB1YX}}}_Immobilizer.png|{{{immobilizer|size}}}|right]]

[[Image:{{{model|FMB1YX}}}_Immobilizer.png|{{{immobilizer|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, 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 ''iButton List Check'' parameter is enabled, the authorization will be successful only if the attached iButton is specified in iButton list.<br/>{{{immobilizer_dout|info}}}

<br/><br/>

<br/><br/>

Ignition off timeout parameter is used to set the duration after which authorization is activated, when ignition is turned off. For example, if 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.

Ignition off timeout parameter is used to set the duration after which authorization is activated, when the ignition is turned off. For example, if 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.

[[Image:{{{model|FMB1YX}}}_GNSS_Fuel_Counter.png|{{{gnss_fuel_counter|size}}}|right]]

[[Image:{{{model|FMB1YX}}}_GNSS_Fuel_Counter.png|{{{gnss_fuel_counter|size}}}|right]]

#To configure ''Fuel Counter'' parameters use fuel consumption norms which are presented in 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.

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

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

#''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 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 ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with 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_feature|==DOUT Control Via Ignition==

{{{dout_control_via_ignition_feature|==DOUT Control Via Ignition==