Weak-signal digital setups: where do your decode problems really come from? (time sync, audio levels, CAT, and mode choice)
- Replies 2
- Views 39
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
I'd like to compare notes on the chain between the antenna and the decoder. When a digital mode "doesn't work," the cause is usually not the mode. It is usually one link in the chain: clock error, a clipped audio path, a rig that drifts off frequency, or the wrong mode for the path.
Here is a framework to react to, then a few specific questions.
Time sync. FT8, FT4, WSPR, Q65 and MSK144 are all time-slotted. FT8 uses 15-second periods, FT4 uses 7.5 seconds, WSPR uses 2 minutes, and MSK144 uses 15-second sequences with very short bursts. The decoder reports DT, the offset between your clock and the transmitting station's. A consistent DT of a second or more in either direction means your clock or theirs is off. Windows' default sync interval can be long, so many operators run a dedicated NTP client or a GPS-disciplined source. Keep in mind that a DT shown in WSJT-X includes the other station's error too, so look at the average across many stations before blaming your own clock.
Audio levels. Weak-signal software is more sensitive to overdrive than to low drive. If the transmit audio is too high, the rig's ALC engages, the signal splatters and the effective power drops. A common rule for FT8 is to set the output so that ALC shows little or no movement, then reduce power at the rig rather than pushing the audio. On receive, the WSJT-X level meter should sit well inside the range rather than near the top. Check Windows or macOS audio settings for enhancements, AGC, or any sample-rate conversion that you didn't ask for. 48 kHz, 16-bit is a normal target.
CAT and PTT. CAT lets the software read and set frequency and mode, and optionally key the radio. Common PTT choices are CAT command, RTS/DTR on a serial port, or VOX. VOX works but it can trip on stray audio such as system sounds. For frequency control, WSJT-X's "Split Operation" options (Rig or Fake It) exist to keep the audio tones in the best part of the passband and avoid harmonics from high audio frequencies.
Decode thresholds. The usual numbers quoted for WSJT-X are signal-to-noise ratios referenced to a 2500 Hz noise bandwidth. FT8 decodes down to roughly -20 dB, FT4 is a few dB less sensitive, and WSPR reaches about -30 dB because it trades a 2-minute period for sensitivity. JS8Call is built on FT8-like modulation and offers several speeds, and the slower ones gain a few dB of sensitivity. Treat all these numbers as approximate, because real decode performance depends on fading, QRM, the DT error and the audio passband. Also, S/N reports from different software are not always calibrated the same way, so don't over-read a 2 dB difference.
Mode choice. I think this is the part most often done by habit. FT8 and FT4 are for fast, structured exchanges of call, grid and report. JS8Call is for keyboard-like messaging, relaying and heartbeats with weak signals. PSK31 and RTTY are lower-sensitivity but interactive, and RTTY remains common in contests. Olivia and other MFSK modes are for ragchewing under bad conditions. Hellschreiber is a visual mode, which makes it a different experience. Winlink with VARA, ARDOP or Pactor is about moving email-like messages, and the key concern there is how fast and reliable the link is on your path, not just whether it can decode. VARA is proprietary, and its speed depends on its licensing. Q65 is designed for very weak, fading paths such as EME and ionospheric scatter, and MSK144 is for meteor scatter on VHF.
Grid squares. Maidenhead locators matter because FT8, FT4, WSPR and others carry them in the message. A 4-character grid like FN31 is enough for most FT8 work. A 6-character grid is more precise. If your grid is wrong in the software, your spots and distance calculations will be wrong too, and it is a quick thing to check.
My questions: What is your first check when a station can see you on PSKReporter or WSPRnet but you can't work them? Do you run a separate sync tool or trust the OS? And for those using a sound-card interface, do you prefer a USB codec built into the rig or an external isolated interface?
Link to comment
https://www.hamradiobase.com/forums/topic/11608-weak-signal-digital-setups-where-do-your-decode-problems-really-come-from-time-sync-audio-levels-cat-and-mode-choice/Share on other sites