FMT100 Features settings: Difference between revisions

Latest revision as of 15:18, 18 January 2023

Main Page > Fast & Easy Trackers > FMT100 > FMT100 Configuration > FMT100 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/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.
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 (FMT100 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.

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 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, and an event record is generated and digital output status is changed to 1 when configured.
Detected speed has to be greater than configured max speed +3% of configured max speed for the overspeeding event to start. To stop overspeeding event detected speed has to be lower than configured max speed -3% of configured max speed. Configurable parameters:

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

Network Jamming

When a device detects GSM signal jamming, it activates the Jamming scenario. The device then starts a configurable timeout before responding that is intended to reduce false positives. After the timeout ends, the device generates an event record

Note that this scenario will not work with Deep Sleep, Ultra Deep Sleep (since they disable the device's GSM module to save power) and Online Deep Sleep modes.

Eventual Records parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise, it will be appended only to eventual records.

For a more visual explanation, take a look at the video made by Teltonika explaining the use-case of Jamming Detection: Teltonika Jamming Detection scenario

GNSS Jamming

GNSS Jamming is the transmission of radio signals that disrupts communications between tracker and satellites by decreasing the signal to noise ratio. When a device detects GNSS signal jamming, it activates the GNSS Jamming scenario. The device then generates and sends a record to the server, depending on hardware model activates Digital Output and optionally sends SMS notification to configured GSM number. After device regains GNSS signal, Digital Output is immediately deactivated and a new record is sent to the server. This Digital Output activation can be used to trigger measures to disrupt potential thieves using GNSS signal jamming to steal your vehicle. GNSS Jamming record is stored in AVL ID 318 parameter and has 3 possible values:

0 - No Jamming,

1 - Jamming warning status, which means that signal and accuracy is disrupted but device is able to hold GPS fix for at least 5 seconds.

2 - Jamming critical status, which means that device is not able to acquire GPS fix.

Worth mentioning, that Jamming Detection can go from any state to any other in 1 second intervals. It is completely dependent on received NMEA data by GNSS receiver. Therefore, it is possible in repeated jamming scenario for the state to rapidly go from 0 to 2 and backwards. Also, GNSS Jamming functionality is capable to separate indoor areas (e.g. underground parking) from events when jamming is actually happening. This is possible because in-band jamming will affect internal PGA (Programmable Gain Amplifier) degrade, as a result, CNR (Carrier-to-noise ratio) will degrade as well. On the other hand, if CNR degrade is degraded only because of underground or signal covered, internal PGA gain will keep almost the same.

Eventual Records parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise, it will be appended only to eventual records.

Note: GNSS Jamming is only available since 03.28.03.Rev.03 or newer firmware version.

Note: GNSS Jamming is not available on 3.80, 3.82 but available on 5.10, 5.1.5, 5.1.8 or newer GNSS module firmware versions. GNSS module version can be checked by SMS\GPRS command - getver

Note that this scenario will not work with Deep Sleep, Ultra Deep Sleep and Online Deep Sleep modes, since they disable the device's GNSS module to save power.

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. Descriptions for the values are as follows.

City Consumption (l/100km): Car average fuel consumption in the city. Presented in your car technical documentation.
Highway Consumption (l/100km): Car average fuel consumption on highway. Presented in your car technical documentation.
Average Consumption (l/100km): Car avg fuel consumption in mixed roads (city and highway). Presented in your car technical documentation.

When speed is higher than the highway fuel consumption speed, x% of highway fuel consumption is added every extra y km/h, by default FMT100 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 FMT100 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.

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

@@ Line 3: / Line 3: @@
 |immobilizer_feature =
 |dout_control_via_call_feature =
-|eco_green = 300px
+|Data_output =
+|dout =
+|eco_green = [[Image:FMT100_Green_Eco_Driving_feature.png|300px|right]]
+|txt_ecodout =
 |over_speed = 300px
 |jamming = 378px
-|gnss_fuel_counter = 375px}}
+|gnss_fuel_counter = 375px
+|over_speeding_dout =
+|jamming_dout =
+|SECO =
+|dout_type=
+|dout_control_via_ignition_feature=
+}}
+[[Category:FMT100 Configuration]]