Issue is fixed. Problem was I did not save tq6 certificate and create p12 backup when I received my new tq6 certificate. Had I done that, I would have been prompted to create a passphrase. The

Yes, thanks for that Dave. I have info in Comments that I use when I load a call sign. Don WB6BEE

Great. Thanks! de K1ESE

+ AA6YQ comment sbelow I think this is the replacement page: http://www.arrl.org/iaru-hf-world-championship 10.2.1. The Cabrillo file <http://www.kkn.net/~trey/cabrillo/> format and

NO! THERE IS NO "PROBLEM" WITH JTALERT. The issue is that WSJTX supplies *ONLY ONE FREQUENCY* in it's "QSO Logged" UDP Message. You would find the same result from *direct* integration between WSJTX

Hi Dave, I think this is the replacement page: http://www.arrl.org/iaru-hf-world-championship 10.2.1. The Cabrillo file format and specifications. (This link takes one to the generic "Cabrillo

Thanks Dave. After I posted I figured out that the trouble is with what JTAlert is putting in the ADIF that feeds DXK.

+ AA6YQ comments below + "Failure to retain previous Comment/QSLMsg state" is a defect that has been corrected in the next version of DXKeeper. 73, Dave, AA6YQ

I really like the new Capture Window configuration settings. However, I am not used to the Comment/QSL Message text box always defaulting to QSL Message instead of Comment. I keep forgetting and

+ AA6YQ comments below TQSL start date is 2021-06-30. End date is 2024-06-29 I just now instructed TQSL to create a backup using "help/backuprestore. Never used that tool before Queried Groups.

Please add "read" command to set inizial status of user-defined controls, to be executes when commander is launched to refresh the controls status at initial value. + Commander supports more than 120

Dave - typo. DXK upload is looking for a "TQS passphrase" not "paraphrase". I never recorded a "passphrase" when I received new certificate in June. Jim K7EG

On Mon, Jul 12, 2021 at 10:28 AM, Dave AA6YQ wrote: https://lotw.arrl.org/lotw-help/backuprestore/Dave TQSL start date is 2021-06-30. End date is 2024-06-29 I just now instructed TQSL to create a

Please add "read" command to set inizial status of user-defined controls, to be executes when commander is launched to refresh the controls status at initial value. Thanks

+ AA6YQ comments below + DXKeeper logs the QSO specified by the ADIF record it receives via TCP from JT-Alert; it makes no changes to the contents of this record. 73, Dave, AA6YQ

+ AA6YQ comments below + Did you ever direct TQSL to create a backup, as described here? https://lotw.arrl.org/lotw-help/backuprestore/ + Please start TQSL, select its Main window's "Callsign

Thanks Joe, I changed JTAlert to log to its own ADIF file and it showed the rcv freq the same so I'm thinking the DXK is fine. I've been using the older version of JTAlert because I can't get the

JTAlert 2.16.17 is badly out of date. The current version is 2.50.2 My WSJTX 2.4.0/2.5.0-rc3 and JTAlert 2.50.2 system also logs the TX and RX frequencies the same. AFAIK, that is the way they

I just reverted back to DXK ver 16.1.5 and it's still happening. Dale AA1QD

tQSL "passphrase" is the old password for your certificate. See: <http://www.dxlabsuite.com/dxlabwiki/LotWRemovePassword> in the DxLab Wiki. This information has been around for about as long as