Hello.

Over the last months, I have had several cases of eQSL's showing up as unconfirmed in my eQSL inbox (on www.eqsl.cc). When I check these claimed QSO's in CQRLOG I can find them, but with another mode; in particular, QSLs received for JT9, while I have them logged as FT8.

Usually, I just reject such cards as "incorrect mode", but then just recently I noticed that the CQRLog download from eQSL apparently had matched these JT9 QSL's to my FT8 QSO's, and tagged them as confirmed.

Hi,

i'm using cqrlog 2.1.0 and wsjt-x 1.80rc2 on my Ubuntu 16.04 system.
works all well.

I noticed that in the "remote mode for wsjt" the filed RST sent and receive are not set.
they stay on 599.

In the preferences under the point "fldigi/wsjt interface" you find a "RST from"-option for fldigi, but not for wsjtx. I tried to find out, what cause these behavior. I read the UDP protocol specification of wsjtx and found that the RST rapport is included.

It seems that CQRLOG didn't grab the RST rapport from the UDP WSJTX Messages.

CQRlog uses it's own QSL managers lists, but I noticed my Taiwanese call still refers to my old manager. How and where can I find someone who updates the list?

Updated TQSl to v 2.3.1. Now upload to lotw fails. Invalid mode ft8. I did add ft8 to the mode list in cqrlog. The error occurs as cqrlog tries to sign the upload file. How can I fix this?

I see that the HamQTH site is back up. I can log in and access call information bt I cannot get it to work with CQRLOG. I am still getting the Tag "" not found! error. Is there still work to do or am I doing something wrong? I tried changing my HamQth password but no luck.

73 Bill NZ0t