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

Digital mode setup baseline: time sync, audio levels, CAT, and what decode thresholds actually tell you

ci_cover.jpg

Most digital-mode problems come from the same few things: clock error, bad audio levels, or a CAT/PTT mismatch. They are rarely a matter of the mode itself. This thread is meant as a practical reference. Add corrections or other approaches below.

1. Time sync comes first for the synchronized modes. FT8 (15 s periods), FT4 (7.5 s), WSPR (2 min), Q65 and MSK144 all depend on both stations agreeing on the clock. In WSJT-X, watch the DT column. Values that are consistently near zero are good. A steady offset of a second or more usually means your PC clock is off, not that the band is odd. Windows' default time service can drift between syncs, so many operators use a dedicated NTP client or a GPS-disciplined source. On Linux, chrony or ntpd do the job. A sync tool is only useful if you check that it actually updates.

2. Audio levels: less is usually more. For FT8 and similar modes, use USB or USB-Data, switch off speech processing and compression, and set the transmit audio so the ALC barely moves or does not move at all. Drive the rig with a high-level signal and the result is a splattery, distorted signal and a wider footprint than the mode needs. Power output is set by the rig's power control and audio level together, so it is worth lowering the audio before turning down the power. On receive, WSJT-X's level meter should sit in a moderate range, roughly the middle of the scale, not pinned at the top or buried at the bottom.

3. Sound card interfaces and ground loops. A USB codec built into the radio is the simplest route. External interfaces such as SignaLink-style units, or homemade boxes with 1:1 audio isolation transformers, help break ground loops if you hear buzz, hum, or RF feedback. Ferrites on USB and audio leads and a sensible RF ground are worth the effort. If the PC audio device changes names after a reboot or a USB reshuffle, re-check the input and output selections in WSJT-X or FLDIGI. The wrong device is a common source of 'no decodes' reports.

4. CAT control and PTT. Hamlib-based control in WSJT-X, or rig control in FLDIGI, needs matching serial speed, data bits, stop bits and handshake settings. If the rig has a CAT PTT command, that is usually the cleanest option. RTS/DTR keying or VOX are alternatives, but VOX can key on stray PC sounds. In WSJT-X, the 'Split Operation' settings (Rig or Fake It) help keep the audio tones in a mid-passband range, which avoids driving the rig's audio chain at extreme frequencies and reduces harmonic problems.

5. What decode thresholds mean. Published figures are normally given in a 2500 Hz reference noise bandwidth. Approximate WSJT-X-family numbers are around -21 dB for FT8, around -17 dB for FT4, and around -31 dB for WSPR. They describe what a decoder can recover under ideal conditions with a stable signal, correct timing and no heavy QRM. Fading, drift, a bad DT, a crowded passband and local noise all move the practical limit. A decoder showing -24 on one signal does not make that a number you can rely on every cycle.

6. Choosing a mode. FT8 is the efficient choice for weak, scheduled contacts. FT4 trades some sensitivity for faster exchanges, so it suits contests. WSPR is a propagation beacon mode, not a QSO mode. JS8Call uses FT8-style modulation but adds free text, directed messages and relayed or store-and-forward messaging, at the cost of slower exchanges. Q65 was designed for hard paths such as EME and some scatter propagation, with different submodes and period lengths to match the path. MSK144 is designed for meteor-scatter bursts, mostly on VHF during showers.

7. The older keyboard modes. PSK31 is narrow and efficient for casual chat but sensitive to overdrive and multipath. RTTY with 45.45 baud and 170 Hz shift is still common in contests. Olivia and MFSK variants use forward error correction and a slow pace to get text through poor conditions. Hellschreiber is different again, because you read it visually, which makes it forgiving of some interference patterns. FLDIGI handles all of these in one program.

8. Winlink and VARA. Winlink is a messaging system and not a conversation mode. Winlink Express can use several transports, including packet, ARDOP and VARA. VARA HF and VARA FM are proprietary modems. Check the licensing terms and speed limits for the version you use, and follow the correct frequency and gateway practices for your area. Be sure the channel is clear before you connect.

9. Grid squares. Maidenhead locators go from two letters (field), to two digits (square), to two letters (subsquare). FN31 is a four-character grid and FN31pr is a six-character one. FT8 and WSPR normally send only four characters, so distance and bearing calculations from those will be coarse. If you are chasing grids for an award or a VHF contest, check the rules for how many characters are required and what you must log.

Where do you see people go wrong most often, and which checks do you run first when a setup stops decoding?

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One check I'd add to the list is to look at the waterfall before blaming the decoder. If the noise floor looks uneven, with a strong slope or stripes, you may have receiver AGC or a noise blanker interacting with the signal. A noise blanker on a rig can distort narrow digital tones, so it is worth switching it off to see if decodes improve. The same goes for aggressive DSP noise reduction. Many rigs apply it before the audio reaches the USB codec, and it can smear weak tones that the decoder would otherwise recover.

On time sync, the DT column is also a good indicator of the other station's clock. If many stations on a band show a similar offset, the issue may be yours. If only one shows a large offset, it is probably theirs. When replying to a station with a large DT, the decoder may still handle it, but that does not mean the other side is hearing you correctly.

  • Administrators

On the question of thresholds, I'd stress one practical point: the dB figure in the decode list is a signal-to-noise estimate in a 2500 Hz reference bandwidth. It is not the S-meter and does not map directly to it. A signal can decode at a very low number while your S-meter does not move, because the S-meter reflects total power in the receive filter and the decoder works on a narrow tone pattern.

For interface setup, a quick sanity test is to transmit into a dummy load, check the output on a wattmeter and confirm the ALC is not moving. Then lower the audio gain until the power just begins to drop, and back off slightly from that point. After that, check your own signal on a remote receiver, such as a web SDR or the PSK Reporter map for your callsign, and see whether other stations are reporting a clean decode. If the reports vary a lot from one cycle to the next, look at timing, power supply sag, or RF in the shack before changing software settings.

For Winlink and VARA, the same discipline applies: listen first, since these modes can run for a long time and a busy frequency makes the problem worse for everyone.

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.