WSJT-X 2.0 — Why some FT8 stations don’t respond

Written by admin On November - 15 - 2018 Comments Off on WSJT-X 2.0 — Why some FT8 stations don’t respond

This is just a quick note for those trying to use FT8 after November 12, 2018 — remember that if you’re using WSJT-X version 1.9.1 or earlier, you may not be able to work stations using the latest release candidate of WSJT-X 2.0.

I have adopted WSJT-X 2.o RC4, which will no longer decode FT8 signals from people who aren’t using RC4 or one of the earlier release candidates unless the 77-bit payload message format is turned on.

From the WSJT-X notes about the new version 2.0 release candidates:

For the convenience of beta-testers, the first and second release candidates — releases with “-rc1” or “-rc2” in their names — will have Rx and Tx capability for both the new FT8 protocol and the older one. Starting with the third release candidate (“-rc3”), and in the general-availability full release of WSJT-X 2.0, only the new protocol will be supported.

Those of us using RC4 will operate FT8 about 2khz higher than the normal FT8 working frequencies. If you call and you don’t get a response, it’s likely because the station cannot decode your old-style (75-bit) FT8 signal. Consider updating your software to WSJT-X 2.0 RC4 and all will be well.

Older releases of WSJT-X will be officially obsolete as of December 10, 2018, when all users should be using the official release of WSJT-X 2.0.

Check it all out on the WSJT-x site

Contesting, DXing, General

Enjoy this Post? Share or cast your vote!

E-mail RSS Del.icio.us Digg Reddit Twitter

Comments are closed.