Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Digital mode station checklist: audio levels, CAT, time sync and what decode thresholds actually tell you

ci_cover.jpg

Most digital mode problems trace back to the same few things: audio levels, rig control, clock accuracy, or a mismatch between the mode and the path. This thread is for comparing notes on those basics and on choosing a mode for the conditions, from FT8, FT4 and JS8Call to PSK31, RTTY, Olivia and Winlink.

First, the quoted decode thresholds. The usual figures are signal-to-noise ratios referenced to a 2500 Hz noise bandwidth, and they are approximate. For WSJT-X modes, FT8 is usually given as around -21 dB, FT4 around -17 dB, and WSPR around -31 dB. JS8Call uses FT8-derived modulation with selectable speeds, and the slower settings trade throughput for better sensitivity. Q65 and MSK144 are designed for harder paths: Q65 for EME, ionospheric scatter and tropo, MSK144 for meteor scatter bursts on VHF. A threshold is a best-case number for a stable signal at the right time offset and frequency. Fading, QRM, a drifting transmitter or a bad clock will cost you decodes well before the noise floor does.

Second, bandwidth and speed matter as much as sensitivity. FT8 occupies roughly 50 Hz and runs 15-second periods. FT4 is wider, at roughly 80 Hz, with 7.5-second periods, so it suits contest-style exchanges but gives up some sensitivity. PSK31 is narrow at about 31 Hz and is keyboard-to-keyboard, so a human has to read it, and it falls apart quickly when the signal is weak or the band is busy. RTTY at 45.45 baud and 170 Hz shift is still common in contests because it copes with a crowded band and is easy to run. Olivia and other MFSK modes in FLDIGI deliver text through poor conditions at very slow speeds. Hellschreiber is an odd one: it sends text as images, so you can often read it through noise that would defeat a conventional decoder.

Questions to start with:

1. How do you set transmit audio so there is no ALC action? Do you use the rig's USB codec or an external interface, and what steps did you take to keep RF out of the audio path?

2. For CAT control, do you key PTT through CAT, RTS/DTR, or a separate line, and how do you handle split operation so your audio stays in a clean part of the passband?

3. What do you use to keep the PC clock accurate, and how do you check it?

4. Which mode do you reach for first on a marginal path, and why?

  • Replies 2
  • Views 18
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On audio levels, the principle is that the digital signal should be clean before it ever reaches the final amplifier. These modes are mostly constant-envelope or at least tolerant of limited amplitude variation, but a transmitter driven into ALC compression or into nonlinearity splatters, and you get a wider signal than the mode was designed to produce. A reasonable procedure is to set the radio to a data or USB-D mode with speech processing and compression off, then raise the software's output level while watching ALC, and back it off until the ALC reads at or just above zero. Then set the power with the rig's power control, not the audio level. Several modes, FT8 included, work fine at low power, and a clean 20 W is better than a dirty 100 W.

On the receive side, aim for a moderate level and keep the audio from clipping. In WSJT-X the receive level meter is a rough guide, and the documentation suggests something in the middle of the scale rather than pinned at either end. Also turn off any operating-system sound effects, enhancements or automatic gain on the audio device. They can quietly change levels or add processing you do not want.

If you use a sound card interface with a separate audio path, galvanic isolation through transformers or an isolated USB interface can fix a lot of hum and RF feedback. Ferrite chokes on the USB and audio cables help too. If the software glitches or the PC drops its serial connection every time you key up, suspect RF getting into the cables before you suspect the software.

For CAT, Hamlib is the usual backend in WSJT-X and several other programs. Make sure the baud rate, data bits, stop bits and handshake settings match the radio's menu, and that no two programs are trying to open the same COM port at once. For split, WSJT-X offers a mode where the radio itself is set up in split so the audio tone stays in a clean range, rather than letting the dial move around. That avoids audio harmonics landing inside the radio's passband filtering.

  • Moderators

On time sync, FT8 and FT4 depend on all stations agreeing on the start of each period. WSJT-X shows the time offset, DT, for each decode, and consistently large positive or negative DT values across many stations usually mean your clock is off, not theirs. You can often decode with a clock a second or so out, but your sensitivity suffers and your own transmissions may not be decoded by others. On Windows, the built-in time service can drift between syncs, which is why people use a dedicated NTP client or a GPS-based source. On Linux, chrony or ntpd generally do a good job. If the station has no reliable internet, a GPS receiver with a PPS output is the accurate alternative. In all cases, check the offset against a trusted source, rather than assuming the PC is right.

Grid squares are the other piece people often leave for last. The Maidenhead locator is a letter-and-number code: two letters for the field, two digits for the square, and optionally two more letters for the subsquare. FT8 and similar modes normally exchange the four-character version, for example FN31, which is plenty for awards and for working out distance, but a six-character grid is more useful for VHF and weak signal work where squares matter. Make sure the grid in your software is the one for the operating location, particularly if you are portable, because wrong grids pollute reports and skew distance calculations.

For mode selection on a marginal path, one practical way to think about it is by what the path does. For steady but weak HF signals, FT8 or JS8Call at a slower speed is a good match. For long, patient reporting of propagation, WSPR gives you a map without anyone being at the keyboard. For meteor scatter, MSK144 is built for the short bursts. For EME or troposcatter, Q65 with an appropriate period length and tone spacing is the design target. For email over radio, Winlink can be run over several modems; VARA is widely used but is proprietary and has free and licensed versions with different speed limits, so check the current terms from the author. For casual chat on a quiet band, PSK31 or an MFSK mode in FLDIGI is still fine. For rough conditions where you want to hold a conversation, Olivia is worth trying. The mode that decodes at the lowest SNR is not always the best choice. If you need to exchange information quickly, speed and a clear exchange format count for more than a few dB.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.