1. The network that had to be in the right place at the right time

Carl Sagan’s Contact returns as the recalled work because the signal from Vega does not arrive continuously; it arrives when the Earth has rotated the receiving array into the right position. A LEO desktop faces the same geometry. A ground station can only hear the spacecraft when it is above the horizon, and each pass lasts minutes. The solution is more ground stations, relay satellites, or both.

This entry reads about ground stations, relay networks, modulation, and coding.

2. Ground stations and pass geometry

A ground station’s coverage is a circle on the Earth defined by the minimum elevation angle the link can support. For LEO, a single station might see the spacecraft for five to fifteen minutes per orbit. The time between passes depends on the orbit inclination, the station latitude, and the number of stations.

Options for increasing coverage include:

  • Own ground stations: full control, but expensive to build and operate globally.
  • Ground station networks: commercial services that sell pass time on a shared network, such as KSAT, SSC, or Atlas Space Operations.
  • Relay satellites: constellations like Starlink, Iridium, or Orbcomm that provide near-continuous connectivity from orbit to orbit.

A relay changes the architecture fundamentally. Instead of scheduling short ground passes, the spacecraft maintains a near-continuous link to a relay constellation, which then forwards data to the ground. The trade is cost, data rate, latency, and dependency on a third-party network.

3. Modulation and coding

Modulation is how bits are mapped onto radio waves. Common choices include:

  • BPSK: robust, low spectral efficiency, good for weak links.
  • QPSK: twice the bits per symbol of BPSK at the same symbol rate, slightly less robust.
  • Higher-order PSK and QAM: more bits per symbol but require stronger signals.

Coding adds redundant bits so the receiver can correct errors without retransmission. Forward error correction codes like convolutional codes, Reed-Solomon, Turbo codes, and LDPC allow a link to work at lower signal-to-noise ratios. The trade is overhead: coding reduces the effective data rate but increases reliability.

Adaptive modulation and coding change the modulation and code rate based on link conditions. A spacecraft near zenith might use a high-rate mode; near the horizon it might fall back to a more robust mode.

4. Data rate and latency

The product of the link budget, modulation, coding, and bandwidth is the data rate. For the desktop, the important question is whether the data rate over available passes is enough to empty the data buffers. If a payload produces 10 GB per orbit but the link can only downlink 2 GB, the platform must either store data, be more selective, or increase the link capacity.

Latency is the time between data being collected and data being available on the ground. Direct downlink to a nearby ground station can be minutes. Relay constellations can reduce this to seconds or less, depending on the relay architecture.

5. What this changes

  • Ground station coverage and relay availability determine how often and how long the platform can communicate.
  • Modulation and coding trade data rate against robustness.
  • Adaptive modulation and coding can maximize throughput across a pass.
  • The next entry will read about protocols, latency tolerance, and regulatory constraints.