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

Why do my digital-mode signals decode on some stations but not others? Checking audio, timing, CAT and mode choice

ci_cover.jpg

A lot of digital-mode problems look like propagation problems. A weak-signal mode can only reach its decode threshold if the signal is clean, correctly timed and sent at the right level. This thread is a place to compare notes on the chain from the antenna to the decoder and to decide which mode suits the path.

1. Decode thresholds are not the same as usable QSO thresholds. Published figures are signal-to-noise ratios referenced to a 2500 Hz noise bandwidth. They are approximate and depend on fading, QRM and the decoder. Rough orders of magnitude: FT8 decodes down to about -20 dB, FT4 needs a few dB more, and WSPR goes down to about -30 dB because it uses a 2-minute transmission and carries very little information. Q65 has several sub-modes, with T/R periods from 15 seconds to 5 minutes. Longer periods improve sensitivity but also add fading and Doppler considerations. MSK144 is built for meteor-scatter pings, which may last a fraction of a second. PSK31, RTTY and Olivia usually need a signal you can see on the waterfall, though Olivia and other MFSK modes can work in poorer conditions at the cost of speed.

2. Time sync. FT8, FT4, WSPR, Q65 and MSK144 all depend on accurate clocks. In WSJT-X, a consistent DT (time offset) in the decode window is a quick check. If most stations show similar DT values that are not near zero, your own clock is probably off. Check this before changing anything else. A Windows machine that has not synced for a while, or a laptop that has been asleep, can drift enough to hurt decodes. Use NTP, a GPS-fed time source or a dedicated sync utility, and check that the sync service is actually running. Mode timing tolerance is fairly tight, but it is not a precise-to-the-millisecond problem. A second or so of error is a problem, though.

3. Audio levels and the sound card path. For WSJT-X, avoid overdriving the transmitter. Keep the audio level low enough that ALC shows little or no movement, and treat the Pwr slider in WSJT-X as a power control only if it is the only control you are using. Overdrive produces splatter and spurious products, and the first signs are often other stations complaining about wide signals rather than your own decodes failing. On the receive side, the input level should sit around the middle of the meter range, not pinned. Make sure the OS is not applying audio enhancements, automatic gain or sample-rate conversion on the device you use for the radio. A good 48 kHz sample-rate setup avoids many odd problems. Isolation transformers and ferrites on the USB and audio leads can cut RF feedback and ground-loop hum.

4. CAT control. Rig control gives you frequency readback and, with the right settings, PTT and split operation. Use the correct baud rate and the same data and stop bits as the radio menu. If the rig changes the audio passband in data mode, the waterfall may look different from what you expect. In WSJT-X, use Split Operation (Rig or Fake It) so that the audio tones stay in a clean part of the transmit passband, usually around 1500 Hz or in the area your rig filters cleanly. A frequently reported problem is CAT polling clashing with another program using the same COM port. Only one program can open the port at a time unless a virtual port splitter is in use.

5. Grid squares. Maidenhead locators are used for logs, awards and weak-signal exchange. Four characters, such as FN31, identify a grid square. Six characters add a subsquare for finer position. Use at least the four-character locator in FT8 and similar modes and make sure your own locator is correct in the settings. A wrong grid makes distance calculations and spotting data misleading, and in contests it can cause scoring issues.

6. Picking the mode for the job. FT8 and FT4 are structured and automated and are good for fast contacts on crowded bands. JS8Call is based on the FT8 modulation family but supports free-text messaging, relays and heartbeat-style presence, at the cost of slower exchanges. PSK31 and RTTY are keyboard modes that let you watch a conversation in real time and are common on HF. Olivia, MFSK variants and Hellschreiber are less often used but each has niches: Olivia for robust text in poor conditions, Hellschreiber for decoding visually, even through noise. Winlink with VARA, ARDOP or Pactor-style modes is a message transport rather than a casual chat mode, and it has different configuration (gateway selection, CMS/RMS, bandwidth) from the WSJT-X family. VARA is proprietary software, so check the licence terms and the gateway's supported modes before relying on it.

Questions for discussion: What do you check first when decodes drop off? Do you watch the DT column, the ALC meter or the PSK Reporter map? And which mode do you pick for the same band at different times of day?

  • Replies 2
  • Views 26
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

My order of checks would be time, then audio, then the radio. If the clock is off, nothing else matters. In WSJT-X, the DT column gives away a bad clock quickly. If everyone is around +0.5 and your own transmissions look odd to others, sync first.

On audio, I would add that the level is not the same thing as the signal quality. A transmit audio level that is acceptable to the sound card meter can still drive the rig into ALC if the radio's data input gain is high. The ALC reading should show little or no deflection, and if the rig has a compression or processing setting, it should be off for digital modes. Also check the rig is in a data or USB-D mode and that the transmit bandwidth is wide enough but not wider than needed. Some rigs have narrow filters by default that clip the upper audio region.

One further tip for new operators: keep the audio frequency of your transmission away from the edges of the passband. 1000 to 2000 Hz is a safe range for most radios, though a given rig may be flatter or less flat than that.

  • Moderators

On mode selection, the key distinction is between modes designed for a fixed exchange and modes designed for conversation. FT8, FT4, WSPR and MSK144 all use synchronized slots and a strict message format. That is why they are so sensitive. PSK31 and RTTY are continuous-stream modes, so there is no sync requirement and no fixed message structure. Fldigi also lets you switch between PSK, RTTY, Olivia, MFSK and Hellschreiber without changing the radio setup, so it is a good tool for trying them on the same audio path.

For weak-signal work, WSPR is more of a propagation tool than a QSO mode. Transmit-only beacons and receive-only spotting let you see where your signal is heard without needing a partner. That can tell you whether the antenna is working before you spend time on a contact mode. For VHF and above, Q65 and MSK144 are worth reading about because they target specific propagation mechanisms (EME, tropospheric scatter, meteor scatter), and the settings, such as T/R period and sub-mode, matter much more than for FT8.

For Winlink, remember that it is a different workflow. You need a callsign registered with the system, a station configured with the correct gateway, and a decent understanding of how to pick a frequency and listen first to avoid interfering with an existing connection.

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.