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 setups: where do your decode problems really come from? (time sync, audio levels, CAT, and mode choice)

ci_cover.jpg

I'd like to compare notes on the chain between the antenna and the decoder. When a digital mode "doesn't work," the cause is usually not the mode. It is usually one link in the chain: clock error, a clipped audio path, a rig that drifts off frequency, or the wrong mode for the path.

Here is a framework to react to, then a few specific questions.

Time sync. FT8, FT4, WSPR, Q65 and MSK144 are all time-slotted. FT8 uses 15-second periods, FT4 uses 7.5 seconds, WSPR uses 2 minutes, and MSK144 uses 15-second sequences with very short bursts. The decoder reports DT, the offset between your clock and the transmitting station's. A consistent DT of a second or more in either direction means your clock or theirs is off. Windows' default sync interval can be long, so many operators run a dedicated NTP client or a GPS-disciplined source. Keep in mind that a DT shown in WSJT-X includes the other station's error too, so look at the average across many stations before blaming your own clock.

Audio levels. Weak-signal software is more sensitive to overdrive than to low drive. If the transmit audio is too high, the rig's ALC engages, the signal splatters and the effective power drops. A common rule for FT8 is to set the output so that ALC shows little or no movement, then reduce power at the rig rather than pushing the audio. On receive, the WSJT-X level meter should sit well inside the range rather than near the top. Check Windows or macOS audio settings for enhancements, AGC, or any sample-rate conversion that you didn't ask for. 48 kHz, 16-bit is a normal target.

CAT and PTT. CAT lets the software read and set frequency and mode, and optionally key the radio. Common PTT choices are CAT command, RTS/DTR on a serial port, or VOX. VOX works but it can trip on stray audio such as system sounds. For frequency control, WSJT-X's "Split Operation" options (Rig or Fake It) exist to keep the audio tones in the best part of the passband and avoid harmonics from high audio frequencies.

Decode thresholds. The usual numbers quoted for WSJT-X are signal-to-noise ratios referenced to a 2500 Hz noise bandwidth. FT8 decodes down to roughly -20 dB, FT4 is a few dB less sensitive, and WSPR reaches about -30 dB because it trades a 2-minute period for sensitivity. JS8Call is built on FT8-like modulation and offers several speeds, and the slower ones gain a few dB of sensitivity. Treat all these numbers as approximate, because real decode performance depends on fading, QRM, the DT error and the audio passband. Also, S/N reports from different software are not always calibrated the same way, so don't over-read a 2 dB difference.

Mode choice. I think this is the part most often done by habit. FT8 and FT4 are for fast, structured exchanges of call, grid and report. JS8Call is for keyboard-like messaging, relaying and heartbeats with weak signals. PSK31 and RTTY are lower-sensitivity but interactive, and RTTY remains common in contests. Olivia and other MFSK modes are for ragchewing under bad conditions. Hellschreiber is a visual mode, which makes it a different experience. Winlink with VARA, ARDOP or Pactor is about moving email-like messages, and the key concern there is how fast and reliable the link is on your path, not just whether it can decode. VARA is proprietary, and its speed depends on its licensing. Q65 is designed for very weak, fading paths such as EME and ionospheric scatter, and MSK144 is for meteor scatter on VHF.

Grid squares. Maidenhead locators matter because FT8, FT4, WSPR and others carry them in the message. A 4-character grid like FN31 is enough for most FT8 work. A 6-character grid is more precise. If your grid is wrong in the software, your spots and distance calculations will be wrong too, and it is a quick thing to check.

My questions: What is your first check when a station can see you on PSKReporter or WSPRnet but you can't work them? Do you run a separate sync tool or trust the OS? And for those using a sound-card interface, do you prefer a USB codec built into the rig or an external isolated interface?

  • Replies 2
  • Views 39
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd separate "they hear me" from "I hear them," because the two failures point to different parts of the chain. If a spotting network shows you being received but you decode nothing, look at the receive side: audio level, a wrong sound device selected after a USB re-enumeration, or a clock that is off. If you decode fine but nobody replies, check transmit: ALC, a mismatched split setting, or a rig that is changing its own bandwidth or processing in data mode.

One thing that is easy to miss is rig settings that are fine for SSB but wrong for data. Speech compression, noise reduction, and narrow DSP filters can all change how a digital signal looks. Many operators use the rig's data mode (USB-D or similar) with processing turned off and a wide enough filter that the whole decode window passes through. Also, make sure the TX audio is not being altered by a driver feature on the computer.

For clock checks, the DT column is more useful than people think. If every station you decode is showing around the same DT offset, that is your clock. If only one station is off, it is theirs.

  • Moderators

On sound-card interfaces, I'd say the main choice is between a rig's built-in USB audio and an external interface, and both can work. Built-in USB is simpler, with fewer cables and fewer ground loops, but you depend on the rig's firmware and drivers. An external interface with isolation transformers gives you more control over levels and can help with RF in the shack, but it adds more places to set the wrong level. If you get hum, buzz or random PTT keying, look at common-mode RF and grounding first. Ferrites on USB and audio cables are a reasonable step before replacing anything.

On Winlink, I'd add that choosing the mode depends on the band and the gateway as much as the software. VARA HF, ARDOP and Pactor have different strengths and costs, and gateway availability changes over time, so check a current gateway list instead of assuming one exists near you. Also confirm that your CAT and PTT work reliably in the Winlink software before going on air, because a link that keys and unkeys on the wrong cycle wastes everyone's time.

For the weak-signal modes, I'd add one more thing: use a quiet receive environment. Many decode problems are really local noise, and a mode with a -20 dB threshold gains nothing if your own noise floor is 10 dB higher than it should be.

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.