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 chain checklist: audio levels, time sync, CAT and picking the right mode for the band conditions

ci_cover.jpg

A lot of digital-mode problems come from the station chain rather than the mode itself. A -15 dB FT8 signal decodes fine on a clean setup, while the same signal with a 1.5 second clock error or an overdriven transmit path may never decode. This thread is for working through the chain and then matching the mode to the job.

Here is a rough outline of the layers, so we can poke holes in it.

1. Audio path. This is either a sound card interface (separate USB codec plus PTT line) or the radio's built-in USB audio. The goal is flat, clean audio with no processing. Speech processing, compression and DSP noise reduction on the transmit side should be off. Receive audio should sit in the middle of the soundcard's range, not clipped and not buried in quantization noise.

2. Rig control. CAT through Hamlib (in WSJT-X) or the radio's native commands (in FLDIGI and others) handles frequency and mode. PTT can come from CAT, a serial RTS/DTR line, or VOX, with VOX the least desirable because it can key on stray audio such as system sounds. For FT8 and FT4 on a busy band, split operation ("Rig" or "Fake It" in WSJT-X) keeps the audio tones in a comfortable range so the radio's own transmit filtering does not create harmonics.

3. Time. FT8 uses 15 second slots, FT4 7.5 seconds, WSPR 2 minutes. These modes assume your clock is within roughly a second of everyone else's. The DT column in WSJT-X shows the offset of each decoded signal relative to your clock, and if most stations show a consistent offset, your clock is the likely culprit. NTP-based tools, chrony, or a GPS source are all more reliable than relying on the operating system's default sync interval.

4. Mode choice. The modes sit on a spectrum. FT8 trades speed for sensitivity (decode threshold around -20 dB in a 2500 Hz reference bandwidth), FT4 gives up a few dB for faster exchanges in contest-style operation, and WSPR is a one-way beacon mode with a threshold around -30 dB. JS8Call uses FT8-style modulation but adds free-text messaging and relaying. PSK31 and RTTY have no deep-decode advantage and rely on you being able to hear and see the signal. Olivia and other MFSK modes use heavy forward error correction and are good for messy HF paths where a slow keyboard exchange is acceptable. Hellschreiber is the odd one out, since you read the characters visually and the human eye does the error correction.

Questions for the group: what order do you troubleshoot in when a station is working but nobody replies? And where do you draw the line between a mode being "weak signal" and just being a different way to send text?

  • Replies 2
  • Views 29
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Troubleshooting order matters, so here is one that usually isolates things quickly.

Start with the clock. Look at DT values in the decode window. If the strong stations cluster near 0.0 and yours is the one that looks off, fix time sync before touching anything else. A DT consistently beyond about plus or minus 1 second will reduce decodes noticeably, and beyond that you start losing them entirely.

Next, check transmit audio. In WSJT-X, set the Pwr slider and the soundcard output level so the radio's ALC barely moves, if at all. FT8 and FT4 are constant-envelope modes, so you do not need to push the radio into ALC to get a bigger signal. All that does is spread distortion products on either side of your signal, which people see as a wide, splattery trace on the waterfall. If you are running 100 W rated gear, running well below full output is normal for these modes, since you are keying a continuous carrier-like signal for most of the 15 seconds.

Receive level is the other half. The WSJT-X receive meter has a recommended zone, roughly around 30 dB, and the exact number depends on the app and sound card. What matters is that the noise floor on the waterfall is visible but not saturated. If you can see the waterfall going fully white or fully black, adjust before blaming propagation.

On CAT, the usual traps are mismatched baud rates between the radio menu and the software, and a USB audio device that gets renumbered after a reboot, so the program is pointed at the wrong sound card. The software also needs to be told whether the radio is in USB or a data mode such as USB-D or PKT, and which filter width the radio should use. A 500 Hz filter can quietly clip a 3 kHz FT8 passband, so check filter width on the radio first.

As for how to separate weak-signal from just a different way to send text: if the mode has strong FEC and a defined timing structure so the decoder can integrate over a known window, I call it weak-signal. PSK31 is more of an "is it readable" mode, whereas FT8, WSPR and Q65 are built around statistical decoding.

  • Moderators

On picking modes, a few distinctions help.

FT8 and FT4 are for quick confirmed contacts. A standard FT8 exchange is a grid square and a signal report, so the grid itself carries the "where are you" information. Maidenhead locators are worth understanding rather than copying blindly. A 4-character grid (for example, two letters and two digits) is a square of 2 degrees of longitude by 1 degree of latitude. A 6-character locator adds a subsquare that is 5 minutes of longitude by 2.5 minutes of latitude, which is much better for VHF distance calculations. Many weak-signal setups send only 4 characters, which is enough for HF and for most awards but coarse for VHF and up.

Q65 and MSK144 are more specialised. MSK144 is for meteor scatter, where the signal appears as very short bursts, so its frames are fast and the decoder is tuned for pings rather than long integration. Q65 is aimed at difficult paths such as EME, ionospheric scatter and rain scatter on the higher bands, and it offers multiple sub-mode choices and period lengths, so you pick based on how much frequency spread the path imposes. Using these on a normal HF band is possible, but it is not what they were designed for.

WSPR is useful when the question is "where can I be heard?" rather than "who can I work?". It is a beacon mode with two minute transmissions and very low power requirements, and spots go to a shared database, which makes it a handy antenna comparison tool. Just remember that spot counts depend on how many receivers happen to be listening on that band at that time.

For messaging, Winlink and JS8Call fill different roles. Winlink is email over radio via gateways, with modems such as VARA, ARDOP or Pactor, and is the usual choice for emergency communications where you need to move a real message. VARA is a proprietary modem, and its free version is rate-limited while the registered version is faster. JS8Call is more of a conversational, keyboard-to-keyboard mode with relay capability, and its throughput is low. Olivia and other MFSK modes in FLDIGI sit in between, as a way to hold a slow ragchew on a noisy band where PSK31 would fall apart.

One last point is that decode thresholds are usually quoted in dB relative to a 2500 Hz noise bandwidth. That makes comparisons fair across modes, but it does not account for QRM, fading or timing issues, so treat the numbers as ideal-condition references and not as a guarantee on your own receiver.

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.