Jump to content
  • EN

Template:FMM Features settings: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
No edit summary
 
(20 intermediate revisions by 8 users not shown)
Line 1: Line 1:
==Eco/Green Driving==
==Eco/Green Driving==
[[File:EcoGreen Driving configurator.png|{{{general|size}}}|right]]


{{{eco_green|[[Image:EcoGreen_Driving.gif|{{{general|size}}}|right]]}}}
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<sup>2</sup> units. The scenario is activated until the current Acceleration, Braking, or Cornering value decreases below the set parameter value.<br />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'''.


When vehicle parameters exceed the values of ''Max Acceleration'', ''Max Braking'' or ''Max Cornering'' parameters, the scenario is activated: a record is generated and digital output status is changed to 1 when configured. You can configure all three parameters in m/s<sup>2</sup> units. Scenario is activated until current Acceleration, Braking or Cornering value decreases below the set parameter value.<br/>Parameters used with ''Eco/Green Driving'' functionality are given in a table below.
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'''.  


<table class="nd-othertables" style="width: 68%;">
<table class="nd-othertables" style="width: 68%;">
Line 30: Line 38:
         <td style="width: 8%; text-align:left">Which source (GPS or accelerometer) data will be collected from.</td>
         <td style="width: 8%; text-align:left">Which source (GPS or accelerometer) data will be collected from.</td>
     </tr>
     </tr>
<tr>
    <tr>
        <td style="width: 8%; text-align:left">[[{{{model}}} Features settings#Advanced Eco Driving|Advanced Eco Driving]]</td>
        <td style="width: 8%; text-align:left">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.</td>
    </tr>
    <tr>
         <td style="width: 8%; text-align:left">Eco/Green Driving Duration</td>
         <td style="width: 8%; text-align:left">Eco/Green Driving Duration</td>
         <td style="width: 8%; text-align:left">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.</td>
         <td style="width: 8%; text-align:left">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.</td>
     </tr>
     </tr>
{{{txt_ecodout|<tr>
    {{#switch: {{{model}}}
| FMP100 | FMB010 | FMB020 | FMC800 | FMM800 | FMM80A | FMT100 | FMC880 | FMM880 | FMB001 |FMB003 |FMC003 |FMM003 |FMM00A =
| #default =
    <tr>
         <td style="width: 8%; text-align:left">Output Control</td>
         <td style="width: 8%; text-align:left">Output Control</td>
         <td style="width: 8%; text-align:left">Which [[{{{model|FMM1YX}}}]] Digital Output will be used for accesory (buzzer, LED and etc.) activation/deactivation.</td>
         <td style="width: 8%; text-align:left">Which Digital Output will be used for accesory (buzzer, LED and etc.) activation/deactivation.</td>
     </tr>
     </tr>}}
<tr>
<tr>
        <td style="width: 8%; text-align:left">DOUT ON Duration</td>
     
        <td style="width: 8%; text-align:left">A value in miliseconds (ms), for how long DOUT should be active.</td>
     </tr>
     </tr>
<tr>
<tr>
        <td style="width: 8%; text-align:left">DOUT OFF Duration</td>
        <td style="width: 8%; text-align:left">A value in miliseconds (ms), for how long DOUT should be inactive.</td>
    </tr>}}}
<!--<tr>
         <td style="width: 8%; text-align:left">Send SMS to</td>
         <td style="width: 8%; text-align:left">Send SMS to</td>
         <td style="width: 8%; text-align:left">GSM number of receiver which will get notifications of Eco/Green Driving feature.</td>
         <td style="width: 8%; text-align:left">GSM number of receiver which will get notifications of Eco/Green Driving feature.</td>
Line 53: Line 63:
         <td style="width: 8%; text-align:left">SMS Text</td>
         <td style="width: 8%; text-align:left">SMS Text</td>
         <td style="width: 8%; text-align:left">SMS text, which the receiver will get.</td>
         <td style="width: 8%; text-align:left">SMS text, which the receiver will get.</td>
     </tr> -->
     </tr>
</table>
</table>
<br/><br/>
{{{FMT100_eco|}}}


<br/><br/><br/>
===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.
 
<table class="nd-othertables" style="width: 68%;">
<tr>
      <th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
      <th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
    </tr>
<tr>
        <td style="width: 8%; text-align:left;">Eco Driving Average</td>
        <td style="width: 8%; text-align:left;">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.</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left;">Eco Driving Maximum</td>
        <td style="width: 8%; text-align:left;">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.</td>
    </tr>
</table>
 
 
===Data output===
===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 ([[{{{model|FMM1YX}}}]] must be properly configured in order to send the record). Event value is multiplied by 100 before sending/saving record to get more precision when displaying data.{{{text_dout|<br/>{{{dout|info}}}}}}
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 ([[{{{model|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.{{{text_dout|<br/>}}}<br/><youtube>RlkJELdVGRs</youtube>


===Auto calibration===
===Auto calibration===
----
----
The auto-calibration process is following:
The auto-calibration process is following:
# The vehicle is stopped.
 
# There is a straight road ahead.
#The vehicle is stopped.
# Send SMS ''"auto_calibrate:set"'' to the {{{model_2|FMM}}} device.
#There is a straight road ahead.
# Accelerate to >30 km/h for 5 sec.
#Send SMS ''"auto_calibrate:set"'' to the {{{model_2|FMB}}} device.
# {{{model_2|FMM}}} will send a response when calibration is completed successfully.
#Accelerate to >30 km/h for 5 sec.
#{{{model_2|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.
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 {{{model_2|FMM}}} device: ''"auto_calibrate:get"''.
To check auto-calibration status send a following short text message to the {{{model_2|FMB}}} device: ''"auto_calibrate:get"''.


==Over Speeding==
==Over Speeding==


[[Image:FMB120_Over_Speeding.png|300px|size|right]]
When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}}.<br />Scenario is active until detected speed decreases below the set parameter value. Configurable parameters:
[[Image:Over_Speeding.PNG|{{{general|size}}}|right]]  
<br />
*Scenario settings – defines priority of over speeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.
*Max speed – it is max allowed speed which can be reached. If speed exceeded configured value, then event will occur.
*Send SMS to – GSM number to which SMS event will be sent.
*SMS text – SMS text.
<br /><br /><br /><br /><br />
{{{jamming1|
==Jamming==


When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}}.<br/>Scenario is active until detected speed decreases below the set parameter value.<br/>{{{over_speeding_dout|info}}}
<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>


[[Image:Jamming.gif|{{{general|size}}}|right]]


{{{template_link|}}}
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 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 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.


{{{dout_control_via_call_feature|== DOUT Control Via Call==
Connecting a Buzzer to the Digital Output to emit sounds as soon as jamming is detected is the most straightforward use of this scenario.


[[Image:FMB120_DOUT_Control_Via_Call.png|295px|size|right]]
The Digital Output can be directly connected to the vehicle's alarm system to ensure the thief can not avoid triggering it.


Scenario is activated and digital output is ON when call is received from a number which is on the authorized numbers list.<br/>
It can also be connected to the central lock system to ensure that all the doors are locked.
Call control functionality is following:
 
* When [[{{{model|FMM1YX}}}]] is configured to control {{{text_dout|DOUT1/DOUT2}}} the device waits for an incoming call from a configured secure number. If a call is received [[{{{model|FMM1YX}}}]] turns on {{{text_dout|DOUT1/DOUT2}}} for a user defined ''Duration Timeout''. If duration timeout set to "0" {{{text_dout|DOUT1/DOUT2}}} will be OFF.
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 [[{{{model|FMB1YX}}}_Sleep_modes#Deep_Sleep_mode|Deep Sleep]], [[{{{model|FMB1YX}}}_Sleep_modes#Ultra_Deep_Sleep_mode|Ultra Deep Sleep]] and [[{{{model|FMB1YX}}}_Sleep_modes#Online_Deep_Sleep_mode|Online Deep Sleep]] modes, since they disable the device's GSM module to save power.'''
 
''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: '''[https://www.youtube.com/watch?v=otQd34WqL54 Teltonika Jamming Detection scenario]'''
}}}
{{#switch: {{{model}}}
|FMT100 |FMC880| FMM880 |FMC800 |FMM800 |FMM920 |FMM130 |FMM230 =
|#default =
{{{dout_control_via_call_feature|==DOUT Control Via Call==
 
[[Image:DOUT_Control_Via_Call.gif|{{{general|size}}}|right]]
 
The scenario is activated and digital output is ON when a call is received from a number that is on the authorized numbers list.<br/>
Call control functionality is the following:
* When [[{{{model|FMB1YX}}}]] is configured to control {{{text_dout|DOUT1/DOUT2}}} the device waits for an incoming call from a configured secure number. If a call is received [[{{{model|FMB1YX}}}]] turns on {{{text_dout|DOUT1/DOUT2}}} for a user defined ''Duration Timeout''. If duration timeout set to "0" {{{text_dout|DOUT1/DOUT2}}} will be OFF.
* {{{text_dout|DOUT1/DOUT2}}} can be turned off by ''Duration Timeout'' or by {{{text_din|digital input 1, digital input 2 or digital input 3}}}.
* {{{text_dout|DOUT1/DOUT2}}} can be turned off by ''Duration Timeout'' or by {{{text_din|digital input 1, digital input 2 or digital input 3}}}.
* {{{text_dout|DOUT1/DOUT2}}} will always be ON if, for example, DOUT deactivation is set to DIN1, but DIN1 will be never turned ON, or when duration timeout is set to maximum value (2147483647) which is about 68 years.
* {{{text_dout|DOUT1/DOUT2}}} will always be ON if, for example, DOUT deactivation is set to DIN1, but DIN1 will be never turned ON, or when duration timeout is set to the maximum value (2147483647) which is about 68 years.}}}
{{{dout_control_dout|info}}}}}}
 
{{#switch: {{{model}}}
|FMC880 |FMM880 |FMC800 |FMM800 =
|#default =
==Immobilizer==
[[File:Immobilizer1.png|right]]
'''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.
 
{{#switch: {{{model}}}
|#default =
|FMB125 |FMC125 |FMM125 |FMB225 |FMC225 =
===Alcotest Check===
'''Note:''' This functionality configuration is visible only when RS232 mode Mercury C4 is configured.
 
When Alcotest Check functionality is enabled, immobilizer will authorize only when data is received from a breathalyzer. The breathalyzer result is sent in passive mode and any alcohol value will stop the immobilize authorization.
 
In active mode, the device checks if the result does not exceed the configured BCA Threshold value. The breathalyzer result is held for 3 minutes. After the 3-minute timeout expires, a new alcotest result has to be received to authorize a driver.
 
iButton/Beacon function:
 
*When iButton/Beacon list is not configured, the driver can only be authorized with a breathalyzer.
*When iButton/Beacon list is configured, the driver can be authorized only when an authorized iButton/Beacon is attached and no alcohol was found.
 
'''Note:''' Devices that do not have RS232 will have support for 1-Wire and Beacon only. Device that do not have RS232 and 1-Wire will have support for Beacon Only. Parameter default value has been changed from 0 to 9. After firmware update it should change it’s value automatically if it was set to 0 before.
 
When Alcotest Check functionality is disabled, immobilizer works like usual. Alcotest check has new eventual IO element that is generated each time new breathalyzer result is received. If SMS event is configured, then SMS will be sent to configured number. IO value consists of alcotest result and test mode. IO elements size is 2 bytes. First 14 MSB bits are for alcotest result, and last 2 for test mode. Alcotest value is in relims (‰) multiplied by 1000.
 
Test mode values:
*0 – Passive
*1 – Active
 
Example Data: alcotest result value is 0x0111 → 0b0000000100010001.


<br/>
<table class="nd-othertables" style="width: 80%;">
<tr>
        <th style="width: 10%; text-align:left; vertical-align:left; color:black">Bits</th>
        <th style="width: 20%; text-align:left; vertical-align:left; color:black">Binary Value</th>
        <th style="width: 50%; text-align:left; vertical-align:left; color:black">Description</th>
    </tr>
    <tr>
        <td style="width: 10%; text-align:left;">15..2</td>
        <td style="width: 20%; text-align:left">00000001000100</td>
        <td style="width: 50%; text-align:left">0x44 = 68 → 68/1000 = 0.068‰</td>
    </tr>
    <tr>
        <td style="width: 10%; text-align:left;">1..0</td>
        <td style="width: 20%; text-align:left">01</td>
        <td style="width: 50%; text-align:left">0x01 = 1 → Active mode</td>
    </tr>
</table>
}}


{{{immobilizer_feature|==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.


[[Image:FMB120_Immobilizer.png|300px|size|right]]
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.  


If ''DOUT Control'' is disabled, scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID is attached, {{{text_dout|DOUT1/DOUT2}}} turns OFF. After iButton identification configured ''Ignition Source'' can be turned OFF (''Ignition Source'' is configured to 0) for no longer than 30 seconds, otherwise immobilizer must be repeated. If ''iButton List Check'' parameter is enabled, authorization will be successful only if the attached iButton is specified in iButton list.<br/>{{{immobilizer_dout|info}}}
===No Authentication Timeout===
<br/><br/>
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.
Ignition off timeout parameter is used to set the duration after which authorization is activated, when ignition is turned off. For example, if Ignition off timeout is set to 30 seconds, when the driver turns the ignition off, he has 30 seconds until the immobilizer security check turns on again. In other words, if the driver turns off the ignition and turns it back on in less than 30 seconds, then he will not have to attach the iButton to the reader again.
<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>}}}


{{{ibutton_feature|==iButton Read Notification==
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.


[[Image:FMB120_iButton_Read_Notification.png|375px|size|right]]
===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.


This functionality allows user to see when iButton is read. {{{text_dout|DOUT1/DOUT2}}} turns on for a configured duration and after DOUT ON duration ends {{{text_dout|DOUT1/DOUT2}}} does not turn on even if iButton is left attached.<br/>{{{ibutton_dout|info}}}
'''Note:''' Immobilizer records are only created if ignition is ON.  
<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>}}}


===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.
}}
{{#switch: {{{model}}}
|FMC880 |FMM880 |FMC800 |FMM800| FMT100 =
| #default =
==Authorized Read Notification==
[[File:Authorized Read Notification.gif|right]]
'''Important: iButton Read Notification feature has been replaced with Authorized Read Notification starting from Firmware Ver.03.30.00'''
Authorized read notification feature allows the control of selected DOUT for a configured period, when '''Authorized ID''' is read using '''1-Wire, RFID Reader''' or when Authorized Beacon is detected. If Authorized ID List is empty or Beacon detection is set to All, then any detected ID or Beacon can control selected DOUT. Parameter '''Depend on Ignition''' allows to disable DOUT control, while Ignition is being detected. It is necessary to select at least one source for this functionality to work.
Authorized Read Notification parameters:
*'''Output Control''' – available scenario settings for module Digital output activation/deactivation
*'''DOUT ON Duration''' – a value in seconds, for how long DOUT1/DOUT2 should be active or inactive.
*'''Authorization ID List Checking''' - Provides Authorized ID information from a designated source.
*FMB devices that do not have RS232 will have support for 1-Wire and Beacon only.
*FMB devices that do not have RS232 and 1-Wire will have support for Beacon only.
*'''Depend on Ignition''' - Output will be triggered only if ignition is off.
'''Note:''' Authorized read notification is disabled in '''deep sleep, online deep sleep''' and '''ultra deep sleep''' modes.
}}
{{{gnss_fuel|
==GNSS Fuel Counter==
==GNSS Fuel Counter==


[[Image:FMB120_GNSS_Fuel_Counter.png|375px|size|right]]
[[Image:GNSS_Fuel_Counter.gif|{{{general|size}}}|right]]
 
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.


# 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 [[{{{model|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.
# When speed is higher than the highway fuel consumption speed, x% of highway fuel consumption is added every extra y km/h, by default [[{{{model|FMM1YX}}}]] 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 correction coefficient is 1 and [[{{{model|FMM1YX}}}]] calculates that the amount of used fuel over 35 m distance is 20 ml, the value of 20 ml will be sent to the server, and if correction coefficient is 1.2, the value of 20 * 1.2 = 24 ml will be sent to the server.
# ''Fuel Consumption on Idling'' is used to calculate fuel consumption when the ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with a minimum and maximum of accordingly 0 and 5 l/h. This parameter is less than 1.0 l/h for almost all diesel cars and is equal to about 1.5 – 2.0 l/h for gasoline cars.


{{{dout_control_via_ignition_feature|==DOUT Control Via Ignition==
''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 [[{{{model|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, and if correction coefficient is 1.2, the value of 20 * 1.2 = 24 ml will be sent to the server.


[[Image:DOUT Control via Ignition.png|{{{dout_control_via_ignition|size}}}|right]]
''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.
}}}
{{#switch: {{{model}}}
|FMT100 |FMC880| FMM880 |FMC800 |FMM800 =
|#default =
==DOUT Control Via Ignition==


This feature allows direct control of DOUT by configured ignition source status. When enabled, the function will start to monitor ignition status, and once the ignition changes state from On to Off after configured Ignition Off timeout, selected DOUT (Digital Output) will be turned On.<br/><br/>
[[File:DOUT Control Via Ignition1.png|right]]


Turning DOUT Off is possible with enough voltage applied to the configured DIN (Digital Input). Voltage requirements: DIN1 – 7.5V, DIN2-4 – 2.5V.<br/><br/>
This feature allows direct control of '''DOUT''' (Digital Output)  by the configured ignition source status. When enabled, the function will monitor '''ignition status''', and once the ignition changes state from On to Off after the configured Ignition OFF Timeout, the selected DOUT will be turned On.
 
Turning DOUT Off is possible with sufficient voltage applied to the configured DIN (Digital Input) or by turning on the ignition.  
 
Voltage requirements:  
*'''DIN1''' - 7.5V,  
*'''DIN2-4''' – 2.5V.<br/><br/>


<table class="nd-othertables" style="width: 68%;">
<table class="nd-othertables" style="width: 68%;">
Line 134: Line 293:
         <th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
         <th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
         <th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
         <th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
    </tr>
<tr>
        <td style="width: 8%; text-align:left;">DOUT Control via Ignition Scenario</td>
        <td style="width: 8%; text-align:left">Enable/Disable DOUT Control Via Ignition scenario</td>
     </tr>
     </tr>
<tr>
<tr>
Line 151: Line 306:
         <td style="width: 8%; text-align:left">Duration (in seconds) after which DOUT is turned on, when ignition is turned off</td>
         <td style="width: 8%; text-align:left">Duration (in seconds) after which DOUT is turned on, when ignition is turned off</td>
     </tr>
     </tr>
</table>}}}
</table>
}}
==Ignition ON Counter==
[[File:Ignition on.gif|right]]
===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''').
<br><br>
{{{dout_type|
==DOUT 1 Output Type==
[[File:Dout1 output type.gif|right]] '''DOUT 1 Output Type''' functionality sets the initial ''DOUT1'' state. If functionality is configured in ''Normal'' mode digital output inactive state is low and when it is controlled by any scenario digital output is set to high state. Whenever functionality is configured in ''Inverted'' mode digital output inactive state is high  and when it is controlled by any scenario digital output is set to low state.<br></br>
 
DOUT1 in '''Normal''' state:
[[File:DoutNormal.jpg|thumb|left|500px]]
<br></br><br></br><br></br><br></br></br>
 
DOUT1 in '''Inverted''' state:
[[File:InvertedDout.png|thumb|left|500px]]
<br></br><br></br><br></br>
 
 
 
 
*'''<u>Notice!</u>''' Digital output type control functionality will not affect SMS/GPRS command '''setdigout''' execution. <br></br>
 
[[File:Alert.png|50px]] <b>Available from Firmware version: [[ {{{model|}}}_firmware_errata|3.27.07.Rev.00]] </b>
 
 
}}}
{{{SECO|{{Template:Secure_vehicle_disabling}}}}}

Latest revision as of 11:37, 29 May 2026

Eco/Green Driving

size
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/s2 units. The scenario is activated until the current Acceleration, Braking, or Cornering value decreases below the set parameter value.
Parameters used with Eco/Green Driving functionality are given in a table below.

GPS Source

When selected source is GPS device calculates harsh driving values from GPS data at 1 Hz frequency. This means green driving time accuracy is 1s. Acceleration is calculated every 1 second, based on speed difference between GPS samples.

  • Vehicle speed must be equal or greater than 10 km/h for acceleration/braking.
  • Vehicle speed must be equal or greater than 30 km/h for cornering.

While using Green driving (GPS) harsh cornering is determined by calculating an angle difference and the speed change in m/s between two NMEA coordinates. This leads to calculation and approximation of angular speed of the vehicle in m/s. It is recommended to use accelerometer data to measure harsh driving as GPS source is less accurate.

While Green Driving event is active, two records will be created every second - Event Type and Event Duration.

Parameter name Description
Scenario Settings Enable/Disable Green driving functionality
Max Acceleration Value which can be reached while accelerating without triggering harsh acceleration event.
Max Braking Acceleration Value which can be reached while braking without triggering harsh braking event.
Max Cornering Acceleration Value which can be reached while cornering without triggering harsh cornering event.
Source Which source (GPS or accelerometer) data will be collected from.
[[{{{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.


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

Auto calibration

The auto-calibration process is following:

  1. The vehicle is stopped.
  2. There is a straight road ahead.
  3. Send SMS "auto_calibrate:set" to the FMB device.
  4. Accelerate to >30 km/h for 5 sec.
  5. FMB will send a response when calibration is completed successfully.

Calibration is saved to internal flash memory, which means it will stay after a reset. To check auto-calibration status send a following short text message to the FMB device: "auto_calibrate:get".

Over Speeding

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

size
size


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






Jamming

size
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 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 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 can not 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 and Online Deep Sleep modes, since they disable the device's GSM module to save power.

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

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

DOUT Control Via Call

size
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 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 be never turned ON, or when duration timeout is set to the maximum value (2147483647) which is about 68 years.

Immobilizer

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

Function

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

When attempting to start the vehicle:

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

Authorization

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

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

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


Immobilizer Authorization Timeout

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

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

No Authentication Timeout

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

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

Authorization Timeout Limit

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

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

Sleep Mode Considerations

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

Authorized Read Notification

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

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

Authorized Read Notification parameters:

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

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

GNSS Fuel Counter

size
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 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 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, and if correction coefficient is 1.2, the value of 20 * 1.2 = 24 ml will be sent to the server.

Fuel Consumption on Idling is used to calculate fuel consumption when the ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with a minimum and maximum of accordingly 0 and 5 l/h. This parameter is less than 1.0 l/h for almost all diesel cars and is equal to about 1.5 – 2.0 l/h for gasoline cars.

DOUT Control Via Ignition

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

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

Voltage requirements:

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

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

Ignition ON Counter

Overview

The Ignition ON Counter tracks the total time the ignition has been active, measured in seconds. This counter operates based on your selected Ignition source, which determines when counting starts and stops.

How It Works

  • You can set a starting counter value up to 2147483647 seconds.
  • The counter continues from where it left off each time the ignition turns ON again.
  • When the maximum value is reached, the counter automatically resets to 0.
  • The counter value is saved to internal memory when ignition turns OFF, ensuring data accuracy in case of a restart.

Important Notes

  • Performing a device reset will NOT return the counter to its original configured value.
  • The internal memory is updated each time the ignition turns OFF.
  • Proper function requires correct configuration of your Ignition source

Configuration

1. Enable Ignition ON counter (ID 13500)

  • 0 - disabled
  • 1 - enabled

2. Use the "Ignition On Counter value" parameter to set the initial starting value (in seconds) from which the device will begin counting (ID 13501).

DOUT 1 Output Type

DOUT 1 Output Type functionality sets the initial DOUT1 state. If functionality is configured in Normal mode digital output inactive state is low and when it is controlled by any scenario digital output is set to high state. Whenever functionality is configured in Inverted mode digital output inactive state is high and when it is controlled by any scenario 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



Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Template:FMM_Features_settings&oldid=113871"