Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

EME by band: what 2 m, 70 cm, 23 cm and 10 GHz moonbounce really demand, and how JT65/Q65, Faraday and libration change the plan

ci_cover.jpg

Starting a thread to compare the bands side by side, since EME advice is usually scattered by band. The aim is to line up the physics with the hardware, and then argue about where the real thresholds sit. Corrections welcome, especially on current activity conventions, which vary and should always be checked against what active stations are doing.

The link budget. Round-trip path loss via the Moon is roughly 252 dB on 144 MHz, 261 dB on 432 MHz, 271 dB on 1296 MHz and around 290 dB on 10 GHz. It rises as 20 log f, and it swings about 2 dB between perigee and apogee. The key point is that antenna gain for a fixed physical aperture rises with frequency too, at both ends of the path. So higher bands do not demand proportionally more brute force. A 3 m dish gives roughly 29-30 dBi at 1296 MHz and close to 48 dBi at 10 GHz. What you pay in at the top end is pointing accuracy, tracking, feed and transmit-line losses, and wider Doppler spread.

Rough hardware by band. These are ballpark figures, not guarantees, since results depend on who you are trying to work.

On 2 m, the common approach is an array of long-boom Yagis (four is a typical starting array), a transmit chain in the high hundreds of watts up to the legal limit, very low-loss feedline, and a mast-mounted low-noise preamp. A single long Yagi plus power can hear and work the largest stations in digital modes. It is a limited, schedule-dependent path, but it shows that the entry barrier on 2 m is lower than people assume.

On 70 cm, Yagi arrays are still the usual route because a dish needs to be several metres across to match them at that wavelength. Expect more elements or more Yagis than on 2 m for similar performance. Sky noise is lower than on 2 m, so receive-chain quality counts for more.

On 23 cm, dishes dominate. A 3 m class dish with a good feed, circular polarisation and a few hundred watts at the feed is a recognised stepping stone. Beamwidth is around 5 degrees, so tracking becomes automatic rather than manual.

On 10 GHz, the Moon is only about 0.5 degrees across, and a 3 m dish has a beamwidth of well under a degree. Pointing accuracy, a rigid mount, a stable LO and frequency-calibrated gear matter as much as raw power. Moon and Sun noise measurements are the standard way to verify gain and pointing.

Modes. JT65 has long been the workhorse. JT65B is typical for 144/432 and JT65C for 1296 and up, where wider tone spacing copes with spread. Q65 is the newer WSJT-X mode, with submodes A to E that set the tone spacing for different spread. It generally decodes slightly better than JT65 under comparable conditions and supports averaging across periods. The WSJT-X guide has a recommended submode table, and active groups usually settle on one letter per band. Use the echo test and the Astronomical Data window (Moon azimuth and elevation, Doppler, delay, spread, degradation estimate) to confirm your own setup before you try for a QSO.

Questions to start: where do you think the practical break-even is for a first 70 cm station, Yagis or a dish? What fraction of lost QSOs on 2 m are really polarisation rather than raw signal? And how do you plan skeds when your moon window with the partner is short?

  • Replies 2
  • Views 26
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On the VHF/UHF side, I'd rank the hardware priorities like this: loss ahead of the preamp, then polarisation control, then more gain.

Feedline loss matters twice. On transmit, every 0.5 dB lost in coax is power you paid for and never radiated. On receive, loss before the preamp adds directly to system noise. That is why serious setups put the preamp at the antenna through a low-loss relay, and why the sequencing and relay choice get as much attention as the preamp itself. A preamp with a very low noise figure behind a lossy relay is a false economy. On 2 m the sky temperature is high anyway, from several hundred K to well over a thousand K near the galactic centre, so there is a point past which a better preamp barely helps. On 70 cm and up, you notice the difference much more.

Polarisation is where 2 m differs most from the other bands. Faraday rotation scales roughly with 1/f², so 432 MHz sees about a ninth of the effect at 144 MHz, and 1296 MHz sees only about 1/80. On 2 m, linear polarisation can rotate through large angles, and the signal fades in and out over minutes as the effective angle sweeps through the cross-polarised null. On top of that there is a purely geometric offset between two stations at different locations, because each sees the Moon from a different angle. That spatial term does not average out the way Faraday does.

The usual fixes are the ability to switch between horizontal and vertical, to phase a cross-polarised array, or to physically rotate the antennas. Many serious arrays have it for a reason. Without it, you can be sitting on a perfectly good path and wait for the cycle to come around. With it, you often get a better stretch in the same window.

If I were building up gradually, I'd get a good receive chain and polarisation switching working on one array, check echoes with the WSJT-X Echo mode, and only then scale up gain.

  • Moderators

Picking up the microwave side, because the problems change character there.

Once you go above 1296 MHz, Faraday goes away but libration spread takes over. The Moon's rocking motion spreads the echo in Doppler, and the spread scales roughly with frequency: a fraction of a hertz on 2 m, around a hertz on 23 cm, and tens of hertz at 10 GHz. That means the usual JT65 tone spacing can smear the signal, which is why wider spacing (JT65C, or the higher Q65 letters) is used. It also makes the echo sound rough and fade quickly, so a long decode period with fast fading is common. Libration spread is also not constant over the month, which is another reason to look at the spread figure in WSJT-X before a sked.

Doppler shift is not small either. It is in the hundreds of hertz at 144 MHz, several kilohertz at 1296 MHz, and tens of kilohertz at 10 GHz. Stable references and software Doppler correction are routine. On the 23 cm band and up, the usual convention for circular polarisation is to transmit RHCP and receive LHCP, because reflection flips the sense. Confirm that with your partner rather than assuming it.

Tracking accuracy is the other microwave catch. A 3 m dish at 1296 MHz has a beamwidth of roughly 5 degrees, so slight pointing error costs little. At 10 GHz the beam is well under a degree and about the size of the Moon. A flexible mount or a slow encoder will cost you decibels you cannot recover from the amplifier. Moon-noise and Sun-noise measurements are the practical way to detect that your pointing model is off.

For sked planning, start with the mutual window: both stations need the Moon above a usable elevation at the same time. Then add selection criteria. Perigee gives the best path, low sky noise (Moon away from the galactic plane and the Sun) helps on lower bands, and the Moon at a reasonable elevation avoids ground noise. A common convention in JT65 is that the more easterly station takes the first period, but agree on it explicitly in the sked. Keep the exchange minimal and standard (callsigns, reports, a confirmation, then 73) so that a marginal QSO is not lost to a procedural misunderstanding. The short messages like RO and RRR are decoded at lower signal levels than full messages, which is why they exist.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.