Weak-signal digital station checklist: clock, audio levels, CAT, and what decode thresholds really tell you
- Replies 2
- Views 27
- 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 digital-mode problems turn out to be one of four things: the clock, the audio level, the rig's mode settings, or CAT/PTT. The software (WSJT-X, fldigi, JS8Call, Winlink Express with VARA) gets blamed first, but it is usually the last thing at fault. This thread is meant as a working checklist, with room for disagreement on the details.
Start with the chain. The receiver audio goes through a sound card or the rig's built-in USB codec into the decoder. The transmit audio goes back out through the same path, and PTT is keyed by CAT, VOX, or a serial control line. If any link is wrong, you get the familiar symptoms: decodes that fall far short of what the mode should manage, splatter on the waterfall, or a rig that sticks in transmit.
The mode matters for how much each link is stressed. FT8 uses 15-second periods with a signal about 50 Hz wide. FT4 uses 7.5-second periods and about 80 Hz, so it is faster but needs a stronger signal and a tighter clock. JS8Call borrows FT8-style modulation for keyboard-style messaging, and its slower submodes trade time for sensitivity. WSPR is a beacon mode with 2-minute transmissions and a bandwidth of only a few hertz. Q65 and MSK144 are aimed at VHF and up: Q65 for EME and scatter paths, MSK144 for meteor pings. PSK31 and RTTY are older, narrow keyboard modes that still turn up in contests and on the calling frequencies. Olivia, MFSK and Hellschreiber, usually run through fldigi, are for noisy or fading HF paths where reliability matters more than speed.
On decode thresholds, the commonly quoted figures (around -21 dB for FT8, about -17 dB for FT4, and about -31 dB for WSPR) are referenced to a 2500 Hz noise bandwidth. They describe decoding on a clean, steady path with a properly set-up receiver. Fading, local noise, a drifting clock or an overdriven front end will all move the real threshold. SNR reports from different stations are also not a calibrated measurement, so treat them as relative.
Grid squares deserve a mention too. Maidenhead locators are the currency of FT8, WSPR and the VHF modes. A four-character grid such as FN31 covers 2 degrees of longitude by 1 degree of latitude. Six characters (FN31pr) narrow that to a subsquare. Check that the grid in your WSJT-X settings matches where you really are, because a wrong one corrupts your own spots and your distance and bearing calculations.
Where do you start when decodes are poor? And how do you handle several programs sharing one rig, say WSJT-X, a logger and fldigi, without fighting over the serial port?
Link to comment
https://www.hamradiobase.com/forums/topic/11373-weak-signal-digital-station-checklist-clock-audio-levels-cat-and-what-decode-thresholds-really-tell-you/Share on other sites