Jump to content
  • EN

Template:FMB Features settings: Difference between revisions

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


[[Image:EcoGreen_Drivings.PNG|{{{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 the digital output status is changed to 1 when configured. 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.
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>
{{{txt_advanced|<tr>
    <tr>
         <td style="width: 8%; text-align:left">[[{{{model|FMB1YX}}} Features settings#Advanced Eco Driving|Advanced Eco Driving]]</td>
         <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>
         <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>
<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|FMB1YX}}}]] 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>
<tr>
<tr>
     
    </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 52: 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>


{{{FMT100_eco|==Advanced Eco Driving==
===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'''.


From 03.25.14.Rev.03 base firmware version new '''[[FMB120_Parameter_list|parameter]]''' has been added (Eco Driving Maximum and Eco Driving Average) to '''[[FMT100]]''' device. This parameter is '''enabled''' by default.  
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.


When this parameter is enabled device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to server. When enabled, device does not send Green Driving value IO element '''[[FMT100_Teltonika_Data_Sending_Parameters_ID|254]]'''.
<table class="nd-othertables" style="width: 68%;">
<table class="nd-othertables" style="width: 68%;">
  <tr>
  <tr>
Line 73: Line 93:
         <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>
         <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>
     </tr>
</table>}}}
</table>


===Data output===
===Data output===
Line 93: Line 113:


==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.  
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:
Configurable parameters:
[[Image:OverSpeeding.gif|{{{general|size}}}|right]]
<br />
<br />
*Scenario settings – defines the priority of overspeeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.
*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.  
*Max speed – it is the maximum allowed speed that can be reached. If the speed exceeded configured value, then the event will occur.  
*Output control – available scenario settings for module Digital output activation/deactivation
*DOUT ON/OFF duration – a value in seconds, for how long {{{text_dout|DOUT1/DOUT2}}} should be active or inactive.
*Send SMS to – the GSM number to which the SMS event will be sent.
*Send SMS to – the GSM number to which the SMS event will be sent.
*SMS text – SMS text.
*SMS text – SMS text.
<br />
<br />
{{{jamming1|
==Jamming==
[[Image:Jamming.gif|{{{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 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.
==Network Jamming==


Connecting a Buzzer to the Digital Output to emit sounds as soon as jamming is detected is the most straightforward use of this scenario.
[[File:Network Jamming.png|{{{general|size}}}|right]]


The Digital Output can be directly connected to the vehicle's alarm system to ensure the thief can not avoid triggering it.
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


It can also be connected to the central lock system to ensure that all the doors are locked.
'''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.'''
 
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.  
''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]'''
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==




==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.  
GNSS Jamming is the transmission of radio signals that disrupts communications between tracker and satellites by decreasing the signal to noise ratio.  
Line 137: Line 144:
GNSS Jamming record is stored in AVL ID 318 parameter and has 3 possible values:
GNSS Jamming record is stored in AVL ID 318 parameter and has 3 possible values:


0 - No Jamming,
*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.
*1 - Jamming warning status, which means that signal and accuracy is disrupted but device is able to hold GPS fix for at least 5 seconds.


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


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


'''Note:''' GNSS Jamming is not available on 3.80, 3.82 GNSS modules. Available on 5.10, 5.1.5, 5.1.8 or newer modules. GNSS module version can be checked by SMS\GPRS command - getver
Eventual Records parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise, it will be appended only to eventual records.
 
'''Note:''' GNSS Jamming is only available since 03.28.03.Rev.03 or newer firmware version.
 
'''Note:''' GNSS Jamming is not available on 3.80, 3.82 but available on 5.10, 5.1.5, 5.1.8 or newer GNSS module firmware versions. GNSS module version can be checked by SMS\GPRS command - getver


'''Note that this scenario will not work with [[{{{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.'''
'''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.


{{{dout_control_via_call_feature|==DOUT Control Via Call==
{{#switch: {{{model}}}
|FMT100 =
|#default =
==DOUT Control Via Call==


[[Image:DOUT_Control_Via_Call.gif|{{{general|size}}}|right]]
[[File:DOUT Control Via Call1.png|{{{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/>
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/>
Line 158: Line 172:
* 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.
* 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 the 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.
 
}}
{{#switch: {{{model}}}
| FMT100 =
| #default =
{{{immobilizer_feature|==Immobilizer==
{{{immobilizer_feature|==Immobilizer==


[[Image:Immobilizer.gif|{{{general|size}}}|right]]
[[File:Immobilizer1.png|{{{general|size}}}|right]]


If ''DOUT Control'' is disabled, the 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 (or RFID card) 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, the immobilizer must be repeated. If the ''iButton List Check'' parameter is enabled, the authorization will be successful only if the attached iButton is specified in the iButton list.<br/>
If ''DOUT Control'' is disabled, the 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 (or RFID card) 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, the immobilizer must be repeated. If the ''iButton List Check'' parameter is enabled, the authorization will be successful only if the attached iButton is specified in the iButton list.
<br/><br/>
<br/><br/>
The ignition off timeout parameter is used to set the duration after which authorization is activated when the ignition is turned off. For example, if the 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.
The ignition off timeout parameter is used to set the duration after which authorization is activated when the ignition is turned off. For example, if the 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/>
The No Authentication Timeout sets a time limit for how long the vehicle can stay in the "Wait Authorization" state without receiving any authorization. If this timeout is set (non-zero) and the time spent in the "Wait Authorization" state exceeds the configured value, the system automatically moves to the "Authorized" state. This prevents the vehicle from waiting indefinitely and ensures it can proceed with operations after a set time.


 
If value is entered zero - function "No Authentication timeout" is not activated.
<br/><br/>
From the firmware version '''[https://wiki.teltonika-gps.com/view/{{{model|FMB1YX}}}_firmware_errata 03.25.14]''' iBeacon authentication was introduced. iBeacon authentication works in the same way as iButton authentication. To use authorized iBeacons, the iBeacon list should be filled in the device configurator. Instructions how to list iBeacons in FMB devices can be found '''[https://wiki.teltonika-gps.com/view/{{{model|FMB1YX}}}_Beacon_List here]'''.
From the firmware version '''[https://wiki.teltonika-gps.com/view/{{{model|FMB1YX}}}_firmware_errata 03.25.14]''' iBeacon authentication was introduced. iBeacon authentication works in the same way as iButton authentication. To use authorized iBeacons, the iBeacon list should be filled in the device configurator. Instructions how to list iBeacons in FMB devices can be found '''[https://wiki.teltonika-gps.com/view/{{{model|FMB1YX}}}_Beacon_List here]'''.


By using iBeacon authorization, the immobilizer feature can be used with devices that don't have a 1-wire data connection available.
By using iBeacon authorization, the immobilizer feature can be used with devices that don't have a 1-wire data connection available.
<br/><br/><youtube>gjuiJjAejWU</youtube>}}}
<br/><youtube>gjuiJjAejWU</youtube>
 
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.
}}}
}}


{{{ibutton_feature|==iButton Read Notification==
{{{ibutton_feature|==iButton Read Notification==
Line 198: Line 222:
[[Image:GNSS_Fuel_Counter.gif|{{{general|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. 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.
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.
Line 206: Line 234:
''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.
''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==
{{#switch: {{{model}}}
|FMT100 =
|#default =
==DOUT Control Via Ignition==


[[Image:DOUT_Control_Via_Ignition.gif|{{{dout_control_via_ignition|size}}}|right]]
[[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/>
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). Voltage requirements: DIN1 – 7.5V, DIN2-4 – 2.5V.<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%;">
<table class="nd-othertables" style="width: 68%;">
Line 218: Line 249:
         <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 235: Line 262:
         <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==
==Ignition ON Counter==
Line 245: Line 273:
Example of Ignition On Counter '''I/O''' element:
Example of Ignition On Counter '''I/O''' element:
[[File:Ingintion On counter.gif|left]]
[[File:Ingintion On counter.gif|left]]
<br></br>
<br><br>
 
{{#switch: {{{model}}}
|FMT100 =
|#default =
{{{dout_type|
{{{dout_type|
==DOUT 1 Output 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>
[[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>


DOUT1 in '''Normal''' state:
DOUT1 in '''Normal''' state:
[[File:DoutNormal.jpg|thumb|left|500px]]
[[File:DoutNormal.jpg|thumb|left|500px]]
<br></br><br></br><br></br><br></br></br>
<br><br><br><br>


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






 
*'''<u>Notice!</u>''' Digital output type control functionality will not affect SMS/GPRS command '''setdigout''' execution. <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|03.27.07.Rev.00]] </b>
[[File:Alert.png|50px]] <b>Available from Firmware version: [[ {{{model|}}}_firmware_errata|03.27.07.Rev.00]] </b>
}}}
}}


 
{{#switch: {{{model}}}
}}}
|FMT100 =
|#default =
{{{SECO|{{Template:Secure_vehicle_disabling}}}}}
{{{SECO|{{Template:Secure_vehicle_disabling}}}}}
}}

Latest revision as of 10:54, 27 May 2026

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