Got it, Laurie...thanks to Mike while you were sleeping!

Well, that is convenient! :) Are there any limitations on the port number that you use other than it cannot be in conflict with one already in use? Ed, K0KC k0kc@... http://k0kc.us/

Mike, Thanks for the input...I assumed that was the case. Since the second instance of JTDX (or WSJT-X) requires a different UDP port number, is it not possible for that instance to communicate with J

Laurie, I have been using JTAlert for many years, but never have had the need to launch multiple instances until today. I am using two instances of JTDX and have changed the default UDP port number fr

Laurie, I did find a few minutes to check out the suggestion in the link below and it seemed to take care of the problem...thanks! Ed, K0KC k0kc@... http://k0kc.us/

#FT8 #JTDX

Laurie, I will have to give that a try tomorrow my time...I will let you know. Ed, K0KC k0kc@... http://k0kc.us/

#FT8 #JTDX

Whoops...I was using JTDX 2.0.1 rc133_2. Sorry! Ed, K0KC k0kc@... http://k0kc.us/

#FT8 #JTDX

I experienced a similar problem when using JTDX 2.0.2 rc133_2...went back to JTAlert 2.12.10 and things seem to be working fine. Ed, K0KC k0kc@... http://k0kc.us/

#FT8 #JTDX

Laurie, I currently use both WSJT-X and JTDX with JTAlert. I like the feature of JTDX that allows me to filter call signs so that only calls with CQ/RR73/73 show up in the band activity window. I also

Laurie, The older version is working as expected. Ed, K0KC k0kc@... http://k0kc.us/

Yep, I suspect that FT8 is the culprit! Ed, K0KC k0kc@... http://k0kc.us/

Laurie, I have currently configured JTAlert to automatically upload logged contacts to HRDLog.net. This has worked well for me for several years, but recently I have experienced a number of missing QS

Gary, Send one to K0KC...I will respond if I get it. Ed, K0KC k0kc@... http://k0kc.us/

Bruce, You need to click on the JTAlert window once first to make it the active window (focus) and then hit F5. This has fooled me more than once. Ed, K0KC k0kc@... http://k0kc.us/

Rudi, WSJT-X uses the symbol # for JT65, @ for JT9, and ~ for FT8. JTAlert is just being consistent with that notation. Ed, K0KC k0kc@... http://k0kc.us/

Laurie, I would be pleased to test if you need me. I have made about 250 FT8 QSOs and about 15,000 JT65/JT9 QSOs. Ed, K0KC

#FT8 #Beta

G4EST de K0KC EN80 Ed, K0KC k0kc@... http://k0kc.us/

Dave, JTAlert will notify you when an update is available in the upper left-hand corner of the App window and then you will have to go to the HamApps page to download an up-to-date call sign database.

Laurie, I am glad to hear that it was a bug! I thought that "old-timers disease" was beginning to set in here as I just could not figure out why "confirmed" would be displayed with no boxes checked. E

Laurie, Yes I did have all QSL confirmation types unchecked. I changed it to a check in the LOTW box and re-started JTAlert and everything seems ok now. I am not sure that I understand, but whatever w