You've turned on a repeat in JTAlert or DXLab Mike W9MDB

It doesn't pull...WSJTX pushes. You need to run JTAlert's "Rebuild" at least once to bring in old QSOs from whatever log you have. And then re-run the Rebuild to bring in LOTW confirmations and such t

Logging is done via a data packet sent via UDP from WSJT-X to JTAlert. JTAlert then constructs an ADIF record and will use whatever the logging program needs to send it....typically using a TCP connec

That's JTAlert -- looks like the DX Call box got cleared before JTAlert logged it since the partner field is blank. Either you cleared the fields or you have JTDX set to clear the fields after logging

Mike W9MDB

The ???m indicates WSJTX is not talking to JTAlert. Turn off JTAlert and run message_aggregator in the WSJTX\bin directory. message_aggregator will show you messages WSJTX is sending out and confirm W

You don't need the secondary UDP server. Turn it off. JTAlert does all the talking to ACLog. Mike W9MDB

And if you don't want to load a 3rd party application I have a powershell script on my QRZ page that should work on Windows 10 Here's a direct link. https://www.dropbox.com/s/e9iwx6avh8kpvv4/jtalertem

If have any AC adaptors like 24VAC for sprinkler or alarm systems those are great pickup sources from all the wiring involved (nice big antenna field on those systems). So you can choke those AC wires

You select what log to use -- but it should be the adi file. The others are not QSO logs at all. Strongly recommend you get one the logging programs though...will make your life much easier although t

The other thing that has worked is to export your database. Delete the old one. Make new one. Then import. Mike W9MDB

WSJT-X only enables TX on CQ calls. Seems like it should also do it if it contains your own call....not sure if that's supposed to happen. But it would be a WSJTX limitation -- not JTAlert. Mike W9MDB

#FT8

Can we get the FFMAGrid as a separate user-defined checkbox though? I can easily modify my script to check for FFMAGrid but that would then defeat the regular grid alert which one would want to suppre

https://support.microsoft.com/en-us/windows/add-an-exclusion-to-windows-security-811816c0-4dfd-af4a-47e4-c301afe13b26 Mike W9MDB

Antivirus removed it. Reinstall Make an exclusion for the JTAlert program folder. Mike

Your menu doesn't look like this? Mike W9MDB

Mike W9MDB

Try HamApps\JTAlert\KX9Q\Config Mike W9MDB

Just rename it temporarily to HamAppsOld JTAlert will create a new config. This fixed one other user that I know of. Mike W9MDB

Shut down JTAlert and try renaming the HamApps directory then start JTAlert again. See if that fixes the problem. Mike W9MDB