Changes

[[Image:Fmb120_green_driving.png|300px|right]]

[[Image:Fmb120_green_driving.png|300px|right]]

When vehicle exceeds the values of ''Max Acceleration'', ''Max Braking'' or ''Max Cornering'' parameters, a 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² (meter per second squared) units. Scenario is activated until current Acceleration, Braking or Cornering value decreases below the set parameter value.<br/>Parameters used with ''Green Driving'' functionality are given in a table below.

When vehicle exceeds 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² (meter per second squared) units. Scenario is activated until current Acceleration, Braking or Cornering value decreases below the set parameter value.<br/>Parameters used with ''Green Driving'' functionality are given in a table below.

{| class="wikitable"

{| class="wikitable"

* Cornering force exceeds defined value.

* Cornering force exceeds defined value.

Data from accelerometer/GPS are continiously monitored and processed and is used to decide whether a harsh event is detected. If either of three cases is satisfied, an event is generated. Record is saved and sent to the server (FMB120 must be properly configured in order to send the record). Event value is multiplied by 10 before sending/saving record to get more precision when displaying data.

Data from accelerometer/GPS are continiously monitored and processed and is used to decide whether a harsh event is detected. If either of three cases is satisfied, an event is generated. Record is saved and sent to the server (FMB120 must be properly configured in order to send the record). Event value is multiplied by 10 before sending/saving record to get more precision when displaying data.

Digital output 1 or digital output 2 can be activated for a period of time to warn the driver. Output on-time should/can be configured separately for each feature case.

Digital output 1 or digital output 2 can be activated for a period of time to warn the driver. Output on-time is configured separately for each feature case.

===Auto calibration===

===Auto calibration===

# Send SMS ''"auto_calibrate:set"''.

# Send SMS ''"auto_calibrate:set"''.

# Accelerate to > 30 km/h for 5 sec.

# Accelerate to > 30 km/h for 5 sec.

# FMB will send a response when calibration is successfully complete.

# FMB will send a response when calibration is completed successfully .

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: ''"auto_calibrate:get"''.

To check auto-calibration status send: ''"auto_calibrate:get"''.

[[Image:Fmb120 over speeding.png|300px|right]]

[[Image:Fmb120 over speeding.png|300px|right]]

When vehicle speed exceeds configured maximum speed value a scenario is activated, a record is generated and digital output status is changed to 1 (if configured).<br/>Scenario is active until current speed decreases below the set parameter value.

When vehicle speed exceeds configured maximum speed value the scenario is activated:a record is generated and digital output status is changed to 1 (if configured).<br/>Scenario is active until current speed decreases below the set parameter value.

<br/><br/><br/><br/><br/><br/><br/><br/><br/>

<br/><br/><br/><br/><br/><br/><br/><br/><br/>

[[Image:Fmb120_jamming.png|300px|right]]

[[Image:Fmb120_jamming.png|300px|right]]

When jamming is detected a scenario is activated, a record is generated and digital output status is changed to 1 (if configured).<br/>Jamming timeout time can be configured. Digital output control and jamming event will be generated once ''Jamming'' timeout runs out. If jamming ends during timeout countdown no event will be generated 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: a record is generated and digital output status is changed to 1 (if configured).<br/>Jamming timeout time can be configured. Digital output control and jamming event will be generated once ''Jamming'' timeout runs out. If jamming ends during timeout countdown no event will be generated 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.

<br/><br/><br/><br/><br/>

<br/><br/><br/><br/><br/>

# To configure these 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 these 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.

# When speed is higher than the highway fuel consumption speed, x% of highway fuel consumption is added every extra y km/h, by default FMB120 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 FMB120 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 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 FMB120 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 FMB120 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 about 1.5 – 2.0 l/h for gasoline cars.

# ''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 about 1.5 – 2.0 l/h for gasoline cars.

==DOUT controls==

==DOUT controls==

Please refer to [[FMB120 DOUT controls|DOUT controls]].

Please refer to [[FMB120 DOUT controls|DOUT controls]].