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 modes and weak signal setup: where decode thresholds, time sync and audio levels actually decide your results

ci_cover.jpg

Most problems with FT8, FT4, JS8Call and the other digital modes come from the plumbing, not the mode: audio levels, clock accuracy, CAT/PTT behavior and filter settings. This thread is for comparing setups and sorting out which mode fits which job. Corrections are welcome.

Start with decode thresholds, because they are often misquoted. The WSJT-X documentation gives sensitivity as S/N in a 2500 Hz reference bandwidth, not the bandwidth the signal occupies. FT8 decodes down to roughly -21 dB on that scale, FT4 is a few dB less sensitive (around -17 dB), and WSPR goes down near -31 dB. A 2-minute WSPR cycle against a 15-second FT8 cycle shows the basic tradeoff: more sensitivity costs more time on air. Q65 is the flexible one. It has several T/R period lengths, from 15 seconds up to 5 minutes, and tone-spacing submodes tuned for ionospheric scatter, tropo and EME. MSK144 is built for meteor scatter, where the useful signal is a burst of a few hundred milliseconds. That is why it uses fast 15-second sequences and very short frames instead of long integration.

The mode families split roughly like this. FT8, FT4, WSPR, Q65 and MSK144 are structured modes with fixed message formats, forward error correction and strict timing. They are efficient, but they are not conversational. JS8Call keeps the FT8-style modulation and adds a keyboard-to-keyboard layer with selectable speeds, directed messages and relaying. It is slower than a keyboard mode like PSK31, but it can get a message through when PSK31 would not. PSK31 (31.25 baud, narrow) and RTTY (usually 45.45 baud, 170 Hz shift) are older, free-flowing modes. Olivia and other MFSK modes in fldigi trade speed for robustness, and Hellschreiber works almost like a fax, since you read the character shapes yourself. Winlink is a different category: it is message transport, not a QSO mode. Depending on the path, it runs over VARA, ARDOP, Pactor or packet, and VARA HF/FM are proprietary Windows-based modems.

Time sync deserves more attention than it gets. FT8 and FT4 assume your clock lines up with everyone else's to within about a second, and the closer to zero the better. If your decodes show consistently large DT values, or you decode people who never seem to answer you, check the clock before the antenna. A PC that only syncs occasionally can drift. Use a proper NTP client, or GPS-disciplined time if you work portable without internet, and watch the DT column as a free diagnostic. Lots of stations at DT +0.5 or higher, with yours different from the rest, points at your clock.

Audio levels are the other classic problem. Digital modes need a clean, linear transmit chain. Turn off the speech processor and EQ, set the rig to its data mode (USB-D, DATA-USB or whatever your radio calls it), and keep the Windows or Linux mixer from adding enhancements or system sounds. Drive the audio just far enough to reach the power you want, and keep the ALC reading at zero or barely moving. Running a 100 W rig at full power on FT8 is rarely necessary, and an overdriven signal splatters the neighboring audio slots and is just bad on-air behavior. On receive, set the input level so the WSJT-X meter sits around the middle of its range rather than pinned or near empty, which leaves headroom for strong signals and for noise to decode against.

CAT control adds its own choices. You can use CAT for frequency and mode and a separate method for PTT, or let CAT do both. Hamlib, the manufacturer's own protocol and a virtual COM port all work, but each adds a failure point. For split operation on FT8, WSJT-X offers 'Rig' and 'Fake It'. Both aim to keep the transmitted audio within the radio's cleanest passband, since audio harmonics get worse toward the edges. If your radio reads back frequency slowly or drops serial traffic during transmit, simplify it: lower the baud rate, check for USB RF pickup, and use ferrites before you suspect the software.

Grid squares matter more than they look. Maidenhead locators use field and square pairs (like FN31) and optionally subsquares (FN31pr). A 4-character grid is enough for most FT8 work and for award tracking, but 6 characters matter for VHF and microwave weak signal work, where distance and bearing precision count. Check that your grid is entered correctly in WSJT-X. A typo means wrong distance data on PSKReporter and wasted effort on tropo or meteor scatter schedules.

Questions for the thread: Which interface do you trust most, such as a built-in USB audio codec, a separate isolated sound card interface, or an external box? What do you use for time sync when you're away from home? And if you only had two modes for HF, which would you pick, and why?

  • Replies 2
  • Views 27
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

For interfaces, isolation matters more than brand. A lot of 'my decodes are weird' reports turn out to be ground loops, RF getting into the audio line, or a radio's USB audio and USB serial sharing a cable that picks up hash. If you hear birdies or the waterfall shows a comb of lines, try a ferrite on the USB lead and move the interface away from the antenna feedline before replacing anything. Isolation transformers on the audio lines are cheap and often fix exactly this.

On the two-mode question, the answer depends on your station. If you run low power or have a compromise antenna, FT8 gives the best return on effort because the 15-second cycle and narrow bandwidth let you work stations that voice or PSK31 would lose. For a second mode, JS8Call is a strong pick if you want something closer to conversation, relayed messages and signal reports, while keeping similar sensitivity. If your station is more about emergency communications, Winlink with VARA or ARDOP is the more practical choice over any chat mode.

  • Moderators

One caution on thresholds: -21 dB for FT8 is a decoding limit, not a promise. The number assumes the signal is steady and the DT is within tolerance. QSB, local noise, a crowded sub-band and your own receiver's AGC all push real-world results toward the less sensitive end. So treat the chart as a comparison between modes, not a guarantee of what your antenna will do. A station that decodes a weak signal on one band may not manage it on another with a noisier location.

For time sync away from home, a phone hotspot with a normal NTP client works if you have signal. Without one, a cheap GPS receiver and a time service on your PC does the job. Whatever you choose, check the DT column against a few strong stations before you transmit. And keep Q65 in mind for VHF and up. It lets you pick the T/R period to match the path, so it is worth the setup time if you do tropo or scatter work.

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.