Getting digital modes right: time sync, audio levels, CAT and what the decode thresholds actually mean
- Replies 2
- Views 39
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Lee 1 post
-
Mod_Chrissy 1 post
Most trouble with FT8, FT4, JS8Call, WSPR, PSK31 and RTTY comes from the same few setup issues, not from the software. This thread is for sorting out the common ones in one place and comparing how different modes behave when signals get weak.
Start with time. FT8, FT4, WSPR, Q65 and MSK144 all depend on the computer clock. FT8 uses 15-second periods, FT4 uses 7.5 seconds, and WSPR uses 2 minutes. If your clock is off by more than a fraction of a second, decodes drop even when the signal is strong. Watch the DT column in WSJT-X. If most stations show a consistent offset, the error is probably in your clock, not theirs. A proper NTP client or a GPS-based source is more reliable than relying on a default OS sync that may only update occasionally. PSK31, RTTY and Olivia in FLDIGI are far less picky, because they are not slotted by the clock.
Then the audio chain. Whether you use a USB codec in the radio or an external sound card interface, the principle is the same. Set the sample rate and format in the OS (48 kHz, 16-bit is a safe choice), turn off any audio enhancements, and keep system sounds from leaking into the transmit path. In WSJT-X, set the receive level so the meter sits around the middle of its range. On transmit, use the Pwr slider and the radio's own settings to get the output you want, and keep ALC action at the minimum or zero. A digital signal that is overdriven spreads splatter beyond its narrow occupied bandwidth and gets nothing back in decodes. Power does not need to be high. Many FT8 contacts are made at modest power, and an overdriven rig can be worse than a clean 20 W.
CAT and PTT. CAT through Hamlib or a direct rig-control option lets the software read and set frequency and mode. Use a data mode such as USB-D or DATA-USB, and turn off speech processing, compression and aggressive noise reduction. For PTT you can use CAT, serial RTS/DTR, or VOX. VOX is the most likely to cause trouble because stray sounds can key the transmitter. In WSJT-X, the Split Operation setting (Rig or Fake It) keeps the audio tones within a clean part of the passband rather than pushing harmonics through the radio's filtering.
About those decode numbers. Published thresholds are usually quoted as signal-to-noise ratio in a 2500 Hz reference bandwidth. They are roughly -21 dB for FT8, around -17 dB for FT4 and about -31 dB for WSPR. A -20 dB report is therefore not comparable to an S-meter reading, and a decoded signal can be completely inaudible. Real conditions such as fading, Doppler spread and local noise move these numbers around, so treat them as approximate benchmarks, not guarantees.
Choosing a mode. FT8 is the usual choice for fast weak-signal contacts on HF and 6 m. FT4 trades some sensitivity for speed and is aimed at contest-style exchanges. JS8Call uses FT8-style modulation but adds free-form keyboard messaging, relaying and directed messages, which suits low-power and emergency-communication experiments, with slower exchanges. Q65 has sub-modes with different period lengths and tone spacings, and it is commonly used on VHF and above for tropo, scatter and EME. MSK144 is built for meteor scatter, where the useful signal can be a short burst. WSPR is a beacon mode and is best for testing propagation and antennas, not for conversation. PSK31 and RTTY are older, simpler modes that are still active and easy to decode by eye. Olivia and MFSK in FLDIGI trade speed for robustness. Hellschreiber is interesting because you read the text visually and the human eye can sometimes pick it out of noise.
Grid squares. Maidenhead locators are the standard for these modes. A four-character grid like FN31 is a field-and-square pair, and a six-character one adds a subsquare, giving finer detail. Many weak-signal operators use four characters for casual FT8 and six for VHF work or when distance matters. Make sure the locator in your software matches your real location, since spotting sites and award tracking depend on it.
What are the setup problems you see most often, and which modes do you think are underused? Feel free to post your interface choices, software versions and the band conditions where a mode has been a good fit.
Link to comment
https://www.hamradiobase.com/forums/topic/10895-getting-digital-modes-right-time-sync-audio-levels-cat-and-what-the-decode-thresholds-actually-mean/Share on other sites