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

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

ci_cover.jpg

Many problems on FT8, FT4, JS8Call, PSK31 and RTTY come from the same few things: audio levels, clock accuracy, rig control and expectations about what a decode threshold means. This thread is for comparing notes on those basics, and on how the modes differ once the station is working properly.

Start with time. FT8 uses 15-second transmit/receive periods, FT4 uses 7.5 seconds, and WSPR uses 2-minute periods. WSJT-X can tolerate some error, but a clock that is a second or more off will cost you decodes and may make you transmit on top of other stations. Windows time sync can drift between updates, so many operators run a dedicated NTP client or a GPS-based source. On Linux, chrony or ntpd usually does the job. In WSJT-X, watch the DT column. Values that sit consistently positive or negative across many stations suggest your clock, or a delay in your audio path, is off.

Next is audio. For a sound card interface, whether it is a built-in USB codec in the radio or an external box, the goal is a clean, low-distortion signal. Set the radio to USB (or USB-D/DATA where available) and turn off speech processing, EQ and any other audio filtering. Set the transmit audio so the ALC barely moves, if at all. Digital modes like FT8 are constant-envelope, so overdriving the audio does not add power. It adds splatter and wider products. If you are running 100 W, a good rule is to back the audio off until the power output is clearly at or below the radio's rated level without the ALC reading anything significant. On receive, aim for a healthy but not clipped level in the WSJT-X meter, roughly in the middle of its range, as the documentation suggests.

CAT control is separate from audio, and it is worth keeping the two straight. Audio carries the signal, and CAT carries frequency, mode and often PTT. WSJT-X and FLDIGI can both use Hamlib or other rig control backends, and for PTT you can choose CAT, a serial line such as RTS or DTR, or VOX. If you use split operation in WSJT-X, the Rig or Fake It options keep the audio tones in a comfortable range (often around 1500 to 2000 Hz) by shifting the dial frequency instead of the audio. This helps avoid harmonics or filter edges in your transmit chain.

Decode thresholds are often quoted as signal-to-noise ratios in a 2500 Hz reference bandwidth, not as what the receiver is actually filtering. WSJT-X documentation gives approximate figures such as about -21 dB for FT8 and about -17.5 dB for FT4, and WSPR goes much lower at around -31 dB. A deeper threshold usually costs time. WSPR needs two minutes, and the slower Q65 submodes use longer periods (15, 30, 60, 120 or 300 seconds) to dig further into the noise for EME, scatter and other weak-signal paths. MSK144 does the opposite: it uses very short, fast bursts for meteor scatter, where the path may last only fractions of a second.

The keyboard modes work differently. PSK31 runs at 31.25 baud and occupies about 31 Hz, so it is narrow and efficient but sensitive to drift and multipath. RTTY is typically 45.45 baud with 170 Hz shift, which is wider and more robust against some fading but less sensitive in raw terms. Olivia and MFSK in FLDIGI trade speed for robustness; Olivia in particular has many tone-count and bandwidth combinations, so both ends must agree on settings. Hellschreiber (Feld Hell) is a different idea altogether, because the receiver shows the characters as a pattern you read by eye, and it can be readable when other decoders struggle.

Finally, grid squares. Maidenhead locators like FN31 (four characters) or FN31pr (six) are what FT8, FT4, WSPR and others exchange. Four characters are enough for most contacts and awards, but six characters give a much more accurate position and are useful for VHF and weak-signal work. Make sure your station locator is entered correctly. A wrong grid can make your spots, distance calculations and log entries misleading.

What is your approach to keeping the clock, audio levels and rig control reliable, and which of the less common modes (Olivia, Hell, Q65, MSK144) have you found a use for?

  • Replies 2
  • Views 48
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On audio levels, a mistake that keeps appearing is treating the Windows or Linux mixer as a convenience control and forgetting about it. System sounds, notifications and automatic gain features can all end up in the transmit path if the same sound device is shared. A dedicated USB codec used only for the digital program helps a lot, and so does muting everything else on that device. If the radio has both a front-panel and a rear-panel data connection, check which one gets the DATA input and whether the microphone is disabled in data mode.

The WSJT-X waterfall can also reveal problems that the ALC meter does not show. If you see extra lines or a wide skirt around your own signal when monitoring on a second receiver or SDR, the drive is probably too high or the chain is nonlinear. For FT8, that is the cheap fix: reduce the audio, and keep the radio's power setting to the level you actually want.

One more point on thresholds: a number like -21 dB is a guide, not a promise. Real-world decoding depends on the QRM, the passband, fading and how the other station's signal sits relative to the noise. A weak decode on one band might fail on another even at the same reported SNR.

  • Moderators

A few notes on the less common modes and on Winlink. JS8Call uses FT8-style modulation but is built for keyboard-style messaging, relays and store-and-forward. It has several speeds (Slow, Normal, Fast and Turbo), and the faster ones trade sensitivity for throughput. That makes it good for casual weak-signal chats and for passing short messages, but it is not a replacement for a proper email system.

Winlink is that email system. It is usually used through Winlink Express with a modem such as VARA HF, VARA FM, ARDOP or Pactor, depending on the gateway and the hardware. VARA is a proprietary modem, and the free version is speed-limited, so check the licence terms and what the gateway you plan to use supports. Whatever you choose, test the PTT and audio chain before relying on it for something important. Listen before you transmit, because gateway channels can be busy and a connection attempt can interfere with sessions already in progress.

For Q65 and MSK144, it is worth reading the WSJT-X user guide for the specific submode and period before trying them. Q65 with a long period, say 60 seconds on 6 m or 2 m, behaves very differently from FT8 in time and frequency tolerance, and MSK144 depends on accurate time and a good meteor-scatter schedule. Olivia and Hell are best treated as experiments: agree the settings beforehand, start with a strong signal and a known partner, and then try weaker conditions.

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.