GNSS Signals Explained: Why Your Receiver Ignores Most of the Sky
On this page
TL;DR
More than 100 navigation satellites orbit Earth. A receiver tracks the signals its antenna, RF front-end, and firmware support; its positioning engine then chooses which tracked observations to use. For RTK, matching base-station observations and corrections are the final piece. Your frequency plan decides how much of that fleet the receiver can use.
Before your receiver can calculate a centimeter-level RTK fix, it must capture a signal, track the satellite, and use a compatible observation in the RTK solution. These are three different gates—and each one can shrink the satellite count on your screen.
GNSS Frequencies at a Glance
This guide focuses on the L-band navigation frequencies used by common civil receivers. 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.
| Band | Civil frequency | Why it matters |
|---|---|---|
| L1 | 1575.42 MHz | Primary civil GNSS band shared by GPS L1, Galileo E1, and BeiDou B1C-compatible signals. |
| L2 | 1227.60 MHz | Legacy dual-frequency workhorse for many survey and CORS workflows. |
| L5 | 1176.45 MHz | Modern civil band aligned with GPS L5, Galileo E5a, and BeiDou B2a for L1/L5 receiver designs. |
That worldwide fleet spans GPS, GLONASS, Galileo, BeiDou, QZSS, and NavIC. Its satellites transmit different signals: GPS L1 C/A and L5 use different bands and code designs, legacy GLONASS still uses FDMA, and some satellites also broadcast precise correction data. A receiver needs the right signal support before a satellite can help its position solution.
The useful three-stage model is in view → tracked → used in the solution. Sky geometry determines the first stage; antenna, RF, and firmware determine the second; the positioning mode and, for RTK, compatible base-station data determine the third.
Need-to-Know Terms
- Constellation: A fleet of navigation satellites providing global or regional positioning coverage.
- Frequency band (L1/L2/L5): A named radio-frequency range used by navigation signals; several signal types can share one band.
- CDMA vs FDMA: Two methods satellites use to share the radio spectrum. Modern open signals generally use CDMA (Code Division); legacy GLONASS signals are the FDMA (Frequency Division) exception.
- Open vs restricted service: Open signals are available to civilian users without authorization. Restricted signals require authorization and may serve government or commercial users.
How Many Satellites Can You Actually Use?
The total in orbit is not the number above one receiver. From most locations, Galileo alone normally puts six to eight satellites in view. GPS, BeiDou, and GLONASS add more choices. Count again after applying your antenna horizon and elevation mask: those are the satellites your receiver has a chance to track.
The tracked count then narrows to the satellites used by the position engine. Firmware support, RF coverage, available tracking channels, and signal quality all matter. More well-spread measurements can improve geometry and lower DOP (Dilution of Precision). For RTK, the rover also needs usable observations that match its base station; satellite count alone does not determine whether ambiguities fix.
What Multi-Constellation Buys in an Urban Canyon
A narrow street can leave GPS with too few clean line-of-sight signals for a reliable solution. Tracking Galileo, BeiDou, and GLONASS gives the receiver more candidates from other parts of the sky. That is why multi-constellation support matters most when the view is constrained—but reflections still need to be rejected, not counted as good satellites.
L1, L2, and L5 Frequency Bands
The receiver-design comparison below focuses on three familiar L-band frequencies: L1, L2, and L5. It uses specific GPS civil signals as examples; a frequency band is not a single waveform.
| Property | L1 (1575.42 MHz) | L2 (1227.60 MHz) | L5 (1176.45 MHz) |
|---|---|---|---|
| Example signal | GPS L1 C/A | GPS L2C | GPS L5 |
| Code rate | 1.023 Mcps | CM and CL: 0.5115 Mcps each, interleaved at 1.023 Mcps | 10.23 Mcps |
| Spectrum context | 1559–1610 MHz: RNSS and aviation GNSS | 1215–1300 MHz: RNSS, shared with radiolocation | 1164–1215 MHz: RNSS and aviation GNSS, shared with DME/TACAN |
Both L1 and L5 sit in spectrum used by aviation GNSS under aeronautical radionavigation service (ARNS) protections; ICAO's allocation overview also shows L2 sharing spectrum with radiolocation and L5 sharing with DME/TACAN. These allocations manage licensed emissions; they do not make any GNSS band immune to jamming. Signal design and receiver implementation decide what survives real interference.
Why Dual-Frequency GNSS Helps RTK Receivers
L1+L5 is a strong choice for new receiver designs, while L1+L2 remains central to established survey workflows. Four engineering factors explain the trade-off:
1. Ionospheric correction. Both L1+L2 and L1+L5 give a receiver the two frequencies needed to remove first-order ionospheric delay. Tropospheric delay is a different error and needs other modeling. For the error mechanism behind that benefit, see GNSS Errors Mapped.
2. Sharper GPS code tracking. GPS L5 runs at 10.23 Mcps, ten times the GPS L1 C/A code rate. Its sharper correlation peak helps a capable receiver separate some delayed reflections from the direct signal. It does not recover a direct path blocked by a building.
3. Cross-constellation alignment. GPS L5, Galileo E5a, BeiDou B2a, QZSS L5, and NavIC L5 share 1176.45 MHz. Combined with L1/E1/B1C around 1575.42 MHz, that gives an L1/L5 design a clear frequency plan across several systems. The antenna, RF front-end, baseband, and firmware still need to support each signal you intend to use.
4. Product fit for moving machines. Signal diversity matters when sky view and multipath change along the routes described in RTK GPS for Robotics. It also explains why Kalmix's AG3335 platform choice leans into L1/L5 rather than treating frequency support as a generic spec line. Which L5 signals a given part actually tracks differs across the AG3335 variants, so the band list belongs in the model comparison rather than the platform decision.
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.
Antenna Bandpass Must Match the Frequency Plan
Your antenna's internal bandpass filter must match your receiver's frequency plan. An antenna specified only for L1/L2 can attenuate L5 enough to cause a misleading symptom: strong L1 tracking with persistent L5 dropouts. Check the antenna datasheet for 1176.45 MHz coverage and verify the complete RF path before treating the problem as firmware.
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 uses six orbital planes at an altitude of about 20,200 km and operates more satellites than its 24-satellite baseline to maintain coverage.
| Signal | Frequency | Service | Status |
|---|---|---|---|
| L1 C/A | 1575.42 MHz | Open | Fully operational (all satellites) |
| L1C | 1575.42 MHz | Open | Fielded on GPS III; deployment continuing |
| L2C | 1227.60 MHz | Open | Broadcast by capable IIR-M, IIF and III satellites; GPS.gov lists the service as pre-operational |
| L5 | 1176.45 MHz | Open | Broadcast by capable IIF and III satellites; GPS.gov lists the service as pre-operational |
GPS.gov's civil-signal status distinguishes a signal being broadcast from the declaration that the service is fully operational.
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). Calling a multi-constellation receiver "GPS" hides the signals it really supports. Use "GNSS" when the receiver combines GPS with other systems.
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. Legacy GLONASS assigns satellites to FDMA frequency channels; antipodal satellites can reuse a channel. FDMA introduces inter-frequency receiver biases that matter when combining base and rover observations.
RTCM MT1230 carries GLONASS code-phase biases so a rover can account for differences from its base station and fix GLONASS ambiguities. Receiver support varies: some can use station-identification information instead, while others keep GLONASS ambiguities float when bias information is missing. Modernized GLONASS satellites also transmit CDMA signals alongside the legacy FDMA system.
Galileo (EU): Civilian-First Architecture
Galileo is the European Union's civilian-operated global navigation system. Its open signals span E1 and E5, with additional services carried on E6.
The signal map below shows how Galileo aligns with GPS and BeiDou—and where its free HAS correction data are broadcast:
| 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 | Free HAS on E6-B | Broadcasts precise corrections for supported Galileo and GPS signals |
Galileo offers two capabilities with different jobs. HAS (High Accuracy Service) supplies free precise corrections for Galileo and GPS through E6-B or the internet; a compatible PPP receiver can use the satellite broadcast without NTRIP. Its published Full Service target is 20 cm horizontal accuracy at 95% after convergence, while the current service is still the Initial Service. OSNMA (Open Service Navigation Message Authentication) authenticates Galileo E1 navigation messages. It verifies the data source, not the measured range itself.
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-3 added B1C (1575.42 MHz) and B2a (1176.45 MHz) while continuing B1I (1561.098 MHz) and B3I (1268.52 MHz). B1C and B2a align with GPS L1/L5 and Galileo E1/E5a, giving receiver designers shared frequency targets across the three systems. Tracking a BeiDou signal still requires antenna and RF coverage plus the right baseband and firmware support.
Regional Navigation Systems and Augmentation
Beyond the four global constellations, QZSS and NavIC provide regional navigation signals, while SBAS systems broadcast corrections and integrity information:
- QZSS (Japan): Provides GPS-compatible L1, L2 and L5 navigation signals across its Asia–Oceania service area. Its L6 CLAS (Centimeter Level Augmentation Service) delivers precise corrections in the Japan service area and requires an L6-capable receiver.
- NavIC / IRNSS (India): A regional system designed for India and nearby areas. NavIC broadcasts L5 at 1176.45 MHz, and newer NVS satellites add L1 at 1575.42 MHz. Check current service and receiver support before relying on NavIC in a design.
- SBAS (WAAS / EGNOS / GAGAN / MSAS): Broadcasts wide-area corrections and integrity alerts. It improves standalone positioning in its service region; integrity monitoring is the key feature for aviation.
Keep SBAS and RTK Correction Modes Distinct
Do not count SBAS as another accuracy gain on top of an RTK fixed solution. In RTK mode, the receiver works from base observations carried in RTCM; SBAS serves a different positioning mode. For a robot or vehicle, test how the receiver falls back when RTK corrections disappear so the controller handles changes in fix quality cleanly.
The Frequency Panorama: Selected GNSS Signals
The spectrum diagram below maps selected open-service signals across the L-band. The L1/E1/B1C cluster at 1575.42 MHz and the L5/E5a/B2a cluster at 1176.45 MHz give multi-constellation receivers shared frequency targets. Your receiver still has to decode each signal, and an RTK mountpoint must provide observations your rover can use.
The Developer's Debugging Checklist
Start with NMEA GSV and GSA to compare satellites reported in view with those used in a position solution. For RTK failures, go one level deeper: inspect the receiver's signal diagnostics and the RTCM observations from the base station.
| Symptom | First checks |
|---|---|
| BeiDou not participating in RTK Fix despite L1+L5 hardware | Compare the BeiDou signals tracked by the rover with those in the base station's RTCM MSM stream. RTK works best when both sides observe the same signals; enable supported B1C/B2a only when the correction source carries matching observations. |
| GLONASS tracked, but its ambiguities remain float in RTK | Check for GLONASS observation messages and the bias information your rover needs, such as MT1230 or a supported station-description path. If this rover cannot use GLONASS with the mountpoint, excluding it is an option after diagnosis—not the first move. |
| High SNR on L1, but L5 signals constantly dropping out | Check the antenna datasheet for 1176.45 MHz coverage, then inspect the cable, filters, receiver settings and L5 C/N0. An antenna specified only for L1/L2 can attenuate L5 enough to cause this pattern. |
| Module intermittently resets when 4 constellations are enabled | Check the supply voltage at the module during a reset and compare the power path with that module's peak-current specification. Verify regulator and cable transient margin before changing constellation settings. |
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.
Key Takeaway
Frequency choice is a product decision, not a radio-label detail. L1+L5 favors modern mass-market receivers, outdoor machines, and compact hardware; L1+L2 still matters when survey infrastructure and legacy CORS compatibility define the workflow.
Frequently Asked Questions
What is the difference between GPS and GNSS?
GPS is one global satellite navigation system. GNSS is the broader term for systems including GPS, GLONASS, Galileo, BeiDou, QZSS and NavIC. SBAS systems augment satellite navigation rather than form another core constellation. A multi-constellation receiver can use supported signals from several systems for better availability and geometry.
Why can a receiver track many satellites but still fail to get a fix?
Tracking is only the middle step between a satellite being in view and its observations being used. Weak or reflected signals, missing navigation data, receiver settings and poor geometry can all reduce the used count. For RTK, also compare the rover's signals with the base station's RTCM observations and check the bias information your receiver requires.
Should I choose L1+L5 or L1+L2 for a new GNSS design?
Both combinations support dual-frequency ionospheric correction. L1+L5 aligns modern GPS L5, Galileo E5a and BeiDou B2a signals at 1176.45 MHz, making it a strong choice for new multi-constellation designs. L1+L2 remains valuable when existing survey receivers and CORS networks set the compatibility target. Choose the pair that your antenna, receiver and correction source can all use.
Why is L5 better for urban environments and urban canyons?
GPS L5 uses a 10.23 Mcps code, ten times the GPS L1 C/A rate. Its sharper correlation peak helps a capable receiver separate some delayed reflections from the direct signal. It cannot recover a signal blocked by a building, so antenna placement and multi-constellation tracking still matter in an urban canyon.
Can one L1/L5 antenna receive GPS, Galileo, and BeiDou signals?
Yes. An antenna with coverage at 1575.42 MHz and 1176.45 MHz can receive GPS L1/L5, Galileo E1/E5a and BeiDou B1C/B2a. The receiver must also have the RF, baseband and firmware support to track and decode each signal. Check the antenna datasheet for both frequencies rather than assuming any GPS antenna covers L5.
What is Galileo HAS, and does it replace RTK?
Galileo HAS broadcasts free precise corrections for supported Galileo and GPS signals on E6-B and also distributes them through the internet. A compatible PPP receiver uses those corrections after convergence. HAS is useful when decimeter-class positioning fits the job; it is a different workflow from local RTK. Galileo's published 20 cm horizontal figure at 95% is a Full Service target, not an instant result for every receiver.
Continue exploring
GNSS Accuracy Decoded
CEP, RMS, R95 and DOP: the statistical layer that sits above signal selection.
LateralThe RTK Trick
What carrier phase does with the signals your front-end managed to track.
ChooseGNSS Receiver Guide
Match a receiver class to the bands, constellations and antenna you actually need.
