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

Picking a digital mode by the job: thresholds, time sync, audio levels and CAT setup

ci_cover.jpg

Digital operating covers a lot of ground, from FT8 and FT4 on HF to PSK31 and RTTY keyboard chats, WSPR beacons, Winlink email, and VHF weak-signal modes like MSK144 and Q65. The software and the interface problems overlap more than people expect. This thread is meant to collect practical notes on choosing a mode, and on the setup issues that cause most failed QSOs, whichever program you use.

Start with what each mode is for. FT8 uses 15-second T/R periods and a narrow signal (roughly 50 Hz wide), with a decode threshold usually quoted around -20 dB SNR in a 2500 Hz reference bandwidth. FT4 uses 7.5-second periods and is wider, with a threshold a few dB worse. It is meant for contest-style speed. WSPR is not for QSOs at all. It sends callsign, 4-character grid and power in dBm in a 2-minute transmission, and it decodes much lower still. Reports go to a spotting database, so it works well as a propagation probe. JS8Call borrows FT8-style modulation but adds keyboard messaging, directed calls and relaying, with slower submodes trading speed for sensitivity. PSK31 and RTTY are different animals. They are real-time character streams, so they need a much stronger signal than FT8 but let you chat as fast as you can type.

Timing is where most beginners lose decodes. FT8, FT4, WSPR, Q65 and MSK144 are all time-slotted, so your computer clock has to be close to correct. WSJT-X shows a DT column, and stations consistently showing large offsets usually have a clock problem. Use a proper NTP or other sync tool and do not rely on a default OS sync interval. PSK31, RTTY and Olivia in fldigi don't care about the clock, which makes them useful for telling a timing fault from an audio or CAT fault.

Audio and CAT come next. Use a rig data mode (USB-D or similar), turn off speech processing, compression and any audio enhancement on the PC, and set the transmit drive so ALC barely moves. Weak-signal modes need a clean linear signal, and an overdriven signal splatters sideways. Keep the audio tones in the middle of the passband, and use Split Operation in WSJT-X (Rig or Fake It) if the audio tone drifts toward the edges. For CAT, the baud rate, data bits and stop bits must match the rig menu, and USB devices can change COM port numbers after a reboot or a different port.

Questions to get things started: which of these causes you the most grief, clock drift, audio levels, or CAT and PTT? And which modes are you using as your main one, and for what purpose?

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Time sync is worth checking first, because the symptoms are easy to misread. If you can see strong signals on the waterfall but decodes are sparse, or you decode others who can't decode you, look at the DT column. Consistently large positive or negative DT values on many stations point to someone's clock being off. If it is your own clock, nearly every station will be off by a similar amount in the same direction.

For audio levels, the usual approach is to set the receive level so the WSJT-X meter sits in the lower-middle of its range, not pinned. On transmit, lower the output slider until the rig's ALC is not moving at all, and let the rig power control set the output. A 100 W rig on FT8 is transmitting for most of each period, so running well below full power is sensible for heat and linearity. On a typical rig, 20 to 50 W is often plenty, but check your own radio's manual for its duty-cycle limits.

One more fault that is easy to miss: if the computer's sound card is set to enhancements, spatial audio or a different sample rate than the application expects, you can get spurs that look like extra signals. Turn those off and use the plain 48 kHz setting.

  • Moderators

On mode selection beyond FT8, it helps to think about what the path does to the signal. For tropo and ionospheric scatter on 6 m and 2 m, Q65 is designed for weak, fading signals, with longer T/R periods and a choice of tone-spacing submodes depending on the path. MSK144 is aimed at meteor scatter, where the signal is a brief burst from a trail. It uses very short, fast transmissions, so accurate time and a decent frequency setting matter a lot. Both rely on grid squares as part of the exchange, so get comfortable with Maidenhead: two letters for the field, two digits for the square (for example FN31), and two more letters if you want 6-character precision. Standard FT8 messages usually carry only the 4-character version.

For HF messaging, Winlink is a different kind of operating. It is email by radio, using a gateway station (RMS) and a client such as Winlink Express. Common modes include VARA HF or FM and ARDOP, with Pactor and packet also in use. VARA is a proprietary program that is faster when registered, and ARDOP is a free alternative. Choose a gateway based on the path, and check propagation first. WSPR spots can help here, since a quick look at where your signal is being heard tells you which bands are open.

In fldigi, MFSK and Olivia are the ones to try when conditions are poor but you want to type freeform text. Olivia's FEC lets it decode below the noise level, though at a slow typing speed. Hellschreiber is the odd one: text is sent as a pixel pattern and read by eye, which makes it tolerant of some interference but not exactly fast. If you want a quick comparison, run the same text on a few of these on a quiet band and see which one holds up.

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.