FMM880 Features settings
Eco/Green Driving
When vehicle parameters exceed the values of Max Acceleration, Max Braking or Max Cornering parameters, the scenario is activated: a record is generated. You can configure all three parameters in m/s2 units. The scenario is activated until the current Acceleration, Braking, or Cornering value decreases below the set parameter value.
Parameters used with Eco/Green Driving functionality are given in a table below.
GPS Source
When selected source is GPS device calculates harsh driving values from GPS data at 1 Hz frequency. This means green driving time accuracy is 1s. Acceleration is calculated every 1 second, based on speed difference between GPS samples.
- Vehicle speed must be equal or greater than 10 km/h for acceleration/braking.
- Vehicle speed must be equal or greater than 30 km/h for cornering.
While using Green driving (GPS) harsh cornering is determined by calculating an angle difference and the speed change in m/s between two NMEA coordinates. This leads to calculation and approximation of angular speed of the vehicle in m/s. It is recommended to use accelerometer data to measure harsh driving as GPS source is less accurate.
While Green Driving event is active, two records will be created every second - Event Type and Event Duration.
| Parameter name | Description |
|---|---|
| Scenario Settings | Enable/Disable Green driving functionality |
| Max Acceleration | Value which can be reached while accelerating without triggering harsh acceleration event. |
| Max Braking Acceleration | Value which can be reached while braking without triggering harsh braking event. |
| Max Cornering Acceleration | Value which can be reached while cornering without triggering harsh cornering event. |
| Source | Which source (GPS or accelerometer) data will be collected from. |
| Advanced Eco Driving | When this parameter is enabled device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to server. More details about this option is decribed below. |
| Eco/Green Driving Duration | If enabled, additional record with Eco/Green Driving event duration (ms) will be saved and send to server. When GPS is selected as the data source duration accuracy will be in seconds. |
| Send SMS to | GSM number of receiver which will get notifications of Eco/Green Driving feature. |
| SMS Text | SMS text, which the receiver will get. |
Simple Eco Driving
For simple eco driving vehicle speed must be equal or greater than 10 km/h for acceleration/braking and equal or greater than 30 km/h for cornering.
Noise filter is used to filter out small accelerometer spikes in cases when vehicle is not harsh driving, but drove over a speed bump or a hole.
Noise filter acceptance value is 50%, which means the shortest harsh driving event must last at least 500 ms. This filter generates only one record if harsh driving lasts longer than 1 second.
Advanced Eco Driving
Harsh driving event is detected when acceleration on a specific axis is above the configured threshold for the defined duration. Then, when acceleration on specific axis falls below the threshold for defined „event end duration, an eventual record is made as configured and an SMS message is sent (if configured).
Important: For eco driving with accelerometer to work, auto calibration must not be empty (default or calibrated) and ignition must be on.
The advanced eco driving does not have the green driving value I/O element (AVL ID 254). It is substituted with eco driving average, maximum and duration values.
| Parameter name | Description |
|---|---|
| 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 the server. |
Eco/Green Driving scenario is supported by the FMM880 device.
Data output
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 (FMM880 must be properly configured in order to send the record). Event value is multiplied by 100 before sending/saving records to get more precision when displaying data.
Data output is also supported by the FMM880 device.
Auto calibration
The auto-calibration process is as follows:
- The vehicle is stopped.
- There is a straight road ahead.
- Send SMS "auto_calibrate:set" to the FMB device.
- Accelerate to >30 km/h for 5 sec.
- FMB will send a response when calibration is completed successfully.
Calibration is saved to internal flash memory, which means it will remain after a reset. To check auto-calibration status, send the following short text message to the FMB device: "auto_calibrate:get".
Auto calibration is also supported by the FMM880 device.
Over Speeding
When vehicle speed exceeds the configured maximum speed value, the scenario is activated, and an event record is generated. Detected speed has to be greater than (configured max speed + 3% of configured max speed) for the overspeeding event to start. To stop the overspeeding event, detected speed has to be lower than (configured max speed - 3% of configured max speed). Configurable parameters:
- Scenario settings – defines priority of over speeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.
- Max speed – it is the max allowed speed which can be reached. If speed exceeds the configured value, then an event will occur.
- Send SMS to – GSM number to which an SMS event will be sent.
- SMS text – SMS text.
Over Speeding scenario is supported by the FMM880 device.
Jamming scenario is also supported by the FMM880 device.
GNSS Fuel Counter
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, FMM880 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 the expression ((Used Fuel) * Correction coefficient). By default, it is 1, with minimum and maximum values of 0.01 and 2, respectively. For example, when the correction coefficient is 1 and FMM880 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; if the 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 minimum and maximum of 0 and 5 l/h, respectively. This parameter is usually less than 1.0 l/h for most diesel cars and around 1.5 – 2.0 l/h for gasoline cars.
GNSS Fuel Counter functionality is also supported by the FMM880 device.
Ignition ON Counter
Overview
The Ignition ON Counter tracks the total time the ignition has been active, measured in seconds. This counter operates based on your selected Ignition source, which determines when counting starts and stops.
How It Works
- You can set a starting counter value up to 2147483647 seconds.
- The counter continues from where it left off each time the ignition turns ON again.
- When the maximum value is reached, the counter automatically resets to 0.
- The counter value is saved to internal memory when ignition turns OFF, ensuring data accuracy in case of a restart.
Important Notes
- Performing a device reset will NOT return the counter to its original configured value.
- The internal memory is updated each time the ignition turns OFF.
- Proper function requires correct configuration of your Ignition source
Configuration
1. Enable Ignition ON counter (ID 13500)
- 0 - disabled
- 1 - enabled
2. Use the "Ignition On Counter value" parameter to set the initial starting value (in seconds) from which the device will begin counting (ID 13501).