Changes

==Eco/Green Driving==

==Eco/Green Driving==

[[Image:{{{model|FMB1YX}}}_Eco_Green_Driving.png|275px|right]]

[[Image:{{{model|FMB1YX}}}_Eco_Green_Driving.png|frameless|upright=0.95|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² units. Scenario is activated until 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 digital output status is changed to 1 when configured. You can configure all three parameters in m/s² units. Scenario is activated until 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.

==Over Speeding==

==Over Speeding==

[[Image:{{{model|FMB1YX}}}_Over_Speeding.png|280px|right]]

[[Image:{{{model|FMB1YX}}}_Over_Speeding.png|frameless|upright=0.95|right]]

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.

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.

==Jamming==

==Jamming==

[[Image:{{{model|FMB1YX}}}_Jamming.png|310px|right]]

[[Image:{{{model|FMB1YX}}}_Jamming.png|frameless|upright=0.95|right]]

When jamming is detected the scenario is activated, an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}} once ''Jamming'' timeout runs out. If jamming ends during timeout countdown no event will be generated{{{text_dout| and output will not be controlled}}}.<br/>''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.

When jamming is detected the scenario is activated, an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}} once ''Jamming'' timeout runs out. If jamming ends during timeout countdown no event will be generated{{{text_dout| and output will not be controlled}}}.<br/>''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.

==GNSS Fuel Counter==

==GNSS Fuel Counter==

[[Image:{{{model|FMB1YX}}}_GNSS_Fuel_Counter.png|325px|right]]

[[Image:{{{model|FMB1YX}}}_GNSS_Fuel_Counter.png|frameless|upright=0.95|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 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.

{{{dout_control_via_call|== DOUT Control Via Call==

{{{dout_control_via_call|== DOUT Control Via Call==

[[Image:{{{model|FMB1YX}}}_DOUT_Control_Via_Call.png|300px|right]]

[[Image:{{{model|FMB1YX}}}_DOUT_Control_Via_Call.png|frameless|upright=0.95|right]]

Scenario is activated and digital output is ON when call is received from a number which is on the authorized numbers list.<br/>

Scenario is activated and digital output is ON when call is received from a number which is on the authorized numbers list.<br/>

{{{immobilizer_feature|==Immobilizer==

{{{immobilizer_feature|==Immobilizer==

[[Image:{{{model|FMB1YX}}}_Immobilizer.png|225px|right]]

[[Image:{{{model|FMB1YX}}}_Immobilizer.png|frameless|upright=0.95|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.

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.