Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base -Powered By Ham CQ DX

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.
Solar
SFI 128
SN 73
A 6
K 1 Quiet
X-Ray B7.8
Wind 387.9 km/s
Aurora 3
Updated 01:00 UTC HamQSL · N0NBH
Day 80/40m Fair 30/20m Good 17/15m Good 12/10m Fair
Night 80/40m Good 30/20m Good 17/15m Good 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

WSJT-X time sync issues causing FT8 decode failures

Running into frustrating decode issues with WSJT-X where I'm seeing signals on the waterfall but getting zero decodes. FT8 and FT4 depend on computer time being very accurate and synced with NTP - shouldn't be out more than 0.4 seconds. Windows built-in NTP client can have issues syncing better than 0.6 seconds, so many FT operators use Meinberg NTP Package or Dimension 4. Each FT8 transmission must begin exactly at 00, 15, 30, 45, or 60 seconds - if station clock isn't synchronized, messages will fail to decode. What's everyone's preferred time sync solution for rock-solid operation?

  • Replies 2
  • Views 220
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

Meinberg NTP Package is the current preferred option - been using it for over a year with zero timing issues. The built-in Windows sync is garbage for precision timing applications. Install Meinberg and your decode problems will disappear.

Check your DT column in WSJT-X during receive periods. If you're seeing consistent +/- values beyond 0.5 seconds, that's your smoking gun. When using FT8 and receiving contacts, look at the DT column to verify timing alignment.

Had this exact problem last month! Switched from Windows time sync to Meinberg and went from 10% decode rate to 95% overnight. Also helped that most FT8 users take advantage of online time servers using NTP or GPS signals for automatic time accuracy.

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

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.