1. Introduction

WSJT-X icon MAP65 icon QMAP icon

WSJT-X is an open source computer program designed to facilitate basic amateur radio communication using very weak signals. The first four letters in the program name stand for “Weak Signal communication by K1JT,” while the suffix “-X” indicates that WSJT-X started as an extended branch of an earlier program, WSJT, which was first released by Joe Taylor, K1JT, in 2001. Bill Somerville, G4WJS, Steve Franke, K9AN, and Nico Palermo, IV3NWV, have been major contributors to development of WSJT-X since 2013, 2015, and 2016, respectively. Bill Somerville died unexpectedly in December 2021; Uwe Risse, DG2YCB, joined the core development team soon afterward and worked with us until February 2026. Brian Moran, N9ADG, joined the team in 2022; John Nelson, G4KLA and Charlie Suckling, DL3WDG in 2024; Roger Rehr, W3SZ, in 2025; and Terrell Deppe, KJ5HST, and David Christle, KD0BTO, in 2026. Over the years many other hams have contributed to WSJT-X development in more limited ways. We are extremely grateful for all of these contributions.

WSJT-X provides flexible rig control for nearly all modern radios used by amateurs and a wide variety of special aids such as automatic Doppler tracking for Earth-Moon-Earth (EME) QSOs and lunar-Echo testing. The program analyzes received passbands up to 5 kHz wide and runs equally well on Windows, Macintosh, and Linux systems.

MAP65 and QMAP are companion programs originally written by K1JT to facilitate Earth-Moon-Earth (EME, or "Moonbounce") communication with digital protocols developed for WSJT and WSJT-X. When used with radio-frequency hardware providing coherent signal channels for two orthogonal polarizations, MAP65 can yield automatic polarization-matched reception for every JT65 or Q65 signal in a 90 kHz sub-band. QMAP uses a single polarization channel and only the Q65 mode, also covering a 90 kHz sub-band. It works cooperatively with WSJT-X to provide automatic Doppler compensation and other features important for EME, especially on 1296 MHz and higher amateur bands. These programs are installed automatically along with WSJT-X.

Version Numbers for our programs have major, minor, and patch numbers separated by periods: for example, WSJT-X 3.0.0. Temporary release candidates are sometimes made in advance of a new general-availability (GA) release, in order to obtain user feedback. Release candidates are given version labels such as 3.0.0-rc1, 3.0.0-rc2, etc., leading up to the general availability (GA) release of version 3.0.0. Release candidates should be used only during a defined testing period, and they carry an implicit obligation to provide feedback to the program developers. Release candidates should not be used on the air after a GA release with the same number.

Hamlib is an independent, open-source software library that provides a consistent Application Programming Interface (API) for computer control of radios used by hams. Hamlib is essential to all features of WSJT-X that control your radio, and the latest stable version is included with all of our program releases. Like WSJT-X, Hamlib is under constant development by a group of volunteers. When necessary — perhaps when you acquire a very new radio — you can update your active Hamlib version from within WSJT-X.

1.1. New in Version 3.2

  • JTTY is an entirely new digital mode designed for fast RTTY-like contest exchanges and other keyboard-to-keyboard communication. Its operational feel is similar to standard RTTY, but it has much better weak-signal performance and far lower error rate. JTTY transmissions can start at any time and typically last a few seconds. Error-free throughput is about 30 words per minute for arbitrary text and 60 WPM for the short, fixed-format messages generally used in RTTY-style contesting.

  • MAP65 adds support for 192 kHz sample rate and a new JT65 Full Deep Search mode. JT65 false decodes are substantially reduced, and Q65 decoding sensitivity significantly improved for both single and dual polarization signals. A number of smaller improvements and bug fixes are present. We note that the MAP65 User’s Guide is out-of-date, but still useful. This document is being thoroughly revised, and we hope to make a new version available soon.

  • QMAP now displays decoded callsigns superimposed on its waterfall. An optional vertical waterfall displays callsigns to its right, without obscuring the signal traces. Clicking a callsign in either waterfall sets up (and double-clicking starts) a QSO with that station, with the QSO subsequently conducted in a co-running copy of WSJT-X. A new Stop button ends a Shift+F6 file sequence, as in WSJT-X and MAP65. See QMAP in this guide for more details.

  • Q65 Pileup Mode: a previously unused message bit now indicates whether the station being called was copied in the previous Rx interval. Decodes with this bit set are flagged with "#" in the decoded text window and in the Active Stations window. Everything needed is exchanged over the air; no internet connection is required.

  • Raspberry Pi and other ARM-based computers: pre-built 32-bit (armhf) as well as 64-bit (aarch64) packages are available. Projects such as DigiPi, which runs WSJT-X on the Pi Zero 2 W, can install the current release without building from source.

  • Decoded text panes now keep their scroll position while you review earlier decodes. New decodes will continue to accumulate below, and the pane returns to live output when you scroll back to the end.

  • Highlight orange and Highlight blue prefix lists now accept wildcards (*) and exclusions (!).

  • TX Inhibit for multi-op contesting: with a UDP connection, an external controller can block WSJT-X from transmitting when another transmitter is active on the same band.

  • WSPR and FST4W now upload spots to wsprnet.eu as a backup. Queued spots are preserved across retries when WSPRnet is slow or unavailable.

  • CloudLog and Wavelog integration has been improved, and eQSL uploads now use a secure protocol to protect your login credentials.

  • Band Activity shows U.S.A. and the correct state for a K-family callsign operating portable from a different state, instead of the DXCC entity of the callsign’s home area.

  • Settings dialogs are more accessible, and keyboard navigation and focus handling are improved. Dialogs are laid out responsively rather than clipping controls on constrained window sizes or large accessibility fonts. Decode panes and the startup splash screen are properly named for use with assistive technology.

  • German, Polish, and Ukrainian translations of the user interface have been added, and the Spanish translation updated.

  • Copyright notice and Trademark policy selections have been added to the Help menus for WSJT-X, MAP65, and QMAP, and new icons are used for all three programs.

  • Many other smaller improvements and bug fixes. See the Release Notes for details.

1.2. Documentation Conventions

This guide includes many screen shots to illustrate user settings and program features. Keep in mind that WSJT-X is a multi-platform application; the detailed appearance of windows and user controls will be different in Windows, Linux, or macOS environments. The underlying functionality is the same on all operating systems, however. Where desirable we call special attention to important platform differences.

Most people access the WSJT-X User Guide primarily through a browser. Use the browser’s search function, generally invoked from the keyboard with the keys CTRL+F, to search the guide for help on a particular topic or keyword.

The names of WSJT-X windows, menus, and on-screen controls are displayed in this manual in boldface type, as in Wide Graph. File names and information entered via keyboard is shown in a monospace font, for example all.txt.

In this manual the following icons call attention to particular types of information:

Tips on program features or capabilities that might otherwise be overlooked.
Notes containing information that may be of interest to particular classes of users.
Warnings about usage that could lead to undesired consequences.

1.3. Other Languages

The WSJT-X user interface (UI) is now available in many languages. When a translated UI is available for the computer’s default System Language, it will appear automatically on program startup. The UI language may be overridden if desired by starting WSJT-X with a command line option. For example, to start WSJT-X with its user interface in Spanish or Japanese, start a command-prompt window and enter one of these the commands:

wsjtx --language es

wsjtx --language ja

The top portion of the main window will then look like one of the following examples:

Main Window es
Main Window ja

1.4. Contributing

WSJT is an open-source project hosted at GitHub. If you have programming or documentation skills or would like to contribute to the project in other ways, please make your interests known to the development team. You can submit bug reports, suggestions for new features, and explicit pull requests at the GitHub site. We especially encourage those with translation skills to volunteer their help, either for this User Guide or for the program’s user interface.

1.5. License

WSJT-X, MAP65, and QMAP are free software intended for communication by Amateur Radio. Copyright © 2001-2026 by Joseph Taylor, K1JT, and the WSJT Development Team.

You can redistribute and/or modify these programs under the terms of Version 3 of the GNU General Public License as published by the Free Software Foundation. The programs are distributed in the hope that they will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

2. Modes

WSJT-X offers twelve different protocols or modes: FST4, FT4, FT8, JT4, JT9, JT65, Q65, MSK144, JTTY, WSPR, FST4W, and Echo. The first eight are designed for making reliable QSOs under weak-signal conditions. They use nearly identical message structure and source encoding. JT65 was designed for EME (“moonbounce”) on VHF and higher bands and is mostly used for that purpose today. Q65 is particularly effective for tropospheric scatter, rain scatter, ionospheric scatter, TEP, and EME on VHF and higher bands, as well as other types of fast-fading signals. JT9 was designed for the HF and lower bands. Its submode JT9A is 1 dB more sensitive than JT65 while using less than 10% of the bandwidth. JT4 offers a wide variety of tone spacings and has proven highly effective for EME on microwave bands up to 24 GHz. The “slow” modes use timed sequences of alternating transmission and reception. JT4, JT9, and JT65 use one-minute sequences, so a minimal QSO takes four to six minutes — two or three transmissions by each station, one sending in odd UTC minutes and the other even. FT8 is four times faster (15-second T/R sequences) and less sensitive by a few dB. FT4 is faster still (7.5 s T/R sequences) and especially well-suited for radio contesting. FST4 is designed especially for the LF and MF bands. Both FST4 and Q65 offer a wide variety of timed sequence lengths, and Q65 a range of tone spacings for different propagation conditions. On the HF bands, world-wide QSOs are possible with any of these modes using power levels of a few watts (or even milliwatts) and compromise antennas. On VHF bands and higher, QSOs are possible (by EME, scatter, and other propagation types) at signal levels 10 to 15 dB below those required for CW.

MSK144, and optionally submodes JT9E-H are “fast” protocols designed to take advantage of brief signal enhancements from ionized meteor trails, aircraft scatter, and other types of scatter propagation. These modes use timed sequences of 5, 10, 15, or 30 s duration. User messages are transmitted repeatedly at high rate (up to 250 characters per second for MSK144) to make good use of the shortest meteor-trail reflections or “pings”. MSK144 uses the same structured messages as the slow modes and optionally an abbreviated format with hashed callsigns.

Note that some of the modes classified as slow can have T/R sequence lengths as short as the fast modes. “Slow” in this sense implies message frames being sent only once per transmission. The fast modes in WSJT-X send their message frames repeatedly, as many times as will fit into the Tx sequence length.

JTTY is designed for fast radio contest exchanges and other keyboard-to-keyboard communication. Its operational feel is similar to standard RTTY, but it has much better weak-signal performance and far lower error rate. JTTY transmissions are not timed or synchronized with UTC; they can start at any time and have any duration, but typically last for a few seconds.

WSPR (pronounced “whisper”) stands for Weak Signal Propagation Reporter. The WSPR protocol was designed for probing potential propagation paths using low-power transmissions. WSPR messages normally carry the transmitting station’s callsign, grid locator, and transmitter power in dBm, and with two-minute sequences they can be decoded at signal-to-noise ratios as low as -31 dB in a 2500 Hz bandwidth. FST4W is designed for similar purposes, but especially for use on LF and MF bands. It includes optional sequence lengths as long as 30 minutes and reaches sensitivity thresholds as low as -45 dB. Users with internet access can automatically upload WSPR and FST4W reception reports to a central database called WSPRnet that provides a mapping facility, archival storage, and many other features.

Echo mode allows you to detect and measure your own station’s echoes from the moon and to make other measurements useful for optimizing your EME station’s performance.

3. System Requirements

  • SSB transceiver and antenna

  • Computer running Windows 10 or later, macOS 13 or later, or Linux

  • 1.5 GHz or faster CPU and 200 MB of available memory; faster machines are better

  • Monitor with at least 1024 x 780 resolution

  • Computer-to-radio interface using a serial port or equivalent USB device for T/R switching, or CAT control, or VOX, as required for your radio-to-computer connections

  • Audio input and output devices supported by the operating system and configured for sample rate 48000 Hz, 16 bits

  • Audio or equivalent USB connections between transceiver and computer

  • A means for synchronizing the computer clock to UTC within ±1 second

4. Installation

Installation packages for Windows, Linux, and macOS are found on the WSJT Downloads Page.

4.1. Windows

For 64-bit Windows 10 and later: Download and execute the package file wsjtx-3.2.0-rc1-win64.exe. Install WSJT-X into its own directory, for example C:\WSJTX or C:\WSJT\WSJTX, rather than the conventional location
C:\Program Files …​\WSJTX. All program files relating to WSJT-X will be stored in the chosen installation directory and its subdirectories. Logs and other writeable files are normally found in the directory
C:\Users\<username>\AppData\Local\WSJT-X.

Your computer may be configured so that this directory is “invisible”. It’s there, however, and accessible. An alternative (shortcut) directory name is "%LocalAppData%\WSJT-X\".
  • The built-in Windows facility for time synchronization may not be adequate. We recommend the program Meinberg NTP Client: see Network Time Protocol Setup for downloading and installation instructions. Recent versions of Windows are now shipped with a more capable Internet time synchronization service that is suitable if configured appropriately. We do not recommend SNTP time setting tools or others that make periodic correction steps; WSJT-X requires that the PC clock be monotonically increasing and smoothly continuous.

Having a PC clock that appears to be synchronized to UTC is not sufficient. “Monotonically increasing” means that the clock must not be stepped backwards. “Smoothly continuous” means that time must increase at a nearly constant rate, without steps. Any necessary clock corrections must be applied by adjusting the rate of increase, thereby correcting synchronization errors gradually.
  • WSJT-X uses the OpenSSL libraries for TLS network connections. Current WSJT-X Windows installers include the required OpenSSL runtime DLLs. If they are missing or cannot be loaded, you may see the following error message when using features such as SuperFox verification, Update Hamlib, LoTW downloads, or eQSL uploads.

SSL/TLS

If you installed WSJT-X from the official Windows installer, first try updating to the latest installer package. Reinstalling the same package may help if files in the local installation were removed or damaged. The OpenSSL DLLs must match the Qt libraries used to build the program and are normally installed with WSJT-X, so installing unrelated system-wide OpenSSL DLLs is not the recommended fix.

If you cannot update or reinstall WSJT-X, or do not have an Internet connection on the computer used to run WSJT-X 3.2, you can download the LoTW file manually. Go to https://lotw.arrl.org/lotw-user-activity.csv in a web browser, download the file, then move it to the WSJT-X log files directory. This directory can be opened by selecting File|Open log directory from the main menu.
  • WSJT-X expects your sound card to do its raw sampling at 48000 Hz. To ensure that this will be so when running under recent versions of Windows, open the system’s Sound control panel and select in turn the Recording and Playback tabs. Click Properties, then Advanced, and select 16 bit, 48000 Hz (DVD Quality). Switch off all audio enhancement features for these devices.

  • You can uninstall WSJT-X by clicking its Uninstall link in the Windows Start menu, or by using Uninstall a Program on the Windows Control Panel | Programs and Features option or in File | Settings | Apps.

4.2. Linux

You can use WSJT-X on any 64-bit Linux system by downloading and executing the appropriate "AppImage" file from the WSJT Downloads Page. These packages contain all required dependencies for use of WSJT-X, but they do not provide access to MAP65, QMAP, or any of the related utility programs.

Complete installation packages are provided on the WSJT Downloads Page for 64-bit Debian-based and RedHat-based Linux systems. Be sure to fetch the package built for your machine’s architecture: it will have x86_64 in the file name for Intel/AMD machines, aarch64 for ARM.

  • To install on Debian-based Linux, for example Ubuntu 22.x or later, execute the following command in a terminal:

    sudo dpkg -i <package-name>
  • To uninstall:

    sudo dpkg -P wsjtx

You may also need to execute the following command in a terminal:

sudo apt install libgfortran5 libqt5widgets5 libqt5network5 \
     libqt5printsupport5 libqt5multimedia5-plugins libqt5serialport5 \
     libqt5sql5-sqlite libfftw3-single3 libgomp1 libboost-all-dev \
     libusb-1.0-0 libportaudio2
  • To install on Fedora, CentOS, Red Hat, and other rpm-based systems:

    sudo rpm -i <package-name>
  • To uninstall:

    sudo rpm -e wsjtx

You may also need to execute the following command in a terminal:

sudo dnf install libgfortran fftw-libs-single qt5-qtbase \
     qt5-qtmultimedia qt5-qtserialport qt5-qtsvg \
     qt5-qtserialport libgomp boost libusbx portaudio

4.3. MacOS

For macOS installers are provided for x86_64 (Intel) systems and for ARM64 (Apple silicon) systems. Download the correct package for your system from the WSJT Downloads Page, double-click on the file name, and follow the on-screen prompts in the Installer app.

If you have already installed a previous version, you can retain it by changing its name in the Applications folder (such as from WSJT-X to WSJT-X_3.0). You can then proceed to the installation phase.

Take note also of the following:

  • Use the Mac’s Audio MIDI Setup utility to configure your sound card for 48000 Hz, two-channel, 16-bit format.

If you are using macOS with an external audio device and find that Tx audio spontaneously switches to the motherboard sound device after a few transmissions, try setting the sample rate to 44100 Hz rather than the otherwise recommended 48000 Hz.
  • Use System Preferences to select an external time source to keep your system clock synchronized to UTC.

  • To uninstall simply drag the WSJT-X application from Applications to the Trash Can.

4.4. Building from source

This guide is for developers building WSJT-X, MAP65, or QMAP from source. To install and operate a released version instead, use the platform packages from the official GitHub Releases page.

4.4.1. Know which build you need

The same source can be built for several different purposes. Choose the simplest path that answers your question:

Goal Appropriate path

Edit, compile, and test locally

Use the platform package manager and the instructions in this chapter.

Exercise an installed layout or create an unsigned package

Complete the local build, then use the CMake install or package target.

External contributors should fork the public repository; core team members should use the private development branch assigned to their work. The contribution guide explains the repository model and pull-request workflow.

4.4.2. Common requirements

All platforms require:

  • Git and CMake 3.20 or later for the commands as written. The project configuration retains CMake 3.12 as its minimum for older build environments. With CMake 3.12, replace cmake -S . -B build with mkdir -p build && (cd build && cmake ..). With CMake 3.12 through 3.19, replace ctest --test-dir build --output-on-failure with (cd build && ctest --output-on-failure).

  • Qt 5 Core, Widgets, Network, Multimedia, SerialPort, PrintSupport, Sql, LinguistTools, and WebSockets; Test when developer tests are enabled; and ActiveQt AxContainer on Windows

  • C and C compilers with C17 support

  • a Fortran compiler, normally gfortran

  • FFTW 3, including the single-precision libfftw3f library

  • Boost, libusb, and PortAudio

  • the Hamlib revision selected by the project’s CI configuration

CMake enables developer tests and User Guide generation by default. User Guide generation requires Asciidoctor. If you do not need the local guide, configure with -DWSJT_GENERATE_DOCS=OFF.

Use an out-of-source build directory. This keeps generated files out of the source tree and makes a clean reconfigure as simple as choosing a new directory.

4.4.3. Building on Windows with MSYS2

The supported Windows developer environment is MSYS2 MINGW64. MSYS2 supplies the compiler, Qt, CMake, and most libraries through its signed package repositories. WSJT-X builds the CI-selected Hamlib revision separately.

The project intentionally uses MINGW64 as its current Windows compatibility contract. Do not substitute the MSYS, UCRT64, CLANG64, or another MSYS2 shell: package names, binary formats, paths, and supported Windows APIs can differ.

The MSYS2 Boost package is suitable for local development. Official Windows builds use a separate Boost configuration to support older Windows versions; see .github/workflows/build-windows.yml.
Install and update MSYS2
  1. Download and run the installer from https://www.msys2.org. The default location, C:\msys64, is suitable.

  2. Open the MSYS2 MINGW64 shell.

  3. Update the base system:

pacman -Syu

MSYS2 may ask you to close the terminal during a core update. Close it, reopen MSYS2 MINGW64, and run pacman -Syu again until no further core update is required.

Every command in the remainder of the Windows section runs in that MINGW64 shell. Confirm the environment before installing packages:

echo "$MSYSTEM"

The result must be MINGW64.

Install the local-development dependencies

Install the compiler, build tools, and libraries:

pacman -S --needed \
  git make tar autoconf automake libtool \
  mingw-w64-x86_64-gcc \
  mingw-w64-x86_64-gcc-fortran \
  mingw-w64-x86_64-cmake \
  mingw-w64-x86_64-qt5-base \
  mingw-w64-x86_64-qt5-multimedia \
  mingw-w64-x86_64-qt5-serialport \
  mingw-w64-x86_64-qt5-svg \
  mingw-w64-x86_64-qt5-tools \
  mingw-w64-x86_64-qt5-websockets \
  mingw-w64-x86_64-qt5-activeqt \
  mingw-w64-x86_64-fftw \
  mingw-w64-x86_64-boost \
  mingw-w64-x86_64-libusb \
  mingw-w64-x86_64-openssl \
  mingw-w64-x86_64-portaudio \
  mingw-w64-x86_64-pkg-config

User Guide generation is enabled by default. Install Ruby and Asciidoctor if you want the guide included in the build:

pacman -S --needed mingw-w64-x86_64-ruby
gem install asciidoctor --no-document

If you skip these tools, add -DWSJT_GENERATE_DOCS=OFF to the CMake command in the configure section. The application and automated tests do not require a locally rendered User Guide.

NSIS is required only when creating an unsigned Windows installer:

pacman -S --needed mingw-w64-x86_64-nsis

Check that the MINGW64 programs, rather than programs from another Windows toolchain, will be used:

missing_tools=0
for tool in gcc g++ gfortran cmake qmake-qt5 dumpcpp-qt5; do
  command -v "$tool" || { echo "MISSING: $tool"; missing_tools=1; }
done
if test "$missing_tools" -eq 0; then
  gcc --version
  gfortran --version
  cmake --version
else
  echo "Install the missing tools before continuing." >&2
  false
fi

The MinGW programs should resolve under /mingw64/bin. Do not continue until the check reports a path for every tool and no MISSING line.

Clone the source

Clone from inside the MINGW64 shell. These commands use a predictable workspace under the MSYS2 home directory:

mkdir -p ~/wsjtx-dev
cd ~/wsjtx-dev
git -c core.autocrlf=false -c core.longpaths=true \
  clone https://github.com/WSJTX/wsjtx.git src
cd src
git config core.autocrlf false
git config core.longpaths true

Keeping automatic CRLF conversion disabled prevents generated version metadata from treating an unchanged checkout as modified. Long-path support accommodates deep source and generated-file names used by the Windows build.

External contributors should clone their fork instead and add https://github.com/WSJTX/wsjtx.git as the upstream remote. Core team members should use the private repository and the development branch assigned to their work.

Install OmniRig

Install OmniRig in Windows. The usual location is C:\Program Files (x86)\Afreet\OmniRig\OmniRig.exe. WSJT-X does not link against OmniRig at build time, but dumpcpp reads the COM type library embedded in this executable to generate the ActiveQt interface.

MSYS2 installs this tool as dumpcpp-qt5. The build finds that name directly; do not copy or rename it to dumpcpp.

Build the CI-selected Hamlib revision

The CI configuration selects the Hamlib revision supported by this WSJT-X source. Read it from the checked-out tree rather than assuming that the newest Hamlib branch is compatible:

cd ~/wsjtx-dev/src
HAMLIB_BRANCH=$(awk -F'"' '/hamlib_branch:/ {print $2; exit}' \
  .github/workflows/ci.yml)
if test -n "$HAMLIB_BRANCH"; then
  echo "Building Hamlib $HAMLIB_BRANCH"
else
  echo "hamlib_branch is missing" >&2
  false
fi

If this check fails, inspect the hamlib_branch setting in .github/workflows/ci.yml before continuing.

cd ~/wsjtx-dev
git clone --depth 1 --branch "$HAMLIB_BRANCH" \
  https://github.com/Hamlib/Hamlib.git hamlib-src
cd hamlib-src
./bootstrap
./configure --prefix="$HOME/wsjtx-dev/hamlib-prefix" \
  --enable-shared --disable-static \
  --without-cxx-binding --without-readline \
  CFLAGS="-DNDEBUG -g -O2 -fdata-sections -ffunction-sections" \
  LDFLAGS="-Wl,--gc-sections"
make -j"$(nproc)"
make install-strip

This creates an isolated Hamlib installation under ~/wsjtx-dev/hamlib-prefix; it does not replace another Hamlib installation on the computer.

If the CI pin changes, remove or rename hamlib-src and hamlib-prefix, then repeat this section. A shallow clone made for an older tag may not contain the new revision.

Configure and build WSJT-X

Return to the source tree and configure a local developer build. The normal build includes WSJT-X, MAP65, and QMAP; add -DWSJT_SKIP_QMAP=ON to omit QMAP.

cd ~/wsjtx-dev/src
OMNIRIG=$(cygpath "C:/Program Files (x86)/Afreet/OmniRig/OmniRig.exe")

cmake -G "MSYS Makefiles" -S . -B build \
  -DCMAKE_PREFIX_PATH="$HOME/wsjtx-dev/hamlib-prefix" \
  -DCMAKE_INSTALL_PREFIX=C:/WSJT \
  -DOMNIRIG_TYPE_LIB="$OMNIRIG" \
  -DCMAKE_Fortran_FLAGS="-fallow-argument-mismatch -std=legacy" \
  -DWSJT_SKIP_MANPAGES=ON \
  -DWSJT_FORTRAN_LIBRARY_VARIANTS=OPENMP_ONLY \
  -Wno-dev

cmake --build build -j"$(nproc)"

CMake 4.4 may report that -Wno-dev is deprecated. This notice is harmless; the guide keeps the option because it also works with the documented older CMake versions.

The important options are:

Option Purpose

CMAKE_PREFIX_PATH

Locates the Hamlib installation built above.

CMAKE_INSTALL_PREFIX

Selects the destination used by the install target.

OMNIRIG_TYPE_LIB

Identifies the OmniRig executable whose COM type library dumpcpp reads.

CMAKE_Fortran_FLAGS

Allows current gfortran to compile the project’s legacy Fortran interfaces.

WSJT_SKIP_MANPAGES

Avoids Unix manpage tooling that is not used by the Windows build.

WSJT_FORTRAN_LIBRARY_VARIANTS=OPENMP_ONLY

Builds the normal OpenMP decoder-library variant.

WSJT_GENERATE_DOCS=OFF

Omits the local User Guide when Asciidoctor is not installed.

WSJT_SKIP_QMAP=ON

Omits QMAP from the build.

Run the automated tests

Tests are enabled by default. Hamlib’s DLL must be on PATH while Windows loads test executables that use rig-control code:

cd ~/wsjtx-dev/src
export PATH="$HOME/wsjtx-dev/hamlib-prefix/bin:$PATH"
export QT_QPA_FONTDIR=C:/Windows/Fonts
ctest --test-dir build --output-on-failure

Some GUI tests use Qt’s offscreen platform, which does not find the Windows system fonts automatically. QT_QPA_FONTDIR lets those tests render text without installing a separate font package.

To rerun a single test, substitute its name below:

ctest --test-dir build -R '^test_name$' --output-on-failure

An ordinary local test run does not require a separate pFUnit installation.

Install and run

The build directory is useful for tests, but it is not a self-contained application layout. Install to the prefix selected during configuration:

cmake --build build --target install

This places the application under C:\WSJT. Executables and required runtime DLLs are collected in C:\WSJT\bin; program data is installed under C:\WSJT\share\wsjtx. Run C:\WSJT\bin\wsjtx.exe from Windows Explorer, Command Prompt, or the MINGW64 shell.

The install step matters. A build-tree executable can find compiler and Qt DLLs through the MINGW64 environment, but it does not have the final data-file and plugin layout. It is suitable for a quick launch only:

export PATH="$HOME/wsjtx-dev/hamlib-prefix/bin:$PATH"
export QT_QPA_PLATFORM_PLUGIN_PATH=/mingw64/share/qt5/plugins
./build/wsjtx.exe

Missing Hamlib on PATH produces a DLL-load failure. A missing Qt platform plugin commonly reports that qwindows.dll could not be found or loaded. Even when it starts, the build-tree application is not suitable for normal operation: features that require installed ephemeris, callsign, country, or other data files can fail. For example, an FT8 decode can report ALLCALL7.TXT is too short or broken?, and opening Astronomical Data can fail without the installed ephemeris. Use the installed copy for functional testing.

Create an unsigned installer

After installing NSIS, create a package from the configured build:

cmake --build build --target package

The installer is written under build as wsjtx-<version>-win64.exe. It is unsigned, so Windows SmartScreen may warn about it.

Update safely

Update the MSYS2 environment with:

pacman -Syu

Update the checked-out branch, then rerun the CMake configure command, build, and tests:

cd ~/wsjtx-dev/src
git pull --ff-only

Rebuild Hamlib when the CI-selected revision changes.

Use a new build directory after a major MSYS2 update changes GCC, gfortran, CMake, Qt, the MinGW runtime, or foundational libraries. Cached compiler and dependency paths from an older environment can otherwise produce confusing configure, link, or runtime failures.

Troubleshooting Windows builds

For Windows build failures, check the following:

  • echo "$MSYSTEM" reports MINGW64.

  • Every tool check from the dependency section resolves under /mingw64/bin.

  • OMNIRIG_TYPE_LIB names an existing Windows installation of OmniRig.exe.

  • mingw-w64-x86_64-openssl is installed if CMake reports missing OpenSSL runtime DLLs.

  • ~/wsjtx-dev/hamlib-prefix contains include/hamlib/rig.h, lib/libhamlib.dll.a, and bin/libhamlib-4.dll.

After fixing a configuration error, rerun the configure command.

For a useful support report, include:

echo "$MSYSTEM"
git rev-parse --short HEAD
cmake --version
gcc --version
gfortran --version
pacman -Q | sort

Also include the complete CMake error or failing command, not only its final line, and state whether the failure occurred during configure, compile, test, install, package, or application launch.

4.4.4. Linux and macOS developer builds

Use the native package manager for local-development dependencies, then build the CI-selected Hamlib revision into a private workspace. Keeping dependency source, installed libraries, and generated build files outside the WSJT-X checkout makes updates and clean rebuilds easier.

Install the dependencies

On current Debian or Ubuntu systems, a practical dependency starting point is:

sudo apt update
sudo apt install \
  git build-essential cmake gfortran \
  qtbase5-dev qttools5-dev qtmultimedia5-dev \
  libqt5serialport5-dev libqt5websockets5-dev \
  libqt5sql5-sqlite libqt5multimedia5-plugins \
  libfftw3-dev libboost-log-dev libusb-1.0-0-dev libudev-dev \
  portaudio19-dev autoconf automake libtool pkg-config texinfo \
  asciidoctor

On macOS, install the Xcode command-line tools and the local developer dependencies with Homebrew:

xcode-select --install
brew install cmake gcc qt@5 fftw boost libusb portaudio \
  autoconf automake libtool pkg-config texinfo asciidoctor
Clone the source

Clone the public repository, substituting your fork’s URL if contributing a change. If you already have a checkout, change to its root directory instead.

mkdir -p ~/wsjtx-dev
git clone https://github.com/WSJTX/wsjtx.git ~/wsjtx-dev/src
cd ~/wsjtx-dev/src
Build the CI-selected Hamlib revision

Start in the root of the WSJT-X checkout. Capture its path and read the Hamlib revision selected by that source:

WSJTX_SOURCE=$(git rev-parse --show-toplevel)
WSJTX_WORKSPACE="$HOME/wsjtx-dev"
mkdir -p "$WSJTX_WORKSPACE"

HAMLIB_BRANCH=$(awk -F'"' '/hamlib_branch:/ {print $2; exit}' \
  "$WSJTX_SOURCE/.github/workflows/ci.yml")
if test -n "$HAMLIB_BRANCH"; then
  echo "Building Hamlib $HAMLIB_BRANCH"
else
  echo "hamlib_branch is missing" >&2
  false
fi

If this check fails, inspect .github/workflows/ci.yml before continuing. The remaining commands assume the same terminal session. They create Hamlib source and installation directories beside each other under ~/wsjtx-dev:

git clone --depth 1 --branch "$HAMLIB_BRANCH" \
  https://github.com/Hamlib/Hamlib.git "$WSJTX_WORKSPACE/hamlib-src"
cd "$WSJTX_WORKSPACE/hamlib-src"
./bootstrap
./configure --prefix="$WSJTX_WORKSPACE/hamlib-prefix" \
  --enable-shared --disable-static \
  --without-cxx-binding --without-readline
make -j"$(getconf _NPROCESSORS_ONLN)"
make install-strip

If the CI-selected revision changes, remove or rename hamlib-src and hamlib-prefix, then repeat this section.

Configure, build, test, and install

These local builds skip manpage generation, which requires additional tools. On Linux, configure WSJT-X with the explicit source and workspace paths:

cmake -S "$WSJTX_SOURCE" -B "$WSJTX_WORKSPACE/wsjtx-build" \
  -DCMAKE_PREFIX_PATH="$WSJTX_WORKSPACE/hamlib-prefix" \
  -DWSJT_SKIP_MANPAGES=ON \
  -DCMAKE_INSTALL_PREFIX="$HOME/wsjtx-prefix"
cmake --build "$WSJTX_WORKSPACE/wsjtx-build"
ctest --test-dir "$WSJTX_WORKSPACE/wsjtx-build" --output-on-failure
cmake --build "$WSJTX_WORKSPACE/wsjtx-build" --target install

On macOS, include the Homebrew library prefixes and select Homebrew’s gfortran explicitly.

cmake -S "$WSJTX_SOURCE" -B "$WSJTX_WORKSPACE/wsjtx-build" \
  -DCMAKE_PREFIX_PATH="$WSJTX_WORKSPACE/hamlib-prefix;$(brew --prefix qt@5);$(brew --prefix fftw);$(brew --prefix boost);$(brew --prefix libusb);$(brew --prefix portaudio)" \
  -DCMAKE_Fortran_COMPILER="$(brew --prefix gcc)/bin/gfortran" \
  -DWSJT_SKIP_MANPAGES=ON \
  -DCMAKE_INSTALL_PREFIX="$HOME/wsjtx-prefix"
cmake --build "$WSJTX_WORKSPACE/wsjtx-build"
ctest --test-dir "$WSJTX_WORKSPACE/wsjtx-build" --output-on-failure
cmake --build "$WSJTX_WORKSPACE/wsjtx-build" --target install

Menus at top of the main window offer many options for configuration and operation. Some are self-explanatory; additional details for others are provided below. Keyboard shortcuts for some frequently used menu items are listed at the right edge of the menu.

5.1. WSJT-X menu

Mac App Menu

This menu appears on the Macintosh only. Settings appears here, labeled as Preferences, rather than on the File menu. About WSJT-X appears here rather than on the Help menu.

5.2. File menu

File Menu

5.3. Configuration Menu

File Menu

Some users prefer to create and use entries on the Configurations menu for switching between modes. Simply Clone the Default entry, Rename it as desired, and then make all desired settings for that configuration. All settings will be restored whenever you select that configuration.

As well as switching between configurations while running WSJT-X, you can also start the application from the command line in any desired configuration. Use the command-line option --config <configuration-name>, or -c for short, as in these examples for configurations named FT8 and Echo:

wsjtx --config FT8
wsjtx -c Echo

5.4. View Menu

Most items on the View menu can be clicked to display a specified window. Some are self-explanatory or described in detail elsewhere in this guide; additional details for others are included below.

View Menu
Active Stations

Active Stations is a window with two distinct purposes. The first can help you work the most distant stations, in particular for the distance-scored ARRL International Digital Contest. You can set the maximum length of the list and the maximum “Age” of displayed decodes, measured in Rx sequences. You can request display of only ready-to-be-called stations: those whose most recent transmission is a CQ, RR73, or 73 message. For the ARRL International Digital Contest the window displays scoring Rate (points in the most recent hour), your total accumulated Score, and the number of Band Changes in the past hour.

Active Stations

When WSJT-X is used together with sister program QMAP, the Active Stations window displays the frequencies, SNRs, Q65 sub-modes, and Maidenhead locators for stations recently decoded by QMAP over its full 90 kHz bandwidth. Stations using a 30-second sub-mode of Q65 are highlighted in yellow. You can limit the displayed list by checking the Wanted only and/or CQ only boxes. The total number of QSOs found in wsjtx.log is shown, for example to follow your progress in an EME contest. Fo more details about using QMAP, see Section 9.9.

Active Stations
SWL Mode

SWL Mode reduces the main window to show just the menus, decodes windows, and status bar. You may find this useful when running multiple instances of the application. The size and location of the main window are saved and recalled independently for this view.

View SWL
Message Creator, QSY Monitor, and Enable Message Popups

A special messaging system can be used to invite your QSO partner to move to another band or mode (for example, during a contest), or to convey some short canned messages. There are two main parts, the Message Creator and the QSY Monitor. Received messages are displayed in popup windows.

Use the Message Creator to create and send these special messages with just a few clicks. When using this feature for the first time, make sure that your IARU Region has been set (upper right on the File | Settings | General tab). Activate the Message Creator window by checking its name on the View menu. Four tabs are available: HF, VHF, EME and General:

Creator Tabs

To send a message, select the appropriate tab and then the band, mode, and kHz part of frequency for a QSY request, or a canned message from the General tab. The actual message to be sent will be shown in the field labeled Message on each tab. Click Send Message to have this message conveyed in your next scheduled transmission. Enable Tx will be activated automatically, and your message will be sent to the callsign in the DX Call field of the main window. The example below shows the creation of a message to W3SZ asking him to QSY to 145.550 using FM.

Creator window

To prepare for receiving special messages, check Enable Message Popups on the View menu. A screenshot showing the example message sent to W3SZ is shown below. As recipient, W3SZ can click Reply Yes or Reply No, and his reply message will be sent in the next Tx interval to the callsign present in the recipient’s DX callsign box.

Received message
After use, the Message System text remains in the Tx 6 field. Tx 6 can be reset to the standard CQ message by clicking the Generate Std Msgs

You can view messages sent to other stations, as well as to yourself. To do so, check QSY Monitor on the View menu. An example showing a number of received messages is shown below.

QSY Monitor
Band Buttons

Optional band select buttons can be switched on or off from the View menu. Two sets of buttons are available. Check Band Buttons to get an HF-oriented set for 160 m through 70 cm, and also VHF / UHF Buttons to display a set for 8 m through 24 GHz. Clicking on a band button switches the program to a mode-dependent default frequency selected from the frequency table for that band. In FT8 mode, right-clicking a band button will set dial frequency to the conventional DXpedition frequency (or on 6 m, to the intercontinental frequency). To define your own preferred default frequencies, check the relevant Pref boxes on the File | Settings | Frequencies tab.

bandbutton1
Dark Style

Select Dark Style to switch to a dark-background theme for all windows. To make it effective you will probably want to redefine your color settings.

dark

5.5. Filters Menu

filters menu

The Filters menu lets you control a wide variety of message-filtering options. Many of them are defined on the File | Settings | Filters tab. You can hide, ignore, or highlight stations worked before on the current band, worked today or yesterday, or those present in the Ignore List. A checkbox labelled BP on the main window (just left of the Log QSO button) allows all filtering options to be bypassed temporarily with a single click. This action can be used, for example, if you have filtered out your own continent to display only DX stations but now wish to monitor all band activity.

5.6. Mode Menu

Mode Menu

5.7. Decode Menu

All WSJT-X modes offer Fast, Normal, and Deep decoding options. Deep usually provides the best sensitivity, at the cost of slower processing and a slightly higher probability of false decodes.

In FT8 mode you can select a multithreaded decoder with many additional options. You may wish to experiment with the various possibilities to obtain best overall performance in your setup. In general we find the multithreaded decoder yields a greater number of decodes on a busy band, while the single-threaded Deep setting is best for extreme weak signal work.

Decode Menu

Full Duplex Mode can also be selected from the Decode menu. Audio input can be taken from a second local receiver or from a WebSDR on the internet. Duplex operation works for slow modes (FT8, FT4, Q65, … ) and fast modes like MSK144. Your own transmitted messages will be highlighted in the Band Activity window in the color you selected for "Transmitted message" on the File | Settings | Colors tab.

An additional option to disable mouse clicks on the waterfall, visible only when Q65 mode is selected, and VHF Features are enabled, can be selected to prevent inadvertent mouse clicks on the waterfall from changing the Rx and/or Tx offset frequencies. When selected, frequency changes can still be made using the mouse by holding down the ALT key.

5.8. Save Menu

Save Menu

You can control the types of information that _WSJT-X saves during an operating session, perhaps for future analysis or diagnostic purposes. For example, check Save decoded to save audio files for all receiving sequences producing at least one decode. The file ALL.TXT is a record of everything you have transmitted or received. You can choose to have it automatically split into smaller chunks by month or year, or to disable it entirely. Some diagnostic logging of events always takes place. Diagnostic mode lets you collect more data to troubleshoot problems with the program, or with its communication with your rig.

Diagnostic mode

5.9. Tools Menu

Tools Menu

5.10. Help Menu

Help Menu

6. Settings

Select Settings from the File menu or by typing F2. (On Macintosh select Preferences from the WSJT-X menu, or use the keyboard shortcut Cmd+,). The following sections describe setup options available on tabs selectable near the top of the window.

6.1. General

Select the General tab on the Settings window. Under Station Details enter your callsign, grid locator (preferably the 6-character locator) and IARU Region number. (Region 1 is Europe, Africa, the Middle East, and Northern Asia; Region 2 the Americas; and Region 3 Southern Asia and the Pacific.) Meanings of remaining options on the General tab should be mostly self-explanatory after you have made some QSOs using WSJT-X. You can return to set these options to your preferences later.

Settings Window
If you are using a callsign with an add-on prefix or suffix, or wish to work a station using such a call, be sure to read the section Nonstandard Callsigns.
Checking Enable VHF/UHF/Microwave features disables the wideband multi-decode capability of JT65. In most circumstances you should turn this feature off when operating at HF.

6.2. Radio

WSJT-X offers CAT (Computer Aided Transceiver) control of relevant features of most modern transceivers. To configure the program for your radio, select the Radio tab.

Radio Tab
  • Select your radio type from the drop-down list labeled Rig, or None if you do not wish to use CAT control.

    • Alternatively, if you have configured your station for control by DX Lab Suite Commander, Flrig, Ham Radio Deluxe, Hamlib NET rigctl, or Omni-Rig, you may select one of those program names from the Rig list. In these cases the entry field immediately under CAT Control will be relabeled as Network Server. Leave this field blank to access the default instance of your control program, running on the same computer. If the control program runs on a different computer and/or port, specify it here. Hover the mouse pointer over the entry field to see the required formatting details.

    • Select Omni-Rig Rig 1 or Omni-Rig Rig 2 to connect to an Omni-Rig server installed on the same computer. Omni-Rig will be started automatically by WSJT-X.

  • Set Poll Interval to the desired interval for WSJT-X to query your radio. For most radios a small number (say, 1 – 3 s) is suitable.

  • CAT Control: To have WSJT-X control the radio directly rather than through another program, make the following settings:

    • Select the Serial Port or Network Server including the service port number used to communicate with your radio.

      A special value of USB is available for custom USB devices like those used by some SDR kits. This is not the same as the virtual serial port provided by USB connected transceivers and CAT interfaces, for those use the COM or serial port name that refers to them.
    • Serial Port Parameters: Set values for Baud Rate, Data Bits, Stop Bits, and Handshake method. Consult your radio’s user guide for the proper parameter values.

    CAT interfaces that require handshaking will be non-responsive until the correct Handshake setting is applied.
    • Force Control Lines: A few station setups require the CAT serial port’s RTS and/or DTR control lines to be forced high or low. Check these boxes only if you are sure they are needed (for example, to power the radio serial interface).

  • PTT Method: select VOX, CAT, DTR, or RTS as the desired method for T/R switching. If your choice is DTR or RTS, select the desired serial port (which may be the same one as used for CAT control).

    With DTR or RTS PTT, an external controller can hold off PTT and rig Tune while WSJT-X continues its transmit sequence and audio. Enable Accept UDP requests on the Reporting tab to accept these TX Inhibit commands. While enabled, WSJT-X periodically advertises TX Inhibit availability on the configured UDP reporting stream. Transmission resumes when all holds clear, provided the transmit sequence is still active.

    Configure UDP reporting on the Reporting tab so the controller can receive WSJT-X messages and send hold commands to the sending instance. Multicast reporting allows several companion applications to receive the messages. With unicast reporting, the controller must be the configured receiver or receive the messages through a relay.

    Each controller refreshes its hold while needed, then releases it. Holds also expire if refreshes stop. With multiple controllers, PTT remains off until every hold has cleared. Turning off Accept UDP requests withdraws TX Inhibit availability and stops accepting commands; existing holds remain until they expire.

    When using a proxy application for rig control, CAT is usually the correct option for PTT Method assuming the proxy application is capable of keying your transceiver independently.
  • Transmit Audio Source: some radios permit you to choose the connector that will accept Tx audio. If this choice is enabled, select Rear/Data or Front/Mic.

  • Mode: WSJT-X uses upper sideband mode for both transmitting and receiving. Select USB, or choose Data/Pkt if your radio offers such an option and uses it to enable the rear-panel audio line input. Some radios also offer wider and/or flatter passbands when set to Data/Pkt mode. Select None if you do not want WSJT-X to change the radio’s Mode setting.

  • Split Operation: Significant advantages result from using Split mode (separate VFOs for Rx and Tx) if your radio supports it. If it does not, WSJT-X can emulate such behavior. Either method will result in a cleaner transmitted signal, by keeping the Tx audio always in the range 1500 to 2000 Hz so that audio harmonics cannot pass through the Tx sideband filter. Select Rig to use the radio’s Split mode, or Fake It to have WSJT-X adjust the VFO frequency as needed, when T/R switching occurs. Choose None if you do not wish to use split operation.

When all required settings have been made, click Test CAT to test communication between WSJT-X and your radio. The button should turn green to indicate that proper communication has been established. Failure of the CAT-control test turns the button red and displays an error message. After a successful CAT test, toggle the Test PTT button to confirm that your selected method of T/R control is working properly, the button turns red if the rig has been successfully keyed. (If you selected VOX for PTT Method, you can test T/R switching later by using the Tune button on the main window.)

6.3. Audio

Select the Audio tab to configure your sound system.

_WSJT-X_ Audio Configuration Screen
  • Soundcard: Select the audio devices to be used for Input and Output. Usually the Mono settings will suffice, but in special cases you can choose Left, Right, or Both stereo channels.

    • Be sure that your audio device is configured to sample at 48000 Hz, 16 bits.

      If you select the audio output device that is also your computer’s default audio device, be sure to turn off all system sounds to prevent inadvertently transmitting them over the air.
      Windows 7 and later may configure audio devices using the Texas Instruments PCM2900 series CODEC for microphone input rather line input. (This chip is used in many radios with built-in USB CODECs, as well as various other audio interfaces.) If you are using such a device, be sure to set the mic level in the Recording Device Properties to 0 dB.
  • Save Directory: WSJT-X can save its received audio sequences as .wav files. A default directory for these files is provided; you can select another location if desired.

  • AzEl Directory: A file named azel.dat will appear in the specified directory. The file contains information usable by another program for automatic tracking of the Sun or Moon, as well as calculated Doppler shift for the specified EME path. The file is updated once per second whenever the Astronomical Data window is displayed.

  • Remember power settings by band: Checking either of these will cause WSJT-X to remember the Pwr slider setting for that operation on a band-by-band basis. For example, when Tune is checked here and you click the Tune button on the main window, the power slider will change to the most recent setting used for Tune on the band in use.

6.4. Tx Macros

Tx Macros are an aid for sending brief, frequently used free-text messages such as the example shown below.

Tx Macros Screen
  • To add a new message to the list, enter the desired text in the entry field at top, then click Add.

  • Remember that a transmitted free-text message is limited to 13 characters, including blanks.

  • To remove an unwanted message, click on the message and then on Delete.

  • You can reorder your macro messages by using drag-and-drop. The new order will be preserved when WSJT-X is restarted.

  • Messages can also be added from the main window’s Tx5 field. Simply hit [Enter] after the message has been entered.

  • If the first word of a message is $DXCALL (or the shortened form $DX), that word will be replaced on transmission by the base callsign in the DX Call field.

6.5. Reporting

Reporting Screen
  • Logging: Choose any desired options from this group. Operators in a multi-operator station may wish to enter their home callsign as Op Call.

  • Network Services: Check Enable PSK Reporter Spotting to send reception reports to the PSK Reporter mapping facility.

  • UDP Server: This group of options controls the network name or address and port number used to exchange information with a third party application that inter-operates with WSJT-X. Exchanged information includes decoded messages, general program status, QSOs logged, highlighting of callsigns in the Band Activity window, and limited facilities to initiate QSOs in response to CQ or QRZ messages. Full details of the protocol can be found in comments at the top of this file in our source code repository: https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/Network/NetworkMessage.hpp

The Outgoing interfaces and Multicast TTL fields are only present when a multicast group IP address has been entered in the UDP Server field.

Companion programs like JTAlert use the UDP Server feature to exchange information with WSJT-X. If you are using JTAlert to send requests to WSJT-X, be sure to check the box Accept UDP requests.

6.6. Frequencies

By default, the Working Frequencies table contains a list of frequencies conventionally used for specific modes. Conventions may change with time, or by user preference; you can modify the frequency table as desired.

Frequency Screen
  • To change an existing entry, double-click to edit it, type a desired frequency in MHz or select from the drop-down list of options, then hit Enter on the keyboard. You can mark an entry as Preferred, provide a descriptive label, and indicate starting and ending dates and times for it to be displayed on the band-select control. The program will format your changed entries appropriately.

  • To add a new entry, right-click anywhere on the frequency table and select Insert. Enter your desired information and click OK. The table may include more than one frequency for a given mode and band.

Add Frequency window
  • To delete an entry, right-click it and select Delete. Multiple entries can be deleted in a single operation by selecting them before right-clicking.

  • Right-click anywhere within the table body and click Reset button to return the table to its default configuration.

Other more advanced maintenance operations are available on the right-click context popup menu.

Frequency Calibration: If you have calibrated your radio using WWV or other reliable frequency references, or perhaps with the technique described in Accurate Frequency Measurements with your WSPR Setup, enter the measured values for Intercept A and Slope B in the equation

Dial error = A + B*f

where “Dial error” and A are in Hz, f is frequency in MHz, and B is in parts per million (ppm). Frequency values sent to the radio and received from it will then be adjusted so that frequencies displayed by WSJT-X are accurate.

Station Information: You can save Band, Offset and Antenna Description information for your station. The antenna information will be included in reception reports sent to PSK Reporter. By default the frequency offset for each band is zero. Nonzero offsets may be added if (for example) a transverter is in use.

  • To simplify things you might want to delete any unwanted bands — for example, bands where you have no equipment. Then click on a Frequency entry and type Ctrl+A to “select all,” and drag-and-drop the entries onto the Station Information table. You can then add any transverter offsets and antenna details.

  • To avoid typing the same information many times, you can drag-and-drop entries between the lines of the Station Information table.

  • When all settings have been configured to your liking, click OK to dismiss the Settings window.

6.7. Colors

Colors Screen
Decode Highlighting
  • WSJT-X uses colors to highlight decoded CQ messages of particular interest. Check the box Show DXCC, grid, and worked-before status on the File |Settings | General tab, and any boxes of interest to you on the Colors tab. You can drag any line up or down to raise or lower its logical priority. Right-click any line to set a new foreground or background color. Foreground and background colors are applied separately, and careful choices of foreground, background, and priority can provide two indications of worked-before status.

  • Press the Reset Highlighting button to reset all of the color settings to default values.

  • Check Highlight by Mode if you wish worked-before status to be per mode.

  • Check Only grid Fields sought if you are only interested in the leading two character grid locator Fields rather than the four character grid locator Squares.

  • Check Include extra WAE entities if you are interested in the extra entities defined for DARC WAE and CQ Marathon awards.

  • Worked-before status is determined from file wsjtx_log.adi in your log directory. You can replace ADIF log file with one exported from your station logging application. Clicking Rescan ADIF Log will rebuild the WSJT-X worked-before index from the current ADIF log file.

Logbook of The World User Validation

Stations who are known to have uploaded their logs to the ARRL LoTW QSL matching service can be highlighted. The data used to determine this is available online.

  • Fetch Now will download a fresh dataset from the Users CSV file URL. The LoTW team normally update this data weekly.

  • Adjust Age of last upload less than to set the period within which a station must have uploaded their log to LoTW to trigger highlighting.

Alternative Highlighting

Some users find an alternative color scheme with pastel-like colors easier on the eyes and more suitable for the dark style. You can select either the original WSJT-X or the alternative style. With the alternative style, stations uploading their logbook to LoTW will have black foreground color, others red. Stations worked-before are displayed with grey background.

Decode Highlighting

It is still possible for you to customize the color scheme according to your own preferences. In addition, you can highlight individual callsigns, grids, prefixes, or directional CQ calls such as DX, POTA, and SOTA with an orange or blue background. Callsigns, grids, and directional calls are separated by commas and can be mixed (e.g. "K1JT, DG2YCB, JO33, DX, POTA, SOTA,"). Spaces after commas are allowed. Directional calls are matched as whole list items, so list order has no effect and no leading comma is needed. A single directional call does not need a comma. You must include a comma after each callsign or grid, and also at the end of the line. Prefixes must be followed by a semicolon (e.g. "VK;ZL;T88;"). The Wanted audible alert uses the same orange and blue entries.

6.8. Advanced

Settings Advanced
JT65 VHF/UHF/Microwave decoding parameters
  • Random erasure patterns logarithmically scales the number of pseudo-random trials used by the Franke-Taylor JT65 decoder. Larger numbers give slightly better sensitivity but take longer. For most purposes a good setting is 6 or 7.

  • Aggressive decoding level sets the threshold for acceptable decodes using Deep Search. Higher numbers will display results with lower confidence levels.

  • Check Two-pass decoding to enable a second decoding pass after signals producing first-pass decodes have been subtracted from the received data stream.

Miscellaneous
  • Set a positive number in Degrade S/N of .wav file to add known amounts of pseudo-random noise to data read from a .wav file. To ensure that the resulting S/N degradation is close to the requested number of dB, set Receiver bandwidth to your best estimate of the receiver’s effective noise bandwidth.

  • Set Tx delay to a number larger than the default 0.2 s to create a larger delay between execution of a command to enable PTT and onset of Tx audio.

    For the health of your T/R relays and external preamplifier, we strongly recommend using a hardware sequencer and testing to make sure that sequencing is correct.
  • Check x 2 Tone spacing or x 4 Tone spacing to generate Tx audio with twice or four times the normal tone spacing. This feature is intended for use with specialized LF/MF transmitters that divide generated frequencies by 2 or 4 as part of the transmission process.

Special Operating Activity

  • Check this box and select the type of activity to enable auto-generation of special message formats for contesting and DXpeditions. For ARRL Field Day, enter your operating Class and ARRL/RAC section; for FT Roundup, enter your state or province. Use “DX” for section or state if you are not in the US or Canada. In the FT Roundup, Stations in Alaska and Hawaii should enter “DX”.

  • Check Fox if you are a DXpedition station operating in FT8 DXpedition Mode, and SuperFox mode if you are using that variation. Check Hound if you wish to make QSOs with such a DXpedition. Be sure to read the FT8 DXpedition Mode User Guide and the SuperFox User Guide, as appropriate. Both guides are available directly from the Help menu.

6.9. Audible Alerts

WSJT-X can be configured to issue audible alerts when messages with specified content are decoded. This feature requires computer access to at least two audio output devices: one for transmitted audio, and a different one for audible alerts. The device for transmitted audio is selected on the Audio tab; alerts are always played on the Default audio device, most commonly the loudspeaker of your computer. To activate audio alerts, check any desired boxes on the Alerts menu and click the button Enable Audio Alerts.

Settings Alerts

Categories above the line require checking the box Show DXCC, grid and worked before status in the Display section of the File | Settings | General tab. To identify what triggered one of these alerts, ensure that corresponding categories in the File | Settings | Colors tab are selected. Use the checkboxes Highlight DX Call in message and Highlight DX Grid in message in the Display section of File | Settings | General to help identify what triggered an alert for DX Call or DX Grid in message.

If a callsign appears in the Ignore list or falls in a checked Ignore …​ category on the Filters menu, no alert sounds will be played unless you have checked the BP (Bypass) checkbox. This feature can be used to mute the alerts for a certain callsign with one click on the Ignore button (just below the DX Grid box on the main window). To reset everything and reactivate the alert, click on File | Erase Ignore List or uncheck the Filters | Ignore …​ item.
Before using of audio alerts, make sure they are played only on your local speaker and not sent to the transmitter! You can check by right-clicking on the Band Hopping button in Tab 3, as shown below. A test message will then be played.
testalerts

6.10. Filters

Filters provide a way to limit what is displayed in the Band Activity window. Define desired filtering categories using entry fields and checkboxes on the Filters tab. You can turn many filters on or off by checking lines on the main-window Filters menu.

Filters

You can specify up to four territories for which hiding messages can be switched on or off using options on the main window Filters menu. You can hide messages from a specific continent, or stations worked before on a band. There are entry fields for a Blacklist, a Whitelist, and an Always Pass list, and these can be used in combination. Blacklist might be used to suppress decodes from pirate stations, contest messages, or other messages with unwanted content. You can enter whole callsigns, parts of callsigns, or keywords. Whitelist can be used if you’re interested only in messages with certain grids, calls, or keywords. All other messages (except those allowed by the Always Pass list) will then be suppressed. Always Pass will enable display of decodes from specific stations even though the respective country or continent is hidden.

You can optionally apply filters only to callsigns of transmitting stations, or use the filters only for Wait and Pounce operation. In the latter case, all messages will be displayed in the Band Activity window, but Wait and Pounce will respond only to stations that meet the set filter criteria.

When any filter is active that limits display of some decodes, the status label at bottom left of the main window changes from green "Receiving" to cyan "Receiving, Filters on".

Filters are automatically disabled for Special Operating modes, to ensure that you don’t accidentally miss a station.
Ignore List

A click on the Ignore button (located on the main window below the DX Grid box) adds the callsign present in the DX Call box to your Ignore List. If you have also checked the box Ignore stations from the Ignore List on the main-window Filters menu, such stations are automatically ignored when you use one of the CQ: …​ options or Wait and Reply. The "Ignore List" will be created in your log directory the first time a station is added to it. You can erase the "Ignore List" from the File menu.

For callsigns in the Ignore List or corresponding to a selected Ignore …​ Quick Filters, no alert sounds are played unless you have activated the BP (bypass) checkbox. This can be used to temporarily mute the alerts for a certain callsign.

7. Keyboard and Mouse Commands

7.1. Keyboard Shortcuts

Select Keyboard shortcuts from the Help menu (or use function key F3) to display the following list of quick-action shortcuts:

Keyboard Shortcuts

Select Special Mouse Commands from the Help menu (or use function key F5) to display the following list of mouse commands:

7.2. Special Mouse Commands

Special Mouse Commands

7.3. GUI Keyboard Navigation

Use Tab and Shift+Tab to move forward and backward among controls in the main window. Use the arrow keys to change the selection within grouped controls.

You can control the transmitted-message sequence without leaving the keyboard. On the Standard Messages page, the six radio buttons in the Next column act as a single Tab stop: Tab reaches the currently selected message, and the arrow keys choose which of Tx1 through Tx6 will be sent in the next transmission. Further Tab presses reach the Now buttons, which select the corresponding message and, during a transmission, switch to it immediately, followed by the editable message fields. When the vertical 1 / 2 / 3 message-page selector has focus, use the arrow keys or the keys 1, 2, and 3 to select a page.

8. Transceiver Setup

Receiver Noise Level
  • If it is not already highlighted in green, click the Monitor button to start normal receive operation.

  • Be sure your transceiver is set to upper sideband (USB or USB Data) mode.

  • Use the receiver gain controls and/or the computer’s audio mixer controls to set the background noise level (scale at lower left of main window) to around 30 dB when no signals are present. It is usually best to turn AGC off or reduce the RF gain control to minimize AGC action.

Bandwidth and Frequency Setting
  • If your transceiver offers more than one bandwidth setting in USB mode, it may be advantageous to choose the widest one possible, up to about 5 kHz.

  • If you have only a standard SSB filter you won’t be able to display more than about 2.7 kHz bandwidth. Depending on the exact dial frequency setting, on HF bands you can display the full sub-band generally used for one mode.

Transmitter Audio Level
  • Click the Tune button on the main screen to switch the radio into transmit mode and generate a steady audio tone.

  • Listen to the generated audio tone using your radio’s Monitor facility. The transmitted tone should be perfectly smooth, with no clicks or glitches. Make sure that this is true even when you simultaneously use the computer to do other tasks such as email, web browsing, etc..

  • Adjust the Pwr slider (at right edge of main window) downward from its maximum until the RF output from your transmitter falls slightly. This is generally a good level for audio drive.

  • Toggle the Tune button once more or click Halt Tx to stop your test transmission.

9. Basic Operating Tutorial

This section introduces the basic user controls and program behavior of WSJT-X, with particular emphasis on the FT8 mode. Most new users should go through the full HF-oriented tutorial, preferably while at your operating setup. Subsequent tutorial sections will cover additional details on Making QSOs, WSPR mode, and VHF+ Features.

9.1. Download Samples

The following steps will download sample audio Wave files that were originally recorded by WSJT-X. These files can be opened and processed at another time, to partially simulate real-time operation.

  • Select Download samples…​ from the Help menu.

  • Download some or all of the available sample files using checkboxes on the screen shown below. For this tutorial you will need at least the FT8 files.

Download Samples

9.2. Wide Graph Settings

The WSJT-X Wide Graph window displays the frequency spectrum of received audio. Usually, the upper portion shows a waterfall plot of the frequency spectrum (a spectrogram) and a line plot of the current or average spectrum. Controls at the bottom of the window are used to set up the displayed audio frequency range, color palette, and scaling of the spectrum displays. A control Spec nn% at the bottom right lets you adjust the vertical fraction of the window occupied by the spectrum line plot. It is important to set appropriate lower and upper audio frequency limits for the Wide Graph because these limits define the FT8 decoder’s search window. For this tutorial, the limits will be set to cover 100-3300 Hz:

  • Set Start = 100 Hz.

  • Set Bins/Pixel = 5. Smaller or larger values make the Wide Graph cover a smaller/larger frequency range.

  • Use the mouse to grab the left or right edge of the Wide Graph, and adjust its width so that the upper frequency limit is about 3300 Hz.

  • Set N Avg = 2. This number determines how many spectra are averaged to produce each line in the spectrogram. Smaller values make the spectrogram scroll and update more frequently, resulting in signals being more spread out in the vertical (time) direction. Larger values make it easier to detect very weak signals.

The Palette setting controls the color scheme used for the spectrogram:

  • Set Palette = Fldigi

When Flatten is checked, WSJT-X attempts to correct for slope or curvature in the receiver’s passband shape.

  • Flatten = checked

The line plot can be set to display the current (un-averaged) spectrum or the cumulative (averaged) spectrum:

  • Select Cumulative for data display

  • Set the Gain and Zero sliders for the waterfall and spectrum to near midscale

The Spec nn% setting determines what fraction of the vertical extent of the Wide Graph will be used for the line plot of the spectrum. Setting Spec to 0 will eliminate the line plot and a setting of 100 will eliminate the spectrogram and show only the line plot:

  • Set Spec = 50%

9.3. FT8

Main Window:
  • Click the Stop button on the main window to halt any data acquisition.

  • Select FT8 from the Mode menu and Deep from the Decode menu.

  • Double-click on Erase to clear both text windows.

Open a Wave File:
  • Select File | Open and navigate to ...\save\samples\FT8\210703_133430.wav. The waterfall and Band Activity/Rx Frequency windows should look something like the following screen shots:

  • You may want to pretend you are K1JT by entering that callsign temporarily as My Call on the Settings | General tab. Your results should then be identical to those shown in the screen shot below. Don’t forget to change My Call back to your own call when you are done!

ft8 decodes
Decoding Overview

Decoding takes place at the end of a receive sequence. With Decode set to Deep, three decoding passes will be done and the Decode button on the main window will illuminate three times, once for each pass. The first decoding attempt in each pass is done at the selected Rx frequency, indicated by the U-shaped green marker on the waterfall frequency scale. All decodes appear in the left (Band Activity) window. The right (Rx Frequency) text window displays any decodes obtained at the current Rx frequency along with any decodes addressed to My Call (K1JT in this case). The red marker on the waterfall scale indicates your Tx frequency.

Twenty-one FT8 signals are decoded from the example file. The number of decodes is shown in a box at the bottom of the main window. When this file was recorded HA5WA was finishing a QSO with K1JT, and his 73 message is shown in red because it is addressed to My Call (in this case K1JT). By default, lines containing CQ are highlighted in green, and lines with My Call (K1JT) in red. Notice that K1JT now has two additional callers; HA0DU and EA3AGB.

Decoding Controls

To gain some feeling for controls frequently used when making QSOs, try double-clicking with the mouse on the decoded text lines and on the waterfall spectral display. You should be able to confirm the following behavior:

  • Double-click on one of the decoded CQ messages highlighted in green. These actions produce the following results:

    • Callsign and locator of the station calling CQ are copied to the DX Call and DX Grid entry fields.

    • Messages are generated for a standard minimal QSO.

    • The Tx even box is checked or cleared appropriately, so that you will transmit in the proper (odd or even) minutes.

    • The Rx frequency marker is moved to the frequency of the CQing station.

    • You can modify the double-click behavior by holding down the Shift key to move only the Tx frequency or the Ctrl key to move both Rx and Tx frequencies. (On a Mac computer, use the Command key instead of Ctrl).

    • In addition, if Double-click on call sets Tx enable is checked on the Settings | General tab then Enable Tx will be activated so that a transmission will start automatically at the proper time.

    You can prevent your Tx frequency from being changed by checking the box Hold Tx Freq.
  • Double-click on the decoded message K1JT HA0DU KN07, highlighted in red. Results will be similar to those in the previous step. The Tx frequency (red marker) is not moved unless Shift or Ctrl is held down. Messages highlighted in red are usually in response to your own CQ or from a tail-ender, and you probably want your Tx frequency to stay where it was.

  • Click with the mouse anywhere on the waterfall display. The green Rx frequency marker will jump to your selected frequency, and the Rx frequency control on the main window will be updated accordingly.

  • Do the same thing with the Shift key held down. Now the red Tx frequency marker and its associated control on the main window will follow your frequency selections.

  • Do the same thing with the Ctrl key held down. Now both colored markers and both spinner controls will follow your selections.

  • Double-clicking at any frequency on the waterfall does all the things just described and also invokes the decoder in a small range around the Rx frequency. To decode a particular signal, double-click near the left edge of its waterfall trace.

  • Ctrl-double-click on a signal to set both Rx and Tx frequencies and decode at the new frequency.

  • Click Erase to clear the right window.

  • Double-click Erase to clear both text windows.

To avoid QRM from competing callers, it is usually best to answer a CQ on a different frequency from that of the CQing station. The same is true when you tail-end another QSO. Choose a Tx frequency that appears to be not in use. You might want to check the box Hold Tx Freq.
Keyboard shortcuts Shift+F11 and Shift+F12 provide an easy way to move your Tx frequency down or up in 60 Hz steps.
Sliders and spinner controls respond to Arrow key presses and Page Up/Down key presses, with the Page keys moving the controls in larger steps. You can also type numbers directly into the spinner controls or use the mouse wheel.
An online FT8 Operating Guide by ZL2IFB offers many additional tips on operating procedures.

9.4. FT4

FT4 is designed for contesting, particularly on the HF bands and 6 meters. Compared with FT8 it is 3.5 dB less sensitive and requires 1.6 times the bandwidth, but it offers the potential for twice the QSO rate.

Main Window:
  • Select FT4 on the Mode menu.

  • Double-click on Erase to clear both text windows.

Wide Graph Settings:
  • Bins/Pixel = 5, Start = 100 Hz, N Avg = 1

  • Adjust the width of the Wide Graph window so that the upper frequency limit is approximately 3300 Hz.

Open a Wave File:
  • Select File | Open and navigate to ...\save\samples\FT4\200514_182053.wav. The waterfall and Band Activity window should look something like the following screen shots. This sample file was recorded during a practice contest test session, so most of the decoded messages use the FT Roundup message formats.

Wide Graph Decode FT4
  • Click with the mouse anywhere on the waterfall display. The green Rx frequency marker will jump to your selected frequency, and the Rx frequency control on the main window will be updated accordingly.

  • Do the same thing with the Shift key held down. Now the red Tx frequency marker and its associated control on the main window will follow your frequency selections.

  • Do the same thing with the Ctrl key held down. Now both colored markers and both spinner controls will follow your selections.

  • Now double-click on any of the lines of decoded text in the Band Activity window. Any line will show similar behavior, setting Rx frequency to that of the selected message and leaving Tx frequency unchanged. To change both Rx and Tx frequencies, hold Ctrl down when double-clicking.

ft4 decodes
Best S+P Button

The FT4 user interface includes a button labeled Best S+P.

Best S+P

Clicking Best S+P during an Rx cycle arms the program to examine all CQ messages decoded at the end of the Rx sequence. The program will select the best potential QSO partner (from a contesting perspective), and treat it as if you had double-clicked on that line of decoded text. Here "best potential QSO partner" means "New Multiplier" (1st priority) or "New Call on Band" (2nd priority). "New Multiplier" is currently interpreted to mean "New DXCC".

Best S+P is a useful feature only if you have defined what "best" is supposed to mean. This is done by configuring suitable options on the Settings | Colors tab. Selection and ordering of color-highlighting options determines what potential QSO partners will be chosen by the "Best S+P" feature. Optimum choices will be different for different contests. In a contest using FT Roundup rules we recommend activating My Call in message, New DXCC, New Call on Band, CQ in message and Transmitted message, reading from top to bottom.

Keyboard shortcuts Shift+F11 and Shift+F12 provide an easy way to move your FT4 Tx frequency down or up in 90 Hz steps.
For easy keyboard control of transmitted messages, check Alternate F1–F6 bindings on the File | Settings | General tab. In contest-style operation you can then hit F1 to solicit a QSO by sending CQ. Similarly, keys F2 to F5 will send the messages in entry fields Tx2 to Tx5. More details on contest-style operation can be found in The FT4 Protocol for Digital Contesting.

9.5. FST4

Do not confuse FST4 with FT4, which has a very different purpose! FST4 is designed primarily for making weak-signal 2-way QSOs on the LF and MF bands. T/R periods from 15 s up to 1800 s are available. Longer sequences provide better sensitivity only if Tx and Rx frequency instability and channel Doppler spread are small enough that received signals will remain phase coherent over periods spanning several transmitted symbols. Generally speaking, Rx and Tx frequency changes during the transmission and channel Doppler spread should each be small compared to the symbol keying rate. (See Table 7 in the Protocol Specifications section.) For example, the keying rate for FST4-1800 is 0.089 Baud, so successful operation requires frequency stability to be better than (and Doppler Spread less than) around 0.05 Hz.

Operation with FST4 is similar to that with other WSJT-X modes. Most on-screen controls, auto-sequencing, and other features behave in familiar ways. However, operating conventions on the 2200 and 630 m bands have made some additional user controls desirable. Spin boxes labeled F Low and F High set lower and upper frequency limits used by the FST4 decoder, and these limits are marked by dark green angle-bracket symbols < > on the Wide Graph frequency scale:

FST4 Decoding Limits


FST4 center

It’s best to keep the decoding range fairly small, since QRM and transmissions in other modes or sequence lengths will slow down the decoding process (and of course will be undecodable). By checking Single decode on the File | Settings | General tab, you can further limit the decoding range to the setting of F Tol on either side of Rx Freq.

A noise blanker can be enabled by setting the NB percentage to a non-zero value. (This control is located just above the input level thermometer.) The NB setting determines how many of the largest-amplitude samples will be blanked (zeroed) before the data is submitted to the decoder. Most users find that settings between 0% (no blanking) and 10% work best. If the noise blanker percentage is set to -1%, then the decoder will try 0, 5, 10, 15, and 20 % in succession. Similarly, a setting of -2% causes the decoder to loop over blanking percentages 0, 2, 4, …​ 20 %. To save time, the multiple blanking percentages triggered by negative NB settings are tried only for signal candidates located near (within +/- 20 Hz) of the Rx frequency setting.

Open a sample Wave File:
  • Select FST4 on the Mode menu. Set T/R to 60 s and Decode | Deep.

  • Set NB (noise blanker) to 0%.

  • Set up the Wide Graph display with settings appropriate for the FST4-60 mode. For example, try Bins/Pixel 2 and N Avg 4. Set the Start frequency and the width of the Wide Graph to include the frequency range that you want to decode. For this example, make sure that Start is less than 1000 Hz and that the Wide Graph extends to above 1400 Hz.

  • Set F Low 1000, F High 1400. These settings define the decoder’s frequency search range.

  • Open a sample Wave file using File | Open and select the file …​\save\samples\FST4+FST4W\210115_0058.wav. After WSJT-X has processed the file you should see something similar to the following screen shot:

FST4 1

9.6. FST4W

FST4W is used in the same way as WSPR, but FST4W has significant advantages for use on the 2200 m and 630 m bands. By default the central Rx Freq is 1500 Hz and F Tol is 100 Hz, so the active decoding range is 1400 to 1600 Hz. However, for added flexibility you can select different center frequencies and F Tol values. A drop-down control below F Tol offers a round-robin mode for scheduling FST4W transmissions:

FST4W RoundRobin

If three operators agree in advance to select the options 1/3, 2/3, and 3/3, for example, their FST4W transmissions will occur in a fixed sequence with no two stations transmitting simultaneously. Sequence 1 is the first sequence after 00:00 UTC. For WSPR-like scheduling behavior, you should select Random with this control.

Open a Wave File:
  • Select FST4W on the Mode menu and Deep on the Decode menu.

  • Set T/R to 1800 s.

  • Set NB to 0%.

  • Select appropriate wide graph settings. For example, try Bins/Pixel 1, Start 1200 Hz and N Avg 150.

  • Open a sample Wave file using File | Open and select the file …​\save\samples\FST4+FST4W\201230_0300.wav. When it is finished you should see a single decode as shown in the screenshot: