GNSS Signals Explained: Why Your Receiver Ignores Most of the Sky
TL;DR
- GNSS receivers do not use every satellite in the sky; they use the satellites their constellation settings, RF front-end, antenna, and correction stream can actually support.
- L1, L2, and L5 define more than frequency labels — they affect antenna design, multipath behavior, interference resilience, RTK compatibility, and power budget.
- L1+L5 is becoming the mass-market dual-frequency path, while L1+L2 remains deeply embedded in surveying and legacy CORS infrastructure.
- Most “missing satellite” problems are debugging problems across firmware configuration, RTCM messages, antenna bandpass, or power delivery.
GNSS signal selection is the first hardware-level filter behind every position fix: a receiver can only use satellites whose constellation, frequency, antenna path, and correction data all match the system design.
Right now, more than 130 navigation satellites are orbiting above your head — GPS (31), GLONASS (24), Galileo (30), and BeiDou (46), plus regional systems like QZSS and NavIC. But quantity is only half the story. These satellites don't speak the same language. Some use modern CDMA, one uses legacy FDMA. Some broadcast on the traditional L1 band, others on the modernized L5 band, and a few carry free centimeter-level correction services baked directly into their signal structure.
How many of these 130+ satellites your receiver actually uses depends entirely on your constellation and frequency configuration. This volume disassembles the physical infrastructure behind GNSS signals to help you make deliberate, power-efficient hardware integration decisions.
Need-to-Know Terms
- Constellation: A fleet of navigation satellites providing global or regional positioning coverage.
- Frequency Band (L1/L2/L5): The radio frequency on which a satellite broadcasts its navigation signal.
- CDMA vs. FDMA: Two methods satellites use to share the radio spectrum. All modern constellations use CDMA (Code Division); GLONASS is the legacy FDMA (Frequency Division) exception.
- Open vs. Restricted Service: Open signals are freely available to all civilian users. Restricted signals are encrypted for military or authorized government use.
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 your DOP (Dilution of Precision). Lower DOP translates to faster, more reliable RTK initialization — particularly in environments where half the sky is obstructed.
Engineer’s Takeaway
In an urban canyon, single-constellation GPS may see only 4–6 satellites — barely enough for a standalone fix. Four-constellation tracking pulls that number above 25, often the difference between a stubborn Float and a solid RTK Fix. Multi-constellation support isn't a luxury; it's a prerequisite for obstructed environments.
The Frequency Layer: L1, L2, L5
All GNSS signals are broadcast in the L-band (1–2 GHz), with three primary slots allocated for civilian navigation:
| Property | L1 (1575.42 MHz) | L2 (1227.60 MHz) | L5 (1176.45 MHz) |
|---|---|---|---|
| Code Bandwidth | Narrow (C/A: 1.023 MHz) | Medium (L2C: 1.023 MHz) | Wide (10.23 MHz) |
| Multipath Rejection | Weak | Moderate | Strong |
| Interference Protection | Standard | Standard | Strong (ARNS Band) |
| RF Front-End Complexity | Lowest (mature silicon) | Moderate | Higher (wideband RF required) |
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 L1+L5 Is the Mass-Market Dual-Frequency Standard
L1+L5 has rapidly overtaken L1+L2 as the mass-market dual-frequency configuration due to four converging factors:
- The wide frequency gap (~400 MHz) between L1 and L5 produces highly effective ionosphere-free linear combinations, improving atmospheric error cancellation.
- L5's 10.23 MHz code bandwidth gives roughly 10× the multipath discrimination of L1 C/A, dramatically improving performance in reflected-signal environments.
- Consumer-market scale, especially from smartphones, automotive platforms, and IoT devices, has driven L1+L5 chipset BOM costs down to near single-frequency levels. This is why compact RTK receivers such as Kalmix SCOUT PRO can use L1+L5 without moving into traditional survey-grade price tiers.
- The L5 signal sits inside a protected aeronautical radionavigation band, giving modern L1/L5 designs a stronger interference-resilience story 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.
Pro Tip: Antenna-Frequency Alignment
Your antenna's internal bandpass filter must match your receiver's frequency plan. Pairing a legacy L1/L2 survey antenna with a modern L1/L5 receiver will physically block the 1176 MHz L5 signal — a common and frustrating integration mistake that shows high L1 SNR but persistent L5 dropouts.
The Four Global Constellations
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, unlocking practical civilian accuracy overnight. Currently, GPS maintains 31 operational satellites across 6 orbital planes at an altitude of ~20,200 km.
| Signal | Frequency | Service | Status |
|---|---|---|---|
| L1 C/A | 1575.42 MHz | Open | Fully operational (all satellites) |
| L1C | 1575.42 MHz | Open | Deploying on Block III/IIIF |
| L2C | 1227.60 MHz | Open | Deploying — not yet on all satellites |
| L5 | 1176.45 MHz | Open | Deploying on Block IIF and III/IIIF |
Pro Tip: GPS vs. GNSS
Because GPS was the pioneer, the acronym became the generic term for all satellite positioning. However, modern receivers track multiple global constellations simultaneously. The standard, technically accurate term for the entire infrastructure is GNSS (Global Navigation Satellite System). Using "GPS" to describe a modern multi-constellation RTK receiver technically ignores over 70% of the satellites it actually tracks.
GLONASS (Russia) — The FDMA Exception
Currently 24 satellites. GLONASS 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
Currently 30 satellites. The only global constellation designed civilian-first — its entire 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:
| Signal | Frequency | Service | Notes |
|---|---|---|---|
| E1 | 1575.42 MHz | Open | Interoperable with GPS L1; carries OSNMA authentication |
| E5a | 1176.45 MHz | Open | Aligned with GPS L5 / BeiDou B2a |
| E5b | 1207.14 MHz | Open | Used in E1+E5b dual-frequency RTK configurations |
| E6 | 1278.75 MHz | Commercial / HAS | Carries HAS correction data for approximately 20 cm horizontal accuracy under supported service conditions |
Galileo offers two capabilities no other constellation provides. HAS (High Accuracy Service) on E6 delivers free satellite-broadcast corrections for approximately 20 cm horizontal accuracy under supported service conditions — 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
Currently 46 satellites across a unique three-layer orbital architecture (GEO + IGSO + MEO), providing the highest satellite visibility of any single constellation 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 deliberately moved to B1C (1575.42 MHz) and B2a (1176.45 MHz) — precisely aligning with GPS L1/L5 and Galileo E1/E5a. This strategic 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 — functionally similar 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.
Integration Warning
SBAS is a free accuracy upgrade for single-frequency consumer applications. However, SBAS and RTK do not stack. When computing an RTK fixed solution using RTCM data, your receiver completely ignores SBAS corrections — the RTK engine supersedes them. Enabling SBAS alongside RTK won't cause errors, but it also won't improve your Fix.
The Frequency Panorama: All Signals on One Map
The spectrum diagram below maps every major open-service signal across the L-band. By visualizing how these bands overlap — especially the L1/E1/B1C cluster at 1575 MHz and the L5/E5a/B2a cluster at 1176 MHz — you can see why modern dual-frequency receivers achieve seamless interoperability across constellations with a single RF front-end, and why your NTRIP mountpoint must match your receiver's actual RF hardware capabilities.
* = Carries free satellite-based precise correction services (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:
- BeiDou not participating in RTK Fix despite L1+L5 hardware Check firmware config. Your receiver may be defaulting to BDS-2's legacy B1I instead of BDS-3's interoperable B1C/B2a signals. Explicitly enable B1C and B2a tracking in the constellation configuration.
- GLONASS visible in GSV but absent from GSA / RTK solution Missing MT1230 in the RTCM stream. Confirm your NTRIP mountpoint includes MT1230; if the caster doesn't provide it, disable GLONASS entirely to free DSP channels for constellations that are actually participating.
- High SNR on L1, but L5 signals constantly dropping out Antenna mismatch. You're likely using a legacy L1/L2 survey antenna with a modern L1/L5 receiver. The antenna's internal bandpass filter is physically blocking the 1176 MHz L5 signal. Verify the antenna datasheet explicitly lists L5/E5a band support.
- Module intermittently resets when 4 constellations are enabled Power supply bottleneck. Full-constellation tracking causes baseband current spikes up to 150–200 mA above idle. If your device is powered through a current-limited USB port or unpowered hub, the host's Overcurrent Protection (OCP) will hard-reset the device. Add independent voltage regulation or a powered hub.
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 — How GNSS Works: One Equation, Four Satellites — walks through the mathematical pipeline that transforms these invisible RF broadcasts into your first three-dimensional position fix.
Key Takeaway
Your receiver’s usable sky is not defined by how many satellites exist. It is defined by constellation configuration, RF frequency support, antenna bandwidth, RTCM compatibility, and available processing and power budget.
Frequently Asked Questions
What is the difference between GPS and GNSS?
GPS is one satellite navigation constellation operated by the United States. GNSS is the broader term for all satellite navigation systems, including GPS, GLONASS, Galileo, BeiDou, QZSS, NavIC, and SBAS. A modern RTK receiver usually tracks multiple GNSS constellations at the same time to improve satellite visibility, geometry, and fix reliability.
Why can a receiver track many satellites but still fail to get a fix?
Tracking a satellite does not mean the receiver can use it in the final position solution. A receiver may exclude satellites when signal strength is too low, ephemeris data is missing or stale, the geometry is poor, the correction stream does not support that constellation, or required bias messages such as RTCM MT1230 for GLONASS RTK are absent. For debugging, compare GSV satellite visibility with GSA solution participation and fix status.
Should I choose L1+L5 or L1+L2 for a new GNSS design?
For new robotics, vehicle, and IoT designs, L1+L5 is usually the more forward-looking choice because GPS L5, Galileo E5a, and BeiDou B2a align around 1176.45 MHz and benefit from stronger multipath rejection and protected-band interference resilience. L1+L2 remains important for professional surveying and legacy CORS infrastructure, so the right choice depends on whether your product prioritizes modern mass-market integration or compatibility with older survey workflows.
Why is L5 better for urban environments and urban canyons?
L5 uses a much wider code bandwidth than legacy L1 C/A. Inside the receiver, that creates a sharper correlation peak, making it easier to separate the direct satellite signal from reflected multipath signals bouncing off buildings, glass, metal, and wet ground. This is why L1+L5 receivers are usually more stable than older single-frequency designs in urban canyons, although antenna placement, obstruction, and receiver algorithms still matter.
Can one L1/L5 antenna receive GPS, Galileo, and BeiDou signals?
Yes, if the antenna is designed for both L1 and L5 bands. GPS L1, Galileo E1, and BeiDou B1C share the 1575.42 MHz region, while GPS L5, Galileo E5a, and BeiDou B2a share the 1176.45 MHz region. A properly designed L1/L5 antenna can support these constellations through one RF path, but a generic “GPS antenna” may only support L1.
What is Galileo HAS, and does it replace RTK?
Galileo HAS is a free satellite-broadcast correction service that can provide approximately 20 cm horizontal accuracy under supported service conditions without NTRIP or internet-delivered corrections. It does not replace RTK for centimeter-level applications. Instead, it sits between standalone GNSS and full RTK, making it useful when decimeter-level positioning is enough or connectivity is unreliable.
You Might Also Like
How GNSS Works: One Equation, Four Satellites
See how these RF signals become pseudoranges and a 3D position fix.
LateralGNSS Accuracy Decoded
Understand CEP, RMS, R95, and DOP — the statistical layer above signal selection.
ApplyKalmix SCOUT PRO
Evaluate L1/L5 signal tracking, antenna matching, and RTK behavior on a field-ready receiver.
