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 412.9 km/s
Aurora 1
Updated 14: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

Getting started with EME: what each band really demands, and where new stations get stuck

ci_cover.jpg

Moonbounce looks like a station-size problem, but it is mostly a link-budget problem. Once you know what the path costs and which losses you can recover, the equipment choices on each band make more sense. This thread is for comparing approaches on 2 m, 70 cm, 23 cm and the microwave bands, and for the operating details that decide whether a sked works.

Round-trip path loss is roughly 250 dB or more on 144 MHz. It rises by about 20 log of the frequency ratio, so expect roughly 9 to 10 dB more on 432 MHz and another 9 to 10 dB on 1296 MHz. The moon's distance changes the loss too. Perigee versus apogee is worth about 2 dB, which is a real difference when you are working at the decode threshold. The round-trip delay is about 2.5 seconds, which is why you can hear your own echo and why a quick echo test is the first sanity check.

On 2 m, the usual entry point for digital EME is an array of several long-boom Yagis. Four is a commonly discussed minimum, with more for a comfortable margin, plus a mast-mounted low-noise preamp and a legal-limit-class amplifier. Exact results depend on your local noise, feedline loss and who you are working. Big stations can work smaller ones on JT65 or Q65, but a small station will not hear its own echo and has to rely on the other end's ears. 70 cm needs less physical size for the same gain, but you need more elements or more antennas, tighter mechanical accuracy and a very good feedline. On 23 cm, a dish of roughly 3 m is a common starting point. With about 55% efficiency that gives around 30 dBi and a beamwidth near 5 degrees. At 10 GHz the same 3 m dish gives roughly 47 dBi, but the beamwidth drops to about 0.7 degrees, so tracking accuracy becomes the main challenge. The moon itself is only about half a degree across.

Receive performance matters as much as transmit power. A low-noise preamp close to the feed point, sequenced T/R switching and as little loss as possible ahead of the first stage are the basics. Sky temperature is a big factor on 2 m, where galactic noise can dominate when the moon sits in a hot part of the sky. Measuring sun noise or moon noise gives you a useful check on whether your system is as good as you think.

For modes, JT65 was the long-time standard for weak-signal EME. Q65 in WSJT-X is the newer option, and its submodes let you match tone spacing to the Doppler spread you expect on a band. Spread is mostly caused by libration, the moon's slight rocking, and it scales with frequency. It is modest on 2 m, much more obvious on 23 cm, and large on 10 GHz. Pick the submode for the band and for what the other station is using. Check the WSJT-X documentation for current recommendations instead of relying on old rules of thumb.

Polarization is where many first schedules go wrong. On 2 m and to a lesser extent 70 cm, Faraday rotation in the ionosphere can swing the received polarization significantly, so signals fade in and out even when everything else is fine. Spatial polarization offset also exists because the two stations see the moon from different places. Cross-polarized Yagi arrays with switching or phasing help here. On 23 cm and above, Faraday rotation shrinks and fixed linear or circular feeds are more practical. If you use circular polarization, remember that reflection reverses the sense, so agree a convention with your partner.

For planning, you want a mutual moon window, a reasonable moon declination, favorable sky noise and a Doppler offset you can manage. Tools such as MoonSked and VK3UM's EME calculator help with windows and expected performance. The hardware that follows the moon is the rotor, or the az/el mount with its controller and software. It needs to be accurate enough for the beamwidth you have, with a backlash and calibration routine you actually trust.

Questions for the thread: what is the smallest 2 m array you consider worth building today for Q65? And what is your preferred way to check pointing and system noise before a sked?

  • Replies 2
  • Views 36
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the first question, I would stop thinking in terms of a magic element count and look at the whole system. A four-Yagi array with good low-loss feedline, a preamp with a genuinely low noise figure, and a clean location will often beat a larger array with lossy cable and a noisy site. The one thing the array size does set is whether you can hear your own echo. That ability is very valuable because it lets you test the transmit and receive chain without anyone else involved. Without it, you are relying on tests with larger stations and on what they report back.

For checking pointing, sun noise is hard to beat on 2 m and above when the sun is available, because it is a strong, repeatable source. Moon noise measurements are possible with larger apertures. In both cases, compare the Y-factor against what the antenna and receiver should deliver. A big shortfall usually points to feedline loss, a preamp problem, or pointing error, and you can separate those by changing one thing at a time.

  • Moderators

One thing I would add for anyone planning 70 cm or 23 cm: do not overlook Doppler and frequency accuracy. On 2 m the shift is small enough that people sometimes ignore it. At 1296 MHz the shift is roughly nine times larger, and at 10 GHz it is far worse. WSJT-X can handle Doppler correction and has an echo test tool, but your radio's frequency stability and any transverter or LO chain need to be solid. A drifting transverter makes the decode much harder than the path itself.

On the polarization point, I would treat the polarization setup as something to practice before a real sked. It is easy to lose a whole window because the antenna is sitting at an angle that happens to be bad at that time. If you have a rotatable feed or switchable cross-polarized array, try different settings during echo tests or schedule setups and write down what works at different moon positions. On 2 m, expect the best angle to keep changing, and agree with your partner in advance how you will handle it, for example by alternating polarization between periods.

Finally, for planning the sked, include a margin for the real world. Moon elevation, local obstructions, sky noise, wind loading on a big dish and the other station's own window can all cut the usable time well below what the calculator shows.

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.