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

Weak-signal digital station checklist: clock, audio levels, CAT, and what decode thresholds really tell you

ci_cover.jpg

Most digital-mode problems turn out to be one of four things: the clock, the audio level, the rig's mode settings, or CAT/PTT. The software (WSJT-X, fldigi, JS8Call, Winlink Express with VARA) gets blamed first, but it is usually the last thing at fault. This thread is meant as a working checklist, with room for disagreement on the details.

Start with the chain. The receiver audio goes through a sound card or the rig's built-in USB codec into the decoder. The transmit audio goes back out through the same path, and PTT is keyed by CAT, VOX, or a serial control line. If any link is wrong, you get the familiar symptoms: decodes that fall far short of what the mode should manage, splatter on the waterfall, or a rig that sticks in transmit.

The mode matters for how much each link is stressed. FT8 uses 15-second periods with a signal about 50 Hz wide. FT4 uses 7.5-second periods and about 80 Hz, so it is faster but needs a stronger signal and a tighter clock. JS8Call borrows FT8-style modulation for keyboard-style messaging, and its slower submodes trade time for sensitivity. WSPR is a beacon mode with 2-minute transmissions and a bandwidth of only a few hertz. Q65 and MSK144 are aimed at VHF and up: Q65 for EME and scatter paths, MSK144 for meteor pings. PSK31 and RTTY are older, narrow keyboard modes that still turn up in contests and on the calling frequencies. Olivia, MFSK and Hellschreiber, usually run through fldigi, are for noisy or fading HF paths where reliability matters more than speed.

On decode thresholds, the commonly quoted figures (around -21 dB for FT8, about -17 dB for FT4, and about -31 dB for WSPR) are referenced to a 2500 Hz noise bandwidth. They describe decoding on a clean, steady path with a properly set-up receiver. Fading, local noise, a drifting clock or an overdriven front end will all move the real threshold. SNR reports from different stations are also not a calibrated measurement, so treat them as relative.

Grid squares deserve a mention too. Maidenhead locators are the currency of FT8, WSPR and the VHF modes. A four-character grid such as FN31 covers 2 degrees of longitude by 1 degree of latitude. Six characters (FN31pr) narrow that to a subsquare. Check that the grid in your WSJT-X settings matches where you really are, because a wrong one corrupts your own spots and your distance and bearing calculations.

Where do you start when decodes are poor? And how do you handle several programs sharing one rig, say WSJT-X, a logger and fldigi, without fighting over the serial port?

  • Replies 2
  • Views 27
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Start with time, because it costs nothing to check. FT8 and FT4 decoders assume both ends transmit on the period boundary. The DT column in the decode window shows how far each received signal is from your clock. If most stations show a similar offset, the error is probably yours. If only one station is off, it is probably theirs. A PC that only syncs occasionally can drift by a second or more, and FT4's short periods make that worse. Run an NTP client set to sync frequently, or use a GPS-disciplined source if the machine will be offline in the field.

Next is receive audio. WSJT-X's documentation suggests setting the input so the receive level meter reads about 30 dB. Too low and you are working with quantization noise. Too high and strong signals clip and raise the noise floor for everyone else. Use the sound card's native 48 kHz, 16-bit format, and turn off any Windows or macOS audio enhancements. Also make sure system alert sounds do not go to the same device that feeds the transmitter, or one notification will end up on the air.

On transmit, set the rig to USB (or the DATA-USB mode if it has one), and turn off the speech processor, compression and any audio equalization. Then set the drive so ALC shows little or no movement. FT8 is close to a continuous carrier for most of each period, so run well under the rig's continuous rating. A clean 20 to 30 watts beats a splattering 100, and a waterfall with spurs beside your signal is the proof that it is overdriven. Keeping the audio tone in the middle of the passband, around 1500 Hz, also helps keep harmonics out of the rig's filtering, and WSJT-X's Split Operation setting (Rig or Fake It) can manage that for you.

For the shared-port problem, one serial port can usually only be opened by one program. The usual fixes are rigctld from Hamlib, flrig, or OmniRig on Windows, so the rig is controlled by one process and everything else talks to that. Check that the baud rate, stop bits and handshake in the program match the rig's menu. A mismatch often shows up as intermittent frequency readout rather than a clean failure.

  • Moderators

One caution on thresholds: sensitivity is not the only thing that decides which mode to use. A mode that decodes at -28 dB is no use if the exchange takes so long that the path closes, or if the other end cannot run it. FT8 became the default because it is fast and tolerant, and the cost is a rigid message structure. JS8Call gives you free-form text, heartbeats and relaying, but its slower submodes take noticeably longer per message, and the decodes are only as good as your clock and audio. WSPR is not for contacts at all. Its value is propagation data: transmit a beacon, then check the reports on wsprnet.org and see where you were heard.

For VHF and up, Q65 and MSK144 depend on matching the mode to the propagation. MSK144 works from short, fast bursts off meteor trails, so you need fast alternating periods and a patient operator. Q65 has submodes with different period lengths and tone spacings, and the letter at the end (A, B, C and so on) sets the tone spacing. Wider spacing tolerates the Doppler spread of EME and some scatter paths, at some cost in sensitivity. Choose the submode to match the path, not just the biggest number you can find.

For the fldigi modes, think of them as a trade-off between speed and bandwidth. PSK31 is narrow at about 31 Hz and easy on the rig, but it has no forward error correction and suffers on a fading path. RTTY at 45.45 baud with 170 Hz shift is simple and robust enough for contesting. MFSK and Olivia add error correction and interleaving, so they can hold up when a signal is going in and out of the noise, and the cost is slower typing and a wider signal. Hellschreiber is different: it paints the characters on the screen and your eye does the decoding, which can be readable when software decoders give up. It is mostly a curiosity, but a useful one.

Winlink is a different use case: message transfer through gateways rather than live chatting. VARA HF and VARA FM run on a sound card like the other modes. VARA is proprietary, and the unregistered version is rate-limited, so higher speeds need a license. Whatever the mode, listen before you transmit, and check your band plan and local rules, since the digital sub-bands and permitted bandwidths differ between countries.

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.