Clean digital-mode station setup: audio levels, CAT, time sync and what decode thresholds really tell you
- Replies 2
- Views 26
- 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 the station setup, not the mode. A short checklist of the things that most often go wrong, then some questions for the group.
Audio chain. WSJT-X and FLDIGI both work through a sound card, either the rig's built-in USB codec or an external interface. Three things matter most. First, turn off Windows or macOS audio "enhancements", system sounds and automatic gain on those devices, otherwise your transmit audio can be altered or other apps can leak into the signal. Second, set the receive level so the WSJT-X level meter sits around the middle of its range, roughly 30 dB on the bar, rather than pinned at either end. Third, on transmit, set the rig's USB audio or data input and the software output slider so the ALC shows little or no deflection. Digital modes are mostly constant-envelope, so a clean 30 W is far better than a splattery 100 W. Heavy ALC action or compression adds distortion, and other stations will see it as a wide, ugly trace on the waterfall.
CAT control. Hamlib is built into WSJT-X, and FLDIGI can use Hamlib or its own rig control. CAT gives you frequency readback and PTT without a separate serial line. In WSJT-X, the Split Operation setting (Rig or Fake It) keeps your audio offset in the ideal range for the transmit passband. Without it, a signal sent at a high audio offset can generate harmonics inside the passband. If you're on an interface with no CAT, DTR/RTS or VOX PTT works, but VOX can key from stray audio, so use it with care.
Time sync. FT8, FT4, WSPR, Q65 and MSK144 are all time-slotted. The software uses the DT column to show how far your clock is from the other station's. If DT is consistently off by half a second or more, fix your clock before touching anything else. Operating-system time sync can drift or update infrequently, so many operators use a dedicated NTP client or a GPS-backed source. Check the clock before a session, especially on a laptop that has been off or on battery.
Decode thresholds. The published figures are signal-to-noise ratios referenced to a 2500 Hz noise bandwidth, not dB over the noise floor in the signal's own bandwidth. This lets you compare modes, but only roughly. FT8 decodes down to about -20 dB, FT4 is a few dB less sensitive in exchange for shorter cycles, and WSPR goes to about -30 dB because it sends very slowly with a much narrower bandwidth. MSK144 is designed for meteor-scatter pings that last a fraction of a second, and Q65 is aimed at EME, tropo and ionospheric scatter. A lower threshold is not always "better"; it buys sensitivity at the cost of speed and message content.
Grid squares. FT8 and FT4 exchanges use a four-character Maidenhead locator (for example, two letters, two digits). Check that yours is entered correctly in settings, because a wrong grid pollutes PSK Reporter, logs and award tracking. A six-character locator gives you much better distance accuracy for weak-signal VHF work.
Questions for the group: What's your preferred way to keep the PC clock accurate? How do you decide between JS8Call, Winlink and a keyboard mode like PSK31 or Olivia when conditions are marginal? And does anyone still use Hellschreiber or RTTY regularly for anything other than contests?
Link to comment
https://www.hamradiobase.com/forums/topic/11347-clean-digital-mode-station-setup-audio-levels-cat-time-sync-and-what-decode-thresholds-really-tell-you/Share on other sites