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

Digital modes troubleshooting: why you decode FT8 fine but nobody decodes you, and when to pick another mode

ci_cover.jpg

This thread is for sorting out the usual problems with weak-signal and keyboard digital modes: audio levels, time sync, CAT/PTT, and choosing a mode that suits the path. A common starting point is a station that shows a full waterfall and plenty of decodes in WSJT-X but gets few or no spots on PSK Reporter. Here is a rough checklist, then some mode-selection questions.

Receive working does not mean transmit is clean. In WSJT-X, set the rig to USB (or a data mode such as USB-D/DATA-USB, if your radio's data mode bypasses the mic EQ and processing). Turn off speech compression, noise reduction and any DSP that rewrites audio. Set the Tx audio so the ALC barely moves, then adjust output power at the rig. FT8 and FT4 are full-duty-cycle modes, so many operators run well below the rig's rated power to reduce heat and distortion. A splattery signal can look fine on your own meter and still be badly decoded by others.

Time is half the mode. FT8 transmits in 15-second periods, FT4 in 7.5-second periods, and decoding depends on both ends agreeing closely on the clock. The DT column in WSJT-X shows the offset between your clock and the received station's. If many stations show consistent DT offsets in the same direction, suspect your own PC clock. A dedicated sync tool, NTP/chrony, or a GPS-disciplined source is more dependable than relying on the operating system's default schedule.

CAT and PTT. CAT control lets the software read and set frequency and mode, and it can key the transmitter. Check the baud rate, port, and rig model, and decide whether PTT will come from CAT, a serial line (RTS/DTR), or VOX. VOX is a poor idea with digital modes because computer sounds can key the transmitter. In split operation, WSJT-X can use "Rig" or "Fake It" split to keep the audio tones in the best part of the passband. If your rig shifts audio filters or changes mode on its own, you may see distorted or offset signals.

Grid squares. FT8, FT4, WSPR and others commonly exchange a 4-character Maidenhead locator, such as FN31. The first two letters are the field, the two digits the square, and a 6-character locator adds a subsquare (FN31pr). A wrong grid in your settings will not stop you decoding, but it will give incorrect distance and spot information.

On decode thresholds: the quoted figures are signal-to-noise ratios referenced to a 2500 Hz noise bandwidth, not the bandwidth actually occupied by the signal. FT8 decodes down to about −20 dB on that scale, and FT4 needs a few dB more. WSPR can go roughly ten dB or more lower than FT8 because it uses a 2-minute period and a very narrow bandwidth. Slower modes buy sensitivity at the cost of exchange speed.

Questions for the thread: what do you reach for when FT8 is too slow or too crowded, and which mode fits which job (MSK144 for meteor scatter, Q65 for EME and scatter paths, JS8Call for keyboard messaging, or Winlink for emergency email)?

  • Replies 2
  • Views 66
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One thing worth separating is the "which mode" question from the "why isn't it working" question. The mode should follow the path and the purpose.

For general DX on HF, FT8 is the default because of the activity level, and FT4 is for contests where a 7.5-second cycle matters. JS8Call uses FT8-style modulation but adds free-text keyboard messaging with several speed settings. Its slower speeds trade throughput for sensitivity. It is good for casual messaging and relaying, but it is not a fast QSO mode.

For VHF and above, MSK144 is designed for meteor scatter: you are decoding short bursts and pings, so the software uses fast decoding and short messages. Q65 is intended for paths with fading or slow Doppler spread such as EME, tropo, ionoscatter and rain scatter, and it has multiple T/R period options. Pick the period according to the path rather than just the longest one, since longer periods need more stable timing and frequency.

WSPR is a beacon mode. It does not make contacts, but it is a very good propagation and antenna test. Run it for a while on one band and compare your spots with the numbers other stations get. It also tests whether your frequency stability and clock are good.

  • Moderators

On the older and keyboard modes, which have different problems from WSJT-X: PSK31 and RTTY are still used, and Olivia, MFSK and Hellschreiber have niches of their own.

PSK31 runs at 31.25 baud and is very narrow, so even a small amount of ALC distortion makes the signal wider and worse. Many operators keep power low. RTTY at 45.45 baud with a 170 Hz shift is common in contests, and it can be generated by AFSK from a sound card or by FSK keying where the rig supports it. FLDIGI handles these and many more, and it is a better choice than WSJT-X for any conversational mode.

Olivia and the MFSK family are built to work in poor conditions with forward error correction. Olivia gives you the option of different tone counts and bandwidths, and both ends must match the settings. Hellschreiber is a different approach: the receiver displays the characters as an image, so you read the text visually instead of relying on a decoder. It tolerates certain kinds of noise well, but it is slow and not suited to precise exchanges.

For Winlink, the radio side depends on the gateway. VARA HF/FM, ARDOP, packet and Pactor are all used, with VARA being a separate program with its own license terms. Whichever you choose, set up your sound card interface carefully: separate the audio paths if the rig has a dedicated data port, use isolation, and add ferrite chokes if RF is getting into the USB and audio leads. Most failures with these modes come from the interface level and RF feedback, not from the software.

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.