FT8 troubleshooting
FT8 could not start#
The message FT8 could not start: β¦ means the decoder didn't load. Reload the page (Ctrl+F5 to bypass the cache). The client checks for updated decoder files each time the tab first opens, so a reload picks up a new version.
No receive audio yet#
The waterfall says No receive audio yet and the chip shows RX waiting or RX off.
- Connect the radio on the Radio tab first, and check you can hear it. FT8 uses that audio stream.
- Check the RemoteTx main Audio tab to see that audio is activated and levels are correct. (Click Green Restart Audio button.)
- Click Start monitoring (or Monitor).
- In Settings β Audio, Input should be RemoteTx audio (radio).
Signals on the waterfall, but no decodes#
- Make sure the radio is in Upper Side Band. (WebFT8 client does not set or change radio mode setting.)
- Clock. Check your computer's clock against UTC (for example at time.is). More than about 1 s off and FT8 won't decode. On Windows run
w32tm /resyncas administrator. - Level. The meter should read about β40 to β25 dBFS. Too low or overloaded both hurt decoding. Adjust the radio's audio output or Input gain.
- Radio filter. Use a wide (about 3 kHz) filter in the data mode, with no noise reduction or noise blanker.
- Range. Check Low Hz / High Hz in Decoding cover where the signals are.
DT values are all around +0.3 to +0.5#
The radio audio comes over the Internet with a small delay. If decoded DT values are consistently offset, set Rx time offset in Decoding: e.g. +400 ms for DTs around +0.4.
Nothing happens when I transmit#
- The PTT chip must be green (PTT RemoteTX). A β means the radio isn't connected on the Radio tab.
- My Call must be set (the chip shows No callsign otherwise).
- Check Enable Tx is on and a message is selected under Next.
- Use Settings β Radio β Test PTT and then Tune to check the radio keys and puts out power.
- Keep the FT8 tab or its pop-out window visible while transmitting.
The radio keys but there's little or no power#
- The radio Mod-Source setting must be USB not Mic.
- Raise Tx level in the top bar (or Settings β Audio). Use Tune and watch the radio's power and the ALC meter.
- Check the radio's USB audio input level menu.
The ALC meter turns amber or red#
The transmit audio is too loud for the radio, which distorts your FT8 signal. Lower Tx level in the top bar (mouse wheel, 1 dB per notch) until the bar is green. If the power then drops too far, check the radio's USB audio input level menu, and its power setting.
Queue Multiple Callers isn't on the screen#
It only shows while Auto Answer on CQ is ticked. Tick Auto Answer on CQ, and Queue Multiple Callers appears below it; tick that, and Tries and Reports first appear under it.
A Queue Multiple Callers run stopped by itself#
- Enable Tx went off: the Tx watchdog pauses runs too, after its time without you touching the controls (6 minutes by default). Click Enable Tx and the run carries on with the same queue. Setting Tx watchdog to 0 disables it. See Settings β Sequencing.
- Halt Tx, double-clicking a station, or unticking Auto Answer on CQ or Queue Multiple Callers ends the run on purpose.
- A queued station is dropped if it doesn't answer within Tries overs. With nobody else waiting, the client calls CQ again, and keeps the run going for the next caller.
The other station doesn't hear me / I keep calling#
- Make sure you're transmitting in the opposite period to them (double-clicking sets this; check Tx even/1st).
- Try another Tx Hz in a clear part of the waterfall.
- Check power and ALC with Tune.
The logger doesn't see the FT8 tab#
- There's no Logger chip: click EC on the Radio tab and check that RTx EasyConnect is running on this computer.
- Logger off (amber): turn on WSJT-X UDP and/or N1MM broadcasts in EasyConnect's FT8 β loggers card.
- The logger's double-click doesn't call the station: tick Accept UDP requests in EasyConnect, and see its README for firewall and multicast settings.