FT8 Not Decoding? A Practical Checklist for WSJT-X, Audio, and CAT Control
When FT8 misbehaves, the symptoms are vague: the waterfall looks fine but nothing decodes, the radio keys but nobody answers, or WSJT-X loses the rig halfway through a session. The cause is almost always one of four things: time, audio, CAT/PTT, or reporting. Work through them in that order and most problems disappear.
1. Check your clock first
FT8 runs in fixed 15-second cycles, and both stations must agree on where those cycles begin. If your computer clock is off by more than about a second, you will miss decodes, and other stations will miss you. Look at the DT column in the decode window. Most stations should show values near zero. If nearly everyone shows a similar offset, such as +1.0 or -0.8, the problem is your clock, not theirs.
- Make sure automatic time sync is enabled in your operating system.
- Use a dedicated time-sync utility if your OS only syncs occasionally.
- On a Raspberry Pi, confirm that an NTP service such as chrony or systemd-timesyncd is running and has actually synchronized. Pis have no battery-backed clock, so a headless Pi with no network can drift or start with the wrong time.
2. Get the audio path right
If the waterfall is blank or flat, WSJT-X is listening to the wrong input. Open File > Settings > Audio and select the radio's USB audio device or your external interface for both input and output. Then check these points:
- Sample format: In your operating system's sound settings, use 48000 Hz, 16-bit for the device if you have the choice.
- Disable audio extras: Turn off system sounds, enhancements, and anything that might route notifications through the radio's audio device. A stray alert tone going out on the air is a common and embarrassing mistake.
- Receive level: The WSJT-X level meter should sit roughly around the middle, with the User Guide suggesting about 30 dB. Too low and weak signals vanish. Too high and you risk clipping on strong ones.
- Radio settings: Use USB or the radio's data mode (often labeled USB-D, DATA, or PKT), keep the receive filter wide enough for the whole 200 to 3000 Hz range, and turn off noise reduction, notch filters, and speech processing. These can damage digital signals.
If the waterfall shows signals but nothing decodes, suspect time first, then confirm you are on the right mode and sideband. FT8 and FT4 are different modes with different sub-bands and timing. A common FT8 frequency on 20 meters is 14.074 MHz, but verify the current band plan for your region before transmitting.
3. Transmit audio: less is more
Many new digital operators overdrive their transmitters. FT8 is a constant-envelope mode, so a clean signal does not need much drive. Set the radio to a modest power level, then adjust the WSJT-X output slider until the ALC meter barely moves or stays at zero. If the ALC is working hard, the signal is being distorted, which creates splatter and lowers your decode rate at the other end.
Also remember that FT8 transmits for most of the cycle, so the duty cycle is far higher than SSB. Running a radio at full rated power for long periods can overheat it. Backing off to a fraction of rated output is good practice and often costs you very little in practical results.
4. CAT control and PTT
CAT lets WSJT-X read and set frequency, mode, and PTT through the radio's serial or USB connection. Under Settings > Radio, choose your rig from the list, select the correct serial port, and match the baud rate to the radio's menu setting. Then click Test CAT. A green button means communication works. Test PTT separately, since a rig can accept frequency commands and still fail to key.
Typical failure points:
- Port conflicts: Only one program can normally open a serial port. If a logger or rig-control program already has it, WSJT-X cannot connect. Either let one program own the port and share it through Hamlib's rigctld, or use a virtual serial port tool.
- Wrong port after reboot: USB port numbers can change. Recheck the COM port or
/dev/ttyUSBdevice name if things worked yesterday and fail today. - Baud mismatch: The radio and software must use the same rate. Some radios also have a separate CI-V or CAT rate setting for USB.
- Split operation: Under Radio, choose Rig or Fake It to keep your audio tones in the radio's cleanest range. Avoid None if your transmit audio frequency sits high in the passband, because harmonics may leak outside the intended channel.
- RF in the shack: If CAT drops out only when you transmit, you probably have RF getting into the USB cable or interface. Ferrite chokes, better grounding, and a decent common-mode choke on the antenna feedline often cure this.
For PTT, CAT PTT is simplest when it works. Otherwise use a serial line (RTS or DTR) on an interface that supports it, or VOX if you must. VOX is less predictable with computer audio, though.
5. Confirm your signal with PSK Reporter
Once you transmit, the easiest reality check is PSK Reporter. In WSJT-X, enable PSK Reporter spotting on the Reporting tab. Then search for your callsign on the PSK Reporter map to see who is hearing you, on which band, and at what signal level. If you transmit for several cycles and nobody reports you, check antenna, band conditions, power, and whether the radio is actually outputting RF.
Do not confuse this with the Reverse Beacon Network. RBN uses skimmer receivers mainly for CW and RTTY, so it is the right tool for those modes, but it will not show your FT8 signal. For FT8, JS8Call, and similar modes, PSK Reporter is the usual feedback tool.
6. Make your logger cooperate
WSJT-X can write an ADIF log and broadcast QSO information by UDP, which loggers such as Log4OM can use. If contacts do not appear in your logger, check that the UDP server address and port match on both sides and that your firewall is not blocking local traffic. For contest software such as N1MM+, there are supported ways to work with digital modes, but setup varies by version, so check the current documentation. Avoid running two programs that both try to control the radio unless you have deliberately planned how they will share the CAT connection.
A quick diagnostic order
- Is the clock synchronized, and do DT values cluster near zero?
- Does the waterfall show signals, and is the input level reasonable?
- Is the radio in the right data mode on a legitimate FT8 frequency?
- Does Test CAT pass, and does PTT key the rig?
- Is ALC quiet and power conservative?
- Does PSK Reporter show you being heard?
The same logic carries over to JS8Call, Winlink soundcard modems, and packet or APRS TNC setups. Time sync, clean audio levels, reliable PTT, and a single owner for the CAT port are the foundation of nearly every digital station. Fix those, and the software side of the hobby becomes much more predictable.
Recommended Comments