HF Digital Contest Operating: RTTY and FT4 Strategy for Competitive Scores

Digital contesting occupies a strange middle ground — it's faster than CW for many operators but more technical than phone. RTTY has decades of contesting tradition, with major events like CQ WW RTTY and ARRL RTTY Roundup drawing thousands of participants. FT4, designed explicitly for contesting, is the newer challenger that's reshaping how we think about rates and strategy.

I've been active in digital contests for eight years, progressing from tentative first entries to consistent top-100 finishes in my category. Here's what I've learned about turning digital contests from a casual activity into competitive operations.

RTTY Contesting: The Established Game

Software Setup

You need three things working together:

1. Logging program: N1MM+ is the standard. Free, powerful, excellent RTTY integration.
2. RTTY engine: MMTTY (within N1MM+) or 2Tone (better for selective decoding). Both are free. MMTTY handles most situations; 2Tone's twin-peak algorithm resolves overlapping signals better in crowded conditions.
3. Radio interface: Your rig's sound card or USB audio. Set your TX audio levels so ALC shows zero deflection — RTTY should drive the transmitter at constant power without ALC action.

Critical N1MM+ settings for RTTY:

• Enable SO2V (Single Operator, 2 VFOs) if your radio supports it. This lets you decode one frequency while calling CQ on another.
• Set up your function keys with proper macros (more on this below).
• Enable the RTTY bandmap — it shows decoded callsigns at their frequencies. This is your hunt-and-pounce goldmine.

RTTY Macro Templates

Your macros make or break your rate. Here's what works:

CQ: CQ CQ TEST {MYCALL} {MYCALL} CQ

Short. Don't send "CQ contest" — everyone knows it's a contest. Don't send your call three times on HF; twice is enough. On VHF where signals might be marginal, three is fine.

Exchange (to answer a caller): {HISCALL} 599 {EXCH}

Where {EXCH} is your zone, state, serial number, or whatever the contest requires. No "UR" or "RST" filler. Just the data.

Repeat: {HISCALL} AGN? or just AGN?

Don't resend your entire exchange when they ask for a fill. Send what they missed.

QRZ: QRZ {MYCALL}

After logging a contact, immediately send QRZ with your callsign. Keeps the rate flowing.

RTTY Frequency Strategy

RTTY subbands on HF:

• 20m: 14.080-14.099 (US), extending to 14.100 during big contests
• 40m: 7.030-7.060 (varies by region)
• 15m: 21.080-21.099
• 10m: 28.080-28.099

During major contests, find a clear frequency near the middle of the subband for CQ. Edges are where newbies and casual operators tend to cluster — mid-band gets more sweep traffic from experienced operators using the bandmap.

Running vs. Search & Pounce (S&P): If you can sustain 30+ contacts per hour running, keep running. If your rate drops below 20/hr, switch to S&P until you find a better run frequency. Early in the contest, run to build multipliers. Late in the contest, S&P to find missing multipliers.

The 599 Myth

Every RTTY exchange includes 599 because the mode is either decoded or it isn't. Nobody sends 479 in RTTY. It's a formality inherited from CW contesting. Just send it and move on.

FT4 Contesting: The New Paradigm

How FT4 Differs from FT8

FT4 was designed by K1JT specifically for contesting:

• Cycle time: 7.5 seconds (vs. 15 seconds for FT8)
• Bandwidth per signal: 83.3 Hz
• Minimum SNR for decode: about -17.5 dB (FT8 is about -21 dB; FT4 trades 3.5 dB of sensitivity for speed, which is adequate for contest conditions)
• Exchange format: Fixed contest exchanges (grid square, state, serial number depending on contest)

The faster cycle time means a theoretical maximum rate of about 120 QSOs/hour (one per 30 seconds through four cycles). In practice, sustained rates of 60-80/hr are achievable by strong stations.

WSJT-X Setup for FT4 Contesting

WSJT-X handles FT4 natively. Key settings:

• Mode: Select FT4 (not FT8)
• Special operating activity: Check this box, select the specific contest
• Frequencies: Standard FT4 contest frequencies are:
  • 3.575, 7.0475, 14.080, 21.140, 28.180 MHz
• Auto-sequencing: Enable it. Manual sequencing in FT4's 7.5-second windows is humanly possible but exhausting.
• Fox and Hound: Leave it off. It is FT8 DXpedition mode, where the rare station runs Fox and the callers run Hound, not part of FT4 contesting.

Critical: Set your audio levels correctly. FT4 is more sensitive to overdriving than FT8. Watch your ALC — it should show zero deflection. The protocol's timing precision means any power compression artifacts can prevent decodes.

FT4 Contest Strategy

FT4 contesting is tactically different from both RTTY and FT8:

Calling CQ in FT4: You appear on other stations' waterfalls. Your callsign is decoded and displayed. They click you to call. This is more passive than RTTY — your signal quality and frequency choice matter more than CQ rate.

Picking your frequency: Avoid the center of the passband where everyone clusters. The edges (1500-2000 Hz or 500-800 Hz audio) get less QRM. In WSJT-X, right-click the waterfall to select your TX frequency.

Multi-band strategy: FT4 contacts happen fast. Switch bands frequently to maximize multipliers. Unlike RTTY where finding a good run frequency takes minutes, FT4 lets you CQ immediately on any clear slot.

Dual-decode: Some operators run WSJT-X instances on two bands simultaneously (with two radios or SO2R). The auto-sequencing handles the timing — you just confirm QSOs as they complete.

FT4 vs. RTTY: When to Use What

In contests that allow both modes:

Use RTTY when:

• You have a strong signal (500W+, good antenna)
• Bands are open and clear
• The contest rewards RTTY contacts specifically
• You can sustain high run rates

Use FT4 when:

• Your signal is modest (QRP or compromise antenna)
• Conditions are marginal (low bands, high noise)
• You're working DX that can't copy your RTTY through their local noise
• The contest allows FT4 contacts for credit

Common Mistakes and How to Avoid Them

Mistake 1: Over-Driving the Transmitter

This is the #1 problem in digital contesting. RTTY and FT4 are constant-duty-cycle modes. Your transmitter must handle continuous keydown for the entire transmission duration.

• Set power to 75% of your rig's max rating for RTTY
• Watch for ALC deflection — it means you're overdriving
• Monitor your signal on a nearby receiver or SDR to check for splatter

A clean 500W RTTY signal outperforms a dirty 1000W signal every time. Splatter earns you enemies and complaints to the contest committee.

Mistake 2: Wrong Audio Tones

RTTY uses two tones (mark and space) separated by 170 Hz. Standard mark frequency is 2125 Hz, space is 2295 Hz (or reversed depending on software configuration).

If your tones are wrong, your signal will be off-frequency from where the logging program thinks it is. Other stations using bandmap-click tuning will tune to the wrong spot and miss you.

Verify your setup: transmit into a dummy load, decode yourself on a nearby receiver or SDR. Confirm the frequency matches what N1MM+ reports.

Mistake 3: Ignoring Rate Meters

N1MM+ shows your current rate and projected score in real-time. Watch these numbers. When your rate drops, change strategy immediately. Common triggers:

• Band closing (switch to a lower band)
• Frequency going QRM (move)
• Time of day shift (more stations switching to your band, increasing competition)

Mistake 4: Not Leveraging Spotting Networks

In contests that allow it (most do for single-op assisted categories), use the DX cluster and RBN feeds integrated into N1MM+. New multipliers appear on your bandmap in real-time. When a new multiplier pops up, pounce immediately — others will too.

Mistake 5: Poor Band Change Timing

Band changes waste time — you lose your run frequency, need to tune, find a spot. Change bands with purpose:

• A new multiplier is spotted on another band
• Your current band rate has died below 15/hr
• Propagation charts indicate better conditions elsewhere

Don't band-hop every five minutes. Commit to a band for at least 10-15 minutes before evaluating.

Hardware Considerations

Interface Settings

For RTTY contesting with N1MM+:

• Radio CAT control: Essential for automatic frequency logging and bandmap integration
• PTT method: Hardware PTT is fastest and most reliable. VOX works but adds delay.
• Sound card levels: Set output so ALC reads zero. Input so decoded text is clean without AGC pumping.

Computer Speed

RTTY decoding is lightweight. FT4 decoding is more demanding — WSJT-X runs FFTs on every 7.5-second window. A modern i5/Ryzen 5 handles it easily. Older machines might miss decodes if the CPU can't complete the FFT in time.

Dual Monitor

Seriously, get a second monitor for digital contesting. Screen 1: logging program and bandmap. Screen 2: RTTY/FT4 decode window. This lets you watch for new callsigns without switching windows.

Contest Calendar

Major digital contests worth marking:

• CQ WW RTTY (September): The big one. Massive activity, all bands.
• ARRL RTTY Roundup (January): North American focus, great for new contesters.
• CQ WW RTTY WPX (February): Prefix multipliers add strategy depth.
• ARRL International Digital Contest (June): FT4/FT8 specific.
• Makrothen RTTY (multiple dates): 24-hour events with distance-based scoring.

Start with ARRL RTTY Roundup — it's shorter (30 hours), single-band-per-contact multipliers are simple, and the exchange is just state/province or serial number.

Building Your Score Over Time

Your first digital contest, just focus on making contacts and learning the rhythm. Don't worry about rate or strategy — get comfortable with the software flow and exchange patterns.

Second contest: practice running. Find a frequency, call CQ, handle the responses. Learn to use macros smoothly.

Third contest and beyond: start optimizing. Track your rates, plan your band changes, leverage spotting, aim for improvement over your previous score.

Digital contesting rewards consistent practice more than raw power. An operator who knows their software cold and times band changes well will beat a bigger station with a confused operator every time.