auto start WSJT-X strangeness

Post Reply
M0PTB
Novice Class
Posts: 3
Joined: 20 Jan 2020, 15:48

auto start WSJT-X strangeness

Post by M0PTB »

I'm attempting to automate my FT8 set up. Log4OM auto-starts WSJT-X with some odd problems:

* The WSJT-X'Wide Graph' doesn't show. Its icon is in the taskbar and clicking that brings it up. So does WSJT-X¦file¦view waterfall. Starting WSJT-X 'manually' shows the graph. Not a showstopper but annoying. And possibly a symptom/clue to the rest?

* JTALERT won't communicate with the auto-started WSJT-X. Eventually JTALERT spits out a box with details of the WSJT-X instance and a page from the help file about the appropriate UDP settings. The running WSJT-X is set up just like that!

* Closing WSJT-X and JTALERT does NOT resolve the comm problem. Only closing Log4OM frees the comms.

Dell PC running Win 10 Pro 64 bit.
Log4OM 2 version 2.2.60.0.0
WSJT-X v2.6.1
JTALERT 2.60.4

JTALERT box:
-----------------------------------------------------------------------------------------------------------------
Unable to communicate with the WSJTX process.
UDP Port : 2237
IP Address : 224.0.0.1
Values read from WSJTX config file...
C:\Users\pete_\AppData\Local\WSJT-X\WSJT-X.ini

WSJTX Detected Instance...
Process Window Title : WSJT-X v2.6.1 by K1JT et al.
Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

Decode alerts and logging will be unavailable until corrected.
------------------------------------------------------------------------------------------------------------------
WSJT_X UDP settings.jpg
WSJT_X UDP settings.jpg (98.53 KiB) Viewed 5188 times
Post Reply