I'd tell you a UDP joke... but you might not get it. de Laurie VK3AMA

JTAlert provides for setting one or more myQTHIDs to be used for any of the Alert types with each Alert type having independent settings. This allows for setting the State Alert to only consider speci

Dave, I note the VK CB lookup returns a bad url message for "https://www.aca.gov.au". The address should be "https://www.acma.gov.au" de Laurie VK3AMA

Edit the adif file and replace the incorrect header tag <eh> with the correct tag <eoh> This is a defect in the current WSJT-X release. de Laurie VK3AMA

Ed, What does the QSO after this one look like in the DXK log, does it have the same name & address information? If so, than you likely started a new QSO in WSJT-X (DX Call got changed) before you had

JTAlert correctly identifies OD5KU as being in Lebanon. The QRZ XML lookup also correctly returns the Lebanon data. Do you perhaps have a previous QSO with OD5KU in your DXK log that has the incorrect

IMHO, if you want to spot your Log, at least spot the Mode. None of your 6m Cluster spots contain any message. de Laurie VK3AMA

Have you enabled the logging of Contest Exchanges in JTAlert? You need to enable the "Log WSJT-X Contest Exchanges" option in the JTAlert Settings, Logging section. You will need to scroll the "Loggin

FYI, JTAlert doesn't do anything specific with Launcher, it is just another executable and treats it no different from any other executable. The JTAlert Auto-Start code doesn't have any executable spe

1. Wrong. JTAlert can log to DXKeeper and HRDLog.net simultaneously as well as several other online logs (but not LoTW). 2. Wrong. JTAlert can upload QSOs to QRZ.com BTW it is JTAlert not JT-Alert wit

There have been no recent posts on the HamApps group regarding SFI data not being logged. There are no messages waiting moderator approval. I don't know where you posted your question, it definitely w

JTAlert doesn't include non-active Lotw participating callsigns in the database. VP8PJ last uploaded to LoTW ~11 years ago. 11 years is outside the threshold of 3 years uses to strip non-active callsi

Installers randomly running the setup of an unrelated program is not common, but common enough that I have seen it several times over the years. A common cause is a Temp directory that is long-overdue

Bill, I would not classify this as misuse. The option was provided (many years ago) after numerous requests for such since JTAlert was automatically logging the Distance. Since there is no adif standa

Paul, JTAlert Settings window, Logging section, scroll the options down until you see the "Log bearing (heading) to ANT_AZ field" checkbox then enable it. The value logged is the value JTAlert used to

My 2cents, also consider excluding the DXKeeper & SpotCollector databases (directories and files) from AV real-time scanning. These database files get hit with lots of reads/writes and some AV softwar

Also, the OP mentioned JTDX which can be a real CPU hog if it hasn't been configured correctly. JTDX has an extended set of decoding options (compared to WSJT-X) in an effort to pull out more weak dec

Are you sure their local spots and not spots entering SC from the Cluster? de Laurie VK3AMA

Turn off DXKeeper logging in JTDX. de Laurie VK3AMA

Paul, JTAlert SpotCollector spots are only local, they never leave SpotCollector, that is they never reach the DX Cluster for the world to see. SpotCollector spots are useful for those who may have JT