Jamming detection operates as follows:

1. Signal strength is measured on each channel and compared against a defined noise threshold

2. If the signal strength is greater than or equal to the threshold, the channel is marked as disturbed

3. The total number of disturbed channels is then compared to a preset limit. If this limit is exceeded, jamming is detected

4. Once jamming is detected, the buzzer or ignition blocking are activated, depending on the configuration

Considerations:

· Jamming cannot always be successfully detected and false alarms may occur, as in certain environmental conditions the module may detect high noise levels on some channels due to interference from external devices, radios, reflected signals, etc

· Jamming detection is active all the time in the device even without configuring it. The purpose of the configuration is to set up a method to inform the server (along with packed data) or the driver of the jamming is present

· To use the jamming detection functionality with LTE Cat M1 models, the modem firmware version must be BG96MAR02A07M1G_01.018.01.018 or newer. The modem firmware version can be checked using the modrev SMS command

To enable this functionality and log interference events, the IO “GSM/UMTS jamming” (ID_88) must be activated:

1. Check for cellular signal losses (ID_27: GSM/UMTS signal level)

2. Monitor operator changes (ID_150: GSM/UMTS operator) where GPRS status (ID_418) does not immediately report status 1

3. Retrieve the current configuration file from the device. Slightly increasing the IO Debounce value may help reduce false positives:

4. Attempt to capture a physical log using the Terminal app where the issue can be replicated

Jamming detection, IO settings, GSM/UMTS jamming, ID_88, debounce.