Laurie: Been doing some digging. They had server issues earlier in the week that I reported. You cannot get into their help website/page. I'm guessing it is there problem as you suggested. Bob W8RID

#HRD #JTDX #FT8

Several posts by affected users on the Yahoo forum, but nothing from QRZ staff. https://forums.qrz.com/index.php?threads/xml-feed-down-again.630140/page-2 de Laurie VK3AMA

#HRD #JTDX #FT8

QRZ is not authenticating XML requests. Logins to the webpage are also failing. The problem is with QRZ, so we will have to wait until they sort out whatever problems they are having. de Laurie VK3AMA

#HRD #JTDX #FT8

This one is weird. It was working fine yesterday and all along. Now this morning, It is not pulling the Name and QTH of the contacts I am working. With this it leaves the name blank when it posts to H

#HRD #JTDX #FT8

Philip, Thanks for the confirmation that setting change was the fix. I received about 6 other similar reports, so I am confident that is the answer. The next JTAlert release, currently with the Beta t

#FT8 #JTDX

Fixed it for me. Philip G7JUR

#FT8 #JTDX

Bobby, JTAlert doesn't control whether WSJT-X initiates Transmission, that is controlled by WSJT-X itself. Unless there have been any changes I am unaware of, WSJT-X will only activate TX if the decod

#FT8 #JTDX

Laurie, what I meant was the problem of clicking a call in JTAlert would work the first time and sometimes the second, but after that it would not enable the transmit. After a restart, it would work a

#FT8 #JTDX

JTDX is not compatible with JTAlert 2.13.0 with respect to Callsign highlighting instructions sent by JTAlert. JTDX users need to turn off the "Color Band Activity Callsign with alert colors" checkbox

#JTDX #Important #Announcement

Laurie: Just installed 2.13.0 and made the change. So far it has corrected the issue. I will give it a better workout later today and tomorrow and if anything comes up I will let you know. Thanks Bob

#FT8 #JTDX

What problem is that? Are you referring to the problem reported by JTDX users? I can't see how that would be the case as their problem is related to how JTDX is coded internally. Does this help... htt

#FT8 #JTDX

Same problem with WSJTX. Back to prior JTAlert version and all OK. Bobby/N4AU

#FT8 #JTDX

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@arrl.net http://k0kc.us/ Ed, Try 2.13.0 again. See this

#FT8 #JTDX

Laurie, I will have to give that a try tomorrow my time...I will let you know. Ed, K0KC k0kc@arrl.net http://k0kc.us/ Ed, Try 2.13.0 again. See this message... https://hamapps.groups.io/g/Support/mess

#FT8 #JTDX

Ed, Try 2.13.0 again. See this message... https://hamapps.groups.io/g/Support/message/23581 Let me know if this corrects the JTDX problems you experienced. de Laurie VK3AMA

#FT8 #JTDX

Bob, Try 2.13.0 again, but this time go into the JTAlert Settings and turn off Callsign Coloring. "Applications -> WSJT-X" section of the Settings window. Let me know if that corrects the JTDX behavio

#FT8 #JTDX

Whoops...I was using JTDX 2.0.1 rc133_2. Sorry! Ed, K0KC k0kc@arrl.net 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@arrl.net http://k0kc.us/

#FT8 #JTDX

Weird issue here. I upgraded today. Using JTDX and JTAlertX. Everything was seemingly working fine. Click on a call sign in JTAlertX and it triggered JTDX. Logged fine. Then clicked on a call sign and

#FT8 #JTDX

Got it fixed. I mistyped one of the TCP server numbers. Bob

#JTDX #HRD