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

Planning a first EME station: what 2 m, 70 cm, 23 cm and 10 GHz each demand in hardware and operating habits

ci_cover.jpg

Starting a thread to collect practical notes on moonbounce from 144 MHz up through the microwave bands. Many station plans seem to start from the antenna you can fit on the property, when the better starting point is the link budget and the operating mode. The numbers below are ballpark. Run your own station through an EME planning calculator (VK3UM's is widely used) before buying metal.

Round-trip path loss is roughly 252 dB on 2 m, about 9 to 10 dB more on 70 cm, and another 9 to 10 dB on 23 cm. Each tripling of frequency costs about 9.5 dB. Antenna gain rises with frequency too, so a given physical aperture recovers most of that loss. What you lose is pointing tolerance, surface accuracy and feedline loss margin. The Moon's distance also varies. Perigee versus apogee is worth about 2 dB, so the same station will be easier or harder to work depending on the date.

JT65 made small-station EME realistic because it decodes well below the noise floor. The usual convention is JT65A on 2 m, JT65B on 70 cm and 23 cm, and JT65C on the higher microwave bands, because the wider tone spacing copes with more Doppler spread. Q65 in newer WSJT-X releases adds submodes for the same purpose, plus averaging and better handling of fading. Check the current WSJT-X guide and what your sked partners actually run, since the preferred submode and period length can differ by band.

Questions I'd like to see discussed. What is a sensible minimum on each band if the goal is to work the big stations, not just hear your own echo? Where do preamp placement and feedline loss matter most? How do people handle polarization on 2 m? And how do you plan a sked when the Moon window overlaps by only an hour or two?

  • Replies 2
  • Views 34
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On 2 m and 70 cm, the array and the receive chain share the job. A common entry point on 2 m is a phased array of several long-boom Yagis (four is typical) with a legal-limit amplifier. Single-Yagi operation is possible, but you will mostly hear only the largest stations. Whatever the array, the first thing to check is the receive noise figure. A mast-mounted low-noise preamp with a very low noise figure and a good sequencer so the transmit relay never hot-switches are worth more than an extra dB of antenna gain you cannot hear.

Feedline loss counts twice, once on transmit and once as added noise on receive. As a rule of thumb, 0.1 dB of loss ahead of the preamp adds about 7 K to system noise. That is why the preamp sits at the antenna and why the relay and connectors ahead of it should be the best you can get. On 2 m the sky itself is noisy, especially when the Moon is near the galactic plane, so the same hardware performs differently from day to day. WSJT-X's Astronomical Data window shows sky temperature and a degradation figure for exactly this reason.

Polarization is where 2 m differs most from the higher bands. Faraday rotation in the ionosphere scales roughly with the inverse square of frequency, so it is severe on 144 MHz, much smaller on 432 MHz, and negligible from 1296 MHz upward. On 2 m the rotation changes over minutes to hours, so a fixed linear polarization can fade to nothing for a while even when everything else is right. There is also a geometric offset between the two stations' views of the Moon. Common answers are a crossed-Yagi array with a polarization switch or phasing network, or a mechanically rotatable array. Pure horizontal or vertical can work, but you should expect a share of unavoidable fades.

For operating, put the quick things on your list: use the correct JT65 or Q65 submode, set your Doppler correction properly, and agree on which of you transmits in the first period. Use the shorthand messages sparingly and only when your partner's software expects them.

  • Moderators

To add the microwave end: on 23 cm and above you normally go to a dish, and the design priorities change. Gain scales with aperture and efficiency, so a 3 m dish on 1296 MHz comes out near 30 dBi, and a 4 m dish a couple of dB more. That is useful gain from a single structure, with no phasing harness. The tradeoff is pointing. A 4 m dish at 23 cm has roughly a 4 degree beamwidth, but a 3 m dish at 10 GHz is down around 0.7 degrees, and the Moon itself is about 0.5 degrees across. At 10 GHz the mount, the tracking and the surface accuracy (a couple of millimetres rms) all matter. Wind alone can drop you out of the beam.

Moon tracking can come from a computer-controlled az/el mount fed by your logging or tracking software, with WSJT-X supplying a cross-check through its Az/El and Doppler readouts. At the higher bands, a sun noise or Moon noise measurement is the standard way to confirm that the dish is pointed correctly and the receive chain is healthy. If you cannot measure noise rise, you do not really know your system's numbers.

Polarization on 23 cm and up is usually circular, and the reflection reverses the sense of rotation. Stations normally agree on a convention, often transmit one sense and receive the opposite. Confirm that with your sked partner instead of assuming it, because a mismatch costs you most of your signal.

Libration fading is the other effect that grows with frequency. The Moon's apparent wobble spreads the echo in frequency. The spread is a fraction of a hertz on 2 m, a few hertz on 23 cm and tens of hertz at 10 GHz. That spread is why the wider-tone JT65 and Q65 submodes exist, and why signals that look fine on the waterfall may refuse to decode on the higher bands. Look at the predicted spread before you blame your hardware.

For planning skeds, the real constraint is the shared Moon window: both stations need the Moon above a usable elevation at the same time. Check that before agreeing on a date. Prefer dates near perigee when you are marginal, and avoid times when the Moon sits in a noisy part of the sky on 2 m or 70 cm. Settle the time, frequency, mode, first/second period and polarization in advance, and leave some margin in case the first attempt fails.

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.