Building a clean digital chain: time sync, audio levels, CAT and choosing between FT8, JS8Call, WSPR, Olivia and the rest
- Replies 2
- Views 26
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Nancy 1 post
A lot of digital-mode problems that look like "the band is dead" or "my decodes are bad" come from the station chain rather than the propagation. This thread is for comparing notes on the whole path, from clock to sound card to CAT to mode choice, so the weak-signal modes can do what they are designed to do.
Start with time. FT8, FT4, WSPR, Q65 and MSK144 all depend on the sender and receiver agreeing on the clock. FT8 uses 15-second periods and FT4 uses 7.5-second periods. In WSJT-X the DT column shows the offset between your clock and the other station's timing. If most decodes sit consistently positive or negative by more than a few tenths of a second, suspect your PC clock before you suspect anyone else. A computer's default sync interval can be too loose, so many operators run a dedicated NTP client or a GPS-disciplined source. Check it by comparing a few strong stations: if they all show a similar DT, the offset is probably yours.
Audio levels matter more than power. Set Windows or Linux sound levels so the receive audio shows a healthy but not clipped level in WSJT-X (the guideline is roughly 30 dB on the meter, with room to spare). On transmit, use the Pwr slider and the radio's data mode so ALC barely moves. FT8 is a constant-envelope signal, so a rig run hard on a 100% duty cycle gets hot. Backing the output down well below the rated maximum is normal practice and keeps splatter off the band. Turn off speech processing, noise reduction and any audio EQ when the radio is in a data mode (USB-D/DATA).
CAT or not? CAT through Hamlib in WSJT-X, or the radio-specific driver in FLDIGI, saves you from retyping frequencies and lets the software handle PTT and split. Match the baud rate, data bits, stop bits and the CI-V address where applicable. If you see random PTT drops or errors only when transmitting, suspect RF getting back into the USB or audio lines. Ferrites on the cables, a decent common-mode choke on the feedline and a proper ground are the usual fixes. "Split" in WSJT-X (Rig or Fake It) keeps your audio tones in a comfortable part of the passband so harmonics from the sound chain stay out of the transmit signal.
Where do the modes fit? Rough comparison: FT8 decodes down to around -21 dB S/N in a 2500 Hz reference bandwidth, and FT4 is a bit less sensitive (roughly -17 dB) but faster. WSPR works much lower (about -31 dB) because it uses a two-minute period and a very narrow signal; it is a beacon mode, not for conversation. JS8Call uses FT8-style modulation with free-text messaging, and its speed submodes trade sensitivity against transmission time. PSK31 and RTTY are real-time keyboard modes that need a stronger signal than FT8 but let you converse. Olivia and MFSK modes in FLDIGI are designed for rough conditions, at the cost of slow throughput. Hellschreiber is more of a visual curiosity that can still get through when other modes fail, because you read the text with your eyes. Q65 and MSK144 are for specialist work: Q65 for EME and scatter paths, MSK144 for meteor-scatter pings on VHF.
Winlink is a different category: it is email over radio rather than a contact mode. Winlink Express can use VARA HF, VARA FM, ARDOP, packet and Pactor, depending on your hardware. The VARA modems are proprietary, with a free version that is speed-limited.
Which part of this chain gave you the most trouble: clock drift, RF feedback, audio levels, or CAT? And what mode do you actually pick when the band is noisy?
Link to comment
https://www.hamradiobase.com/forums/topic/11515-building-a-clean-digital-chain-time-sync-audio-levels-cat-and-choosing-between-ft8-js8call-wspr-olivia-and-the-rest/Share on other sites