Matching the digital mode to the path: FT8, FT4, WSPR, Q65, MSK144, JS8Call and the keyboard modes, plus the audio, CAT and clock setup behind them
- Replies 2
- Views 95
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
Most problems with digital modes come from three things: picking a mode that doesn't suit the path, a transmit audio chain that isn't clean, and a PC clock that has drifted. This thread is for comparing notes on all three. The figures below are approximate and come from the published mode designs. Check the current WSJT-X and fldigi documentation and your local band plan before relying on any of them.
Weak-signal modes, roughly in order of sensitivity versus speed. FT8 uses 15 second transmit/receive periods, occupies about 50 Hz, and decodes down to around -21 dB (SNR in a 2500 Hz reference bandwidth). FT4 uses 7.5 second periods and about 80 Hz, with a threshold a few dB worse, which is the trade for faster contest-style exchanges. WSPR is a beacon mode rather than a QSO mode. It uses 2 minute periods and about 6 Hz of bandwidth, and decodes at roughly -30 dB, so it is a good tool for checking whether a band is open and how an antenna performs. Q65 in WSJT-X comes in several period lengths (15, 30, 60, 120 and 300 s) with different tone spacings. It is aimed at difficult paths such as EME, tropo scatter and ionospheric scatter on VHF and up. MSK144 is for meteor scatter, where the signal is a burst of a fraction of a second, so the software has to catch short pings, not integrate for a long period.
Keyboard and messaging modes. PSK31 (31.25 baud, narrow) is a conversational mode and is sensitive to overdriven audio, which creates IMD products on either side of the signal. RTTY (traditionally 45.45 baud, 170 Hz shift) is still common in contests and is more tolerant of poor conditions than its age suggests. MFSK modes in fldigi add forward error correction and handle fading better than PSK. Olivia is an MFSK variant that trades speed for robustness, with settings such as 8/250, 16/500 and 32/1000 (tones/bandwidth). It can copy text well below the noise, but slowly. Hellschreiber is different: the receiver paints the characters on the waterfall or display, so you read the text visually, and it can be readable when a decoder would give up. JS8Call uses FT8-style modulation but adds free-text messaging, heartbeats, relaying and store-and-forward. It offers several speeds (Slow, Normal, Fast, Turbo), and faster speeds need a stronger signal.
Winlink, VARA and the like. Winlink is an email-over-radio system, not a single mode. It can run over several transports, including packet, ARDOP and VARA. VARA HF and VARA FM are proprietary and free to use at a reduced throughput, with registration unlocking the higher speeds. Winlink sessions are connected, ARQ-style transfers, so before you transmit you need to listen for activity on the frequency, because a hidden-node collision will wreck someone else's transfer.
Time sync. FT8, FT4, WSPR, Q65 and MSK144 all depend on both stations agreeing on the clock. For FT8, a DT (time offset) consistently beyond about half a second means your clock or the other station's is off. Windows' default sync can be loose, so many operators use a dedicated NTP client or a GPS-disciplined source, and Linux users typically run chrony or ntpd. If decodes look fine but nobody replies, check DT before you check the antenna.
Grid squares. A Maidenhead locator like FN31 is two letters for the field and two digits for the square. Adding two more letters (FN31pr) gives a subsquare. FT8 normally exchanges only the four-character grid. WSPR and some other modes can carry six, and a precise locator matters more on VHF/UHF weak-signal work where distance records and awards are scored by grid.
Interface and CAT. A sound card interface (an external USB codec, a rig's built-in USB audio, or a transformer-isolated adapter) carries audio in both directions. Transmit audio should be set so the radio's ALC barely moves, with speech processing, compression and EQ off, and the radio in a data mode (USB-D, DATA-U or similar). Do not raise audio level to compensate for low power, because the clean answer is usually to lower the level and let the radio's power control set the output. CAT control through Hamlib or a manufacturer driver handles frequency and PTT, and in WSJT-X the split setting (Rig or Fake It) can keep transmit audio in the sweet spot of the radio's passband. Serial PTT via RTS/DTR, CAT PTT, and VOX each behave differently, and a ground loop between the PC, interface and radio is a common source of RFI and hum.
Which of these do people find the biggest source of failed decodes in practice: clock drift, overdriven audio, or CAT/PTT misconfiguration? And what mode do you reach for when FT8 is not enough?
Link to comment
https://www.hamradiobase.com/forums/topic/10961-matching-the-digital-mode-to-the-path-ft8-ft4-wspr-q65-msk144-js8call-and-the-keyboard-modes-plus-the-audio-cat-and-clock-setup-behind-them/Share on other sites