Jump to content
  • EN

Template:FMB Features settings: Difference between revisions

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


[[Image:Fmb120_green_driving.png|300px|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 exceeds on of Max Acceleration, Max Braking or Max Cornering parameters value, scenario is activated, record will be generated and digital output status will be changed to 1 (if configured). You can configure all three parameters in m/s<sup>2</sup> (meter per second squared) units. Scenario is activated until current Acceleration, Braking or Cornering value decreases below parameter value.<br/>
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.
Parameters used with Green Driving functionality are given in a table below.


{| class="wikitable"
While Green Driving event is active, two records will be created every second - '''Event Type''' and '''Event Duration'''.  
|+
! style="width: 150px; background: black; color: white;"  | Parameter name
! style="width: 500px; background: black; color: white;" | Description
|-
! style="text-align: left; vertical-align: top;" | Scenario Settings
| style="text-align: left; vertical-align: top;" | Enable/Disable Green driving functionality.
|-
! style="text-align: left; vertical-align: top;" | Max Acceleration
| style="text-align: left; vertical-align: top;" | Value which can be reached while accelerating without triggering harsh acceleration event.
|-
! style="text-align: left; vertical-align: top;" | Max Braking Acceleration
| style="text-align: left; vertical-align: top;" | Value which can be reached while braking without triggering harsh braking event.
|-
! style="text-align: left; vertical-align: top;" | Max Cornering Acceleration
| style="text-align: left; vertical-align: top;" | Value which can be reached while cornering without triggering harsh cornering event.
|-
! style="text-align: left; vertical-align: top;" | Source
| style="text-align: left; vertical-align: top;" | Which source (GPS or accelerometer) data will be collected from.
|-
|}


===Data output===
<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;">Scenario Settings</td>
        <td style="width: 8%; text-align:left">Enable/Disable Green driving functionality</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Max Acceleration</td>
        <td style="width: 8%; text-align:left">Value which can be reached while accelerating without triggering harsh acceleration event.</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Max Braking Acceleration</td>
        <td style="width: 8%; text-align:left">Value which can be reached while braking without triggering harsh braking event.</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Max Cornering Acceleration</td>
        <td style="width: 8%; text-align:left">Value which can be reached while cornering without triggering harsh cornering event.</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Source</td>
        <td style="width: 8%; text-align:left">Which source (GPS or accelerometer) data will be collected from.</td>
    </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">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>
    {{#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">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">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>
    </tr>
<tr>
        <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>
    </tr>
</table>
 
===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.


Green driving functionality generates events on three cases. If vehicles:
<table class="nd-othertables" style="width: 68%;">
* Acceleration exceeds defined parameter value.
<tr>
* Deceleration (braking) exceeds defined value.
      <th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
* Cornering force exceeds defined value.
      <th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
Program continously monitors and process data from accelerometer/GPS than decides whether harsh event is detected or not. If any of three cases are satisfied event is generated. Record is saved and sent to server (FMB120 must be configured properly). Event value is multiplied by 10 before sending/saving record to get more precision when displaying data*.
    </tr>
Digital output 1 or digital output 2 can be activated for a period of time to warn driver. Output on-time should/can be configured separately for each feature case.
<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 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 as follows:


# Vehicle is stopped.
#The vehicle is stopped.
# Road is straight.
#There is a straight road ahead.
# Send SMS ''<span style=color:#F6A83E>auto_calibrate:set</span>''.
#Send SMS ''"auto_calibrate:set"'' to the {{{model_2|FMB}}} device.
# Accelerate to > 30 km/h for 5 sec.
#Accelerate to >30 km/h for 5 sec.
# FMB will send response when calibration is success.
#{{{model_2|FMB}}} will send a response when calibration is completed successfully.
Calibration is saved to Internal Flash, after restart should be the same.
 
To check autocalibration status send: ''<span style=color:#F6A83E>auto_calibrate:get</span>''.
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|FMB}}} device: ''"auto_calibrate:get"''.


==Over Speeding==
==Over Speeding==
[[File:Overspeeding.png|{{{general|size}}}|right]]
When vehicle speed exceeds configured maximum speed value the scenario is activated, and an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}}.<br />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:
<br />
*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.
<br />
==Network Jamming==
[[File:Network Jamming.png|{{{general|size}}}|right]]
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 [[{{{model|FMB1YX}}}_Sleep_modes#Deep_Sleep_mode|Deep Sleep]], [[{{{model|FMB1YX}}}_Sleep_modes#Ultra_Deep_Sleep_mode|Ultra Deep Sleep]] (since they disable the device's GSM module to save power) and [[{{{model|FMB1YX}}}_Sleep_modes#Online_Deep_Sleep_mode|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: '''[https://www.youtube.com/watch?v=otQd34WqL54 Teltonika Jamming Detection scenario]'''
==GNSS Jamming==
[[Image:GNSS_Jammingass.PNG|{{{general|size}}}|right]]
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.


[[Image:Fmb120 over speeding.png|300px|right]]
*2 - Jamming critical status, which means that device is not able to acquire GPS fix.


When vecicle speed exeeds configured max speed value scenario is activated, record will be generated and digital output status will be changed to 1 (if configured).<br/>Scenario is activated until current speed decreases below parameter value.
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.
<br/><br/><br/><br/><br/><br/><br/><br/><br/>
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.


==Jamming==
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.


[[Image:Fmb120_jamming.png|300px|right]]
'''Note:''' GNSS Jamming is only available since 03.28.03.Rev.03 or newer firmware version.


When jamming is detected scenario is activated, record will be generated and digital output status will be changed to 1 (if configured).<br/>Jamming timeout time can be configures. After Jamming trigger count configured timeout (in seconds), digital output control and jamming event will be generated after this timeout. If Jamming ends during timeout counting no event will be generated and output will not be controlled.<br/>You can configure eventual records parameter: when he is disabled scenario status value will be appeared in each AVL record, and when he is enabled scenario status value will be appended only to eventual records.
'''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
<br/><br/><br/><br/><br/>


== DOUT Control Via Call==
'''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 GNSS module to save power.


[[Image:Fmb120_dout_via_call.png|300px|right]]
{{#switch: {{{model}}}
|FMT100 =
|#default =
==DOUT Control Via Call==


Scenario is activated and digital output is ON, when call is received from number which is in authorized numbers list.<br/>
[[File:DOUT Control Via Call1.png|{{{general|size}}}|right]]
Call control functionality:
* When FMB120 is configured to control DOUT1/DOUT2 device waits incoming call from configured secure number. If call is received FMB120 turns on DOUT1/DOUT2 for user defined Duration timeout (s). If Duration timeout set to „0“(s), DOUT1/DOUT2 will be OFF.
* DOUT1/DOUT2 can be turned off by Duration timeout (s) or by digital input 1, digital input 2 or digital input 3 (DOUT deactivation settings).
* DOUT1/DOUT2 can be turned off before Duration timeout (s) by selected DIN (DOUT deactivation settings).
* DOUT1/DOUT2 always will be ON, if DOUT deactivation set to DIN1 for example, but DIN1 will be never turned ON or set Duration timeout to Max value (2147483647) it is about 68 years.


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}}} 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.
}}
{{#switch: {{{model}}}
|FMC880 |FMM880 |FMC800 |FMM800| FMT100 =
|#default =
==Immobilizer==
==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.
<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 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.
}}
{{{ibutton_feature|==iButton Read Notification==
[[Image:IButton_Read_Notification.gif|{{{general|size}}}||right]]
Output control parameter lets the user choose which DOUT will iButton blink. After connecting iButton, DOUT will blink for a period of time, which is configured in DOUT ON Duration parameter. The iButton List checking parameter configures whether the device reads the iButton ID from iButton list or not. For example if configured as Enabled, device will not blink DOUT unless the iButton is in the iButton list.
If 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 duration – a value in seconds, for how long {{{text_dout|DOUT1/DOUT2}}} should be active.
*iButton List checking - parameter configures that device reads the iButton ID from list or not.
*Depend on Ignition - Output will be triggered only if ignition is off
<br/><br/>}}}
{{{gnss_fuel|
==GNSS Fuel Counter==
[[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. 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 [[{{{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.
''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.
''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 =
|#default =
==DOUT Control Via Ignition==
[[File:DOUT Control Via Ignition1.png|{{{general|size}}}|right]]
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 a timeout, selected DOUT (Digital Output) will be turned On.<br/><br/>
Turning DOUT Off is possible with enough 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%;">
<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">DOUT Control</td>
        <td style="width: 8%; text-align:left">Scenario controls configured DOUT if ignition timeout exceeds its limit</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">DOUT Deactivation Via DIN</td>
        <td style="width: 8%; text-align:left">DOUT is turned off if configured DIN is in on (voltage applied) state</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Ignition Off timeout</td>
        <td style="width: 8%; text-align:left">Duration (in seconds) after which DOUT is turned on, when ignition is turned off</td>
    </tr>
</table>
}}
==Ignition ON Counter==
[[File:Ignition on.gif|right]]
'''Ignition ON Counter''' scenario counts the time spent with the ignition in the resolution of seconds. <br>
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:
[[File:Ingintion On counter.gif|left]]
<br><br>


[[Image:Fmb120_immobilizer.png|300px|right]]
{{#switch: {{{model}}}
|FMT100 =
|#default =
{{{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>


If Dout Control is disabled, scenario will only generate events without digital output activation. If Dout Control is enabled DOUT1/DOUT2 (optional) turns ON if Ignition turns ON (configured Ignition Source =1). After iButton ID is read (any iButton is attached), DOUT1/DOUT2 turns OFF. After iButton identification, Ignition (configured Ignition Source) can be turned OFF (configured Ignition Source = 0) for no longer than 30 seconds3, otherwise immobilizer must be repeated. If iButton list checking parameter is enabled, authorization will be successful only if attached iButton is specified in the iButton list.
DOUT1 in '''Normal''' state:
<br/><br/><br/><br/><br/><br/><br/><br/><br/>
[[File:DoutNormal.jpg|thumb|left|500px]]
<br><br><br><br>


==iButton Read Notification==
DOUT1 in '''Inverted''' state:
[[File:InvertedDout.png|thumb|left|500px]]
<br><br><br>


[[Image:Fmb120_iButton_read.png|300px|right]]


This functionality allows user to see when iButton is being readed. Selected DOUT1 turns on for configured duration, after DOUT ON duration ends configured DOUT don’t turns on, even if iButton is left attached.
<br/><br/><br/><br/>


==GPS Fuel Counter==
*'''<u>Notice!</u>''' Digital output type control functionality will not affect SMS/GPRS command '''setdigout''' execution. <br>


[[Image:Fmb120_gps_fuel_counter.png|300px|right]]
[[File:Alert.png|50px]] <b>Available from Firmware version: [[ {{{model|}}}_firmware_errata|03.27.07.Rev.00]] </b>
}}}
}}


Configuration of fuel consumption:
{{#switch: {{{model}}}
# To configure this parameters use fuel consumption norm which are presented in your car technical documentation. By default speeds for this fuel consumption norms are: City – 30 km/h, Average - 60km/h, Highway - 90 km/h. If you want, you can change it.
|FMT100 =
# When speed are higher than highway fuel consumption speed, we add for highway fuel consumption x % of highway fuel consumption every y km/h, by default FMB1YX add 20% every 50 km/h. It means that fuel consumption is (1.2 * Highway Fuel Consumption) on 140 km/h speed, (1.4 * Highway Fuel Consumption) on 190 km/h speed.
|#default =
# Correction coefficient is use for correction every value of fuel consumption which is send to server (Used Fuel * Correction coefficient). By default it is 1, min 0.01 and max 2. For
{{{SECO|{{Template:Secure_vehicle_disabling}}}}}
example when correction coefficient is 1 and FMB1YX calculate that used fuel of 35 m distance is 20 ml, to server will be sent value: 20 ml, if correction coefficient is 1.2 to server will be sent value: 20 * 1.2 = 24 ml.
}}
# Fuel consumption on idling used to calculate fuel consumption when ignition is on, but vehicle speed is 0 km/h. By default it is 1 l/h, min 0 and max 5 l/h. Almost in all diesel cars this parameter is less than 1.0 l/h. In gasoline cars this parameter is about 1.5 – 2.0 l/h.

Latest revision as of 10:39, 28 May 2026

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