Working a Satellite Pass: Orbits, Doppler Shift, Spin Fading, and Setting Uplink Power

Concept

This lesson closes out the whole Waves, Signals, and Modes unit, and it does that by asking a Technician to use nearly everything the unit built rather than adding one more isolated fact. Working an amateur satellite means putting a signal through a spacecraft passing a few hundred miles overhead, and predicting how that signal behaves calls directly on three things already in place: T3A's lesson that a signal's behavior can shift for reasons that have nothing to do with the transmitter, just the changing physical situation between the two ends of a contact; T8A's vocabulary for choosing an emission type to fit a given situation; and T0C's discipline of treating transmitter power as something to actively manage rather than simply maximize. Amateur satellites themselves are modest machines by satellite standards: small, often built and paid for by amateur radio operators and clubs rather than governments, carrying a low-power transponder that relays signals between ground stations rather than doing anything more elaborate. A station on the ground doesn't need commercial-grade equipment to use one — a handheld radio, a directional antenna, and some planning are enough to turn a few hundred miles of empty sky into a working, if brief, radio path.

Concept

Nearly every amateur satellite in common use flies in what's called a low Earth orbit, an orbit close enough to the planet's surface that gravity pulls the spacecraft all the way around in something like ninety minutes to just past a hundred, rather than the twenty-four hours a satellite parked in a much higher, geostationary orbit takes to circle once. That short orbital period is exactly why an amateur satellite contact looks nothing like a phone call: the spacecraft isn't hanging in a fixed spot in the sky the way a geostationary satellite does, so a ground station only has access to it while it happens to be rising above the local horizon, arcing across the sky, and setting again on the far side — a window that, for a satellite in low orbit, typically lasts somewhere in the ballpark of ten to fifteen minutes before it's gone below the horizon again and a station has to wait for the next orbit to bring it back around. Everything a Technician does during a satellite contact — tuning, calling, listening, adjusting power — has to happen inside that short, moving window, which is part of why the rest of this lesson's protocols exist: there simply isn't time to fumble.

Concept

A satellite contact always has two separate legs, and amateur operators have their own vocabulary for each: the uplink is the path from a ground station up to the satellite, the signal a Technician actually transmits, while the downlink is the path back down, the signal a ground station listens to on a completely different receiver, often tuned to a different band altogether than the one used to transmit. Putting the uplink and downlink on separate bands isn't an accident or a quirk — it keeps a station's own powerful transmitted signal, sitting right next to a receiver trying to hear a whisper-quiet signal arriving from hundreds of miles away, from drowning out the very downlink that station is trying to copy. Satellites advertise which bands they use for each leg with a short shorthand built from band letters, one letter for the uplink band and one for the downlink band, so an operator can tell at a glance, before ever touching a dial, which two bands a given bird needs tuned in at once. Most transponder satellites relay whatever comes up on the uplink back down on the downlink continuously, the way a small, orbiting mailbox forwards everything dropped into one slot back out through another, rather than the satellite ever originating traffic of its own.

Concept

T8A already laid out why SSB suits a weak, marginal signal and FM suits a strong, reliable one, and satellites split cleanly along that same line depending on how their transponder is built. A linear transponder doesn't pick out one channel; it takes a whole slice of spectrum arriving on the uplink and retransmits that entire slice on the downlink, so however many stations are using SSB or CW inside that slice at once, all of them ride through simultaneously, each occupying its own narrow sliver — exactly the kind of power-efficient, narrow-bandwidth mode T8A already showed reason to prefer whenever spectrum and power both have to be shared carefully. Other satellites instead carry a single FM repeater, handling one conversation at a time the same way a terrestrial FM repeater does, complete with the same capture-effect behavior T8A described: whichever FM signal reaches the satellite strongest is the one that gets relayed, and everyone else is shut out until that transmission ends. A satellite's band pairing gets written as a short two-letter code, one letter marking the uplink band and one marking the downlink band; a bird that takes calls on the 70-centimeter band and answers back on 2 meters carries a code built from exactly those two bands, and checking that code before keying up is as routine as checking a repeater's offset.

Concept

T3A already made the point that a signal can behave differently from one moment to the next for reasons that have nothing to do with what the transmitter is doing — multipath and a shifting ionosphere were the culprits there. A satellite pass introduces a different culprit entirely, and it changes frequency instead of strength: as a satellite in low orbit races along at several miles per second, first approaching a ground station and then, partway through the pass, receding from it, the frequency that station actually hears drifts away from the frequency the satellite is genuinely transmitting, compressed higher while the satellite closes the distance and stretched lower once it's pulling away — the identical physics behind a car horn sounding higher pitched as it approaches and lower as it passes and recedes. Because a satellite in low orbit is close and moving fast relative to the ground, that shift is large enough to matter on both the uplink and the downlink, and it isn't a one-time correction: it keeps changing continuously through the whole pass, meaning a station either has to nudge its dial in small steps every minute or so to stay centered on the transponder, or lean on tracking software that recalculates and applies that correction automatically as the pass unfolds. Skip the correction entirely and a signal that started out clearly centered on frequency can drift most of the way out of a receiver's passband by the time the satellite reaches the horizon on the far side.

Concept

A second in-pass effect shows up alongside Doppler shift and gets confused with it constantly, even though the two have almost nothing in common apart from both happening during the same pass. Doppler shift changes frequency; this second effect, called spin fading, changes strength instead, and its cause is entirely different: many small satellites aren't stabilized to hold one fixed orientation the way a ground-based antenna is bolted in place — instead they slowly tumble or spin as they orbit, dragging their onboard antenna through that same tumble. T3B already established that a receiving antenna picks up a signal best when its own physical orientation lines up with the arriving wave's polarization; a tumbling satellite antenna sweeps through every possible orientation over and over as the spacecraft rotates, so the signal it radiates toward the ground swings from well-aligned to badly mismatched to well-aligned again on a cycle tied to the satellite's own spin rate, independent of anything happening with distance or relative velocity. The practical result is a slow, rhythmic rise and fall in signal strength layered on top of whatever else the pass is doing, and recognizing it as spin fading rather than a weakening signal or a Doppler problem is mostly a matter of noticing that rhythm: periodic, tied to the satellite's rotation, and just as present at the strongest point of the pass as anywhere else.

Concept

Tuning around Doppler shift by ear and knowing exactly when and where to look for a satellite both depend on knowing that satellite's orbit precisely, which is far more than a Technician could reasonably calculate by hand pass to pass — which is exactly the gap satellite tracking software fills. That software needs a compact numerical description of the orbit itself to work from, a standard set of orbital parameters published and regularly updated for every active satellite, describing the shape, tilt, and timing of its path around the Earth — numbers commonly called the Keplerian elements, after the astronomer whose laws first described how orbits behave. Feed a current set of those parameters into a tracking program along with a ground station's own location, and the software can work out everything that matters for the pass ahead of time: when a given satellite will next rise above the horizon, which direction and how high in the sky it will track across during that pass, and when it will set again, plus, moment to moment once the pass begins, exactly how far the transmitted frequency needs to be nudged at any instant to cancel out the Doppler shift discussed two blocks back — sometimes even driving a radio's tuning automatically rather than leaving an operator to chase it by hand. Because a satellite's orbit decays and shifts slightly over time from atmospheric drag and other small forces, that orbital data goes stale — a program running on parameters from months ago will mispredict a pass, so keeping that data current is as routine a piece of upkeep as checking a battery before a portable operation.

Concept

Every active amateur satellite also transmits something independent of whatever traffic is riding through its transponder at a given moment: a beacon, a steady signal generated by the satellite itself rather than relayed from the ground, typically running around the clock whether or not anyone happens to be using the transponder right then. A beacon carries telemetry — a continuous readout of how the spacecraft itself is doing internally, things like battery voltage, internal temperature, and which subsystems are currently active — packaged into a signal built to be simple enough that basic ground equipment can decode it without anything exotic. That openness is deliberate and matches the wider spirit of amateur radio generally: satellite telemetry isn't restricted to the team that built or operates the spacecraft, and no special key or credential is needed to listen in — any station capable of receiving the downlink can copy it, which is part of why satellite telemetry data ends up feeding hobbyist tracking and monitoring projects well beyond the satellite's own operating team. Because the beacon runs continuously and at a power level the satellite's own operators set and know precisely, it turns out to be useful for something else entirely too, which the next block picks up: it gives every station working the satellite a fixed, known reference to compare against.

Concept

T0C already established that transmitter power is something a station actively manages rather than simply maximizes, for the RF-exposure reasons that lesson covered — and a satellite uplink adds a second, equally concrete reason to keep power in check that has nothing to do with exposure limits at all. A satellite's transponder, whether linear or FM, only has so much capacity to relay signals, and every extra watt one station pushes at it beyond what's actually needed is a watt that isn't available for anyone else sharing that same limited resource; run noticeably more uplink power than necessary and the practical effect is crowding other operators off the bird rather than improving one's own contact at all. The beacon covered in the last block turns out to be the practical fix for the obvious next question — how does an operator know how much uplink power is actually enough — because the beacon transmits continuously at a steady, known power that every station can hear on the same downlink their own signal comes back on. Bring uplink power up gradually while listening to how loud that returning downlink signal sounds compared to the beacon sitting alongside it, and the right amount of power is the point where a station's own signal reaches roughly that same loudness on the downlink — not buried well under the beacon, and not blasting in dramatically louder than it — since going past that point doesn't make the contact any more reliable, it only takes capacity away from everyone else and adds nothing an already-adequate signal wasn't already delivering. Good satellite operating protocol generally follows that same minimum-necessary instinct: keep transmissions brief given how short a pass already is, listen for a gap before calling, and treat the transponder as a shared, finite resource for the whole few minutes it's in reach rather than a channel any one station owns.

Concept

Pull a whole pass together and satellite operation stops looking like a grab-bag of vocabulary and starts looking like one continuous sequence: a station checks a tracking program before a low-orbit satellite ever rises, using its current orbital data to know exactly when and where to look and picking an emission mode that matches whether the bird carries a linear transponder or a single FM channel; through the few minutes the pass actually lasts, that station nudges frequency to keep pace with a steadily changing Doppler shift, expects a separate rhythmic fade tied to the satellite's own spin rather than mistaking it for a weakening signal, checks in on the ever-present beacon both for the spacecraft's own health and as a reference for keeping uplink power at exactly enough and no more, and treats the whole brief window as shared time rather than a channel to hold onto. That's every thread this unit has spent since T3A weaving together — propagation reality, mode selection, and the RF-power discipline from T0C — landing in one operating scenario that asks for all of it at once, which is exactly why satellite operation closes out Waves, Signals, and Modes rather than sitting earlier in it. From here the course turns to what actually gets that signal off the ground in the first place: the next unit, Antennas and Feed Lines, opens with antenna theory itself — polarization, gain, and the dipole's radiation pattern — vocabulary this lesson has already leaned on informally every time it mentioned a satellite's antenna orientation, and vocabulary a satellite station depends on just as much as any of the modes or protocols covered here.