482
edits
Changes
Template:FMB Features settings (view source)
Revision as of 15:48, 13 April 2023
, 15:48, 13 April 2023→GNSS Jamming
==Eco/Green Driving==
==Eco/Green Driving==
[[Image:EcoGreen_Driving.gif|{{{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, 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.
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.
<table class="nd-othertables" style="width: 68%;">
<table class="nd-othertables" style="width: 68%;">
</tr>
</tr>
<tr>
<tr>
</tr>}}}
</tr>}}}
<!--<tr>
<!--<tr>
==Over Speeding==
==Over Speeding==
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. Configurable parameters:
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:
[[Image:OverSpeeding.gif|{{{general|size}}}|right]]
[[Image:OverSpeeding.gif|{{{general|size}}}|right]]
<br />
<br />
*Scenario settings – defines the priority of over speeding 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 which can be reached. If speed exceeded configured value, then 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.
*Send SMS to – the GSM number to which the SMS event will be sent.
*Send SMS to – GSM number to which SMS event will be sent.
*SMS text – SMS text.
*SMS text – SMS text.
<br />
<br />
[[Image:Jamming.gif|{{{general|size}}}|right]]
[[Image: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 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.
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]] 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.
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.
*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.
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.
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
''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''' 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==
{{{dout_control_via_call_feature|==DOUT Control Via Call==
*Output control – available scenario settings for module Digital output activation/deactivation
*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.
*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.
*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
*Depend on Ignition - Output will be triggered only if ignition is off
{{{dout_control_via_ignition_feature|==DOUT Control Via Ignition==
{{{dout_control_via_ignition_feature|==DOUT Control Via Ignition==
[[Image:DOUT_Control_Via_Ignition.gif|{{{dout_control_via_ignition|size}}}|right]]
[[Image:DOUT Control Via Ignition.jpg|{{{dout_control_via_ignition|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%;">
<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>
<tr>
<tr>
}}}
}}}
{{{SECO|{{Template:Secure_vehicle_disabling}}}}}
