Jump to content
  • EN

Template:FMC Features settings: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
No edit summary
Updating per 04 FW rewrite
 
(4 intermediate revisions by the same user not shown)
Line 137: Line 137:
'''Auto calibration is also supported by the {{{model|FMB1YX}}} device.'''
'''Auto calibration is also supported by the {{{model|FMB1YX}}} device.'''


==Over Speeding==
==OverSpeeding==
[[File:Overspeeding.png||right]]
The Overspeeding feature helps prevent drivers from exceeding a fixed speed limit and triggers alerts using a buzzer, LED, etc. when the configured maximum speed is surpassed. During an overspeeding event, the selected DOUT will be blinking, its status will change to 1 (if configured) and an event record will be generated. Once vehicle speed is lower than the configured Max Allowed Speed the scenario will stop. 


When vehicle speed exceeds the configured maximum speed value, the scenario is activated, and an event record is generated. Detected speed has to be greater than (configured max speed + 3% of configured max speed) for the overspeeding event to start. To stop the overspeeding event, detected speed has to be lower than (configured max speed - 3% of configured max speed). Configurable parameters:
===Configurable parameters===
[[Image:Over_Speeding.PNG|{{{general|size}}}|right]]
<br />
*Scenario settings – defines priority of over speeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.
*Max speed – it is the max allowed speed which can be reached. If speed exceeds the configured value, then an event will occur.
*Send SMS to – GSM number to which an SMS event will be sent.
*SMS text – SMS text.
<br /><br />


'''Over Speeding scenario is supported by the {{{model|FMB1YX}}} device.'''
*'''''Scenario Settings'''''  – Defines priority of over speeding scenario: 
:*'''0 – Disabled'''
:*'''1 – Low'''
:*'''2 – High'''
:*'''3 – Panic'''
*'''''Max speed'''''  – Maximum allowed speed that can be reached. If speed exceeds the configured value, an event will occur. 
*'''''Output Control''''' – Available scenario settings for module Digital output activation/deactivation. 
*'''''DOUT ON/OFF Duration''''' – How long DOUT should be active or inactive in milliseconds.  
*'''''Send SMS to''''' – GSM number to which an SMS event will be sent. 
*'''''SMS Text''''' – SMS text.


{{{jamming1|
===Conditions to Detect Overspeeding===
==Jamming==
In order for the scenario to detect Overspeeding, make records and/or control DOUT the following conditions have to be met: 
*Ignition has to be '''ON'''; 
*If Speed Source Parameter ('''ID: 133''') is configured as: 
:*'''OBD/CAN''' – detected speed value has to be higher than 0 km/h. 
:*'''GNSS''' – detected speed value has to be higher or equal than 10 km/h and data FIX should be present. 
*Event trigger and end criteria: 
:*The detected speed has to be greater than configured max speed + 3 % of configured max speed for Overspeed event to be triggered. 
:*The detected speed has to be lower than configured max speed – 3% of configured max speed for Overspeed end event to be triggered. 
When Overspeed start or end event is detected, a record ('''AVL ID: 255''') and speed value is generated.


{{#switch: {{{model}}}
|FMC880 |FMM880 =
| #default =
==GNSS Jamming==
[[File:GNSS Jamming configurator.png|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. 


[[Image:Jamming.gif|{{{general|size}}}|right]]
It is important to note, 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. 


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


Connecting a Buzzer to the Digital Output to emit sounds as soon as jamming is detected is the most straightforward use of this scenario.
From '''04.01.00.Rev.01''' Jamming Detection Delay parameter has been  introduced. This parameter controls the time needed for the device to register a change in GNSS data to switch states.  


The Digital Output can be directly connected to the vehicle's alarm system to ensure the thief cannot avoid triggering it.
For example, with timeout set to a default value of 60, if GNSS is not being jammed, the device needs to register a jamming warning or jamming detected for 60 seconds for the device to consider jamming as ongoing (during this time, device can register warning and jamming states, this will not reset the counter). If no jamming is detected during the configured Jamming Detection Delay period at least once, the counter is reset to 0 and the countdown begins again.


It can also be connected to the central lock system to ensure that all the doors are locked.
===Additional Notes===
 
*GNSS Jamming is only available from '''03.28.03.Rev.03 or newer'''  firmware version.
A relay can be used to disable the starter motor. Usually used with the Immobilizer scenario.
*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'''''.
 
*This scenario will not work with [[{{{model}}}_Sleep_modes#Deep_Sleep_mode|Deep Sleep]], [[{{{model}}}_Sleep_modes#Ultra_Deep_Sleep_mode|Ultra Deep Sleep]] and [[{{{model}}}_Sleep_modes#Online_Deep_Sleep_mode|Online Deep Sleep]] modes.''' '''since they disable the device's GNSS module to save power'''.
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]] (since they disable the device's GSM module to save power) and [[{{{model|FMB1YX}}}_Sleep_modes#Online_Deep_Sleep_mode|Online Deep Sleep]] modes.'''
 
''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]'''
}}}


'''Jamming scenario is also supported by the {{{model|FMB1YX}}} device.'''
'''Jamming scenario is also supported by the {{{model|FMB1YX}}} device.'''
Line 320: Line 336:
     </tr>
     </tr>
<tr>
<tr>
         <td style="width: 8%; text-align:left">Momevemt timeout</td>
         <td style="width: 8%; text-align:left">Movement timeout</td>
         <td style="width: 8%; text-align:left">Accelerometer's instant movement timeout after which output will be activated (GNSS OFF)</td>
         <td style="width: 8%; text-align:left">Accelerometer's instant movement timeout after which output will be activated (GNSS OFF)</td>
         <td style="width: 8%; text-align:center">12256</td>
         <td style="width: 8%; text-align:center">12256</td>

Latest revision as of 15:59, 5 June 2026

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