Line 3: |
Line 3: |
| [[Image:Fmb120_green_driving.png|300px|right]] | | [[Image:Fmb120_green_driving.png|300px|right]] |
| | | |
− | When vehicle exceeds on of Max Acceleration, Max Braking or Max Cornering parameters value, scenario is activated, record will be generated and digital output status will be changed to 1 (if configured). You can configure all three parameters in m/s<sup>2</sup> (meter per second squared) units. Scenario is activated until current Acceleration, Braking or Cornering value decreases below parameter value.<br/> | + | When vehicle exceeds the values of Max Acceleration, Max Braking or Max Cornering parameters, a scenario is activated, a record will be generated and digital output status will be changed to 1 (when configured). You can configure all three parameters in m/s<sup>2</sup> (meter per second squared) units. Scenario is activated until current Acceleration, Braking or Cornering value decreases below the parameter value.<br/>Parameters used with Green Driving functionality are given in a table below. |
− | Parameters used with Green Driving functionality are given in a table below. | |
| | | |
| {| class="wikitable" | | {| class="wikitable" |
Line 30: |
Line 29: |
| ===Data output=== | | ===Data output=== |
| ---- | | ---- |
− | Green driving functionality generates events on three cases. If vehicles: | + | Green driving functionality generates events in following case when vehicle's: |
| * Acceleration exceeds defined parameter value. | | * Acceleration exceeds defined parameter value. |
| * Deceleration (braking) exceeds defined value. | | * Deceleration (braking) exceeds defined value. |
| * Cornering force exceeds defined value. | | * Cornering force exceeds defined value. |
− | Program continously monitors and process data from accelerometer/GPS than decides whether harsh event is detected or not. If any of three cases are satisfied event is generated. Record is saved and sent to server (FMB120 must be configured properly). Event value is multiplied by 10 before sending/saving record to get more precision when displaying data*. | + | Program continiously monitors and processes data from accelerometer/GPS and then decides whether harsh event is detected or not. If either of three cases is satisfied, an event is generated. Record is saved and sent to server (FMB120 must be configured properly). 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 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 driver. Output on-time should/can be configured separately for each feature case. |
| | | |
| ===Auto calibration=== | | ===Auto calibration=== |
| ---- | | ---- |
− | # Vehicle is stopped. | + | The process is following: |
− | # Road is straight. | + | # The vehicle is stopped. |
| + | # There is a straight road ahead. |
| # Send SMS ''<span style=color:#F6A83E>auto_calibrate:set</span>''. | | # Send SMS ''<span style=color:#F6A83E>auto_calibrate:set</span>''. |
| # Accelerate to > 30 km/h for 5 sec. | | # Accelerate to > 30 km/h for 5 sec. |
− | # FMB will send response when calibration is success. | + | # FMB will send response when calibration is successfully complete. |
− | Calibration is saved to Internal Flash, after restart should be the same. | + | Calibration is saved to Internal Flash, which means it will stay after a restart. |
| To check autocalibration status send: ''<span style=color:#F6A83E>auto_calibrate:get</span>''. | | To check autocalibration status send: ''<span style=color:#F6A83E>auto_calibrate:get</span>''. |
| | | |