Jump to content
  • EN

Template:FMC Features settings: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
Replaced immobilizer image. Added text about immobilizer changes. [GTPGTM-11057]
No edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Eco/Green Driving==
==Eco/Green Driving==
[[File:EcoGreen Driving configurator.png|{{{general|size}}}|right]]


[[Image:eco_green_driving_calculator.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.


<table class="nd-othertables" style="width: 65%;">
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%;">
  <tr>
  <tr>
         <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>
Line 16: Line 24:
<tr>
<tr>
         <td style="width: 8%; text-align:left">Max Acceleration</td>
         <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 a harsh acceleration event.</td>
         <td style="width: 8%; text-align:left">Value which can be reached while accelerating without triggering harsh acceleration event.</td>
     </tr>
     </tr>
<tr>
<tr>
         <td style="width: 8%; text-align:left">Max Braking Acceleration</td>
         <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 a harsh braking event.</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">Calculate</td>
        <td style="width: 8%; text-align:left">Setting which can be used to create customised calculations for Max Acceleration, Max Braking and Max Cornering based on the user's vehicle. PLEASE NOTE: calculations will show as 0.5 until vehicle weight and power number are inserted.</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Select Drive Type</td>
        <td style="width: 8%; text-align:left">Based on vehicle's drive type, e.g. front-wheel drive, rear-wheel drive, all-wheel drive</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Select Transmission Type</td>
        <td style="width: 8%; text-align:left">Based on vehicle's transmission type, e.g. manual, automatic, dual clutch (DCT)</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Select Driving Mode</td>
        <td style="width: 8%; text-align:left">This is used to set low, medium and high settings for early acceleration. Sensitive – for most restrictive settings, for example carrying cargo. Normal – medium restrictive settings, used for normal day-to-day operations. Insentitive Clutch – least restrictive settings for drivers</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Enter Vehicle Weight (kg)</td>
        <td style="width: 8%; text-align:left">Actual weight of the car or the one registered in the logbook (required)</td>
     </tr>
     </tr>
<tr>
<tr>
         <td style="width: 8%; text-align:left">Enter Vehicle Power (kw)</td>
         <td style="width: 8%; text-align:left">Max Cornering Acceleration</td>
         <td style="width: 8%; text-align:left">Actual engine power of the vehicle, same as registered in the logbook (required)</td>
         <td style="width: 8%; text-align:left">Value which can be reached while cornering without triggering harsh cornering event.</td>
     </tr>
     </tr>
<tr>
<tr>
Line 50: 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, the device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to the server. More details about this option are described 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, an additional record with Eco/Green Driving event duration (ms) will be saved and sent to the 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 accessory (buzzer, LED 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 milliseconds (ms), for how long DOUT should be active.</td>
     </tr>
     </tr>
<tr>
        <td style="width: 8%; text-align:left">DOUT OFF Duration</td>
        <td style="width: 8%; text-align:left">A value in milliseconds (ms), for how long DOUT should be inactive.</td>
    </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>
Line 79: Line 64:
         <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>
 
===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>
</table>


Line 165: Line 178:
'''Jamming scenario is also supported by the {{{model|FMB1YX}}} device.'''
'''Jamming scenario is also supported by the {{{model|FMB1YX}}} device.'''


{{#switch: {{{model}}}
|FMM920 |FMC880 |FMM880 |FMC800 |FMM800 =
|#default =
{{{dout_control_via_call_feature|==DOUT Control Via Call==
{{{dout_control_via_call_feature|==DOUT Control Via Call==


Line 176: Line 192:


'''DOUT Control Via Call scenario is also supported by the {{{model|FMB1YX}}} device.'''
'''DOUT Control Via Call scenario is also supported by the {{{model|FMB1YX}}} device.'''
 
}}
{{#switch: {{{model}}}
|FMC880 |FMM880 |FMC800 |FMM800 =
|#default =
{{{immobilizer_feature|==Immobilizer==
{{{immobilizer_feature|==Immobilizer==


Line 187: Line 206:


By using iBeacon authorization, the immobilizer feature can be used with devices that do not have a 1-wire data connection available.
By using iBeacon authorization, the immobilizer feature can be used with devices that do not have a 1-wire data connection available.
<br/><br/><youtube>gjuiJjAejWU</youtube>}}}
<br/><br/><youtube>gjuiJjAejWU</youtube>


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.
Line 195: Line 214:
'''Immobilizer scenario is also supported by the {{{model|FMB1YX}}} device.'''
'''Immobilizer scenario is also supported by the {{{model|FMB1YX}}} device.'''


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 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.
 
}}}
}}
{{#switch: {{{model}}}
|FMC880 |FMM880 |FMC800 |FMM800 =
|#default =
{{{seco_feature|==SECO==
{{{seco_feature|==SECO==
[[Image:SECO.png|right]]
[[Image:SECO.png|right]]
Line 289: Line 312:


'''SECO functionality is also supported by the {{{model|FMB1YX}}} device.'''
'''SECO functionality is also supported by the {{{model|FMB1YX}}} device.'''
}}


{{#switch: {{{model}}}
|FMC880 |FMM880 |FMC800 |FMM800 =
|#default =
{{{ibutton_feature|==iButton Read Notification==
{{{ibutton_feature|==iButton Read Notification==
[[Image:IButton_Read_Notification.gif|{{{general|size}}}||right]]
[[Image:IButton_Read_Notification.gif|{{{general|size}}}||right]]
Line 324: Line 351:
''Fuel Consumption on Idling'' is used to calculate fuel consumption when the ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with minimum and maximum of 0 and 5 l/h, respectively. This parameter is usually less than 1.0 l/h for most diesel cars and around 1.5 – 2.0 l/h for gasoline cars.
''Fuel Consumption on Idling'' is used to calculate fuel consumption when the ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with minimum and maximum of 0 and 5 l/h, respectively. This parameter is usually less than 1.0 l/h for most diesel cars and around 1.5 – 2.0 l/h for gasoline cars.
}}}
}}}
 
}}
'''GNSS Fuel Counter functionality is also supported by the {{{model|FMB1YX}}} device.'''
'''GNSS Fuel Counter functionality is also supported by the {{{model|FMB1YX}}} device.'''


{{#switch: {{{model}}}
|FMC880 |FMM880 |FMC800 |FMM800 =
{{{dout_control_via_ignition_feature|==DOUT Control Via Ignition==
{{{dout_control_via_ignition_feature|==DOUT Control Via Ignition==


Line 359: Line 388:


'''DOUT Control Via Ignition scenario is also supported by the {{{model|FMB1YX}}} device.'''
'''DOUT Control Via Ignition scenario is also supported by the {{{model|FMB1YX}}} device.'''
 
}}
==Ignition ON Counter==
==Ignition ON Counter==
[[File:Ignition on.gif|right]]
[[File:Ignition on.gif|right]]

Latest revision as of 10:56, 27 May 2026

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