The first thing to look at if there is failed comms with WSJTX is the UDP Server settings in WSJTX. Use the JTAlert "Help -> WSJT-X UDP Setup" menu to bring up the help file and check that you have WS

Your Callsign, AD7J, is recorded in the Callsigns database and shows you in NV and use eQSL(AG) and LoTW. Each JTAlert release automatically includes the most up-to-date Callsign database at the time

#FT8

Is this a JTAlert installer created shortcut or one you created/modified yourself? The correct parameter is, /wsjtx . There is no hyphen. Make sure the is no space between the slash and the "wsjtx" de

JTAlert doesn't perform any scanning of the log at startup. The first time JTAlert access the log to lookup B4 data is when the first batch of decodes is received. There is no pre-scanning. What you'r

Check your email. I sent a new build for you to test. de Laurie VK3AMA

To be clear, WSJTX does not send bad or good information to JTAlert, it simply sends what was decoded. The extra information about a decoded callsign, like B4 and Wanted status, is determined by WSJTX

In addition to Joe's (W4TV) excellent reply here https://HamApps.groups.io/g/Support/message/37188 I will point out that the re-scanning of the WSJTX ADIF will have zero affect on the JTAlert B4. JTAl

Ed, there is no special requirement for closing JTAlert or the Callsigns window. My preferred method is to simply close JTAlert and let it manage closing the other windows automatically. When you say

George, Sounds like you have the "Follow JTAlert window" option enabled. With that option set, any change in the main JTAlert window bring-forward/minimize/restore window state will be reflected in an

If your getting DX Alerts on US stations calling CD DX, then very likely you have the USA still set as needed for that Band and Mode in JTAlert. What log type are you using with JTAlert? Are you perio

First do a Windows restart to ensure that any pending updates are applied. Then check that you have WSJT-X and JTAlert setup correctly for multicast UDP. See the JTAlert "Help -> WSJTX UDP Setup" menu

If you're using Unicast then it is likely that ACLog is seizing exclusive control of the UDP port and preventing JTAlert from receiving the UDP messages. Either turn off ACLog integration with WSJTX o

In addition to what Bill said... Typically when a user reports that the "Rebuild" is incorrectly setting Countries and States ,for example, as still needed when they already exist in the Log it is due

What version of WSJTX? If not 2.4.0 or the 2.5.0-rc try updating to the latest release and see if the decoding works correctly without stopping. de Laurie VK3AMA

Excellent suggestion Jim. I hadn't considered that scenario. The extra effort to right-click a POTA Callsign and adding it to the temp ignored list is minimal, a couple of mouse clicks.With the infreq

If you want alerting visual and or audio alerting on previously worked Callsigns (B4) you have a number of options... For the Alert type set it to ignore the B4 status. For the B4 settings set a suita

Trolling is my guess. Poster is infamous for his recent two word "Up Yours" post on the WSJTX group that got him banned. https://wsjtx.groups.io/g/main/message/27844 <https://wsjtx.groups.io/g/main/me

The easiest way to test the entire Messaging infrastructure is to send a message to yourself. This will test all parts of the pipeline, Your PC -> Messaging Server -> Your PC. de Laurie VK3AMA

This is why in all my messages, release notes & help files, I deliberately use the word "Desktop". Not much more I can do if that advice goes unheeded or ignored. de Laurie VK3AMA

Sorry Jim, you're incorrect. The first reply (mine) to the initial post in the thread advised setting up multicast UDP along with instructions on how to find the setup instructions. Subsequent message