Skip to main content

Jamming Detection

The Antares 4G can detect GPS and cellular jamming through the modem's built-in jamming detection capability.

warning

JO Tag Not Implemented

The JO extended tag is not yet implemented in the current firmware. Jamming detection is available through signals only, not via the JO tag.

How It Works

The modem continuously monitors the radio frequency environment. When jamming is detected:

  1. Signal F23 (SIGNAL_MDM_JAMMING_DETECTED) activates.
  2. If jamming persists, signal G04 (SIGNAL_MDM_JAMMING_PERSISTED) activates.

Signals

SignalNameDescription
F23SIGNAL_MDM_JAMMING_DETECTEDMomentary jamming detection event
G04SIGNAL_MDM_JAMMING_PERSISTEDJamming condition continues to persist

Configuring an Event for Jamming

Use the ED command to create an event that triggers when jamming is detected:

Objective: Send a report when jamming is detected.

Command:

>SED00NA0;F23+<
FieldValueDescription
EDEvent DefinitionCommand
00IndexEvent number (E00)
NHandlerN = Normal Report (send position report)
AEvent IDA type event
0DestinationDestination address 0
F23SignalJamming detected signal
+SensePositive edge (signal goes HIGH)

Query the event:

>QED00<

Response:

>RED0NA0;F23+<

When jamming is detected:

  1. Log the event with a position report.
  2. If jamming persists (G04), escalate the alert.

Limitations

  • Detection accuracy depends on the modem firmware and signal environment.
  • False positives may occur in areas with dense cellular activity.
  • The JO tag (real-time jamming indicator in report messages) is not yet available. It will be added in a future firmware release.