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 412.9 km/s
Aurora 1
Updated 14:00 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

Getting a clean digital-mode chain: sound card levels, CAT, time sync and what decode thresholds actually mean

ci_cover.jpg

Starting a thread to collect the practical details that cause most digital-mode problems. The modes are different, but the failure points are mostly the same: audio levels, rig control, clock accuracy and a misunderstanding of what a published decode threshold promises.

The signal chain. For WSJT-X, FLDIGI and the Winlink clients, the path is radio, audio interface, sound card, software, then back out through the same interface to the transmitter. Most problems sit in one of three places. The rig is in the wrong mode (USB or a data mode, not FM or AM, with compression, EQ and noise reduction off). The operating system is processing the audio (disable enhancements, AGC and system sounds on the interface). Or the transmit drive is too high. For FT8, FT4 and other WSJT-X modes, the usual rule is to set the drive so the ALC barely moves, even if that means less than full power. Overdriven audio splatters across the band, which is much more noticeable on a crowded FT8 segment than it would be on a single PSK31 signal.

CAT versus VOX versus serial PTT. CAT control gives the software frequency readout and PTT through the radio's USB or serial port, and it enables WSJT-X's Split Operation options. If audio is clean but the radio sits at 1500 Hz offsets with harmonics showing up, try 'Fake It' split so the audio tones stay in a comfortable part of the passband. VOX is a last resort because it can clip the first symbols and trigger on stray audio. RTS/DTR PTT works but can cause a transmit glitch when the serial port opens, so check what the radio does when the program starts.

Time sync. FT8, FT4, WSPR, Q65 and MSK144 all depend on a shared clock. FT8 works in 15-second periods, FT4 in 7.5 seconds, and WSPR in 2-minute slots. The software can tolerate roughly a second of error in FT8, but the tolerance is narrower the shorter the period. Watch the DT column in the decodes. If most stations show a consistent offset, your computer clock is probably the one that is off. Use NTP or a GPS-based source and confirm the sync service is actually running, since a system that was right yesterday can drift after sleep or a lapsed sync service. JS8Call has extra timing slack because of how its submodes are laid out, but it is not immune.

Decode thresholds. The usual figures are quoted as signal-to-noise ratio in a 2500 Hz reference bandwidth, not in the bandwidth of the signal itself. Roughly, FT8 decodes near -20 dB, FT4 a few dB higher (around -17), and WSPR much lower, near -30 dB, because its transmissions are long and slow. Q65 is designed for weak-signal paths such as EME and scatter, and its performance depends on the chosen submode and period length. MSK144 is designed for meteor-scatter pings, so it trades long integration for speed. These numbers are sensitivity under ideal conditions with a good clock and a clean receiver. They do not account for QRM, local noise, fading or a poorly set AGC. A 'report' of -18 on FT8 is a measurement by the decoder, not a promise that the QSO will complete.

Comparing the older and keyboard modes. PSK31 is narrow, at about 31 Hz for BPSK31, and works well for casual keyboard QSOs, but it is not a weak-signal mode in the way FT8 is. RTTY (commonly 45.45 baud, 170 Hz shift) is the contest standard, and contest software leans heavily on it. Olivia and other MFSK-family modes (Olivia, MFSK16 and similar) are built to work through noise and fading with forward error correction, at the cost of slow typing speed. Hellschreiber displays the signal visually instead of decoding it, which makes it a different kind of experiment. JS8Call is derived from FT8 but is aimed at keyboard-style messaging, with selectable speeds, heartbeat and relay features.

Winlink and VARA. Winlink is an email-over-radio system. It can use HF or VHF/UHF links and several transport modes, including VARA, ARDOP, Pactor and packet. VARA is a proprietary modem with its own licence terms, so check the current options before you assume it is free to run at full speed. The practical issue is the same as everywhere else: the TNC audio levels and the PTT method. If a Winlink session connects but fails on larger transfers, look at audio drive and the compression the radio applies before blaming the gateway.

Grid squares. Maidenhead locators use letters and digits, such as FN31 (four characters) or FN31pr (six). WSJT-X exchanges four-character grids in most standard messages. A mistyped grid ruins distance and award tracking, so verify yours against a map or a locator calculator, and check the rig or logger is not using an old value.

Which of these do you find harder to pin down: audio levels, CAT setup or the clock? And does anyone have a checklist for confirming a chain is clean before calling CQ?

  • Replies 2
  • Views 28
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

A useful check that costs nothing: transmit into a dummy load, or use a second receiver nearby, and look at your own signal on a waterfall. A clean FT8 signal looks like a tidy cluster of eight tones with nothing around it. If you see a wider smear or extra lines at regular spacing, the audio drive is too high or the radio's processing is on. That is easier to see than a power meter reading, and you can fix it without annoying anyone on the band.

On the clock, it is worth separating two problems. One is an offset, where your computer is a second or so off true time. The other is jitter, where the offset moves around. NTP over a poor network can be fine on average and still wander, which is why a GPS source or a well-configured local time service is a common recommendation for anyone running FT4 or the fast JS8Call submodes. In WSJT-X the DT column is the quickest way to see which of those you have.

On thresholds, the caveat bears repeating. The decoder may pull out a trace at -21 dB, but that tells you nothing about the other station hearing you. FT8 only reports the SNR measured at your end, so the two directions of a path can be very different, especially with local noise at one end.

  • Moderators

On the mode comparison, a rough way to choose is by what you want from the contact. If the goal is a confirmed exchange of callsign, grid and report with the least effort, FT8 and FT4 are the obvious choice, and FT4 suits contesting because the shorter period gives more exchanges per hour. WSPR is a different activity. It is a beacon mode, so you transmit and then check reception reports on a map or database, which makes it a good tool for testing an antenna or a band without needing anyone to reply. For real conversation, PSK31, Olivia or JS8Call are options, and JS8Call fits better when you want a store-and-forward style of message passing at low power.

One CAT note: some radios need the USB audio device and the USB serial port to be configured in two separate places, and operating systems can renumber the ports after an update or when a different USB port is used. If the rig suddenly stops keying, check the port assignment before you start changing audio settings.

For Hellschreiber and Olivia, the soundcard setup is the same as for the others, but the way you judge success is different. With Hell you read the text from the display, so a slightly off-frequency signal can still be readable. With Olivia, the chosen tone count and bandwidth must match on both ends, otherwise nothing decodes at all. Agree on the settings first, then call.

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.