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

Matching the digital mode to the path: FT8, FT4, WSPR, Q65, MSK144, JS8Call and the keyboard modes, plus the audio, CAT and clock setup behind them

ci_cover.jpg

Most problems with digital modes come from three things: picking a mode that doesn't suit the path, a transmit audio chain that isn't clean, and a PC clock that has drifted. This thread is for comparing notes on all three. The figures below are approximate and come from the published mode designs. Check the current WSJT-X and fldigi documentation and your local band plan before relying on any of them.

Weak-signal modes, roughly in order of sensitivity versus speed. FT8 uses 15 second transmit/receive periods, occupies about 50 Hz, and decodes down to around -21 dB (SNR in a 2500 Hz reference bandwidth). FT4 uses 7.5 second periods and about 80 Hz, with a threshold a few dB worse, which is the trade for faster contest-style exchanges. WSPR is a beacon mode rather than a QSO mode. It uses 2 minute periods and about 6 Hz of bandwidth, and decodes at roughly -30 dB, so it is a good tool for checking whether a band is open and how an antenna performs. Q65 in WSJT-X comes in several period lengths (15, 30, 60, 120 and 300 s) with different tone spacings. It is aimed at difficult paths such as EME, tropo scatter and ionospheric scatter on VHF and up. MSK144 is for meteor scatter, where the signal is a burst of a fraction of a second, so the software has to catch short pings, not integrate for a long period.

Keyboard and messaging modes. PSK31 (31.25 baud, narrow) is a conversational mode and is sensitive to overdriven audio, which creates IMD products on either side of the signal. RTTY (traditionally 45.45 baud, 170 Hz shift) is still common in contests and is more tolerant of poor conditions than its age suggests. MFSK modes in fldigi add forward error correction and handle fading better than PSK. Olivia is an MFSK variant that trades speed for robustness, with settings such as 8/250, 16/500 and 32/1000 (tones/bandwidth). It can copy text well below the noise, but slowly. Hellschreiber is different: the receiver paints the characters on the waterfall or display, so you read the text visually, and it can be readable when a decoder would give up. JS8Call uses FT8-style modulation but adds free-text messaging, heartbeats, relaying and store-and-forward. It offers several speeds (Slow, Normal, Fast, Turbo), and faster speeds need a stronger signal.

Winlink, VARA and the like. Winlink is an email-over-radio system, not a single mode. It can run over several transports, including packet, ARDOP and VARA. VARA HF and VARA FM are proprietary and free to use at a reduced throughput, with registration unlocking the higher speeds. Winlink sessions are connected, ARQ-style transfers, so before you transmit you need to listen for activity on the frequency, because a hidden-node collision will wreck someone else's transfer.

Time sync. FT8, FT4, WSPR, Q65 and MSK144 all depend on both stations agreeing on the clock. For FT8, a DT (time offset) consistently beyond about half a second means your clock or the other station's is off. Windows' default sync can be loose, so many operators use a dedicated NTP client or a GPS-disciplined source, and Linux users typically run chrony or ntpd. If decodes look fine but nobody replies, check DT before you check the antenna.

Grid squares. A Maidenhead locator like FN31 is two letters for the field and two digits for the square. Adding two more letters (FN31pr) gives a subsquare. FT8 normally exchanges only the four-character grid. WSPR and some other modes can carry six, and a precise locator matters more on VHF/UHF weak-signal work where distance records and awards are scored by grid.

Interface and CAT. A sound card interface (an external USB codec, a rig's built-in USB audio, or a transformer-isolated adapter) carries audio in both directions. Transmit audio should be set so the radio's ALC barely moves, with speech processing, compression and EQ off, and the radio in a data mode (USB-D, DATA-U or similar). Do not raise audio level to compensate for low power, because the clean answer is usually to lower the level and let the radio's power control set the output. CAT control through Hamlib or a manufacturer driver handles frequency and PTT, and in WSJT-X the split setting (Rig or Fake It) can keep transmit audio in the sweet spot of the radio's passband. Serial PTT via RTS/DTR, CAT PTT, and VOX each behave differently, and a ground loop between the PC, interface and radio is a common source of RFI and hum.

Which of these do people find the biggest source of failed decodes in practice: clock drift, overdriven audio, or CAT/PTT misconfiguration? And what mode do you reach for when FT8 is not enough?

  • Replies 2
  • Views 95
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the audio chain, the quickest check is to watch your own transmitted signal on a second receiver or an SDR. A clean FT8 or PSK31 signal should look like a few tidy tones with nothing around them. If you see a skirt of spurs on either side, the level is too high somewhere, whether in the PC mixer, the interface gain, or the radio's data input. Windows is notorious for enhancements, system sounds and automatic gain getting in the way, so the sound card should be set to a fixed level with all effects disabled. Many rigs also behave differently on the rear data connector compared with the USB codec, so check which input your menu is routing to and which gain setting applies to it.

A related habit: don't judge power by the wattmeter alone on a mode with a constant envelope like FT8. A steady carrier-like output with a tiny bit of ALC action is usually a good place to be. If you run a linear amplifier, low drive and low duty cycle are even more important, because the amp and the radio are heated continuously over the whole 12.6 seconds of an FT8 transmission.

  • Moderators

For the path question, it helps to separate propagation types. On HF, FT8 is the default because so many stations are on it, and it is usually decoded before you can finish a sentence in the log. WSPR is more useful as a measurement tool. You can run low power on a band, and the reports on the public spot database give you a map of where your signal landed. That tells you more about an antenna change than a handful of QSOs would.

On 6 m and up, mode choice depends on the mechanism. Meteor scatter calls for MSK144, with accurate time and a fixed schedule or calling frequency. Q65 is the one to learn if you are looking at tropo, scatter or EME, because the sub-mode letter and period have to match between stations, and a mismatch looks exactly like no signal. For something like emergency or off-grid messaging, JS8Call and Winlink serve different jobs. JS8Call is good for informal keyboard contact and relaying short messages between stations, whereas Winlink is for formatted email that has to reach an internet gateway. Neither replaces proper training or a local net plan, and it is wise to test them on a quiet band before they are needed.

One last point on CAT: if you also run a logger or another program on the same radio, use a shared CAT arrangement or a rig-control server (rigctld, for example) so two programs do not fight over the serial port. This is a common reason that frequency readouts freeze or PTT drops partway through a transmission.

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.