I followed the setup instructions in the help file and I still have the problem that the State/Province field is blank. If I simulate logging a QSO by clicking on Log QSO in WSJT and fill in the blank

When I had the situation earlier when no states were transferred, at that time I hadn't set WSJT into contest mode, I was just having regular QSO's and tried to log them, each one failed with an error

Thanks Laurie, might be worth while to add a sentence or two to the help file, I am sure there are others who may fall into the same trap I did since my default logging program doesn't really care whi

I used it today and it worked flawlessly during that 30 minute test window. I am not sure I will use it tomorrow, it appeared today to me that the default integration between JTAlert and DXK is much b

Like Garry, the state/province field never gets populated here either, all other fields are populated. Doesn't seem to be a problem when the QSO gets logged though. (and I followed the instructions po

I used almost the same setup, FT8 through JTAlerts and DXKeeper, RTTY through N1MM+. When you export from N1MM+ to an ADIF file, it perfectly imports into DXKeeper, I have done that before. So, Sunday

It is pretty straight forward, you position your cursor on a row in the band activity window, you should select the row that has the call sign in it that you wish to make contact with. Once you double

#FT8

Same issue here, downgraded to 2.15.3

Works fine here as well, absolutely no issues. I do have to add, what an amazing piece of software someone (we all know who) has added in his spare time and makes it available to everyone free of char

I see the opposite, most of my grids logged are 6 digits (I use WSJT-X, JTAlertX, DXLab). Occasionally, I find a logged record with a 4 character grid, those seem to always be the ones that respond di