WSJTX-Controller-v2

Assistant for WSJT-X (the extremely popular amateur radio weak-signal digital modes program).
Modified WSJT-X is required, see installer releases at
https://github.com/avantol/WSJT-X_2.7.0/releases/tag/v2.7.0-172
More details at https://www.qrz.com/db/WM8Q

Use all appropriate caution since transmit can start at any time once you select "Enable Tx" in WSJT-X!!! Whenever the "Enable Tx" button is red, your antenna can be energized.

At first run, basic mode:


Later, advanced mode:


As a start, the Controller stores up calls that are interesting to you that come in while you're working another call, then replies to each in turn.

You can also do things like:
- call CQ, or listen for interesting stations (listening conserves bandwidth)
- reply exclusively and repeatedly to calls from "rare DX" stations and expeditions
- call "CQ DX" and ignore non-DX replies
- reply automatically to "CQ DX" from stations that are actually DX to you
- reply automatically to local or DX stations you haven't worked yet
- reply automatically to CQs from POTA or SOTA stations
- reply automatically to multi-stream stations
- automatically detect and transmit on the clearest section of a congested band
- manually queue up the interesting calls for automatic reply
- bypass WSJT-X's clunky way of skipping the grid message or using RR73
- transmit multiple directed CQs of your choice, for those hard-to-get QSOs
- optimize your success rate by logging as soon as 2-way signal reports are confirmed
- sound an alert when someone wants your state or country
- reply automatically to CQs directed to your state or country
- never miss a "late" 73 again... instead, it gets logged
- automatically start and/or stop transmitting at specified time(s)
- reply to new countries "by mode" (FT8, FT4, etc.)
- call whoever someone else is calling (like that rare DX!) with just one action
- have much more time to research callers on QRZ, PSKReporter, and LOTW...

Tips:

The Controller and the modified WSJT-X program run as a "versioned" pair, and the Controller checks for the correct WSJT-X version when it starts. Be sure to download and install both programs!

If you already have another WSJT-X version installed: You can install the required (modified) WSJT-X 2.7.0 program in an alternate destination folder if you like. Neither WSJT-X version will interfere with the other, and they share the same settings and preferences... convenient!

When the Controller is not running, the modified WSJT-X 2.7.0 "forgets" its modifications and runs like the standard unmodified version.

The UDP address/port for the WSJT-X Controller "UDP Server" is detected automatically by the Controller.

For best results, set the WSJT-X "UDP Server" (Settings | Reporting tab) to address 239.255.0.0 and port 2237, with all "Outgoing interfaces" selected.

If you experience any problems with the Controller, close all other programs that interface with WSJT-X, then re-open them one at a time to determine which one causes the problem.

It's best to use JTAlert in a passive mode, where it does not forward log data or control WSJT-X. This has caused problems for several users.

HRD is reported to not inter-operate well with the Controller, when JTAlert is used to forward log data to HRD.

DX Aggregator is reported to conflict with the communication between the Controller and WSJT-X.

Logger32 does not inter-operate with the Controller, since it is (apparently) designed to "run" WSJT-X by itself.

To get QSOs with stations "per mode" (ex: work an FT8 station, and later work the same station using FT4), in WSJT-X on the "Colors" tab, select "Highlight by Mode".

The Controller does not work for contests, since contests are designed as tests of skill, not automated assistance. Contest calls and modes are specifically and purposely ignored.

The Controller is disabled when Hound is selected, since call traffic management is done properly by the Fox station.