FYI, Information overload can be managed by applying filters. On very busy bands, filtering out non-alerting callsignsns greatly reduces the number of callsigns displayed. I personally go one further

Setting up SpotCollector to work with WSJTX is no different from JTAlert, both require a single item to be checked. Under SpotCollector it is a checkbox, under JTAlert it is a menu entry. Setting up W

I mentioned HamSpots only because it showed me that you're using JTAlert, which prompted me to post my last message If you don't want DXKeeper performing a lookup when the DXCall in WSJTX changes then

HamSpots shows you're posting spots via JTAlert. That to me suggests you have DXKeeper lookups enabled within JTAlert. Turn them off via the "Applications -> DXLab Suite" section of the main Settings

When I first read the MS fluff, it reminded my of the ill-fated Windows Metro style first introduced with Win8. Lots of social-media type content, tiles and widgets, primarily geared to mobile/tablet

If JTAlert is repeatedly sending the WSJT-X DXCall to DXView it will be because JTAlert is getting repeated updates on the DXCall. Based on recent similar issues, the problem is very likely incorrect

Is that done through using multicast UDP or unicast with unique ports for each WSJT-X instance? de Laurie VK3AMA

It doesn't. It only ever sends one instruction, no repeats ever. A zombie JTAlert process running perhaps? I suggest the OP restarts his PC and see if that corrects the behavior. FWIW, there have been

The go QRT response (from me) was an attempt at levity. Sorry you took it literally. Your problem is that you don't want to see spots of your Callsign from other FT8 users. You can't force everyone el

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