- Joined
- Jul 30, 2026
- Messages
- 121
- Thread Author
- #1
Short answer: An SDR can capture civil GPS L1 at 1575.42 MHz, but the spread-spectrum signals are below the raw noise floor and require a suitable active GNSS antenna, bias supply, stable clock, enough clean bandwidth and a GNSS software receiver. A visible narrow peak is not GPS.
Before you start
- Keep GNSS and drone work passive unless the experiment has explicit authorization and an RF-controlled environment; do not jam, spoof or interfere with navigation or aircraft.
- Record receiver clock, antenna, gain, sample rate, observation location precision and ground truth before interpreting anomalies.
Step-by-step method
- Step 1: Use an L1 GNSS antenna with clear sky view and verify its LNA voltage/current. Provide bias through a compatible bias tee while protecting DC-sensitive equipment.
- Step 2: Choose an SDR and sample rate supported by the GNSS software, commonly several MSPS with sufficient clock stability. Record I/Q without clipping from strong nearby signals.
- Step 3: Enter exact sample rate, center frequency and sample format into the GNSS receiver. Begin with acquisition, then inspect correlation peaks and carrier-to-noise values.
- Step 4: Validate decoded time and position against a trusted receiver while keeping precise private location out of public logs.
Concrete example
GPS L1 C/A signals normally do not appear as obvious carriers on a conventional waterfall because processing gain comes from correlation with satellite codes. The diagnostic is acquisition and stable tracking, not a bright line at 1575.42 MHz.How to judge the result
Reception is successful when several satellites acquire, tracking remains stable and navigation/time results agree with an independent trusted reference within expected uncertainty.What to record
- Separate frequency-reference accuracy from absolute time alignment: 10 MHz disciplines frequency while PPS marks a time boundary.
- Use multiple independent observables for GNSS interference or spoofing claims, such as spectrum, AGC behavior, correlation, navigation consistency and trusted reference data.
- For direction finding or RF classification, report uncertainty and test across channels, distances, devices and temperatures.
Common mistakes
- Changing several hardware, software or RF variables at once, which removes the controlled comparison needed to identify the cause.
- Treating one autoscaled screenshot or one unusually good result as proof without recording the settings and repeating the test.
- Using a generic wideband whip indoors often provides too little sky view and no active-antenna gain, even though the SDR tunes to L1.