Eco-Drive Parameters Description

2020/08
VILNIUS

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
0
support@ruptela.com | www.ruptela.com
Contents
1 Preface................................................................................................................................... 3
1.1 Introduction ..................................................................................................................... 3
1.2 Document application ....................................................................................................... 3
1.3 Legal notice ..................................................................................................................... 3
1.4 Document change log ....................................................................................................... 3
2 Eco-Drive parameter compatibility with tracking devices ............................................................. 5
3 Engine state detection logic ..................................................................................................... 6
3.1 Detection based on “Engine” field settings in “Data collection” section .................................. 6
3.2 Detection based on “Custom engine source” field settings in “Eco-drive” section .................... 8
3.2.1 Custom engine source – feature description ................................................................. 8
3.2.2 Custom engine source – configuration ......................................................................... 9
3.2.3 Custom engine source – operation examples .............................................................. 11
3.2.4 Calculate data only when engine is on ....................................................................... 12
4 Ignore RPM values when fuel rate is below defined limit ........................................................... 13
5 Ignore over speeding when fuel rate is below defined limit ....................................................... 14
6 Ignore RPM values when angle of inclination is above defined limit ........................................... 15
7 ECO Driving parameters......................................................................................................... 16
7.1 ECO max speed .............................................................................................................. 16
7.2 ECO overspeeding timer .................................................................................................. 16
7.3 ECO RPM in red band timer ............................................................................................. 17
7.4 ECO max RPM ................................................................................................................ 17
7.5 ECO braking counter ....................................................................................................... 17
7.6 ECO extreme harsh brake counter .................................................................................... 18
7.7 ECO harsh acceleration counter ....................................................................................... 19
7.8 ECO idling time............................................................................................................... 20
7.9 ECO cruise control timer .................................................................................................. 20
7.10 ECO engine on timer ....................................................................................................... 21
7.11 ECO RPM in green band distance ..................................................................................... 21
7.12 ECO RPM in red band distance ......................................................................................... 21
7.13 ECO normal speed distance ............................................................................................. 22
7.14 ECO cruise control distance ............................................................................................. 22
7.15 ECO cornering counter .................................................................................................... 23
7.16 ECO idling event ............................................................................................................. 23
7.17 ECO Absolute idling time ................................................................................................. 24

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
1
support@ruptela.com | www.ruptela.com
 7.18 ECO braking value .......................................................................................................... 24
7.19 ECO acceleration value .................................................................................................... 25
7.20 ECO cornering value ....................................................................................................... 26
8 Extended ECO drive parameters ............................................................................................. 27
8.1 Extended parameters for FM4 devices .............................................................................. 27
8.2 ECO fuel used while idling ............................................................................................... 30
8.3 ECO free rolling distance ................................................................................................. 30
8.4 ECO engine overloaded distance ...................................................................................... 30
8.5 ECO engine overloaded fuel used ..................................................................................... 30
8.6 ECO overspeeding distance ............................................................................................. 30
8.7 ECO overspeeding fuel used ............................................................................................ 30
8.8 ECO cruise control on distance ......................................................................................... 31
8.9 ECO cruise control on fuel used ....................................................................................... 31
8.10 ECO highest gear distance ............................................................................................... 31
8.11 ECO highest gear fuel used ............................................................................................. 31
8.12 ECO RPM range1 distance ............................................................................................... 31
8.13 ECO RPM range1 fuel used .............................................................................................. 31
8.14 ECO RPM range2 distance ............................................................................................... 31
8.15 ECO RPM range2 fuel used .............................................................................................. 31
8.16 ECO RPM range3 distance ............................................................................................... 32
8.17 ECO RPM range3 fuel used .............................................................................................. 32
8.18 ECO RPM range4 distance ............................................................................................... 32
8.19 ECO RPM range4 fuel used .............................................................................................. 32
8.20 ECO engine braking distance ........................................................................................... 32
8.21 ECO stops counter .......................................................................................................... 32
8.22 ECO braking distance ...................................................................................................... 33
8.23 ECO braking duration ...................................................................................................... 33
8.24 ECO retarder duration ..................................................................................................... 33

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
2
support@ruptela.com | www.ruptela.com
1 Preface
1.1 Introduction
The aim of this solution is to teach drivers fuel efficient driving and to cut transport operation costs. The
main principles of Eco-Drive are to drive safely and avoid wasting fuel. This also helps to reduce damage
to the vehicle, environment and people’s health.
A variety of reports on fuel efficient driving allow to analyse drivers’ performance and improve where
needed. The data to enable Eco-Drive can be gathered from vehicles on-board computer, accelerometer
and GPS. Data is sorted into a number of different Eco-Drive parameters, which are then processed in
real time transport monitoring and control system TrustTrack, which provides you with the insights on
how to reduce and optimize fuel consumption.

1.2 Document application

This feature description applies to FM devices with the latest firmware version in them.

You can get the latest firmware and configurator from our documentation website: doc.ruptela.lt

1.3 Legal notice

Copyright © 2020 Ruptela. All rights reserved. Reproduction, transfer, distribution or storage of parts or
all of the contents in this document in any form without the prior written permission of Ruptela is
prohibited. Other products and company names mentioned in this document are trademarks or trade
names of their respective owners.

1.4 Document change log

Date Version Change details
2015-12-03 1.0 Initial draft.
2016-02-22 1.1 Various description improvements.
2016-06-22 1.2 New data sources (GPS+CAN and GPS+OBD) included in the description.
2016-10-10 1.3 Added a description for engine’s state detection logic.
2016-11-24 1.4 Changes related with the “Alternative data source selection” check box.
2016-12-07 1.5 Corrections in the “Engine state detection logic” chapter.
2017-01-06 1.6 Voltage ranges defined in the “Engine state detection logic” chapter.
2017-02-13 1.7 Custom engine state description in the “Engine state detection logic” chapter.
Option to ignore RPM values when fuel rate is below defined limit;
2017-04-14 1.8 “ECO braking counter” and “ECO extreme and harsh brake counter”
parameters calculation mechanism description improved.
New “ECO RPM in red band distance” IO parameter;
2017-05-17 1.9
Ignore over speeding, when the fuel rate is below the set limit.
2017-08-23 1.10 Review of the “ECO driving idling event” description.
2017-09-18 1.11 Added a new “ECO engine braking distance” parameter.
2017-12-08 1.12 Added description for the “Calculate data only when engine is on” function.
New extended parameters added: “ECO stops counter”, “ECO braking
2018-05-29 1.13
distance”, “ECO braking duration”, “ECO retarder duration”.
FM3 generation devices removed. Descriptions of “ECO braking counter”
2018-09-03 1.14
and “ECO extreme harsh brake counter” parameters updated.
2020-04-07 1.15 Parameter compatibility table updated.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
3
support@ruptela.com | www.ruptela.com
 Parameter compatibility table is updated.
Section “Ignore RPM values when angle of inclination is above defined limit”
2020-07-20 1.16
is added.
Section “Engine state detection logic” is updated.
2020-08-13 1.17 Section “Extended ECO drive parameters” is corrected.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
4
support@ruptela.com | www.ruptela.com
2 Eco-Drive parameter compatibility with tracking devices
FM-Eco4
FM-Tco4 HCV
Parameter HCV5 LCV5 Pro5 Trace5 FM-Pro4 FM-Eco4 S FM-Plug4
FM-Tco4 LCV
FM-Eco4 T
ECO max speed • • • • • • • •
ECO overspeeding •
timer • • • • • • •
ECO RPM in red
band timer • • • • • •
ECO max RPM • • • • • •
ECO brake counter • • • • • • • •
ECO extreme and •
harsh brake • • • • • • •
counter
ECO harsh •
acceleration • • • • • • •
counter
ECO idling timer • • • • • • • •
ECO cruise control
timer • • • • •
ECO engine on •
timer • • • • • • •
ECO RPM in green
band distance • • • • • •
ECO RPM in red
band distance1 • • • • •
ECO normal speed •
distance • • • • • • •
ECO cruise control
distance • • • • •
ECO cornering •
counter • • • • • • •
ECO idling event • • • • • • • •
ECO Absolute idling •
time • • • • • • •
ECO braking value • • • • • • • •
ECO acceleration •
value • • • • • • •
ECO cornering •
value • • • • • • •
1
This parameter is available only for HCV5, Pro5, FM-Tco4 HCV and FM-Pro4 devices. To enable this parameter for
the 4th generation devices, you must use v1.1 protocol version.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
5
support@ruptela.com | www.ruptela.com
3 Engine state detection logic
Engine state detection logic can be influenced by:
FM device type.
Current settings in the “Data collection” section, “Engine” field.
Current settings in the “Eco-drive” section, “Custom engine source” field.
Current settings in the “Eco-drive” section, “Data source” field.
Firmware version currently present in the FM device.

Note
It is particularly important to pay extra attention to the “engine source” configuration since it can be done
in two different places. Possible configuration variants:
Engine source is configured only in “Data collection” section, “Engine” field.
Engine source is configured in “Data collection” section, “Engine” field and in “Eco-drive” section,
“Custom engine source” field.

3.1 Detection based on “Engine” field settings in “Data collection” section

Engine source is configured only in “Data collection” section, “Engine” field and “Eco-drive” section,
“Custom engine source” field is disabled. This means that the same engine state detection logic is used
for data sending, entering/exiting sleep modes, Eco-Drive parameter calculation and other processes.
Possible configurations and their effect are described below.

Tables below define how engine state will be detected. Description for used abbreviations:
Always – the engine is considered to be always on.
RPM – the engine is considered to be on, when the FM device receives RPM data from the data
source.
DIN4 + Voltage* – the engine is considered to be on, when the battery voltage level is within
acceptable limits and signal level in the DIN4 is high.
Movement + Voltage* – the engine is considered to be on, when the battery voltage level is
within acceptable limits and the built-in movement sensor detects motion.
Custom - engine is considered to be on, when conditions defined in the “Custom Ignition”
configuration are satisfied.
Movement + Voltage* / Power pin – the engine is considered to be on, when the battery
voltage level is within acceptable limits and the built-in movement sensor detects motion, or when
the voltage level in OBD pin16 is within acceptable limits.
Voltage* / Power pin – the engine is considered to be on, when the battery voltage level is
within acceptable limits, or when the voltage level in OBD pin16 is within acceptable limits.
RPM / DIN4+Voltage* – the engine is considered to be on, when the FM device receives RPM
data from the data source, or when the battery voltage level is within acceptable limits and signal
level in the DIN4 is high.
RPM / Movement + Voltage* – the engine is considered to be on, when the FM device receives
RPM data from the data source, or when the battery voltage level is within acceptable limits and
the built-in movement sensor detects motion.
RPM / Custom – the engine is considered to be on, when the FM device receives RPM data from
the data source, or when conditions defined in the “Custom Ignition” configuration are satisfied.
N/A – this combination is not possible.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
6
support@ruptela.com | www.ruptela.com
 *Voltage ranges:

Eco and Advanced family devices Engine ON condition Engine OFF condition
Voltage range for light vehicles Voltage > 13000 mV Voltage < 13000 mV
Voltage range for trucks Voltage > 26000 mV Voltage < 18000 mV

FM-Plug4 Engine ON condition Engine OFF condition

Voltage range for light vehicles Voltage > 13200 mV Voltage < 12800 mV
Voltage range for trucks Voltage > 27000 mV Voltage < 12600 mV

“Eco-Drive - Data source” and “Data collection – Engine” configuration relations tables
HCV5, LCV5
Data source CAN / CAN+ACC /
CAN+GPS CAN + Alternative data
ACC / GPS
OBD / OBD+ACC / source selection
“Data collection” - Engine OBD+GPS
Always on Always Always Always
Custom Custom RPM RPM / Custom

Pro5
Data source
CAN / CAN+ACC / CAN + Alternative data
ACC / GPS
CAN+GPS source selection
“Data collection” - Engine
Always on Always Always Always
Custom Custom RPM RPM / Custom

Trace5
Data source
ACC / GPS
“Data collection” - Engine
Always on Always
Custom Custom

FM-Eco4 FM-Plug4
Data source
ACC / GPS ACC / GPS OBD
“Data collection” - Engine
Always on Always Always Always
Ignition(DIN4) DIN4 + Voltage N/A N/A
Movement + Movement + Voltage /
Mov Sensor RPM
Voltage Power pin
Custom Custom N/A N/A
Power voltage N/A Voltage / Power pin RPM

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
7
support@ruptela.com | www.ruptela.com
 FM-Pro4
Data source
CAN / CAN+ACC / CAN + Alternative data
ACC / GPS
CAN+GPS source selection
“Data collection” - Engine
Always on Always Always Always
Ignition(DIN4) DIN4 + Voltage RPM RPM / DIN4+Voltage
Mov Sensor Movement+Voltage RPM RPM / Movement+Voltage
Custom Custom RPM RPM / Custom
Power voltage N/A N/A N/A

FM-Tco4 HCV, FM-Tco4 LCV

Data source CAN / CAN+ACC /
CAN+GPS CAN + Alternative data
ACC / GPS
OBD / OBD+ACC / source selection
“Data collection” - Engine OBD+GPS
Always on Always Always Always
Ignition(DIN4) DIN4 + Voltage RPM RPM / DIN4+Voltage
Mov Sensor Movement+Voltage RPM RPM / Movement+Voltage
Custom Custom RPM RPM / Custom
Power voltage N/A N/A N/A

3.2 Detection based on “Custom engine source” field settings in “Eco-drive”

section
Engine source is configured in “Data collection” section, “Engine” field and in “Eco-drive” section, “Custom
engine source” field. This means that the engine state detection logic used for data sending,
entering/exiting sleep mode and other processes is not the same as the engine state detection logic used
for calculating eco drive parameter values.

Note
When “Custom engine source” in “Eco-drive” section is configured, “Alternative data source selection”
and “Data source” field values have no effect on engine state detection logic used for calculating Eco-
Drive parameter values.

3.2.1 Custom engine source – feature description

Engine state used for calculating Eco-Drive parameter values is based on the state of other IO parameters.
List of them is available below:
1. DIN1
2. DIN2
3. DIN3
4. DIN4
5. Mov sensor
6. CAN ignition (from CAN)
7. Power supply voltage
8. RPM (from CAN)

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
8
support@ruptela.com | www.ruptela.com
During custom engine source configuration, a specific set of parameters is combined together.
Combination means that a certain number of them have to be selected. This is done in the configurator.
More information on the configuration procedure is available in the next chapter.
These parameters can be linked with a logical “AND” operator or a logical “OR” operator. The user decides
which should be used. By default, “AND” is used.

AND
This means that conditions for all selected parameters have to be satisfied. Only then the ignition will be
considered to be on.

OR
Logical “OR” operation means that conditions for at least one of the selected parameters have to be
satisfied. Only then the ignition will be considered to be on.

3.2.2 Custom engine source – configuration

Follow these steps to configure your tracking device:
1. In the configurator choose your device.
2. In the global settings, in the Eco-Drive section click on the Options button.
3. The Eco-Drive settings window will be displayed. Find the Custom Engine source checkbox and
tick it. The Customize button will be enabled on the right.
4. The Customize button opens a new popup window. Custom engine ignition pickup configuration for
Eco-Drive is done here.

2
.

1
.

4
.
3
.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
9
support@ruptela.com | www.ruptela.com
Notes
The custom engine source functionality also depends on interface configuration, which is done in the
IO settings window, Interfaces section. RPM and CAN ignition sections in the Custom Engine
source window will be greyed out, if CAN: FMS/HCV/LCV is not enabled or if Deep sleep mode is
activated in the configurator.
Note that not all FM devices have CAN interfaces.

Some data sources for parameters have an option to be enabled/disabled, other sources also have
configurable threshold values. A detailed description available below.
5. Logic selection – for the custom engine source configuration a specific set of parameters have to
be combined together. Available parameters are listed in the previous chapter. Combination means
that a certain number of them have to be selected. These parameters can be linked with a logical
“AND” operation or a logical “OR” operation.
6. DIN1, DIN2, DIN3 and DIN4 – engine ignition detection based on digital inputs states.
7. Mov Sensor – detects vehicle movement and considers the engine to be on. Movement sensor
sensitivity is configurable in the Global settings section.
8. CAN ignition – in some cases CANbus data obtained from specific vehicles contains information
about the vehicle’s ignition state. When CAN interface on the FM device is set to FMS/HCV/LCV mode,
this information could be read and used as custom ignition parameter.
9. Power supply voltage
ON – voltage level in mV. Range from 0 mV to 65535 mV. When power supply voltage is greater
than the value provided by the user this condition is considered to be “TRUE”.
OFF – voltage level in mV. Value must be lower than voltage entered in the ON column. Range
from 0 mV to 65534 mV. When power supply voltage is lower than the value provided by the
user this condition is considered to be “FALSE”.
10. RPM – RPM’s value, obtained from CAN data.
ON – range from 0 rpm to 8031 rpm. When RPM value is greater than the value provided by the
user this condition is considered to be “TRUE”.
OFF – range from 0 rpm to 8030 rpm. Value must be lower than RPM number entered in the ON
column. When RPM value is lower than the value provided by the user this condition is considered
to be “FALSE”.

Note
If the device receives an error value for RPM data from CAN source, then the Boolean value for this
parameter will be “FALSE”.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
10
support@ruptela.com | www.ruptela.com
 5
.

6
7
.
8
.
.9
10 .
.

3.2.3 Custom engine source – operation examples

Case 1
“AND” logic is used to combine custom engine detection parameters. Ignition detection is based on the
DIN4 state and engine RPM value. Other parameters are not enabled.
Ignition State

Ignition ON

Ignition Off

DIN4 - 1
Conditions

DIN4 - 0

RPM≥ON rpm - True

RPM≤OFF rpm - False

0 10 20 30 40 50 60 70

Time, s

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
11
support@ruptela.com | www.ruptela.com
Case 2
“OR” logic is used to combine custom engine parameters. Ignition detection is based on the DIN4 state
and engine RPM value. Other parameters are not enabled.
Ignition State

Ignition ON

Ignition Off

DIN4 - 1
Conditions

DIN4 - 0

RPM≥ON rpm - True

RPM≤OFF rpm - False

0 10 20 30 40 50 60 70

Time, s
3.2.4 Calculate data only when engine is on
Independently of the configuration or which data source is selected, it is highly recommended to enable
the “Calculate data only when engine is on” function.

Enabling this function will prevent calculation of false values and generation of false records when the
ignition is off, and the vehicle is standing.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
12
support@ruptela.com | www.ruptela.com
4 Ignore RPM values when fuel rate is below defined limit
Description
Ignore RPM values when fuel rate is below defined limit is self-explanatory. Engine RPMs can be set to
be ignored in cases when the fuel rate is lower than the value set by the user. This functionality was
developed to improve Eco-Drive tracking in cases when drivers are engine braking instead of actually
using brakes. Engine braking occurs because of traffic regulations in many countries, which require truck
drivers to always drive with an engaged gear, which in turn provides a certain amount of engine braking.
Ignore RPM works only with the following devices:
HCV5, LCV5, Pro5
FM-Pro4
FM-Tco4 LCV
FM-Tco4 HCV

Data source
This function works only with these data sources:
CAN, CAN + ACC, CAN + GPS

Ignore RPM when fuel rate is below set value function is enabled and configured in the FM device
configurator – Eco-Drive setting window. Here the user can enable the function (disabled by default).
Fuel rate value range is from 0,0 to 25,0 l/h.

Data from the following parameters must be available for this function to work:
ID Name Name in configurator Size, B Value IO factor
116 CANBUS_fuel_rate CAN fuel rate 2 0 - 64255 0,05 L/h per Bit
197 CANBUS_RPM CAN engine speed 2 0 - 65535 0,125 RPM /Bit

When the fuel rate is below configured limit, values will not be counted for the following IO parameters:
ID Name Name in configurator Size, B Value IO factor
132 ECO_rpm_red ECO RPM in red band timer 2 0 - 65535 1 s/Bit
ECO_RPM_in_red_ ECO RPM in red band
539 2 0 - 65535 5 m/Bit
band_distance distance

When the previously mentioned IO parameters are ignored, the FM device recognizes the distance
travelled during that time as ECO RPM in green band distance:
ID Name Name in configurator Size, B Value IO factor
ECO_rpm_ ECO RPM in green band
140 4 0-4294967295 1 m/Bit
green distance

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
13
support@ruptela.com | www.ruptela.com
5 Ignore over speeding when fuel rate is below defined limit
Description
Vehicle over speeding can be ignored in cases, when the fuel rate is lower, than the value set by the user.
This functionality was developed to improve Eco-Drive tracking in cases, when drivers are engine braking
instead of actually using brakes. Engine braking occurs because of traffic regulations in many countries,
which require truck drivers to always drive with an engaged gear, which in turn provides a certain amount
of engine braking.

Ignore overspeeding works only with the following devices:

HCV5, LCV5, Pro5
FM-Pro4
FM-Tco4 LCV
FM-Tco4 HCV

Data source
This function works only with these data sources: CAN, CAN + ACC, CAN + GPS

Ignore over speeding, when fuel rate is below set limit can be enabled and configured in the FM
device configurator – Eco-Drive settings window. This function is disabled by default. Fuel rate value
range is from 0,0 to 25,0 l/h.

Data from the following parameters must be available for this function to work:
ID Name Name in configurator Size, B Value IO factor
CAN high resolution
92 CANBUS HRFC engine total fuel 4 0 - 4211081215 0,001 L per Bit
used
CAN high resolution
114 CANBUS Distance 4 0 - 4211081215 5 m per Bit
total vehicle distance
116 CANBUS_fuel_rate CAN fuel rate 2 0 - 64255 0,05 L/h per Bit
CAN wheel based
210 CANBUS WBSpeed 2 0 - 65535 1/256 km/h per Bit
speed

When fuel rate is below configured limit, values will not be counted for the following IO parameters:
ID Name Name in configurator Size, B Value IO factor
131 ECO_overspeed ECO overspeeding timer 2 0 - 65535 1 s/Bit
ECO_overspeeding_di ECO overspeeding
544 2 0 - 65535 5 m/Bit
stance distance
ECO_overspeeding_fu ECO overspeeding fuel
545 2 0 - 65535 1 ml/Bit
el_used used

When the previously mentioned IO parameters are ignored, the FM device recognizes the distance
travelled during that time as ECO normal speed distance:
ID Name Name in configurator Size, B Value IO factor
141 ECO_normal_speed ECO normal speed distance 4 0-4294967295 1 m/Bit

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
14
support@ruptela.com | www.ruptela.com
6 Ignore RPM values when angle of inclination is above defined limit
Description
This functionality ignores the high RPM, which occurs when driving uphill and the Eco-Drive panel will not
indicate it as a violation.

Ignore RPM values works only with the following devices:

HCV5, LCV5, Pro5
FM-Pro4
FM-Tco4 LCV
FM-Tco4 HCV

Data source
This function works only with these data sources: CAN, CAN + ACC, CAN + GPS

Ignore RPM values when angle of inclination is above can be enabled and configured in the
tracking device configurator – Eco-Drive settings window. This function is disabled by default. The angle
value range is from 0 to 90°.

Note
This functionality will only work if the accelerometer is calibrated.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
15
support@ruptela.com | www.ruptela.com
7 ECO Driving parameters
The common ECO-drive parameters and extended ECO-drive parameters have different FMIO ID
numbers, therefore they can be configured independently.

Common ECO-drive parameters are described in sections 7.1 - 7.20.

7.1 ECO max speed

ID Name Name in configurator Size, B Value IO factor
130 ECO_max_speed ECO max speed 1 0 - 255 1 km/h / Bit

Description
Maximum speed value during overall data period. Parameter value is expressed in km/h.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS) – Parameter value is calculated from speed values that were taken
from CAN data. If data from CAN is not available, but “Alternative data source selection” check
box is enabled, then speed value from GPS data is used.
2. OBD (OBD+ACC, OBD+GPS) – Parameter value is calculated from speed values that were taken
from OBD data. If data from OBD is not available, but “Alternative data source selection” check
box is enabled, then speed value from GPS data is used.
3. Accelerometer - Parameter value is calculated from speed values that were taken from GPS data.
4. GPS - Parameter value is calculated from speed values that were taken from GPS data. (When
information for Eco drive parameters is obtained from GPS data, they will be counted as valid only
when HDOP level is lower or equal to 1.5).

7.2 ECO overspeeding timer

ID Name Name in configurator Size, B Value IO factor
131 ECO_overspeed ECO overspeeding timer 2 0 - 65535 1 s/Bit

Description
Duration, when the vehicle was over speeding (the speed limit is configurable) during overall data period.
Parameter value is expressed in seconds.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS) – parameter value is calculated from speed values that were taken
from CAN data. If data from CAN is not available, but “Alternative data source selection” check
box is enabled, then speed value from GPS data is used.
2. OBD (OBD+ACC, OBD+GPS) – parameter value is calculated from speed values that were taken
from OBD data. If data from OBD is not available, but “Alternative data source selection” check
box is enabled, then speed value from GPS data is used.
3. Accelerometer – parameter value is calculated from speed values that were taken from GPS data.
4. GPS – parameter value is calculated from speed values that were taken from GPS data. (When
information for Eco drive parameters is obtained from GPS data, they will be counted as valid only
when HDOP level is lower or equal to 1.5).

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
16
support@ruptela.com | www.ruptela.com
7.3 ECO RPM in red band timer
ID Name Name in configurator Size, B Value IO factor
132 ECO_rpm_red ECO RPM in red band timer 2 0 - 65535 1 s/Bit

Description
Duration, for which the RPM value was out of the acceptable range (RPM range is configurable) during
overall data period. Parameter value is expressed in seconds.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS) – parameter value is calculated after analysing RPM values that were
taken from CAN data.
2. OBD (OBD+ACC, OBD+GPS) – parameter value is calculated after analysing RPM values that were
taken from OBD data.
3. Accelerometer – parameter unavailable.
4. GPS – parameter unavailable.

7.4 ECO max RPM

ID Name Name in configurator Size, B Value IO factor
133 ECO_max_rpm ECO max RPM 2 0 - 65535 1 RPM/min / Bit

Description
Maximum RPM value during overall data period.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS) – parameter value is calculated after analysing RPM values that were
taken from CAN data.
2. OBD (OBD+ACC, OBD+GPS) – parameter value is calculated after analysing RPM values that were
taken from OBD data.
3. Accelerometer – parameter unavailable.
4. GPS – parameter unavailable.
7.5 ECO braking counter
ID Name Name in configurator Size, B Value IO factor
134 ECO_braking events ECO brake counter 1 0 - 255 1 event/Bit

Description
Number of stops since the last record. Value is expressed as a number of events.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS) – parameter value is calculated from speed and brake pedal position
values that were taken from CAN data. This is valid for FMS, LCV and HCV modes.
a. If speed data from CAN is not available (FF values or no data at all), but “Alternative data
source selection” checkbox is ticked, then speed value from GPS data is used. Brake pedal
position values are still taken from CAN data.
b. If speed data from CAN is available, but brake pedal position values from CAN are not
available (FF values or no data at all), then the “ECO braking counter” parameter will not
be calculated at all, unless the “Ignore CAN brake switch” checkbox is ticked. CAN speed

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
17
support@ruptela.com | www.ruptela.com
 data is used for parameter calculation in this case. This is true even if “Alternative data
source selection” checkbox is ticked.
c. If speed and brake pedal position data from CAN is not available (FF values or no data at
all), then the “ECO braking counter” parameter will not be counted at all, unless the “Ignore
CAN brake switch” and “Alternative data source selection” checkboxes are ticked. GPS
speed is used for parameter calculation in this case.

2. OBD (OBD+ACC, OBD+GPS) – parameter value is calculated from speed values that were taken
from OBD data. If data from OBD is not available, but “Alternative data source selection” check
box is enabled, then speed value from GPS data is used.
3. Accelerometer – parameter value is calculated from detected acceleration.
4. GPS – parameter value is calculated from speed values that were taken from GPS data. (When
information for Eco-Drive parameters is obtained from GPS data, they will be counted as valid only
when HDOP level is lower or equal to 1.5).

Methodology
1. Braking events are detected after analysing acceleration and brake pedal position data.
2. Information from several different data sources can be used to gather acceleration data. The data
source is determined in the configuration. It can be CAN, OBD, Accelerometer and GPS data.
3. Acceleration needed to register a braking event is -0,5 m/s2.
4. Braking event will be registered, when braking acceleration value is lower than -0,5 m/s2.
5. If one braking event was registered, then the next such event can be registered only after the
acceleration value increases above the -0,4 m/s2 limit.

7.6 ECO extreme harsh brake counter

ID Name Name in configurator Size, B Value IO factor
ECO_ext_hrsh_ ECO extreme and harsh brake
135 1 0 - 255 1 event/Bit
braking counter

Description
Extreme braking – number of events stored in the first 4 bits. This number represents extreme braking
events registered since the last record. An extreme braking event is registered, when braking acceleration
exceeds the configured limit. Extreme braking limit is set in the Eco-Drive section in the configurator.

Harsh braking – number of events stored in the last 4 bits. This number represents harsh braking events
registered since the last record. A harsh braking event is registered, when braking acceleration exceeds
the configured limit. Harsh braking limit is set in the Eco-Drive section in the configuration.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS) – Parameter value is calculated from speed and brake pedal position
values that were taken from CAN data. This is valid for FMS, LCV and HCV modes.
a. If speed data from CAN is not available (FF values or no data at all), but “Alternative data
source selection” check box is enabled, then speed value from GPS data is used. Brake
pedal position values are still taken from CAN data.
b. If speed data from CAN is available, but brake pedal position values from CAN are not
available (FF values or no data at all), then the “ECO extreme harsh braking counter”
parameter will not be calculated at all, unless the “Ignore CAN brake switch” checkbox is
ticked. CAN speed data is used for parameter calculation in this case. This is true even if
“Alternative data source selection” checkbox is ticked.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
18
support@ruptela.com | www.ruptela.com
 c. If speed and brake pedal position data from CAN is not available (FF values or no data at
all), then the “ECO extreme harsh braking counter” parameter will not be calculated at all,
unless the “Ignore CAN brake switch” and “Alternative data source selection” checkboxes
are ticked. GPS speed is used for parameter calculation in this case.

2. OBD (OBD+ACC, OBD+GPS) – parameter value is calculated from speed values that were taken
from OBD data. If data from OBD is not available, but “Alternative data source selection” check
box is enabled, then speed value from GPS data is used.
3. Accelerometer – parameter value is calculated from detected acceleration.
4. GPS – parameter value is calculated from speed values that were taken from GPS data. (When
information for Eco drive parameters is obtained from GPS data, they will be counted as valid only
when HDOP level is lower or equal to 1.5).

Methodology for “harsh” braking detection

1. Braking events are detected after analysing acceleration and brake pedal position data.
2. Information from several different data sources can be used to gather acceleration data. The data
source is determined in the configuration. It can be CAN, OBD, accelerometer and GPS data.
3. Acceleration needed to register a harsh braking event is -1 m/s2.
4. Harsh braking event will be registered, when the acceleration value is lower than -1 m/s2.
5. If one harsh braking event was registered, then the next such event can be registered only after
the acceleration value increases above the -1 m/s2 limit.

Methodology for “extreme” braking detection

1. Braking events are detected after analysing acceleration and brake pedal position data.
2. Information from several different data sources can be used to gather acceleration data. The data
source is determined in the configuration. It can be CAN, OBD, Accelerometer and GPS data.
3. Acceleration needed to register an extreme braking event is -2 m/s2.
4. Extreme braking event will be registered, when the acceleration value is below -2 m/s2 limit.
5. If one extreme braking event was registered, then the next such event can be registered only
after the acceleration value increases above the -2 m/s2 limit.

7.7 ECO harsh acceleration counter

ID Name Name in configurator Size, B Value IO factor
ECO harsh acceleration ECO harsh acceleration
136 1 0 - 255 1 event/Bit
counter counter

Description
Number of harsh acceleration events registered since the last record. Harsh acceleration event is
registered, when the acceleration exceeds configured limit. Harsh acceleration limit is set in the ECO drive
section in the device configuration.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS) – parameter value is calculated from speed values that were taken
from CAN data. If data from CAN is not available, but “Alternative data source selection” check
box is enabled, then speed value from GPS data is used.
2. OBD (OBD+ACC, OBD+GPS) – parameter value is calculated from speed values that were taken
from OBD data. If data from OBD is not available, but “Alternative data source selection” check
box is enabled, then speed value from GPS data is used.
3. Accelerometer – parameter value is calculated from detected acceleration.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
19
support@ruptela.com | www.ruptela.com
 4. GPS – parameter value is calculated from speed values that were taken from GPS data. (When
information for Eco drive parameters is obtained from GPS data, they will be counted as valid only
when HDOP level is lower or equal to 1.5).

7.8 ECO idling time

ID Name Name in configurator Size, B Value IO factor
137 ECO_idling_time ECO idling timer 2 0 - 65535 1 s/Bit

Description
Idling duration – how long vehicle’s engine was on, but it remained stationary. Device counts idling time,
when the engine is on for a certain duration (idling delay) and vehicle‘s speed is lower than the threshold
(idling speed). If time spent with engine on is shorter than the configured limit, then this time will not be
added to the idling duration. If time spent with engine on is longer than the configured limit, then this
time will be added to the idling duration.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. Engine state detection is based on process described in the “Engine state detection logic” chapter.
2. When information for Eco drive parameters is obtained from GPS data, they will be counted as
valid only when HDOP level is lower or equal to 1.5.

7.9 ECO cruise control timer

ID Name Name in configurator Size, B Value IO factor
ECO_cruise_ 0-65535
138 ECO cruise control timer 4B (2B + 2B) 1 s/Bit
control (each)

Description
Cruise plan – cruise control could be on. The first two bytes show, how much time a vehicle have spent
while driving at a certain speed limit or above it (speed limit is configurable). Count starts, if the vehicle
successfully maintains its speed at the speed limit or above it for 60 seconds. Parameter value is expressed
in seconds.
Cruise fact – cruise control was on. The last two bytes show, how much time a vehicle have spent while
driving with cruise control on. Count starts, if the vehicle successfully maintains its speed at the speed
limit or above it for 60 seconds (speed limit is configurable). Parameter value is expressed in seconds.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS) – parameter value is calculated after analysing speed and cruise
control status values that were taken from CAN data. If speed data from CAN is not available, but
„Alternative data source selection“ check box is enabled, then speed value from GPS data is used.
2. OBD (OBD+ACC, OBD+GPS) – parameter unavailable.
3. Accelerometer – parameter unavailable.
4. GPS – parameter unavailable.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
20
support@ruptela.com | www.ruptela.com
7.10 ECO engine on timer
ID Name Name in configurator Size, B Value IO factor
139 ECO_engine_on ECO engine on timer 2 0 - 65535 1 s/Bit

Description
Engine on duration, during overall data period – how much time the vehicle spent with its engine turned
on. Parameter value is expressed in seconds.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. Engine state detection is based on process described in the “Engine state detection logic” chapter.
2. When information for Eco-Drive parameters is obtained from GPS data, they will be counted as
valid only when HDOP level is lower or equal to 1.5.

7.11 ECO RPM in green band distance

ID Name Name in configurator Size, B Value IO factor
ECO_rpm_ ECO RPM in green band
140 4 0-4294967295 1 m/Bit
green distance

Description
Distance travelled, when the RPM value was in the acceptable range (RPM range is configurable). During
overall data period. Parameter value is expressed in meters.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS) – parameter value is calculated after analysing RPM and distance
values that were taken from CAN data.
2. OBD (OBD+ACC, OBD+GPS) – parameter value is calculated after analysing RPM and distance
values that were taken from OBD data.
3. Accelerometer – parameter unavailable.
4. GPS – parameter unavailable.
7.12 ECO RPM in red band distance
ID Name Name in configurator Size, B Value IO factor
ECO_RPM_in_red_ ECO RPM in red band
539 2 0-65535 5 m/Bit
band_distance distance

Description
Distance travelled, when the RPM value was out of the acceptable (green band) range (RPM range is
configurable). During overall data period. Parameter value is expressed in meters.
Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS) – parameter value is calculated after analysing RPM and distance
values that were taken from CAN data.
2. OBD (OBD+ACC, OBD+GPS) – parameter value is calculated after analysing RPM and distance
values that were taken from OBD data.
3. Accelerometer – parameter unavailable.
4. GPS – parameter unavailable.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
21
support@ruptela.com | www.ruptela.com
7.13 ECO normal speed distance
ID Name Name in configurator Size, B Value IO factor
ECO_normal_
141 ECO normal speed distance 4 0-4294967295 1 m/Bit
speed

Description
Distance travelled during overall data period, when vehicle’s speed was below the speed limit (speed limit
is configurable). Parameter value is expressed in meters.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS) – parameter value is calculated after analysing speed and distance
values that were taken from CAN data. If speed data from CAN is not available, but „Alternative
data source selection“ check box is enabled, then speed value from GPS data is used.
2. OBD (OBD+ACC, OBD+GPS) – parameter value is calculated after analysing speed and distance
values that were taken from OBD data. If speed data from OBD is not available, but „Alternative
data source selection“ check box is enabled, then speed value from GPS data is used.
3. Accelerometer – parameter value is calculated from speed and distance values that were taken
from GPS data.
4. GPS – parameter value is calculated from speed and distance values that were taken from GPS
data. (When information for Eco drive parameters is obtained from GPS data, they will be counted
as valid only when HDOP level is lower or equal to 1.5).

7.14 ECO cruise control distance

ID Name Name in configurator Size, B Value IO factor
ECO_cruise_ ECO cruise 8B (4B + 0-4294967295
142 1 m/Bit
control_mileage control distance 4B) (each)

Description
Cruise plan – cruise control could be on. The first two bytes show, how far a vehicle have travelled while
driving at a certain speed limit or above it (speed limit is configurable). Count starts, if the vehicle
successfully maintains its speed at the speed limit or above it for 60 seconds. Parameter value is expressed
in meters.
Cruise fact – cruise control was on. The last two bytes show, how far a vehicle have travelled while
driving with cruise control on. Count starts, if the vehicle successfully maintains its speed at the speed
limit or above it for 60 seconds (speed limit is configurable). Parameter value is expressed in meters.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS) – parameter value is calculated after analysing distance and cruise
control status values that were taken from CAN data.
2. OBD (OBD+ACC, OBD+GPS) – parameter unavailable.
3. Accelerometer – parameter unavailable.
4. GPS – parameter unavailable.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
22
support@ruptela.com | www.ruptela.com
7.15 ECO cornering counter
ID Name Name in configurator Size, B Value IO factor
143 ECO_cornering ECO cornering counter 1 1 - 255 1 event/Bit

Description
Number of harsh cornering events registered since the last record. Cornering event is registered, when
the cornering acceleration exceeds the configured limit. Cornering limit is set in the ECO drive section in
the device configuration.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS)*
a. If only CAN source is used, then parameter unavailable.
b. If CAN+ACC source is used, then parameter value is calculated from detected acceleration.
c. If CAN+GPS source is used and “Alternative data source selection” check box is enabled,
parameter value is calculated from GPS data.

2. OBD (OBD+ACC, OBD+GPS)*

a. If only OBD source is used, then parameter unavailable.
b. If OBD+ACC source is used, then parameter value is calculated from detected acceleration.
c. If OBD+GPS source is used and “Alternative data source selection” check box is enabled,
parameter value is calculated from GPS data.

3. ACC – parameter value is calculated from detected acceleration.

4. GPS – parameter value is calculated from GPS data. (When information for Eco drive parameters
is obtained from GPS data, they will be counted as valid only when HDOP level is lower or equal
to 1.5).
*Firmware versions that support these new data sources can be identified by analysing device firmware change log file.

7.16 ECO idling event

ID Name Name in configurator Size, B Value IO factor
ECO_idling_
169 ECO idling event 1 0-1 1 event/Bit
state

Description
Parameter defines whether the vehicle is idling or not. Device registers the idling event, when the engine
is on for a certain duration (idling delay) and vehicle‘s speed is lower than the threshold (idling speed).
Parameters are configurable. It is recommended to set this IO parameter Event On – Change or
Hysteresis, so the device will generate a record every time the idling state changes.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. Engine state detection is based on process described in the “Engine state detection logic” chapter.
2. When information for Eco drive parameters is obtained from GPS data, they will be counted as
valid only when HDOP level is lower or equal to 1.5.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
23
support@ruptela.com | www.ruptela.com
7.17 ECO Absolute idling time
ID Name Name in configurator Size, B Value IO factor
ECO_absolute_ ECO Absolute idling
175 4 0 - 4294967295 1 s/Bit
idling_time time

Description
Absolute idling time calculation uses the same logic, which was described in the “7.8 ECO idling time”
chapter.
Value of this parameter expresses a sum of all time periods, when this vehicle was idling. Count begins
after device configuration and its connection to the power supply source.

7.18 ECO braking value

ID Name Name in configurator Size, B Value IO factor
ECO_braking_
402 ECO braking value 2 0 - 65535 0,01 m/s2 / Bit
value

Description
Acceleration detected during a braking event.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS)*
a. If only CAN source is used, then parameter value is calculated from speed values that were
taken from CAN data.
b. If CAN+ACC source is used, then parameter value is calculated from detected acceleration.
c. If CAN+GPS source is used, then parameter value is calculated from speed values that
were taken from CAN data. If data from CAN is not available, but “Alternative data source
selection” check box is enabled, then speed value from GPS data is used.

2. OBD (OBD+ACC, OBD+GPS)*

a. If only OBD source is used, then parameter value is calculated from speed values that were
taken from OBD data.
b. If OBD+ACC source is used, then parameter value is calculated from detected acceleration.
c. If OBD+GPS source is used, then parameter value is calculated from speed values that
were taken from OBD data. If data from OBD is not available, but “Alternative data source
selection” check box is enabled, then speed value from GPS data is used.

3. Accelerometer – parameter value is calculated from detected acceleration.

4. GPS – parameter value is calculated from speed values that were taken from GPS data. (When
information for Eco drive parameters is obtained from GPS data, they will be counted as valid only
when HDOP level is lower or equal to 1.5).
*Firmware versions that support these new data sources can be identified by analysing device firmware change log file.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
24
support@ruptela.com | www.ruptela.com
Configuration
1. “Event on” – Monitoring. Braking value can be registered, only if the braking acceleration exceeds
configured lower limit. If this condition is fulfilled, then this parameter will be equal to the highest
braking acceleration value detected in time period between two data records.
2. “Event on” – Change and “Include data only on event” check box enabled. Braking value can be
registered and data record can be generated, only if the braking acceleration exceeds configured
lower limit. If this condition is fulfilled, then data record with the highest braking acceleration value
will be generated as soon as the acceleration drops below the configured lower limit.

7.19 ECO acceleration value

ID Name Name in configurator Size, B Value IO factor
ECO_acceleration_
403 ECO acceleration value 2 0 - 65535 0,01 m/s2 / Bit
value

Description
Detected speedup acceleration value.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS)*
a. If only CAN source is used, then parameter value is calculated from speed values that were
taken from CAN data.
b. If CAN+ACC source is used, then parameter value is calculated from detected acceleration.
c. If CAN+GPS source is used, then parameter value is calculated from speed values that
were taken from CAN data. If data from CAN is not available, but “Alternative data source
selection” check box is enabled, then speed value from GPS data is used.

2. OBD (OBD+ACC, OBD+GPS)*

a. If only OBD source is used, then parameter value is calculated from speed values that were
taken from OBD data.
b. If OBD+ACC source is used, then parameter value is calculated from detected acceleration.
c. If OBD+GPS source is used, then parameter value is calculated from speed values that
were taken from OBD data. If data from OBD is not available, but “Alternative data source
selection” check box is enabled, then speed value from GPS data is used.

3. Accelerometer – parameter value is calculated from detected acceleration.

4. GPS – parameter value is calculated from speed values that were taken from GPS data. (When
information for Eco drive parameters is obtained from GPS data, they will be counted as valid only
when HDOP level is lower or equal to 1.5).
*Firmware versions that support these new data sources can be identified by analysing device firmware change log file.

Configuration
1. “Event on” – Monitoring. Speedup acceleration value can be registered, only if its value exceeds
configured lower limit. If this condition is fulfilled, then this parameter will be equal to the highest
speedup acceleration value detected in time period between two data records.
2. “Event on” – Change and “Include data only on event” check box enabled. Speedup acceleration
value can be registered and data record can be generated, only if the speedup acceleration
exceeds configured lower limit. If this condition is fulfilled, then data record with the highest
speedup acceleration value will be generated as soon as the acceleration drops below the
configured lower limit.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
25
support@ruptela.com | www.ruptela.com
7.20 ECO cornering value
ID Name Name in configurator Size, B Value IO factor
ECO_cornering_
404 ECO cornering value 2 0 - 65535 0,01 m/s2 / Bit
value

Description
Cornering acceleration value detected during tight turns.

Data source
Information from several different data sources can be used to calculate value for this parameter:
1. CAN (CAN+ACC, CAN+GPS)*
a. If only CAN source is used, then parameter unavailable.
b. If CAN+ACC source is used, then parameter value is calculated from detected acceleration.
c. If CAN+GPS source is used and “Alternative data source selection” check box is enabled,
parameter value is calculated from GPS data.

2. OBD (OBD+ACC, OBD+GPS)*

a. If only OBD source is used, then parameter unavailable.
b. If OBD+ACC source is used, then parameter value is calculated from detected acceleration.
c. If OBD+GPS source is used and “Alternative data source selection” check box is enabled,
parameter value is calculated from GPS data.

3. ACC – parameter value is calculated from detected acceleration.

4. GPS – parameter value is calculated from GPS data. (When information for Eco drive parameters
is obtained from GPS data, they will be counted as valid only when HDOP level is lower or equal
to 1.5).
*Firmware versions that support these new data sources can be identified by analysing device firmware change log file.

Configuration
1. “Event on” – Monitoring. Cornering acceleration value can be registered, only if its value exceeds
configured lower limit. If this condition is fulfilled, then this parameter will be equal to the highest
cornering acceleration value detected in time period between two data records.
2. “Event on” – Change and “Include data only on event” check box enabled. Cornering acceleration
value can be registered and data record can be generated, only if the cornering acceleration
exceeds configured lower limit. If this condition is fulfilled, then data record with the highest
cornering acceleration value will be generated as soon as the acceleration drops below the
configured lower limit.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
26
support@ruptela.com | www.ruptela.com
8 Extended ECO drive parameters
8.1 Extended parameters for FM4 devices
Eco-Drive parameters and their structure displayed in the list below are compatible with FM-Tco4 HCV,
FM-Tco4 LCV and FM-Pro4 devices. It is a must to use v1.1 protocol version. Parameter values can be
obtained, only if CANbus data (FMS parameters) can be received from the corresponding vehicle. Main
principles that govern calculations are the same as in FM3 devices.

Eco drive parameters displayed in the list below are available in the “IO settings” window, when the data
source is set to CAN, CAN+ACC or CAN+GPS.

These parameters can be configured to generate records with “Event on”: Monitoring, Change and
Hysteresis. Averaging is not applied for them.
With extended Eco drive parameters, values for the fuel used parameters are calculated according to the
HRLFC (High resolution Liquid Fuel Consumption) data. If HRLFC data is not available, then fuel used
parameters are calculated according to the “Fuel Rate” data. The “Fuel used” parameter (ID 208) itself
will not be calculated.

Extended Eco drive parameters list also contains some new parameters. They are described in chapters
7.3-7.24.
ID Name Name in configurator Size, B Value IO factor
526 ECO_stops_counter ECO stops counter 2 0-65535 1 event/Bit

527 ECO_braking_distance ECO braking distance 2 0-65535 5 m/Bit

528 ECO_braking_duration ECO braking duration 2 0-65535 1 s/Bit

529 ECO_retarder_duration ECO retarder duration 2 0-65535 1 s/Bit

ECO_fuel_used_
540 ECO fuel used while idling 2 0-65535 1 ml/Bit
while_idling
ECO_free_rolling_
541 ECO free rolling distance 2 0-65535 5 m/Bit
distance
ECO_engine_ ECO engine overloaded
542 2 0-65535 5 m/Bit
overloaded_distance distance
ECO_engine_ ECO engine overloaded fuel
543 2 0-65535 1 ml/Bit
overloaded_fuel_used used
ECO_overspeeding_
544 ECO overspeeding distance 2 0-65535 5 m/Bit
distance
ECO_overspeeding_
545 ECO overspeeding fuel used 2 0-65535 1 ml/Bit
fuel_used
ECO_cruise_control_ ECO cruise control on
546 2 0-65535 5 m/Bit
on_distance distance
ECO_cruise_control_ ECO cruise control on fuel
547 2 0-65535 1 ml/Bit
on_fuel_used used
ECO_highest_gear_
548 ECO highest gear distance 2 0-65535 5 m/Bit
distance
ECO_highest_gear_
549 ECO highest gear fuel used 2 0-65535 1 ml/Bit
fuel_used

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
27
support@ruptela.com | www.ruptela.com
 ID Name Name in configurator Size, B Value IO factor
ECO_rpm_range1_
550 ECO RPM range1 distance 2 0-65535 5 m/Bit
distance
ECO_rpm_range1_
551 ECO RPM range1 fuel used 2 0-65535 1 ml/Bit
fuel_used
ECO_rpm_range2_
552 ECO RPM range2 distance 2 0-65535 5 m/bit
distance
ECO_rpm_range2_
553 ECO RPM range2 fuel used 2 0-65535 1 ml/Bit
fuel_used
ECO_rpm_range3_
554 ECO RPM range3 distance 2 0-65535 5 m/Bit
distance
ECO_rpm_range3_
555 ECO RPM range3 fuel used 2 0-65535 1 ml/Bit
fuel_used
ECO_rpm_range4_
556 ECO RPM range4 distance 2 0-65535 5 m/Bit
distance
ECO_rpm_range4_
557 ECO RPM range4 fuel used 2 0-65535 1 ml/Bit
fuel_used
ECO_engine_braking_di
597 ECO engine braking distance 2 0-65535 5 m/Bit
stance

Configuration
In the first part of configuration we show how to enable extended parameters. Follow these steps to
configure your FM Device:
1. In the main configurator window choose your device (FM-Tco4 HCV, FM-Tco4 LCV or FM-Pro4).
2. Under Eco-Drive section put a tick on Enable checkbox.
3. Click the Options button.
4. In the Data source section choose CAN. This action enables fields on the right that were previously
greyed out.
5. Highest gear speed – not every vehicle provides gear parameters in FMS data. It is considered that
vehicle is driven in the highest gear, when its speed is above a set limit. “ECO highest gear distance”
and “ECO highest gear fuel used” parameters are calculated, when the vehicle exceeds this limit.
Value range is from 0 to 255 km/h. Default is 75 km/h.
6. Engine load threshold – “ECO engine overloaded distance” and “ECO engine overloaded fuel used”
parameters are calculated, when Engine Percent Load At Current Speed is above the set limit. Value
range is from 0 to 125 %. Default is 90 %.
7. Free-rolling RPM range – sets RPM range, which is used for “ECO free rolling distance” parameter
calculation. Value range is from 0 to 10000 rpm. The value in the Minimum column cannot be
higher, than in the Maximum column. Default range is 450-650 rpm.
8. RPM range 1, 2, 3 and 4 – sets RPM ranges for 4 “ECO RPM range distance” and 4 “ECO RPM
range fuel used” parameters. Value range in each field is from 0 to 10000 rpm. Value in the Minimum
column cannot be higher, than in the Maximum column.
a. Default value for range 1 is 1 – 900 rpm.
b. Default value for range 2 is 900 – 1300 rpm.
c. Default value for range 3 is 1300 – 1500 rpm.
d. Default value for range 4 is 1500 – 2300 rpm.
9. Engine braking conditions – sets the configurable conditional values that need to be met for the
calculation of the “ECO engine braking distance” parameter.
a. Speed is more than – the condition is met when the speed of the vehicle is above the configured
value. The allowed values are 0-250 km/h. The default value is 0 km/h.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
28
support@ruptela.com | www.ruptela.com
 b. Fuel rate is below – the condition is met when the fuel consumption level of the vehicle is below
the configured value. The allowed values are 0.0-25.0 l/h. The default value is 1.0 l/h.
c. RPM is more than – the condition is met when the RPM of the engine is above the configured
value. The allowed values are 0-10000 rpm. The default value is 650 rpm.

Enable Extended Eco-Drive parameters in IO settings

The second part of the configuration deals with IO events. In order to see Extended Eco-Drive parameters
in reports you have to enable them in the IO settings window.
1. In the IO events section click on the Options button. It opens up a new IO settings window.
2. In Protocol selection section add a tick in Send I/O data with v1.1 protocol checkbox. Now
you will be able to see extended Eco-Drive parameters in the IO list.
3. Select a free slot for a new parameter that you want to enable.
4. In the IO properties section tick the Enable check box, otherwise the slot will remain empty.
5. ID contains the parameters list. Choose and enable all the Eco-Drive parameters.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
29
support@ruptela.com | www.ruptela.com
8.2 ECO fuel used while idling
This parameter counts fuel used value, while vehicle is standing still with its engine running (idling). Fuel
used value will contain diff data (fuel used from the last record) in 0.001 L/bit gain. Idling detection logic
was described in chapter 7.8. If the vehicle fails to meet all the conditions for the idling, then fuel used
value is added to the fuel used while driving.
Fuel used while driving calculations are done on the server (total fuel used difference between records
minus fuel used while idling).

8.3 ECO free rolling distance

This parameter stores driven distance in 5 m/bit gain, while vehicle was free-rolling. Conditions: engine
on, accelerator pedal off (0%), RPM in range 450-650 (configurable).
Distance, when vehicle was not considered free-rolling must be calculated at the server side (distance
between records minus distance while vehicle was free-rolling).

8.4 ECO engine overloaded distance

This parameter stores driven distance in 5 m/bit gain, while engine was overloaded. Conditions: we
calculate engine overloaded distance, when the engine percent load parameter (CAN engine PLCS) is
above the threshold. Threshold value is configurable, default value is 100%, range from 0% to 125%.
Distance, when engine was considered to be in normal load, must be calculated at the server side
(distance between records minus distance while vehicle‘s engine was overloaded).

8.5 ECO engine overloaded fuel used

This parameter stores fuel used in 0.001 L/bit gain, while engine was overloaded. Fuel used is sent as a
diff value (fuel used from the last record). Conditions: we calculate engine overloaded fuel used, when
the engine percent load parameter (CAN engine PLCS) is above the threshold. Threshold value is
configurable, default value is 100%, range from 1% to 125%.
Fuel used, when engine was considered to be in normal load, must be calculated at the server side
(difference of the total fuel used, minus fuel used while engine was overloaded).

8.6 ECO overspeeding distance

This parameter stores driven distance in 5 m/bit gain, while vehicle was over speeding. Conditions:
Vehicle’s speed is above set-up threshold. Threshold is configurable in the ECO-driving menu:
“Overspeeding limit”. Default value is 75 km/h, range is from 1 km/h to 255 km/h.

8.7 ECO overspeeding fuel used

This parameter stores fuel used in 0.001 L/bit gain, while vehicle was over speeding. Fuel used is sent as
a diff value (fuel used from the last record). Conditions: Vehicle’s speed is above set-up threshold.
Threshold is configurable in the ECO-driving menu: “Overspeeding limit”. Default value is 75 km/h, range
is from 1 km/h to 255 km/h.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
30
support@ruptela.com | www.ruptela.com
8.8 ECO cruise control on distance
This parameter stores driven distance in 5 m/bit gain, while cruise control was on, vehicle’s speed is not
important. Distance calculation logic was described in 7.14 chapter, “Cruise fact” section.

8.9 ECO cruise control on fuel used

This parameter stores fuel used in 0.001 L/bit gain, while cruise control was on, vehicle’s speed is not
important.

8.10 ECO highest gear distance

This parameter stores driven distance in 5 m/bit gain. Count starts, when vehicle’s speed exceeds
configured “overspeeding limit”. This signifies that vehicle is driving in the highest gear. Overspeeding
limit is used, because not every vehicle in the fleet provides gear parameters from the FMS. Default
“Overspeeding limit” value is 75 km/h, range is from 1 km/h to 255 km/h.

8.11 ECO highest gear fuel used

This parameter stores fuel used in 0.001 L/bit gain. Fuel used is sent as a diff value (fuel used from the
last record). Count starts, when vehicle’s speed exceeds configured “overspeeding limit”. This signifies
that vehicle is driving in the highest gear. Overspeeding limit is used, because not every vehicle in the
fleet provides gear parameters from the FMS. Default “Overspeeding limit” value is 75 km/h, range is
from 1 km/h to 255 km/h.

8.12 ECO RPM range1 distance

This parameter stores driven distance in 5 m/bit gain, while vehicle’s engine was running in RPM range
1. Default values for RPM range 1 is from 1 rpm to 900 rpm. Range is configurable. Parameter is sent as
a diff value from the last record.

8.13 ECO RPM range1 fuel used

This parameter stores fuel used in 0.001 L/bit gain, while vehicle’s engine was running in RPM range 1.
Default values for RPM range 1 is from 1 rpm to 900 rpm. Range is configurable. Parameter is sent as a
diff value from the last record.

8.14 ECO RPM range2 distance

This parameter stores driven distance in 5 m/bit gain, while vehicle’s engine was running in RPM range
2. Default values for RPM range 2 is from 900 rpm to 1300 rpm. Range is configurable. Parameter is sent
as a diff value from the last record.

8.15 ECO RPM range2 fuel used

This parameter stores fuel used in 0.001 L/bit gain, while vehicle’s engine was running in RPM range 2.
Default values for RPM range 2 is from 900 rpm to 1300 rpm. Range is configurable. Parameter is sent
as a diff value from the last record.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
31
support@ruptela.com | www.ruptela.com
8.16 ECO RPM range3 distance
This parameter stores driven distance in 5 m/bit gain, while vehicle’s engine was running in RPM range
3. Default values for RPM range 3 is from 1300 rpm to 1500 rpm. Range is configurable. Parameter is
sent as a diff value from the last record.

8.17 ECO RPM range3 fuel used

This parameter stores fuel used in 0.001 L/bit gain, while vehicle’s engine was running in RPM range 3.
Default values for RPM range 3 is from 1300 rpm to 1500 rpm. Range is configurable. Parameter is sent
as a diff value from the last record.

8.18 ECO RPM range4 distance

This parameter stores driven distance in 5 m/bit gain, while vehicle’s engine was running in RPM range
4. Default values for RPM range 4 is from 1500 rpm to 2300 rpm. Range is configurable. Parameter is
sent as a diff value from the last record.
This parameter is also used to detect engine braking. 1500-2300 rpms are considered to be the most
effective for engine braking. By analysing this parameter, the client can also tell, if the engine braking
was really used.

8.19 ECO RPM range4 fuel used

This parameter stores fuel used in 0.001 L/bit gain, while vehicle’s engine was running in RPM range 4.
Default values for RPM range 4 is from 1500 rpm to 2300 rpm. Range is configurable. Parameter is sent
as a diff value from the last record.
This parameter is also used to detect engine braking. 1500-2300 rpms are considered to be the most
effective for engine braking. By analysing this parameter, the client can also tell, if the engine braking
was really used.

8.20 ECO engine braking distance

This parameter stores the distance travelled in 5 m/bit gain, while using engine braking (gear engaged)
to slow down the vehicle. The data source must be CAN (CAN+ACC, CAN+GPS). There are 4 conditions
that must be met for the parameter to be calculated:
1. The speed of the vehicle must be more than some configurable value (0-250 km/h; default value:
0 km/h).
2. The position of the acceleration pedal is 0%.
3. The fuel rate is below some configurable value (0.0-25.0 l/h; default value: 1.0 l/h).
4. The RPM of the engine is more than some configurable value (0-10000 rpm; default value: 650
rpm).

8.21 ECO stops counter

This parameter stores the amount of stops made since the last record. The vehicle is considered to have
stopped when CAN wheel based speed is equal to zero.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
32
support@ruptela.com | www.ruptela.com
8.22 ECO braking distance
This parameter stores the distance driven since the last record in 5 m/bit gain while the braking pedal
was pressed.

8.23 ECO braking duration

This parameter stores the time period since the last record in 1 s/bit gain, during which the braking pedal
was pressed and CAN vehicle speed was above zero.

8.24 ECO retarder duration

This parameter stores the time period since the last record in 1 s/bit gain, during which the retarder
torque mode was above zero.

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319
33
support@ruptela.com | www.ruptela.com