FMM001 Features settings

Eco/Green Driving

size

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/s² 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.
Output Control	Which Digital Output will be used for accesory (buzzer, LED and etc.) activation/deactivation.
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.

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 (FMM001 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.

Load video

YouTube

YouTube might collect personal data. Privacy Policy

Continue Dismiss

Auto calibration

---

The auto-calibration process is following:

1. The vehicle is stopped.
2. There is a straight road ahead.
3. Send SMS "auto_calibrate:set" to the FMB device.
4. Accelerate to >30 km/h for 5 sec.
5. 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. To check auto-calibration status send a following short text message to the FMB device: "auto_calibrate:get".

Over Speeding

When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated and digital output status is changed to 1 when configured.
Scenario is active until detected speed decreases below the set parameter value. Configurable parameters:

size

• Scenario settings – defines priority of over speeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.
• Max speed – it is max allowed speed which can be reached. If speed exceeded configured value, then event will occur.
• Send SMS to – GSM number to which SMS event will be sent.
• SMS text – SMS text.

{{#switch: FMM001 |FMT100 |FMC880| FMM880 |FMC800 |FMM800 |FMM920 |FMM130 |FMM230 = |#default =

Immobilizer

Note: Immobilizer scenario requires a device with 1-Wire support or at least 1 DOUT and BLE support.

Function

Immobilizer scenario purpose is to prohibit an unauthorized exploitation of a vehicle. This is accomplished by DOUT controlling the relay, which in turn controls the starter or fuel pump.

When attempting to start the vehicle:

• Selected control DOUT turns high when ignition is detected, preventing the vehicle from starting.
• If iButton is attached or BLE beacon is detected, then DOUT turns low and it is possible to start vehicle.

Authorization

In case if iButton list check is enabled, then device checks for read iButton match in iButton list or if Beacon list check enabled, checks for match in Beacon list (Beacon Detection has to be set to Configured), or if both enabled checks in both lists. If match is not found, then driver will not be able to use vehicle. If driver did not authorize and ignition is turned off, after 25 seconds DOUT will be set to idle state.

From firmware version 04.00.00.Rev.13 and above, the "Authorization ID List Checking" option None was removed as part of a security improvement. Devices now require selecting 1-Wire, RFID (for RS232-capable devices), or Beacons. If the Authorization ID list is empty, the behavior is equivalent to the previous None option - any iButton, RFID card, or Beacon disables the Immobilizer.

Note: iButton list or Beacon list must be configured for proper function. When using Beacon list check, Beacon Detection should be set to Configured. If Beacon Detection is set to All, any visible beacon will be able to turn off the immobilizer.

Immobilizer Authorization Timeout

The authorization timeout is a function that ensures the vehicle remains authorized for a certain period of time after a successful authorization. If the timeout expires, the vehicle is considered unauthorized.

When the vehicle is authorized, the time is stored in the device. This marks the start of the authorization period. On subsequent authorizations, the code calculates the time difference between the current time and the stored authorization time. If the difference is greater than the specified authorization timeout (IgnitionOffTmo, parameter ID = 60068), it means that the authorization period has expired, and the vehicle will be considered unauthorized. This ensures that the vehicle remains authorized only for a specific duration. Once that duration elapses, the vehicle is required to go through the authorization process again.

No Authentication Timeout

No Authentication Timeout is a configurable duration that specifies the maximum allowed time without any authorization during the Wait Authorization state. If none of these authorization criteria are met, the system needs a way to handle situations where the vehicle remains in the Wait Authorization state for an extended period without any authorization. If the No Authentication Timeout value is configured to a non-zero value, the code tracks the time elapsed since the vehicle entered the Wait Authorization state. If this elapsed time exceeds the parameter value, it triggers an action to automatically transition the system to an Authorized state.

If the specified timeout duration is reached, the system assumes authorization to avoid prolonged waiting times and allows the vehicle to proceed with authorized operations.

Authorization Timeout Limit

Authorization Timeout Limit Configures the time window for successful authorization. If authorization fails within this period, an unauthorized event record is generated. Other record generation is not affected.

Note: Immobilizer records are only created if ignition is ON.

Sleep Mode Considerations

Immobilizer scenario can block device from going to sleep mode when Ignition Off timeout (60068) is configured with higher timeout than Sleep Mode Timeout (103) and when Immobilizer Scenario Settings and Output Control are configured. In such case the device will go to sleep mode after Immobilizer Ignition Off timeout passes.

Authorized Read Notification

Important: iButton Read Notification feature has been replaced with Authorized Read Notification starting from Firmware Ver.03.30.00

Authorized read notification feature allows the control of selected DOUT for a configured period, when Authorized ID is read using 1-Wire, RFID Reader or when Authorized Beacon is detected. If Authorized ID List is empty or Beacon detection is set to All, then any detected ID or Beacon can control selected DOUT. Parameter Depend on Ignition allows to disable DOUT control, while Ignition is being detected. It is necessary to select at least one source for this functionality to work.

Authorized Read Notification parameters:

• Output Control – available scenario settings for module Digital output activation/deactivation
• DOUT ON Duration – a value in seconds, for how long DOUT1/DOUT2 should be active or inactive.
• Authorization ID List Checking - Provides Authorized ID information from a designated source.
• FMB devices that do not have RS232 will have support for 1-Wire and Beacon only.
• FMB devices that do not have RS232 and 1-Wire will have support for Beacon only.
• Depend on Ignition - Output will be triggered only if ignition is off.

Note: Authorized read notification is disabled in deep sleep, online deep sleep and ultra deep sleep modes.

GNSS Fuel Counter

size

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 FMM001 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 the correction coefficient is 1 and FMM001 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 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

This feature allows direct control of DOUT (Digital Output) by the configured ignition source status. When enabled, the function will monitor ignition status, and once the ignition changes state from On to Off after the configured Ignition OFF Timeout, the selected DOUT will be turned On.

Turning DOUT Off is possible with sufficient voltage applied to the configured DIN (Digital Input) or by turning on the ignition.

Voltage requirements:

• DIN1 - 7.5V,
• DIN2-4 – 2.5V.
  
  

Parameter name	Description
DOUT Control	Scenario controls configured DOUT if ignition timeout exceeds its limit
DOUT Deactivation Via DIN	DOUT is turned off if configured DIN is in on (voltage applied) state
Ignition Off timeout	Duration (in seconds) after which DOUT is turned on, when ignition is turned off

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