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.
===<u> Introduction </u>===
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.
[[File:FTX SECO.png|right|500px]]
The SECO scenario (Secure Engine Cut Off) is a static scenario module responsible for controlling a digital output (DOUT) to cut off the engine based on configurable speed and movement conditions. It is typically triggered by remote commands (SMS or GPRS) and is used for security or immobilization purposes.
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.
===<u>Prerequisites</u>===
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.
*At least one '''DOUT''' is available.
*'''SECO functionality''' should have DOUT control priority higher than '''Immobilizer''' scenario.
===<u>How It Works</u>===
The SECO scenario supports three distinct engine cut-off modes, each designed for different operational requirements.
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.
'''First Mode'''
===Additional Notes===
*GNSS Jamming is only available from '''03.28.03.Rev.03 or newer''' firmware version.
*In the first mode, DOUT control starts when the vehicle speed goes below a configured speed threshold and remains below this threshold for a specified speed check period.
*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'''.
*In this configuration, the DOUT is activated instantly when the speed condition is met.
*If the speed check period timer is running and the vehicle speed increases above the configured speed threshold before the timer expires, the timer will be reset.
'''Second Mode'''
*The second mode requires a GNSS fix to be present before DOUT control begins.
*In this mode, DOUT pulsing starts when the vehicle speed drops below a configured speed pulse threshold and the speed remains below this threshold for a specified speed check period.
*While pulsing is ongoing, when the vehicle speed drops below a configured speed threshold, the system switches from pulsing to steady DOUT control.
*If the speed check period timer is running and the vehicle speed increases above the configured speed pulse threshold before the timer expires, the timer will be reset.
'''Third Mode'''
*The third mode is used when a GNSS fix is not available, no vehicle movement is detected anymore, and the configured movement timeout has passed.
*In this mode, the system initiates DOUT control only if the vehicle is stationary, location data is unavailable, and the movement timeout condition is met, providing an additional layer of security.
*If the movement timeout has not been reached and movement is detected, the DOUT will not be activated, and the movement timeout will be reset.
<td style="vertical-align: middle; text-align: center;"> Priority of how events are being sent to a server. For example, events with low priority are added to the periodical record, and events with high priority are sent immediately after they occur. </td>
<td style="vertical-align: middle; text-align: left;"> '''0''' = SECO scenario is '''disabled''' <br> '''1''' = SECO scenario is '''low''' <br> '''2''' = SECO scenario is '''high''' <br>
<td style="vertical-align: middle; text-align: center;"> Time span during which speed must be lower than configured for output to activate (GNSS on). </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br> Maximum value = '''65535''' <br>Default value = '''10''' </td>
<td style="vertical-align: middle; text-align: center;"> Duration after which the DOUT will be activated if no movement is detected and GNSS is off. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br> Maximum value = '''65535''' <br>Default value = '''30''' </td>
<td style="vertical-align: middle; text-align: center;">Enables feature status sending only when the event happens (an eventual record). When disabled, feature status will be sent with both eventual and periodical records.</td>
<td style="vertical-align: middle; text-align: left;"> '''0''' = SECO status will be sent with both eventual and periodical records. <br> '''1''' = SECO status will be sent only when the event happens (an eventual record).</td>
<td style="vertical-align: middle; text-align: center;">Pulse functionality adds additional output control which helps to slow down vehicle before fully disabling fuel pump.</td>
<td style="vertical-align: middle; text-align: center;"> A value in milliseconds, for how long DOUT should be inactive. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''10'''<br> Maximum value = '''5000''' <br>Default value = '''1000''' </td>
</tr>
</table>
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}}{{FTX Pin Support List|model={{{model}}}|pin=DOUT2}}{{FTX Pin Support List|model={{{model}}}|pin=DOUT3}}
The Fuel Counter GNSS scenario provides fuel consumption estimation using GNSS-derived distance and user-configured fuel rate. It calculates the amount of fuel used by multiplying traveled distance by the average fuel rate and converting it to appropriate units. It is a software-based alternative when fuel flow sensors are not available.
<td style="vertical-align: middle; text-align: center;">Priority of how events are being sent to a server. For example, events with low priority are added to the periodical record, and events with high priority are sent immediately after they occur.</td>
<td style="vertical-align: middle; text-align: center;">The initial fuel counter value in litres. Can be used to set the starting value or reset the current one.</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0.0'''<br> Maximum value = '''4294967.2''' <br> Default value = '''0.0''' </td>
*TLS/DTLS are security protocols that protect information sent over a network by encrypting the data so only the intended recipient can read it. The protocols also help confirm that the devices communicating with each other are legitimate and ensure that the information is not changed while it is being transmitted. TLS/DTLS encryption creates a secure, private connection so sensitive data can travel safely across networks.
Latest revision as of 15:29, 5 June 2026
GNSS Jamming
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.
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.
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.
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.
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.
Additional Notes
GNSS Jamming is only available from 03.28.03.Rev.03 or newer firmware version.
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.
