Hello,
I’d like to ask if anybody has experience with the jamming protection option in ublox M10 hardware?
I stumbled upon it while browsing the configuraiton in u-center and was surprised it was not enabled by default.
Cheers.
Protocol used in M10 without details.
Detailed description in M8 manual.
https://www.digikey.com/htmldatasheets/production/3448065/0/0/1/spx-15106.pdf
15.3 Jamming/Interference Monitor (ITFM)
The field jammingState of the UBX-MON-HW message can be used as an indicator for both
broadband and continuous wave (CW) jammers/interference. It is independent of the (CW only)
jamming indicator described in Jamming/Interference Indicator above.
I assume it’s not evaluated by AP but the struct is there!
Another thing that did catch my eye, there is a spoofing indication!
16 Spoofing Detection
(Note: this feature is not supported in protocol versions less than 18).
16.1 Introduction
Spoofing is the process whereby someone tries to forge a GNSS signal with the intention of
fooling the receiver into calculating a different user position than the true one.
The spoofing detection feature monitors the GNSS signals for suspicious patterns indicating that
the receiver is being spoofed. A flag in UBX-NAV-STATUS alerts the user to potential spoofing.
32.17.24 UBX-NAV-STATUS (0x01 0x03)
32.17.24.1 Receiver navigation status
…
Bitfield flags2
…
spoofDetState
Spoofing detection state (not supported in protocol versions less than 18)
0: Unknown or deactivated
1: No spoofing indicated
2: Spoofing indicated
3: Multiple spoofing indications
Note that the spoofing state value only reflects the detector state for the current navigation epoch.
As spoofing can be detected most easily at the transition from real signal to spoofing signal, this is
also where the detector is triggered the most. I.e. a value of 1 - No spoofing indicated does not mean
that the receiver is not spoofed, it simply states that the detector was not triggered in this epoch.
That field is currently not used!
1 Like