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

Clean digital-mode station setup: audio levels, CAT, time sync and what decode thresholds really tell you

ci_cover.jpg

Most problems with digital modes come from the station setup, not the mode. A short checklist of the things that most often go wrong, then some questions for the group.

Audio chain. WSJT-X and FLDIGI both work through a sound card, either the rig's built-in USB codec or an external interface. Three things matter most. First, turn off Windows or macOS audio "enhancements", system sounds and automatic gain on those devices, otherwise your transmit audio can be altered or other apps can leak into the signal. Second, set the receive level so the WSJT-X level meter sits around the middle of its range, roughly 30 dB on the bar, rather than pinned at either end. Third, on transmit, set the rig's USB audio or data input and the software output slider so the ALC shows little or no deflection. Digital modes are mostly constant-envelope, so a clean 30 W is far better than a splattery 100 W. Heavy ALC action or compression adds distortion, and other stations will see it as a wide, ugly trace on the waterfall.

CAT control. Hamlib is built into WSJT-X, and FLDIGI can use Hamlib or its own rig control. CAT gives you frequency readback and PTT without a separate serial line. In WSJT-X, the Split Operation setting (Rig or Fake It) keeps your audio offset in the ideal range for the transmit passband. Without it, a signal sent at a high audio offset can generate harmonics inside the passband. If you're on an interface with no CAT, DTR/RTS or VOX PTT works, but VOX can key from stray audio, so use it with care.

Time sync. FT8, FT4, WSPR, Q65 and MSK144 are all time-slotted. The software uses the DT column to show how far your clock is from the other station's. If DT is consistently off by half a second or more, fix your clock before touching anything else. Operating-system time sync can drift or update infrequently, so many operators use a dedicated NTP client or a GPS-backed source. Check the clock before a session, especially on a laptop that has been off or on battery.

Decode thresholds. The published figures are signal-to-noise ratios referenced to a 2500 Hz noise bandwidth, not dB over the noise floor in the signal's own bandwidth. This lets you compare modes, but only roughly. FT8 decodes down to about -20 dB, FT4 is a few dB less sensitive in exchange for shorter cycles, and WSPR goes to about -30 dB because it sends very slowly with a much narrower bandwidth. MSK144 is designed for meteor-scatter pings that last a fraction of a second, and Q65 is aimed at EME, tropo and ionospheric scatter. A lower threshold is not always "better"; it buys sensitivity at the cost of speed and message content.

Grid squares. FT8 and FT4 exchanges use a four-character Maidenhead locator (for example, two letters, two digits). Check that yours is entered correctly in settings, because a wrong grid pollutes PSK Reporter, logs and award tracking. A six-character locator gives you much better distance accuracy for weak-signal VHF work.

Questions for the group: What's your preferred way to keep the PC clock accurate? How do you decide between JS8Call, Winlink and a keyboard mode like PSK31 or Olivia when conditions are marginal? And does anyone still use Hellschreiber or RTTY regularly for anything other than contests?

  • Replies 2
  • Views 26
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On time sync, a quick check is to watch DT over a dozen or so decodes. If the strong stations cluster near zero, with a small offset like 0.1 to 0.3 s that stays consistent, you're fine. If your own clock is off, every station will show the same shift, which is easy to confuse with propagation delay. Mode matters here too. FT8 is tolerant of a bit of error, but FT4 has shorter cycles and MSK144 has very tight timing, so the margin for error shrinks.

On audio levels, one common mistake is chasing a number in the software instead of watching the rig. The WSJT-X Pwr slider or the Windows output volume sets drive, but the correct setting is the one that gives the output power you want with no ALC movement. Many rigs will happily make 100 W of distorted signal if you let them. Back the drive off until the ALC is quiet, then raise power at the PA instead. Also worth remembering that a USB audio codec can show up with a different device name after you replug it or move ports, so re-check the selection in Settings > Audio if decodes or transmit suddenly stop.

For CAT, avoid polling too fast or running a second program on the same COM port. Several apps trying to talk to the same radio is a common cause of random PTT failures and frequency jumps. Use a virtual port splitter or Hamlib's rigctld if you need logging and decoding to share control.

  • Moderators

On picking a mode when things are marginal, it helps to separate the use cases. WSPR is a beacon mode, so it tells you where your signal is going and what the path looks like, but it isn't a conversation. FT8 is great for confirming a contact with minimal information when the band is barely open. JS8Call uses the same kind of modulation as FT8 but adds free-text messaging, relays and heartbeats, so it suits informal keyboard chat on a weak band. Slower JS8Call speeds trade time for sensitivity.

Winlink is about sending actual messages, not making contacts. VARA HF is a proprietary modem that typically gets good throughput in decent conditions, and it's usually run alongside Winlink Express. ARDOP is an open alternative. Neither is a weak-signal mode in the FT8 sense, so a path that works for FT8 might not hold up for a connected session. Check frequency usage and the local rules for automatic or unattended operation before you transmit.

For the older keyboard modes, PSK31 is narrow and efficient but struggles with fading and needs a clean transmit signal, since overdriving it is easy to do. RTTY is more tolerant of poor conditions and remains a contest staple. Olivia and other MFSK modes are slow, but they can be copied at very low signal levels and handle flutter well, which is why they appear in emergency and low-signal nets. Hellschreiber is different because the receive display is image-like and you read it by eye, which makes it surprisingly resistant to noise in some conditions. It's mostly a novelty, but it's a good way to learn what the waterfall is really showing you.

One more thing about grid squares: for 6 m and up, set a six-character locator if you can, because meteor scatter and tropo work often depends on accurate bearings and distances.

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.