Jump to content
  • EN

Template:FMU Features settings: Difference between revisions

Template:FMU Features settings (view source)

Revision as of 15:10, 19 January 2021

3,285 bytes added ,  19 January 2021
no edit summary
VisualWikitext
No edit summary
No edit summary
Line 59: Line 59:
     </tr> -->
     </tr> -->
</table>
</table>


{{{FMT100_eco|}}}
{{{FMT100_eco|}}}
{{{FMT100_eco|==Advanced Eco Driving==
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.
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 '''[[FMB120_AVL_ID|254]]'''.
<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>
}}}
<br>
===Data output===
===Data output===
----
----
Data from accelerometer/GPS are continuously monitored and processed and are used to decide whether a harsh event has occurred. If either of three cases is satisfied, an event is generated and a record is saved and sent to the server ([[{{{model|FMU1YX}}}]] must be properly configured in order to send the record). Event value is multiplied by 100 before sending/saving record to get more precision when displaying data.{{{text_dout|<br/>{{{dout|info}}}}}}
Data from accelerometer/GPS are continuously monitored and processed and are used to decide whether a harsh event has occurred. If either of three cases is satisfied, an event is generated and a record is saved and sent to the server ([[{{{model|FMU1YX}}}]] must be properly configured in order to send the record). Event value is multiplied by 100 before sending/saving record to get more precision when displaying data.{{{text_dout|<br/>}}}<br/><youtube>RlkJELdVGRs</youtube>


===Auto calibration===
===Auto calibration===
Line 78: Line 101:
==Over Speeding==
==Over Speeding==


[[Image:FMB120_Over_Speeding.png|300px|size|right]]
When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}}.<br />Scenario is active until detected speed decreases below the set parameter value.
[[Image:Over_Speeding.gif|{{{general|size}}}|left]] <br /><br /><br /><br />
<br /><br />
<br /><br />
<br /><br />
<br /><br />
<br /><br />
 
==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.
 
Connecting a Buzzer to the Digital Output to emit sounds as soon as jamming is detected is the most straightforward use of this scenario.
 
The Digital Output can be directly connected to the vehicle's alarm system to ensure the thief can not avoid triggering it.


When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}}.<br/>Scenario is active until detected speed decreases below the set parameter value.<br/>{{{over_speeding_dout|info}}}
It can also be connected to the central lock system to ensure that all the doors are locked.
<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>


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


[[Image:FMB120_Jamming.png|frameless|378px|size|right]]
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]'''


When GSM signal jamming is detected the scenario is activated, an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}} once ''Jamming'' timeout runs out. If jamming ends during timeout countdown no event will be generated{{{text_dout| and output will not be controlled}}}.<br/>''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.<br/>{{{jamming_dout|info}}}
<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>


{{{template_link|}}}


{{{dout_control_via_call_feature|== DOUT Control Via Call==
{{{dout_control_via_call_feature|== DOUT Control Via Call==


[[Image:FMB120_DOUT_Control_Via_Call.png|295px|size|right]]
[[Image:DOUT_Control_Via_Call.gif|{{{general|size}}}|right]]


Scenario is activated and digital output is ON when call is received from a number which is on the authorized numbers list.<br/>
The scenario is activated and digital output is ON when a call is received from a number which is on the authorized numbers list.<br/>
Call control functionality is following:
Call control functionality is the following:
* When [[{{{model|FMU1YX}}}]] 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|FMU1YX}}}]] 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 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 maximum value (2147483647) which is about 68 years.
{{{dout_control_dout|info}}}}}}
}}}
 
<br/>


{{{immobilizer_feature|==Immobilizer==
{{{immobilizer_feature|==Immobilizer==


[[Image:FMB120_Immobilizer.png|300px|size|right]]
[[Image:Immobilizer.gif|{{{general|size}}}|right]]


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


{{{ibutton_feature|==iButton Read Notification==
{{{ibutton_feature|==iButton Read Notification==
KarolisKru
0

edits

Retrieved from "https://wiki.teltonika-gps.com/view/Special:MobileDiff/62022"