Template:FMC 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.
[[{{{model}}} Features settings#Advanced Eco Driving|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.

Advanced Eco Driving

From 03.25.14.Rev.03 base firmware version, a new parameter has been added (Eco Driving Maximum and Eco Driving Average) to the FMT100 device. This parameter is enabled by default.

When this parameter is enabled, the device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to the server. When enabled, the device does not send the Green Driving value IO element 254.

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 the Eco Driving event's Average value to be saved and sent 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 the Eco Driving event's Maximum value to be saved and sent to the server.

Eco/Green Driving scenario is supported by the FMB1YX device.

Data output

---

Data from accelerometer/GPS are continuously monitored and processed and are used to decide whether a harsh event has occurred. If either of three cases is satisfied, an event is generated and a record is saved and sent to the server (FMB1YX 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

Data output is also supported by the FMB1YX device.

Auto calibration

---

The auto-calibration process is as follows:

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 remain after a reset. To check auto-calibration status, send the following short text message to the FMB device: "auto_calibrate:get".

Auto calibration is also supported by the FMB1YX device.

Over Speeding

When vehicle speed exceeds the configured maximum speed value, the scenario is activated, and an event record is generated. Detected speed has to be greater than (configured max speed + 3% of configured max speed) for the overspeeding event to start. To stop the overspeeding event, detected speed has to be lower than (configured max speed - 3% of configured max speed). Configurable parameters:

size

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

Over Speeding scenario is supported by the FMB1YX device.

Jamming

size

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 and the digital output status is changed to 1 when configured. If the device regains a GSM signal before the countdown ends, no event will be generated and the output will not be controlled. This Digital Output activation can be used to trigger measures to disrupt potential thieves using GSM signal jamming to steal your vehicle.

Connecting a Buzzer to the Digital Output to emit sounds as soon as jamming is detected is the most straightforward use of this scenario.

The Digital Output can be directly connected to the vehicle's alarm system to ensure the thief cannot avoid triggering it.

It can also be connected to the central lock system to ensure that all the doors are locked.

A relay can be used to disable the starter motor. Usually used with the Immobilizer scenario.

Alternatively, the Digital output can also be connected to an LED visible to the driver to inform the driver when Jamming occurs.

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

Jamming scenario is also supported by the FMB1YX device.

DOUT Control Via Call

size

The scenario is activated and digital output is ON when a call is received from a number that is on the authorized numbers list.
Call control functionality is the following:

• When FMB1YX is configured to control DOUT1/DOUT2, the device waits for an incoming call from a configured secure number. If a call is received, FMB1YX turns on DOUT1/DOUT2 for a user-defined Duration Timeout. If Duration Timeout is set to "0", DOUT1/DOUT2 will be OFF.
• DOUT1/DOUT2 can be turned off by Duration Timeout or by digital input 1, digital input 2 or digital input 3.
• DOUT1/DOUT2 will always be ON if, for example, DOUT deactivation is set to DIN1, but DIN1 will never be turned ON, or when Duration Timeout is set to the maximum value (2147483647) which is about 68 years.

DOUT Control Via Call scenario is also supported by the FMB1YX device.

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.

SECO

The solution, introduced in firmware version 03.28.02, is designed to stop a stolen vehicle without causing accidents. It accomplishes this by pulsing digital output to disable the fuel pump at intervals until the vehicle slows down to a configured speed, at which point the pump is fully disabled.
Parameters used with SECO functionality are given in a table below.

Parameter name	Description	Parameter ID
Scenario Settings	Enable/Disable SECO functionality	12250
Eventual Records	If disabled – scenario status value will be appended in each AVL record	12251
Output Control	Available scenario settings for module Digital output activation/deactivation	12252
Speed	Digital output will be activated if vehicle speed is consistently lower than the configured value during the "Speed check period"	12254
Speed Pulse scenario	Valid if "Output Pulse" feature is enabled. The scenario will be activated if vehicle speed is consistently lower than the configured value during the "Speed check period". After activation, digital output will be activated and disabled continuously until speed is lower than the value configured in the "Speed" field and longer than the "Speed check period".	12259
Speed check period	Time span during which vehicle speed must be lower than configured for output to activate.	12255
Momevemt timeout	Accelerometer's instant movement timeout after which output will be activated (GNSS OFF)	12256
Output pulse	Pulse scenario adds additional output control, which helps to slow down the vehicle before fully disabling the fuel pump.	12253
DOUT ON duration	A value in milliseconds for how long DOUT should be active.	12257
DOUT OFF duration	A value in milliseconds for how long DOUT should be inactive.	12258

SECO SMS Commands

Secure engine cut-off (SECO) functionality is available for devices with at least one DOUT. For SECO functionality to work, DOUT must be selected. SECO has a DOUT control priority higher than the immobilizer scenario.
SECO scenario can only be enabled or disabled by SMS commands:

• "secoon" - to activate SECO functionality.
• "secooff" - to disable SECO functionality.

The structure of sending SMS commands: FMB130 SMS/GPRS Commands

1. SMS responses

To the SMS command „secooff“ the device will give the response: „Seco off received. DOUTX off“.

To the SMS command „secoon“ the responses are:

1. „Seco on received. Waiting for conditions“.

2. „Seco on received. DOUTX pulsing“.

3. „Seco on received. DOUTX on“.

When the response is not 3, all later SMS will be received. Example: SMS 1 is received and pulse configured, then SMS 2 will be received when speed is lower than configured, and SMS 3 will be received when speed reaches 0 km/h.
Note: Sending commands to a device without DOUT will give the response "SECO not available for this device". When DOUT is not selected in the configuration, the response will be: "Error. no DOUT configured". This secure vehicle disabling solution is supported by any Teltonika FMB series tracker (excluding FMX640 series trackers). Also, a SIM card is required to get data to your server.

For more information about SECO configuration, please see here.

SECO functionality is also supported by the FMB1YX device.

iButton Read Notification

Output control parameter lets the user choose which DOUT will blink when an iButton is connected. After connecting an iButton, DOUT will blink for the period of time configured in the DOUT ON Duration parameter. The iButton List Checking parameter configures whether the device reads the iButton ID from the list or not. For example, if configured as Enabled, the device will not blink DOUT unless the iButton is in the iButton list. If the Depend on Ignition parameter is enabled, then Output will be triggered only if ignition is off (in addition to being in a list if iButton List Checking is also enabled). Output control examples when iButton is detected (if None is selected in Output Control – all of the following steps will be skipped):

• If both iButton List Checking and Depend on Ignition are disabled – Output is triggered.
• If iButton List Checking is enabled and Depend on Ignition is disabled – Output is triggered only if iButton is in the list.
• If iButton List Checking is disabled but Depend on Ignition is enabled – Output is triggered only if ignition is off.
• If both iButton List Checking and Depend on Ignition are enabled – Output will trigger if iButton is in the list and ignition is off.

iButton Read Notification parameters:

• Output control – available scenario settings for module Digital output activation/deactivation
• DOUT ON/OFF duration – a value in seconds, for how long DOUT1/DOUT2 should be active or inactive.
• iButton List checking – parameter configures that the device reads the iButton ID from the list or not.
• Depend on Ignition – Output will be triggered only if ignition is off

iButton Read Notification is also supported by the FMB1YX device.

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, FMB1YX adds 20% every 50 km/h of extra speed. For example, the fuel consumption is (1.2 * (Highway Fuel Consumption)) at 140 km/h and (1.4 * (Highway Fuel Consumption)) at 190 km/h.

Correction coefficient is used to correct every value of fuel consumption which is sent to the server through the expression ((Used Fuel) * Correction coefficient). By default, it is 1, with minimum and maximum values of 0.01 and 2, respectively. For example, when the correction coefficient is 1 and FMB1YX calculates that the amount of used fuel over 35 m distance is 20 ml, the value of 20 ml will be sent to the server; if the correction coefficient is 1.2, the value of 20 * 1.2 = 24 ml will be sent to the server.

Fuel Consumption on Idling is used to calculate fuel consumption when the ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with minimum and maximum of 0 and 5 l/h, respectively. This parameter is usually less than 1.0 l/h for most diesel cars and around 1.5 – 2.0 l/h for gasoline cars. GNSS Fuel Counter functionality is also supported by the FMB1YX device.

Ignition ON Counter

Ignition ON Counter scenario counts the time spent with the ignition on in the resolution of seconds.
It is possible to configure a starting value of the counter. Maximum value: 2147483647 seconds or 596523.235 hours. NOTE THAT, when entering a starting value, the value must be in seconds!

Example of Ignition On Counter I/O element:

Ignition ON Counter scenario is also supported by the FMB1YX device.

DOUT 1 Output Type

FMB1YX DOUT 1 Output Type functionality sets the initial DOUT1 state. If the functionality is configured in Normal mode, the digital output inactive state is low, and when it is controlled by any scenario the digital output is set to high state. Whenever the functionality is configured in Inverted mode, the digital output inactive state is high, and when it is controlled by any scenario the digital output is set to low state.

DOUT1 in Normal state:

DOUT1 in Inverted state:

• Notice! Digital output type control functionality will not affect SMS/GPRS command setdigout execution.
  
  

Available from Firmware version: 3.27.07.Rev.00