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

Getting started with EME: what each band demands, JT65 vs Q65, polarization, libration and planning skeds

ci_cover.jpg

This thread is meant as a working overview for people deciding which band to try for moonbounce, and a place to correct the rough numbers below. Treat the figures as ballpark and check them against your own station calculations.

The basic problem is path loss. Round-trip loss to the Moon and back is on the order of 252 dB on 144 MHz, about 261 dB on 432 MHz, about 271 dB on 1296 MHz and around 290 dB on 10 GHz. The Moon's distance changes over each orbit, so path loss swings by a little over 2 dB between perigee and apogee. That is one reason the same station can be marginal one week and comfortable the next. The echo delay is about 2.5 seconds, which is why the weak-signal digital modes use alternating one-minute periods rather than anything interactive.

On 2 m, the usual serious entry point is a phased array of several long Yagis, a mast-mounted low-noise preamp, and hundreds of watts to a kilowatt at the antenna. On 70 cm, people use either more Yagis or a dish, because wavelength shrinks and individual gain per element goes up, but pointing and feedline loss get less forgiving. On 23 cm, dishes dominate, and a few metres of aperture is a common starting point for working larger stations. On 10 GHz, a well-built dish with a good LNA and tens of watts can work, but pointing accuracy, feed alignment and frequency stability become the main challenges.

For modes, JT65 has long been the standard for EME QSOs, and Q65 is the newer option in WSJT-X, generally with somewhat better weak-signal performance and submodes chosen according to Doppler spread. Spread grows with frequency, so the submode that suits 2 m is not the one that suits 23 cm or 10 GHz. Check the current WSJT-X documentation and the activity on your band before choosing. The Echo mode in WSJT-X is worth using before any sked, because hearing your own echoes is the most direct end-to-end test of antenna, pointing, receiver, transmit power and Doppler tracking.

Two propagation effects deserve their own discussion. Faraday rotation twists the polarization of lower-band signals, so a fixed linear antenna can see deep fades as the received polarization rotates. It matters most on 2 m, less on 70 cm, and is generally negligible by 23 cm. Libration fading comes from the Moon's apparent rocking, which spreads the reflected signal in frequency and produces rapid flutter. It gets worse as frequency rises, from a small fraction of a hertz on VHF to tens or hundreds of hertz in the microwave range.

For people planning a first EME setup, which band gives the best return for the effort and cost? And what do you consider the minimum useful polarization and tracking capability on each band?

  • Replies 2
  • Views 21
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On 2 m and 70 cm, the array design usually decides how much you can do. Four reasonably long Yagis give a beam that is wide enough to be forgiving but still gives usable gain. Going to eight or more helps, but it brings tighter pointing requirements, a heavier mechanical load and a much more demanding feed and phasing network. Stacking distances and phasing line lengths matter more than people expect, because a mismatch in the harness wastes the gain you built the array to get.

Receive performance usually matters as much as transmit power. A good mast-mounted preamp with a low noise figure helps only if you keep the loss ahead of it small, so the TX/RX relay and any filtering need to be thought through carefully. The preamp, relays and PA also need proper sequencing, so the amplifier never keys before the relay has switched and nothing is hot-switched. Sky noise matters too: on 2 m, when the Moon is in or near a hot part of the sky, the background noise may hide signals you could otherwise copy. Planning around that can save a lot of wasted time.

For polarization on 2 m, being able to switch or rotate between orientations is far better than a single fixed linear. A common approach is two sets of antennas or cross-polarized elements with a switching or phasing arrangement. Some stations use polarization diversity on receive, which means two polarization channels decoded with software that can combine or pick between them. Even without Faraday rotation, two stations at different locations see the Moon's geometry differently, so there is always a spatial offset between their polarizations. A fixed polarization can therefore be a poor match even in the absence of ionospheric effects.

On the software side, the main thing is to let WSJT-X do the Doppler correction and keep the rig frequency dial accurate. If the dial is a bit off, you will see it immediately in your own echoes, which is why Echo mode is a good routine check.

  • Moderators

On 23 cm and up, the picture changes. Faraday rotation is mostly irrelevant, so polarization becomes a feed design question instead. Most dish stations use circular polarization, and the Moon reverses the sense of circular polarization on reflection, so the transmit and receive senses need to be handled correctly. It is much better to be able to switch the receive sense than to guess and lose several dB. Check the agreed convention for the band you are using before a sked.

Dish performance is determined by surface accuracy, feed placement and illumination. An undersized or poorly focused feed spills energy past the edge of the dish and picks up ground noise, which wastes both transmit and receive performance. On microwaves, a dish's beamwidth can be narrower than the sky distance covered by the Moon's disc, so tracking accuracy and pointing calibration are as important as raw gain. Calibrating on the Sun, and on the Moon's own noise at higher bands, is a practical way to find pointing errors and check the Y-factor of your receive chain.

Libration spread is the reason mode choice and decoding settings change as you go up in frequency. On 23 cm it is already significant, and on 10 GHz it is a large part of why the signals sound like a rough, wide buzz rather than a clean tone. Doppler shift also grows with frequency: hundreds of hertz on 2 m, several kilohertz on 23 cm and tens of kilohertz at 10 GHz. Without automatic Doppler tracking, you will be chasing the signal for the whole session.

For sked planning, the first thing is to check mutual Moon visibility, because the Moon must be above the horizon at both ends and you want it well above the horizon, not scraping the trees. After that, consider the Moon's distance, sky noise at the Moon's position, and each station's capabilities. Agree explicitly on the band, mode, frequency, who transmits in the first minute and what message sequence you will use, because assumptions about the first period are a common cause of a failed sked. Also keep your tracking software tied to the same time source as your decoding software, since a clock error of a second or two can ruin a sked.

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.