Digital modes troubleshooting: why you decode FT8 fine but nobody decodes you, and when to pick another mode
- Replies 2
- Views 66
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
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)?
Link to comment
https://www.hamradiobase.com/forums/topic/10817-digital-modes-troubleshooting-why-you-decode-ft8-fine-but-nobody-decodes-you-and-when-to-pick-another-mode/Share on other sites