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

Getting digital modes right: time sync, audio levels, CAT and what the decode thresholds actually mean

ci_cover.jpg

Most trouble with FT8, FT4, JS8Call, WSPR, PSK31 and RTTY comes from the same few setup issues, not from the software. This thread is for sorting out the common ones in one place and comparing how different modes behave when signals get weak.

Start with time. FT8, FT4, WSPR, Q65 and MSK144 all depend on the computer clock. FT8 uses 15-second periods, FT4 uses 7.5 seconds, and WSPR uses 2 minutes. If your clock is off by more than a fraction of a second, decodes drop even when the signal is strong. Watch the DT column in WSJT-X. If most stations show a consistent offset, the error is probably in your clock, not theirs. A proper NTP client or a GPS-based source is more reliable than relying on a default OS sync that may only update occasionally. PSK31, RTTY and Olivia in FLDIGI are far less picky, because they are not slotted by the clock.

Then the audio chain. Whether you use a USB codec in the radio or an external sound card interface, the principle is the same. Set the sample rate and format in the OS (48 kHz, 16-bit is a safe choice), turn off any audio enhancements, and keep system sounds from leaking into the transmit path. In WSJT-X, set the receive level so the meter sits around the middle of its range. On transmit, use the Pwr slider and the radio's own settings to get the output you want, and keep ALC action at the minimum or zero. A digital signal that is overdriven spreads splatter beyond its narrow occupied bandwidth and gets nothing back in decodes. Power does not need to be high. Many FT8 contacts are made at modest power, and an overdriven rig can be worse than a clean 20 W.

CAT and PTT. CAT through Hamlib or a direct rig-control option lets the software read and set frequency and mode. Use a data mode such as USB-D or DATA-USB, and turn off speech processing, compression and aggressive noise reduction. For PTT you can use CAT, serial RTS/DTR, or VOX. VOX is the most likely to cause trouble because stray sounds can key the transmitter. In WSJT-X, the Split Operation setting (Rig or Fake It) keeps the audio tones within a clean part of the passband rather than pushing harmonics through the radio's filtering.

About those decode numbers. Published thresholds are usually quoted as signal-to-noise ratio in a 2500 Hz reference bandwidth. They are roughly -21 dB for FT8, around -17 dB for FT4 and about -31 dB for WSPR. A -20 dB report is therefore not comparable to an S-meter reading, and a decoded signal can be completely inaudible. Real conditions such as fading, Doppler spread and local noise move these numbers around, so treat them as approximate benchmarks, not guarantees.

Choosing a mode. FT8 is the usual choice for fast weak-signal contacts on HF and 6 m. FT4 trades some sensitivity for speed and is aimed at contest-style exchanges. JS8Call uses FT8-style modulation but adds free-form keyboard messaging, relaying and directed messages, which suits low-power and emergency-communication experiments, with slower exchanges. Q65 has sub-modes with different period lengths and tone spacings, and it is commonly used on VHF and above for tropo, scatter and EME. MSK144 is built for meteor scatter, where the useful signal can be a short burst. WSPR is a beacon mode and is best for testing propagation and antennas, not for conversation. PSK31 and RTTY are older, simpler modes that are still active and easy to decode by eye. Olivia and MFSK in FLDIGI trade speed for robustness. Hellschreiber is interesting because you read the text visually and the human eye can sometimes pick it out of noise.

Grid squares. Maidenhead locators are the standard for these modes. A four-character grid like FN31 is a field-and-square pair, and a six-character one adds a subsquare, giving finer detail. Many weak-signal operators use four characters for casual FT8 and six for VHF work or when distance matters. Make sure the locator in your software matches your real location, since spotting sites and award tracking depend on it.

What are the setup problems you see most often, and which modes do you think are underused? Feel free to post your interface choices, software versions and the band conditions where a mode has been a good fit.

  • Replies 2
  • Views 39
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

One thing worth adding about time sync is that the fix depends on how the machine gets its time. A Windows PC left on defaults may only sync occasionally, so the clock can drift between updates. A dedicated NTP client with a short polling interval is a simple improvement, and a GPS receiver with a PPS source is better still for a station that is off-grid or has no reliable internet. The DT readout in WSJT-X is a quick sanity check. If you are decoding strong stations with DT values all in the same direction, adjust your clock, not your expectations.

On audio, watch the sample-rate mismatch between the OS device, a virtual audio cable and the app. If FLDIGI and WSJT-X are both fed from the same interface, sharing it usually requires virtual cables or a splitter, and each hop is another chance for a level or rate problem. Ground loops are another common cause of hum or spurs on cheap setups. Isolation transformers on the audio lines, ferrites on the USB and audio cables, and a single sensible ground point often help more than any software change.

  • Moderators

Choosing between the keyboard modes mostly comes down to what you need from the contact. PSK31 occupies roughly 31 Hz and is easy on a waterfall, but it does not cope well with fast fading and it has no strong error correction. RTTY at 45.45 baud with 170 Hz shift is wider and less efficient, but it is still the standard for many contests and is tolerant of poor tuning once you understand it. Olivia and the MFSK family in FLDIGI add forward error correction, so you can sometimes copy text when a PSK signal would be garbage, at the cost of slow typing speed. Hellschreiber is a different idea, because the text is drawn on screen like a tiny fax, so it can be read even with some corruption.

For Winlink, remember that the mode is only the transport. The Winlink Express client can use several, including VARA HF, VARA FM, ARDOP, Pactor and packet, and which ones work depends on the gateway and your hardware. VARA is proprietary software with a free version that is speed-limited and a registered version that is faster, so check the current licensing before building a plan around it. Also keep in mind that unattended or automatic operation has its own rules in each country, so check your local regulations and the band plan before running anything that could transmit on its own.

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.