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

Building a clean digital chain: time sync, audio levels, CAT and choosing between FT8, JS8Call, WSPR, Olivia and the rest

ci_cover.jpg

A lot of digital-mode problems that look like "the band is dead" or "my decodes are bad" come from the station chain rather than the propagation. This thread is for comparing notes on the whole path, from clock to sound card to CAT to mode choice, so the weak-signal modes can do what they are designed to do.

Start with time. FT8, FT4, WSPR, Q65 and MSK144 all depend on the sender and receiver agreeing on the clock. FT8 uses 15-second periods and FT4 uses 7.5-second periods. In WSJT-X the DT column shows the offset between your clock and the other station's timing. If most decodes sit consistently positive or negative by more than a few tenths of a second, suspect your PC clock before you suspect anyone else. A computer's default sync interval can be too loose, so many operators run a dedicated NTP client or a GPS-disciplined source. Check it by comparing a few strong stations: if they all show a similar DT, the offset is probably yours.

Audio levels matter more than power. Set Windows or Linux sound levels so the receive audio shows a healthy but not clipped level in WSJT-X (the guideline is roughly 30 dB on the meter, with room to spare). On transmit, use the Pwr slider and the radio's data mode so ALC barely moves. FT8 is a constant-envelope signal, so a rig run hard on a 100% duty cycle gets hot. Backing the output down well below the rated maximum is normal practice and keeps splatter off the band. Turn off speech processing, noise reduction and any audio EQ when the radio is in a data mode (USB-D/DATA).

CAT or not? CAT through Hamlib in WSJT-X, or the radio-specific driver in FLDIGI, saves you from retyping frequencies and lets the software handle PTT and split. Match the baud rate, data bits, stop bits and the CI-V address where applicable. If you see random PTT drops or errors only when transmitting, suspect RF getting back into the USB or audio lines. Ferrites on the cables, a decent common-mode choke on the feedline and a proper ground are the usual fixes. "Split" in WSJT-X (Rig or Fake It) keeps your audio tones in a comfortable part of the passband so harmonics from the sound chain stay out of the transmit signal.

Where do the modes fit? Rough comparison: FT8 decodes down to around -21 dB S/N in a 2500 Hz reference bandwidth, and FT4 is a bit less sensitive (roughly -17 dB) but faster. WSPR works much lower (about -31 dB) because it uses a two-minute period and a very narrow signal; it is a beacon mode, not for conversation. JS8Call uses FT8-style modulation with free-text messaging, and its speed submodes trade sensitivity against transmission time. PSK31 and RTTY are real-time keyboard modes that need a stronger signal than FT8 but let you converse. Olivia and MFSK modes in FLDIGI are designed for rough conditions, at the cost of slow throughput. Hellschreiber is more of a visual curiosity that can still get through when other modes fail, because you read the text with your eyes. Q65 and MSK144 are for specialist work: Q65 for EME and scatter paths, MSK144 for meteor-scatter pings on VHF.

Winlink is a different category: it is email over radio rather than a contact mode. Winlink Express can use VARA HF, VARA FM, ARDOP, packet and Pactor, depending on your hardware. The VARA modems are proprietary, with a free version that is speed-limited.

Which part of this chain gave you the most trouble: clock drift, RF feedback, audio levels, or CAT? And what mode do you actually pick when the band is noisy?

  • Replies 2
  • Views 26
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On the clock, one thing worth checking is how often your OS actually corrects itself. A PC that was fine yesterday can be several tenths of a second off after a long uptime or after waking from sleep. If WSJT-X shows DT drifting for everyone, don't chase the radio first. Force a resync, or run something that polls an NTP server frequently. If you have no internet at a portable site, a GPS puck feeding the PC's time service does the job.

For sound cards: if you use a USB audio codec built into the radio, set both sample rates to the same value (48000 Hz is common) and disable Windows "enhancements" and system sounds on that device. Notification sounds going out on transmit are a classic embarrassment. Also keep the Windows output slider fixed and adjust only the WSJT-X Pwr control, so you know your reference point.

On the interface: a separate isolated interface with a transformer and a separate USB ground can cure hum or RF problems. A built-in USB codec avoids that wiring but ties your audio to the radio's own ground and cable routing, so you still need chokes. Neither approach is better in principle; test with a dummy load first and watch for errors or odd ALC behaviour.

  • Moderators

For picking a mode, ask what you want from the contact. If it is a quick log entry or country count on a marginal band, FT8 is efficient because the exchange is structured: callsign, a 4-character Maidenhead grid, a signal report, then 73. If you want to type to someone, JS8Call or PSK31 gives you that, while Olivia is for when conditions are rough and you accept a slow pace. WSPR is better for finding out where your signal goes than for working anyone. Run it for a few hours on a band, then check the spots on WSPRnet to compare antennas or time of day. Remember that WSPR reports your power in dBm, so the data is only useful if you enter the right figure.

Grid squares deserve a note, since they cause plenty of errors. Maidenhead locators go field (two letters), square (two digits), then subsquare (two letters), so FN31 is a 4-character grid and FN31pr is 6 characters. FT8 messages normally carry only 4 characters. If you are chasing VUCC-type awards or doing VHF weak-signal work, the 4-character grid is what you will log. Make sure you enter yours correctly in WSJT-X settings, because a typo sends wrong information with every CQ.

One caution on decode thresholds: the -21 dB figure is a measure against noise in a 2500 Hz bandwidth, not a promise. Fading, a bad DT or a drifting transmitter can make a signal much harder to decode than the number suggests. Treat the table of thresholds as a comparison between modes, not a guarantee for any particular contact.

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.