Jump to content
  • EN

Template:FMB Features settings: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Eco/Green Driving==
==Eco/Green Driving==
[[File:Eco-Green Driving.png|{{{general|size}}}|right]]
[[File:EcoGreen Driving configurator.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.
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'''.
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 29: 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 51: 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.


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


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 72: 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 139: Line 160:


'''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.
{{#switch: {{{model}}}
|FMT100 =
|#default =
==DOUT Control Via Call==
==DOUT Control Via Call==


Line 148: Line 173:
* {{{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==


Line 164: Line 192:


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/><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.
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 192: 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 200: 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.
}}}
}}}
 
{{#switch: {{{model}}}
|FMT100 =
|#default =
==DOUT Control Via Ignition==
==DOUT Control Via Ignition==


Line 227: Line 263:
     </tr>
     </tr>
</table>
</table>
}}


==Ignition ON Counter==
==Ignition ON Counter==
Line 236: 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"