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 troubleshooting: how do you sort out time sync, audio levels and CAT before blaming the band?

ci_cover.jpg

A lot of "the band is dead" or "my decodes are poor" threads turn out to be station problems rather than propagation. This thread is for sorting out the usual suspects in a sensible order, across FT8, FT4, WSPR, JS8Call, Q65 and MSK144, and the keyboard modes like PSK31, RTTY, Olivia and MFSK in FLDIGI.

Start with the clock. FT8, FT4, WSPR, Q65 and MSK144 all work in fixed time slots. FT8 uses 15 second periods, FT4 uses 7.5 seconds, and WSPR uses 2 minute periods starting on even minutes. WSJT-X shows the time offset (DT) of each decoded signal. If most stations show a consistent DT of, say, +0.7 or -0.8 seconds, the offset is probably in your PC clock rather than in all of them. A DT close to zero for the average station is the goal. Windows does not always sync often enough by default, so a dedicated NTP or similar sync tool, or a GPS-based source, is a common fix. On a field laptop with no internet, a GPS puck or a phone hotspot for sync is worth setting up before you leave.

Next is audio level. The common mistake is driving the rig too hard. Digital modes are generally constant-envelope or close to it, but an overdriven audio chain produces splatter and a dirty signal, and it often shows up as ALC action on the radio. Set the transmit audio so the ALC barely moves, then raise or lower output power at the radio rather than pushing audio. On receive, WSJT-X suggests keeping the input level somewhere around the middle of its meter range, not pinned. Also check that the PC is not applying audio enhancements, system sounds, or sample-rate conversion to the interface. A 48 kHz, 16-bit setup is the usual baseline.

For CAT control, WSJT-X can use Hamlib, and the choices that matter are the rig model, serial port, baud rate, PTT method (CAT, RTS/DTR or VOX), and split operation. Using "Rig" for split is generally cleaner than "Fake It" because the radio holds the audio tones in a better part of its passband, which reduces harmonic problems. If the radio has a built-in USB codec, you may get both CAT and audio on one cable, but check that the PC is not sharing the serial lines with other programs such as logging or a keyer.

Common questions to start with: what is your exact interface (built-in USB codec, external box, or isolated sound card interface), and what shows up on the waterfall when you transmit into a dummy load? A clean tone set on the waterfall with no extra images or wide sidebands is a good sign. Also useful to know: does the decode list improve if you narrow the receive filter, and what is your reported SNR on PSKReporter or WSPRnet compared with nearby stations?

For comparison, the modes differ a lot in what they can do. FT8 has a decode threshold of around -21 dB SNR (in a 2500 Hz reference bandwidth) and a bandwidth of about 50 Hz. FT4 is faster but needs a stronger signal, with a threshold in the neighborhood of -17 dB. WSPR can decode much weaker signals, around -31 dB, but it is beacon-only and not designed for QSOs. JS8Call is built on FT8-style modulation but adds free text and a message relay, at the cost of slower exchanges and variable speeds. Q65 is aimed at difficult paths like EME, scatter, and some terrestrial work with longer periods, and MSK144 is designed for meteor scatter, usually on 6 m and 2 m. PSK31 and RTTY are far less sensitive than those weak-signal modes, but they are simple, widely supported, and good for casual chats and contests.

What is your first check when decodes look wrong: clock, levels, or CAT?

  • Replies 2
  • Views 10
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd add the grid square to the checklist, because a wrong locator quietly makes your spots less useful. A Maidenhead locator has a field (two letters), square (two digits), and subsquare (two more letters), for example FN31pr. FT8 and FT4 normally exchange only the four-character version, like FN31, but WSPR can send a six-character locator in some configurations, and a few weak-signal activities care about it, so check your settings. If you operate portable, update the locator in WSJT-X or you will show up in the wrong place on PSKReporter and WSPRnet.

On time sync: don't rely on a laptop that has been asleep or off the network for weeks. Sync before operating, then check that DT values in the decode window look reasonable. If your own DT looks off but others look fine, your clock is likely the culprit. If they all drift together, something in the decoding path is lagging, such as a slow audio device.

Also separate transmit and receive problems when you diagnose. Seeing lots of decodes yet no replies often points to a transmit issue, such as low power, a poor audio tone set, or a mismatched split setting. Few decodes with a strong band is more likely receive-side: antenna, noise, or levels.

  • Moderators

For the keyboard modes and Winlink side, the failure points are a bit different, though the clock and audio issues overlap. In FLDIGI, PSK31 and RTTY are tolerant of a little timing error because they are not slotted modes, but they are still affected by overdriven audio and bad tuning. Olivia, MFSK and Hellschreiber suit different jobs: Olivia and the slower MFSK variants are designed to survive poor conditions and QRM at the expense of speed, while Hellschreiber is a visual mode where the "text" is displayed as an image and is surprisingly readable in some noise. Pick them for the path, not for novelty.

Winlink is more of an email system over radio than a chat mode. With Winlink Express you pick a connection type such as VARA HF, VARA FM, ARDOP, Pactor or packet, and a station that offers the matching gateway. VARA is proprietary, and some speed levels need a registered license. The gateway, frequency, and mode matter more than your own audio setup in many failed attempts, so check that the station you want is actually listening on that band and has a reasonable path to you before you start retrying.

One practical point on interfaces: a sound card interface with isolation and good cabling (and ferrites on the USB and audio leads) can remove a lot of hum, RF in the audio, and ground-loop noise. If your decode count drops whenever you transmit, or the PC glitches during a key-down, RF getting into the shack wiring is a likely cause, and it is worth checking before anything else.

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.