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

Choosing a digital mode and fixing the usual FT8 problems: time sync, audio levels, CAT and what the decode thresholds mean

ci_cover.jpg

This thread is for sorting out the practical side of digital operating. Mode choice, interface setup and the weak-signal numbers all tie together, and a problem in one area often looks like a problem in another. Questions come up all the time like "why don't I decode anything on a band that is clearly open?" or "why do I get reports of -24 when the signal sounds strong?" Here is a framework to start from, and please correct anything I get wrong.

Start with the modes by what they are built for. FT8 uses 15-second transmit/receive periods, 8-tone FSK and about 50 Hz of bandwidth. It is designed for a minimal exchange (callsign, grid or report, RR73/73) at very low signal-to-noise ratios, with a decode limit often quoted around -21 dB. FT4 uses 7.5-second periods and a wider signal, with a threshold a few dB worse. That trade buys faster contest-style QSOs. WSPR is not for conversations at all. It is a beacon mode with 2-minute transmissions and a very narrow signal, and it is useful for propagation checks because its threshold is far lower, around -30 dB. JS8Call borrows FT8-style modulation but adds free-form keyboard messaging, relaying and store-and-forward, with selectable speeds. Slower submodes decode weaker signals but take longer to send each message.

The older keyboard modes sit in a different category. PSK31 (31.25 baud, a very narrow BPSK signal) and RTTY (commonly 45.45 baud with 170 Hz shift) are much less sensitive than the WSJT-family modes, but a human reads the text in real time. Olivia and other MFSK modes use heavy error correction and long symbol times to get text through under the noise, at a slow typing speed. Hellschreiber is different again: it sends text as a visual raster, so you read the characters on screen instead of relying on a decoder. For those modes FLDIGI is the usual software, and WSJT-X covers the FT8/FT4/WSPR/Q65/MSK144 family.

Where do you start when decodes are missing? In my experience the usual suspects are the clock, the audio level and the radio's mode settings, roughly in that order. What do others check first, and what do you consider a sane default setup for a new interface?

  • Replies 2
  • Views 25
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd go in this order: clock, audio, radio mode, then CAT.

Time first, because the timing-based modes depend on it. In FT8 the decoder shows a DT value for each message, the time offset between the signal and your clock. If most stations show a consistent offset such as +0.5 or -0.8 seconds, your clock is probably the one that's off, not theirs. A decent target is a clock well within a second of true time, and closer is better. Windows' default time sync can be loose, so many operators run a dedicated NTP client or a GPS-based source. If you're not sure, check the DT column before touching anything else.

Then audio. Set the sound card to the sample rate and format the software expects, usually 48 kHz, 16-bit. Disable audio enhancements, system sounds and anything that could route notification beeps into the transmit path. On receive, aim for a modest input level in the WSJT-X meter. The software's guidance is roughly the low end of the green zone, not pinned at the top. On transmit, the common mistake is driving the rig too hard. Keep the ALC barely moving, and reduce power instead of pushing audio. Overdriving causes splatter, which hurts everyone on the band even if you still log contacts.

Radio mode matters too. You want USB (or the rig's data-USB mode), with speech processing off and any narrow filters opened enough to pass the whole audio passband, not FM or AM. For CAT, make sure the serial port settings match the radio's menu (baud rate, stop bits, handshake), because Hamlib will otherwise report errors or hang. If PTT is on RTS or DTR, check that opening the port doesn't key the transmitter by accident. Some USB-serial adapters toggle those lines when the port opens. Good isolation, ferrites and keeping audio cables away from RF also prevent the strange sporadic problems that look like software bugs.

One more thing on the numbers: the S/N in a WSJT-X report is referenced to a 2500 Hz noise bandwidth, so it's an estimate of signal against noise, not an S-meter reading. A -18 report doesn't mean a weak signal in the usual sense. It's just a different scale.

  • Moderators

Adding to the mode-selection side, plus grids and Winlink, since those catch people out.

For weak-signal work beyond HF FT8, the WSJT-X family has specialised modes. MSK144 is meant for meteor scatter, usually on 6 m and 2 m, where a useful signal might exist for only a fraction of a second. Q65 is aimed at difficult paths like EME and tropo/ionospheric scatter, and it has several submodes and selectable period lengths, so you pick a combination suited to the path and frequency. That's a different workflow from FT8. You often need to agree on the submode, period and frequency in advance, usually through a coordination chat or a calling frequency set by convention.

For grid squares, WSJT-X uses the Maidenhead locator. The four-character form, like FN31, identifies a rectangle 2 degrees of longitude by 1 degree of latitude. The six-character form adds a subsquare for finer location. For FT8 and FT4, four characters are normally all that's sent. Make sure your configured grid is correct, because it ends up in your CQ and in logs and reporting sites. A wrong grid makes distance awards and propagation maps unreliable. On VHF and up, where grids drive awards and contest scoring, accuracy matters even more.

For Winlink, treat it separately from the chat-style modes. It's an email system over radio, and the software (Winlink Express) talks to a modem or TNC rather than just using your sound card as an FT8 decoder. VARA is a popular modem for it. It's proprietary, and unlicensed versions limit throughput, so check the author's current terms and licensing before relying on it. Whatever the modem, listen first, because Winlink and similar modes use channels that others may be using. Use frequencies and gateways appropriate to your band plan and license, and don't assume a gateway's availability from old lists.

If you want something to sanity-check your station, WSPR is a good tool. Set a modest power level, let it run for a while, and compare what the network reports against what you'd expect. That helps confirm that your frequency, clock and antenna are working, without needing a QSO partner.

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.