JTAlert gets the frequency from WSJT-X, and passes it along to the log program. JTAlert doesn't have any direct knowledge of the frequency, except what is passed to it by WSJT-X. 73, Jim N6VH

#FT8

Yes, indeed. My question is why does the recorded value for BOTH TX and RX reflect the audio offset associated with my TX? The recorded values for RX and TX are always identical to each other, and equ

#FT8

Split frequency does not change your TX frequency. Remember that USB is suppressed carrier. The only thing you are transmitting is the FT8 tones and they are always at the same frequency as the waterf

#FT8

I've been wondering for a while why the WSJT-X log contains only a single frequency. This is interpreted by my logging programs (e.g., DXKeeper, etc...) as TX==RX and recorded accordingly. In general,

#FT8

Problem solved. As I was looking around the PC trying to work out what the issue was, I found several Windows functions not working - for example right click on the start menu - Control panel wouldn't

#FT8

forgot to mention I am using the single click option to select a call.

#FT8

I found it. I did not have the accept etc. checks in WSJT-X for the UDP address which WAS populated OK. Sorry for not finding this sooner. Now clicking on a call in Alerts works beautifully. 73, K0AZ

#FT8

Suspect I am missing something in JT Alerts set up. Everything else seems to work fine. Cannot answer callsign by double clicking that call in the Alerts window. Any help appreciated. Thanks, K0AZ

#FT8

Both LotW and eQSL provide a file of users (LotW) and AG users (eQSL). Laurie downloads those files and the FCC license database which are included in the JTAlert callsign database that he updates app

#FT8

OK thank you, i will check on his version. I recently updated mine.

#FT8

Just was able to contact someone else via JTAlert texting. He said I had all three icons on my decode so it seems to be working but not sure why my other friend doesn't see them I would still like to

#FT8

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

Also on eQSL I have been authenticated and received the cert. I'll have to ask my friend what it shows for me in PSKReporter. I'm just not sure where these pull their info.

#FT8

I recently upgraded my callsign from W7AMC to AD7J. Now my friend says the only flag he has on my decode is TEXT, NO LoTW or eQSL. LoTW I have updated with new TQSL cert and have been uploading update

#FT8

Hi Joe, just a small correction, the architecture of WSJT-X (32- or 64-bit) is not relevant here. The architecture version of the Microsoft .NET Deskop Runtime needed is the one that matches the archi

#FT8

Sounds like the *wrong version* of dotNET 5.0.x is installed. You must install the *DESKTOP* version. If you look in the right hand column here: <https://dotnet.microsoft.com/download/dotnet/5.0> ther

#FT8

I have the PC now. Reading through the help file for JTAlert, it mentions about copying the information from the "About" screen for the current operating state, so I was going to have a look at that a

#FT8

Hi Laurie/Jim Laurie - SpotCollector has not even been downloaded, so don't think that is the answer. The only DXLab things downloaded are DXKeeper and DXCommander, but I don't think DXCommander is ac

#FT8

Just to be clear. JTAlert and SpotCollector can run concurrently. I do it all the time. But you cannot have SpotCollecter set to work with WSJTX directly. If you require SpotCollector to work with WSJ

#FT8

reading your other responses, my guess is that SpotCollector is running and it has WSJTX integration enabled. In that situation, SpotCollector is taking exclusive control of the UDP port and locking J

#FT8