GNSS Signals Explained: Why Your Receiver Ignores Most of the Sky

Before your receiver's math engine can calculate a centimeter-level RTK fix, it must survive the physical layer: if antenna bandpass, RF front-end, and correction stream do not align, those 100+ satellites in the sky simply do not exist to your system.

GNSS Frequencies at a Glance

GNSS frequencies are the L-band radio slots that carry satellite navigation signals. GPS L1 is centered at 1575.42 MHz, GPS L2 at 1227.60 MHz, and GPS L5 at 1176.45 MHz; Galileo, BeiDou, QZSS, NavIC, and GLONASS either share, align with, or sit beside these bands depending on the signal family.

At any moment, well over 100 navigation satellites are orbiting above your head across GPS, GLONASS, Galileo, BeiDou, and regional systems such as QZSS and NavIC. But quantity is only half the story. These satellites do not all speak the same RF language. Some use modern CDMA, one still carries legacy FDMA behavior, some broadcast on the traditional L1 band, others on the modernized L5 band, and a few carry free precise correction services baked directly into their signal structure.

The rest of this guide separates the problem into three layers: which bands the receiver can physically track, which constellations broadcast usable open signals on those bands, and which correction messages let those signals participate in an RTK solution.

130+ Satellites: How Many Can You Actually Use?

At any given moment, a single constellation makes roughly 8–12 satellites visible above the horizon. Combine all four global systems and that number jumps to 30–40 simultaneously in view.

However, the satellites that actually participate in your position solution depend on three hardware constraints: which constellations your receiver firmware supports, which frequency bands the RF front-end can track, and how many digital processing channels the baseband chip allocates. More usable satellites means better geometry, which directly lowers DOP (Dilution of Precision). Lower DOP translates to faster, more reliable RTK initialization, particularly in environments where half the sky is obstructed.

L1, L2, and L5 Frequency Bands

All GNSS signals are broadcast in the L-band (1–2 GHz), with three primary slots allocated for civilian navigation:

L5 falls within the Aeronautical Radio Navigation Service (ARNS) band, protected by strict international radio regulations. This gives L5 significantly stronger resilience against jamming and out-of-band interference compared to L1.

Why Dual-Frequency GNSS Helps RTK Receivers

L1+L5 has rapidly overtaken L1+L2 as the mass-market dual-frequency configuration due to four converging factors:

1. Atmospheric error separation. The wide frequency gap (~400 MHz) between L1 and L5 produces highly effective ionosphere-free linear combinations, improving atmospheric error cancellation. For the error mechanism behind that benefit, see GNSS Errors Mapped.

2. Sharper code tracking. L5's 10.23 MHz code bandwidth is about 10× wider than legacy L1 C/A, sharpening the receiver correlation peak and improving performance in reflected-signal environments.

3. Lower integration burden. Consumer-market scale, especially from smartphones, automotive platforms, and IoT devices, has pushed L1+L5 chipset BOM toward mass-market levels. The L1/E1/B1C and L5/E5a/B2a clusters also simplify the RF front-end compared with designs that must bridge older L2 workflows, which can shorten antenna matching, filter selection, and production-debug cycles for resource-constrained teams.

4. Better fit for moving machines. The same frequency choice matters for RTK GPS for Robotics when antennas, sky view, and multipath change across outdoor routes. It also explains why Kalmix's AG3335 platform choice leans into L1/L5 rather than treating frequency support as a generic spec line; for model-level boundaries, see the AG3335 variants guide.

5. Protected-band resilience. The L5 signal sits inside a protected aeronautical radionavigation band, giving modern L1/L5 designs stronger interference resilience than legacy L2-centered architectures in many mass-market receiver applications.

L1+L2 is not obsolete; it remains the established workhorse for professional surveying and existing CORS infrastructure. Your choice between L1+L5 and L1+L2 dictates your hardware budget, antenna design, and target market.

GPS, Galileo, BeiDou, and GLONASS Frequencies

GPS (United States): The Original

As the world's first and most universally recognized navigation satellite system, GPS defined the modern positioning era. Developed by the U.S. Department of Defense, the first experimental Navstar satellite launched in 1978. The system reached Initial Operational Capability (IOC) in 1993 and Full Operational Capability (FOC) in 1995. A watershed moment for civilian applications occurred in 2000 when "Selective Availability" (intentional signal degradation) was disabled, opening practical civilian accuracy for everyday receivers. GPS normally maintains roughly 30 operational satellites across 6 orbital planes at an altitude of about 20,200 km.

GLONASS (Russia): The FDMA Exception

GLONASS typically operates with about two dozen satellites. It is the only major constellation still using FDMA (Frequency Division Multiple Access) on its legacy signals. Each satellite transmits on a unique carrier frequency, which increases RF design complexity and introduces inter-frequency hardware biases that differ between receiver manufacturers.

This is exactly why RTCM MT1230 is strictly required for GLONASS RTK: without the code-phase bias corrections it carries, your rover will track GLONASS satellites but silently exclude them from the ambiguity resolution process. The next-generation GLONASS-K2 satellites are transitioning to CDMA (L3OC at 1202.025 MHz), but the FDMA legacy fleet will coexist for years.

Galileo (EU): Civilian-First Architecture

Galileo is the only global constellation designed civilian-first; its signal architecture is optimized for open service from the ground up.

Galileo offers a suite of open and commercial signals across multiple frequency bands, including E1, E5a, E5b, and E6:

Galileo offers two operational capabilities that matter to receiver designers. HAS (High Accuracy Service) on E6 delivers free satellite-broadcast corrections for approximately 20 cm horizontal accuracy under supported service conditions, with no internet connection or NTRIP infrastructure required. OSNMA (Open Service Navigation Message Authentication) on E1 provides cryptographic signal authentication, enabling receivers to detect and reject spoofed signals at the hardware level.

BeiDou (China): Three-Layer Global Expansion

BeiDou uses a three-layer orbital architecture (GEO + IGSO + MEO), which gives the system especially strong satellite visibility in the Asia-Pacific region.

The Interoperability Shift: BDS-2's legacy B1I signal sat on an isolated frequency (1561.098 MHz), requiring dedicated RF hardware. BDS-3 moved to B1C (1575.42 MHz) and B2a (1176.45 MHz), aligning with GPS L1/L5 and Galileo E1/E5a. This frequency alignment allows a single L1+L5 RF front-end to natively track GPS, Galileo, and BeiDou-3 without additional analog hardware.

Regional Augmentation: QZSS, NavIC, and SBAS

Beyond the four global constellations, regional augmentation systems provide localized coverage, integrity, and accuracy enhancements:

• QZSS (Japan): Quasi-zenith orbit providing high-elevation satellite coverage over Japan and Oceania. Broadcasts L6 CLAS (Centimeter Level Augmentation Service) for satellite-delivered centimeter-level corrections, similar in role to Galileo HAS but regionally focused.
• NavIC / IRNSS (India): Dual-frequency (L5 + S-band at 2492.028 MHz) covering the Indian subcontinent. NavIC is the only navigation system broadcasting in the S-band, though receiver support outside India remains limited.
• SBAS (WAAS / EGNOS / GAGAN / MSAS): Geostationary overlay systems broadcasting integrity and wide-area corrections, primarily certified for aviation. Improves single-frequency standalone accuracy from ~2.5 m to ~0.8 m.

The Frequency Panorama: All Signals on One Map

The spectrum diagram below maps every major open-service signal across the L-band. The overlap between the L1/E1/B1C cluster at 1575 MHz and the L5/E5a/B2a cluster at 1176 MHz explains why modern dual-frequency receivers can share one RF front-end across constellations, and why your correction mountpoint must match your receiver's actual RF hardware capabilities.

* = Carries free satellite-based precise correction services, often discussed as Precise Point Positioning (PPP). Note: Regional systems NavIC and QZSS are omitted from the graphic for clarity.

The Developer's Debugging Checklist

When constellation or frequency misconfiguration is the root cause, the symptoms are often subtle. Common GNSS tracking failures and missing satellite issues can be diagnosed using the following troubleshooting steps based on GSV/GSA and NMEA output:

Conclusion

Your receiver's performance is fundamentally bounded by its frequency and constellation configuration. Understanding what each satellite broadcasts, and what your RF hardware can actually track, is the first step toward aligning your design with your application's accuracy and power budget.

Receiving a signal, however, is only step one. The next volume in the Kalmix GNSS Handbook walks through the mathematical pipeline that transforms these invisible RF broadcasts into your first three-dimensional position fix.

Frequently Asked Questions

Zero Jiang

Founder, Kalmix

Dedicated to making high-precision GNSS positioning accessible and reliable for global developers. Passionate about autonomous systems, RTK technology, and robust hardware engineering.