1. The probe that would not stop talking

Michael Crichton’s The Andromeda Strain includes a research team struggling to contain something while communicating under strict protocols. The desktop has a different problem: it must communicate continuously, securely, and flexibly, without becoming a management nightmare. A LEO desktop without a good comms architecture is a very expensive paperweight.

Entry 189 chose a 600 km, 51.6° orbit. This entry designs the communications layer around it.

2. Three traffic classes

Not all data is equal. The desktop should handle three classes:

  • Command and telemetry: low-rate, high-priority, always available. This is the heartbeat.
  • Payload data: moderate to high-rate, scheduled, sometimes bursty. This is the business.
  • High-rate downlink: very high-rate, for large data products or real-time relay. This is the premium channel.

Each class gets a different link strategy.

3. The command and telemetry layer

For routine command and telemetry, the desktop uses a small, omnidirectional UHF or S-band radio. This link does not need high bandwidth, but it must be available through most of the orbit. A network of commercial ground stations, or a relay like Starlink or another LEO constellation, can provide near-continuous coverage.

Cost estimate: a few hundred thousand dollars for the radio and a ground-network subscription.

4. The payload data layer

For routine payload data, the desktop uses a directional X-band or Ka-band link to dedicated ground stations. X-band is proven and widely supported. Ka-band offers higher rates but is more sensitive to weather. A mix of both is reasonable: X-band for reliability, Ka-band for speed when conditions allow.

With a modest antenna and 10–20 minute ground passes several times per day, the desktop can move tens of gigabytes per day.

5. The high-rate layer

For very high-rate data or interactive applications, the desktop can use optical communication. Laser links offer much higher bandwidth than radio and are harder to intercept. The downside is cloud sensitivity for ground optical stations, so optical works best when relayed through a constellation or a dedicated space relay.

A pragmatic first desktop does not need optical on day one. It should reserve mass, power, and pointing budget for a future optical terminal upgrade.

The desktop should also be able to talk to other spacecraft. A crosslink radio lets it receive data from nearby satellites, command a keeper tug, or relay through another platform. This turns the desktop from an endpoint into a node.

7. The architecture summary

  • UHF/S-band omnidirectional for command and telemetry.
  • X-band/Ka-band directional for routine payload data.
  • Optical terminal reserved for future high-rate upgrade.
  • Crosslink radio for spacecraft-to-spacecraft communication.
  • Commercial ground networks and possible relay constellations for coverage.

What this changes

  • The desktop uses a tiered comms architecture matched to traffic class.
  • Routine operations use cheap omnidirectional links; payload data uses directional radio; high-rate future growth uses optical.
  • Crosslinks make the desktop a network node, not just a ground terminal.
  • The next leisure entry can ask who operates all of this.