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.5
Wind 385.0 km/s
Aurora 1
Updated 13:00 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 station planning from 2 m to 10 GHz: what matters most for the first contacts?

ci_cover.jpg

I'd like to start a practical thread on moonbounce station requirements, ordered by what limits you on each band. The basic problem is the same everywhere. The round-trip path loss is roughly 250 dB on 2 m. It rises by about 9.5 dB each time you triple the frequency, which puts 70 cm near 261 dB, 23 cm near 271 dB, and 10 GHz close to 288 dB. Moon distance adds roughly 2 dB of variation between apogee and perigee, so the same station is measurably stronger around perigee.

On 2 m, the usual entry point is a group of long-boom Yagis. Four is a common size, and more is better. Add a legal-limit amplifier, a mast-mounted low-noise preamp, and low-loss feedline. Receive noise matters as much as transmit power. A relay and a few extra tenths of a dB of loss ahead of the preamp can cost you more than a modest drop in amplifier output. Sky noise is high on 2 m, especially when the moon is near the galactic plane, so the same hardware gives noticeably different results on different days.

On 70 cm, the antenna choice shifts toward larger Yagi arrays or a dish. On 23 cm and above, dishes are the norm. As a rough guide, a 3 m dish on 23 cm gives about 30 dBi with a typical efficiency. A 1.8 m dish on 10 GHz is around 43 dBi. The tradeoff is beamwidth. A 3 m dish on 23 cm is around 5 degrees wide, and a 1.8 m dish on 10 GHz is around 1 degree. The moon is only about half a degree across, so pointing accuracy and a solid mount matter a lot more on the microwave bands.

For modes, JT65 and Q65 are the main digital choices, both in WSJT-X. The echo delay is about 2.5 seconds, so you transmit for most of the period and then listen for the return. Q65 has several submodes with different tone spacing. Wider spacing helps as Doppler spread grows on the higher bands. Its decoding threshold is slightly better than JT65A under comparable conditions, but check which mode and submode the active stations on your band are using. The convention I've seen cited for JT65 EME is that the more easterly station transmits in the first period, but confirm that with your partner before the sked.

Where would you spend money first if the goal is a first completed contact: receive noise, antenna gain, or tracking accuracy?

  • Replies 2
  • Views 19
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

For a first contact I'd put receive performance and the ability to hear your own echoes ahead of anything else. If you can't copy your own echo, or at least see it in the WSJT-X Echo tool, you're guessing about the whole system. That's much harder to debug during a sked. You can test the pointing, noise figure, and Doppler settings against the moon without needing another station to be on.

Polarization is where bands differ most. Faraday rotation is a real problem on 2 m because the ionosphere rotates the plane of a linear signal, and the effect falls off roughly with the square of frequency. By 23 cm it is usually negligible. On 2 m that means fades or deep nulls when your polarization is wrong relative to the incoming wave, and some 2 m stations use switchable or rotatable polarization to work around it. There is also spatial polarization offset, which comes from the two stations being in different places. It affects linear systems on all bands, so a dish with a rotatable linear feed is still useful. Circular feeds trade some of that headaches for a few dB of mismatch against a linear station.

Libration fading is a separate effect. The moon's apparent rocking spreads the echo in frequency, which shows up as rapid flutter on the signal. The spread scales with frequency, from a fraction of a hertz on 2 m to a few hertz on 23 cm and much more at 10 GHz. That's one reason wider-tone-spacing submodes matter on the higher bands. It also means a signal that looks marginal on a waterfall may still decode if the software is built for that spread.

  • Administrators

Tracking and scheduling are the parts people underestimate. For tracking, use software with az/el rotor control and keep a regular calibration routine. Sun noise is a convenient reference on microwave bands. If the sun peak shows up offset from where the software says the sun is, your zero or elevation reference is off. Backlash and mast flex that you can ignore on a 2 m array will cost you signal on a narrow dish beam.

Doppler is the other piece. Earth rotation alone can shift the echo by a few hundred hertz on 2 m, and the figure scales with frequency, reaching several kilohertz on 23 cm. WSJT-X can apply Doppler correction, and the usual approach is to choose between correcting your transmit frequency so your partner hears you on the nominal frequency, or correcting for your own echo. Agree in advance on which method you're both using. Otherwise you can end up both looking in the wrong place on the waterfall.

For sked planning, work out when both stations have the moon above the horizon with enough elevation, then look at the date. Perigee and moon declination affect path loss and window length. Sky background near the galactic center on 2 m affects noise, and you should check the moon's position relative to strong sky noise sources. Agree on the band, mode, submode, and period order. Then agree on the fallback plan if one of you can't hear the other, such as using a short message set like RO, RRR, and 73 in JT65. A written plan beats trying to improvise on the air, especially when the signal is only a few dB above the decoding threshold.

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.