Choosing a digital mode and fixing the usual FT8 problems: time sync, audio levels, CAT and what the decode thresholds mean
- Replies 2
- Views 25
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
This thread is for sorting out the practical side of digital operating. Mode choice, interface setup and the weak-signal numbers all tie together, and a problem in one area often looks like a problem in another. Questions come up all the time like "why don't I decode anything on a band that is clearly open?" or "why do I get reports of -24 when the signal sounds strong?" Here is a framework to start from, and please correct anything I get wrong.
Start with the modes by what they are built for. FT8 uses 15-second transmit/receive periods, 8-tone FSK and about 50 Hz of bandwidth. It is designed for a minimal exchange (callsign, grid or report, RR73/73) at very low signal-to-noise ratios, with a decode limit often quoted around -21 dB. FT4 uses 7.5-second periods and a wider signal, with a threshold a few dB worse. That trade buys faster contest-style QSOs. WSPR is not for conversations at all. It is a beacon mode with 2-minute transmissions and a very narrow signal, and it is useful for propagation checks because its threshold is far lower, around -30 dB. JS8Call borrows FT8-style modulation but adds free-form keyboard messaging, relaying and store-and-forward, with selectable speeds. Slower submodes decode weaker signals but take longer to send each message.
The older keyboard modes sit in a different category. PSK31 (31.25 baud, a very narrow BPSK signal) and RTTY (commonly 45.45 baud with 170 Hz shift) are much less sensitive than the WSJT-family modes, but a human reads the text in real time. Olivia and other MFSK modes use heavy error correction and long symbol times to get text through under the noise, at a slow typing speed. Hellschreiber is different again: it sends text as a visual raster, so you read the characters on screen instead of relying on a decoder. For those modes FLDIGI is the usual software, and WSJT-X covers the FT8/FT4/WSPR/Q65/MSK144 family.
Where do you start when decodes are missing? In my experience the usual suspects are the clock, the audio level and the radio's mode settings, roughly in that order. What do others check first, and what do you consider a sane default setup for a new interface?
Link to comment
https://www.hamradiobase.com/forums/topic/11486-choosing-a-digital-mode-and-fixing-the-usual-ft8-problems-time-sync-audio-levels-cat-and-what-the-decode-thresholds-mean/Share on other sites