FT8 Not Decoding? A Practical Checklist for Audio, Time and CAT Control
When WSJT-X shows an empty decode window on a band that should be busy, or the radio won't key, the cause is nearly always one of a handful of things: the clock, the audio levels, or the rig-control link. This checklist works through them in the order that saves the most time.
Step 1: Confirm the basics before touching settings
- Frequency and mode. Make sure the radio is on a standard FT8 frequency, such as 7.074 MHz on 40 m or 14.074 MHz on 20 m (USB, dial frequency), and that WSJT-X is set to FT8 rather than FT4 or another mode.
- Band conditions. A quiet waterfall may just mean the band is closed. Try a band you know is open at that time of day before assuming something is broken.
- Radio mode. Use USB-Data (or the equivalent) so the radio passes a flat audio response and doesn't apply voice processing.
Step 2: Fix your clock first
FT8 works in fixed 15-second slots, and the decoder only tolerates a small timing error between your computer and the station you're hearing. If the waterfall shows signals but nothing decodes, or you only decode some stations, suspect time. Many operators try to keep the clock within a fraction of a second.
- Check that automatic time sync is enabled in your operating system. Default Windows sync intervals can be long, so many operators install a dedicated time-sync utility that polls more often.
- On Linux and Raspberry Pi systems, a running NTP or chrony service normally handles this. On a Pi without a real-time clock, remember it relies on the network to get the time right after boot.
- WSJT-X displays the time offset (DT) of each decoded signal. If most stations show a consistent DT of the same sign and size, the error is probably on your side.
Step 3: Set receive audio levels
In WSJT-X, the level meter at the bottom left shows your incoming audio. The user guide suggests aiming for roughly 30 dB on the meter, and you should avoid anything in the red, which means clipping. Too little audio won't hurt decoding as much as too much will, because overdriven input distorts and spreads signals across the passband.
- Adjust the radio's USB audio output level or the operating system's input slider, not both at once.
- Turn off any audio enhancements, AGC-style processing, noise suppression or microphone boost on the sound device in your operating system.
- Set the sample rate to 48,000 Hz, 16-bit, if your system offers a choice.
- In Settings > Audio, check that the input device is the radio's codec and not a webcam, headset or built-in microphone. USB devices often appear with generic names such as "USB Audio CODEC", and the order can change after a reboot or when you plug into a different port.
Step 4: Get CAT control working
In Settings > Radio, WSJT-X uses the Hamlib library to talk to most transceivers. Choose your rig model, serial port, baud rate, data bits, stop bits and handshake to match the radio's menu settings, then press Test CAT. The button turns green when the link works and red when it doesn't.
If it stays red, check in this order:
- Baud rate mismatch. The radio's CAT or CI-V speed must match what WSJT-X is set to. Some radios also have an auto setting that can cause trouble.
- Wrong COM port. USB-serial adapters can be renumbered by Windows. Check Device Manager or, on Linux, the device list under
/dev/serial/by-id, which is more stable thanttyUSB0style names. - Port in use. Only one program can open a serial port at a time. If a logger, rig-control program or another digital program already holds it, WSJT-X can't connect.
- Driver problems. Many radios use common USB-serial chips. A missing or outdated driver often shows up as a port that vanishes or can't open.
- Radio-side settings. Some radios need CAT enabled, a particular USB or serial function selected, or a CI-V address set to match.
Step 5: Sort out PTT and split
PTT can be keyed by CAT command, RTS or DTR serial lines, or VOX. CAT is usually the simplest on modern radios with built-in USB. Use Test PTT to confirm the radio actually keys before you try a real transmission, ideally into a dummy load.
The Split Operation setting matters more than people expect. WSJT-X is designed to keep your audio tone in a sweet spot (roughly 1500 Hz) while the dial moves. Choosing Rig uses the radio's true split mode, while Fake It retunes the dial around transmissions. If the transmitted signal looks distorted or your radio keeps retuning, try the other option.
Step 6: Don't overdrive the transmitter
FT8 is a constant-envelope mode, but your audio chain still has to be linear. The usual approach:
- Set the radio to a modest power level.
- Use WSJT-X's Pwr slider and your computer's output volume to bring up drive until you see just a hint of ALC movement, then back it off so ALC reads zero or near it.
- Remember that more audio does not mean more power in a clean signal. It means splatter that annoys neighbors on the band.
- Mute system sounds, notifications and other applications so nothing unintended goes out over the air.
Step 7: Check whether anyone hears you
Once you're transmitting, PSK Reporter is a handy independent check. Enable spotting under Settings > Reporting, then look up your callsign on the PSK Reporter website to see which stations reported you and where. Your grid square needs to be correct in WSJT-X for the map to make sense. Spots appearing within a few minutes tell you the whole chain is working; no spots on a band that other stations clearly use points to an antenna, power or audio issue.
For CW and RTTY, the Reverse Beacon Network does a similar job for those modes, though it won't see FT8.
Step 8: Share the radio with logging software
A common trouble spot is running WSJT-X alongside N1MM+ or Log4OM. Both of those programs normally want to control the radio too. Options include:
- Let WSJT-X own the serial port and have your logger read frequency and mode from it via UDP rather than direct CAT.
- Use a rig-control middleman, such as a program that shares the radio between several applications through virtual serial ports.
- Use the radio's second virtual port if it provides one.
For logging, WSJT-X can broadcast its decodes and logged QSOs over UDP, which loggers and helper tools can read. Check that the UDP server address and port match on both ends, and that no firewall is blocking them.
A quick diagnostic table
- Waterfall looks fine, no decodes: clock, wrong mode, or audio level too high.
- Waterfall is blank: wrong input device, muted input, or radio not in USB-Data.
- Test CAT is red: baud rate, COM port, driver or another program using the port.
- Radio keys but no output: output device set to the wrong sound card, or audio muted.
- Transmits but no spots: band closed, wrong grid, or no reporting enabled.
Final thoughts
Change one thing at a time and re-test after each change. Writing down the settings that work once you have a stable setup saves a lot of grief after an operating system update or a new USB port shuffles your devices. If you run a Raspberry Pi or a dedicated shack PC, consider documenting the device names and baud rates somewhere you can find them in a hurry.
Recommended Comments