CQRLOG - open discusion

QSL needed in WSJT-X CQ monitor

Submitted by km4hqe on

I'm seeing QSL needed in the WSJT-X CQ monitor and I have that band worked and confirmed on LoTW for the DXCC country. So I wondered what logic is use to determine a QSL is needed? I have "include LoTW and eQSL confirmed countries in DXCC" and "use LoTW and eQSL confirmed countries for new country or new band country etc info" checked.

I'm running what I think is the latest version of CQRLOG that I built from source. But it shows version 2.2.0 as the version.

73

Stan
KM4HQE

Forums: 

Running on Fedora 28 requires extra package (for now)

Submitted by AJ5E on

In case anybody is upgrading to Fedora 28:

I'm running CQRLOG on Fedora 28. It's working great now, but I had to add an extra package, mariadb-connector-c-devel to get it working. Without that devel package, CQRLOG gives this error:

. . . . Can not load default MySQL library ("libmysqlclient.so.16" or "libmysqlclient.so").

Installing that devel package provides the libmysqlclient.so library, and happiness ensues.

Forums: 

CQRLOG UPLOAD TO CLUBLOG ISSUE

Submitted by K5KV on

CQRLOG ONLINE LOG UPDATE TAKES A LONG TIME TO UPLOAD HALF A DOZEN NEW QSOS TO CLUBLOG . IT UPLOADS A CALL, THEN LATER DELETES IT AND THEN DOES AN UPDATED UPLOAD FOR SAME CALL. IT UPLOADS EACH CALL TWICE AND DELETES EACH CALL ONCE. ANYONE KNOW IF THIS IS CORRECT BEHAVIOUR? IS DELETING ANYTHING CORRECT? A MANUAL UPLOAD TO CLUBLOG WITH AN ADIF FILE SEEMS TO WORK MUCH FASTER.
A RECENT UPDATE WITH THE ONLILNE LOG FEATURE OF CQRLOG GAVE THE FOLLOWING RESULT IN THE STATUS BOX. ALL THIS FOR NINE QSOS.

Forums: 

I can't change from CQRLog v 1.8.2 to v 2.2.0-1

Submitted by dl6ndk on

Dear all,

I have installed the CQRLOG version 1.8.2 and work with this successful.
But now I will change to the newest version 2.2.0-1 and get during the installation try following error message:
libmariadbclient-dev dependence error.

Ok I removed the mysql packet and installing the mariadbclient.
After that the CQRLOG 1.8.2 is again fine working, but during the next installation try from CQRLOG 2.2.0-1, I get the same message as before.

What can or must I do to upgrade the CQRLOG to the version 2.2.0-1?

Forums: 

CQRLOG and WSJT-X FT8

Submitted by km4hqe on

I have CQRLOG working with WSJT-X and rigctld to control my Omni VI and log QSOs. But, I noticed 14.076 is the frequency used for the FT8 QSO on 20 meters. I expected to see 14.074 Why is the logged QSO record showing 14.076 for the frequency? I haven't checked other bands to see how far off they are.

What do the different colors in the WSJT-X cq monitor mean? That's a pretty neat window. Would be nicer if it showed LoTW users and eQSL users. Perhaps that's what the colors mean?

73

Stan
KM4HQE

Forums: 

ANYONE SEEN THIS BEFORE?

Submitted by K5KV on

ClubLog: Uploading WB6BEE ... OK
ClubLog: Uploading AE4DT ... OK
ClubLog: Uploading AF5WS ... OK
ClubLog: Deleting original WB6BEE ... OK
ClubLog: Uploading updated WB6BEE ... OK
ClubLog: Deleting original AE4DT ... OK
ClubLog: Uploading updated AE4DT ... OK
ClubLog: Deleting original AF5WS ... OK
ClubLog: Uploading updated AF5WS ... OK
ClubLog: Deleting original WB6BEE ... OK
ClubLog: Uploading updated WB6BEE ... OK
ClubLog: Deleting original AE4DT ... OK
ClubLog: Uploading updated AE4DT ... OK

Forums: 

Cqrlog+Lotw issues

Submitted by hi8smx on

Dear all, I'm a first time Raspi user and first time Cqrlog user, with minimum experience in Raspian so please bear with me, as probably I'm asking a dumb question.

I've been enjoying my Raspberry 3 Pi with Cqrlog for a couple of days now and so far so good with just one exception: uploading and downloading from Lotw. Whenever I try to download from Lotw I get the following message:

NOT Logged
Error: -2
Error:
Error: ssl_openssl

And when I try to export to Lotw I get the following message (the adi file is created and signed correctly):

Forums: 

DXCluster Spots

Submitted by km4hqe on

Is there a way to change the mode the New QSO window defaults to when one double clicks on a spot in DXCluster? For example, I double click on a spot in DXCluster that's 14.074, which would "normally" be FT8, but the New QSO window defaults to RTTY when Auto is checked. So, is there a way to define what range of frequencies are "normally" used for a given mode?

73

Stan
KM4HQE

Forums: 

Long County-field

Submitted by oh1kh on

Hi!

Just happened to get error popup "Data too long for column county" when logging FT8. Right answer is "OK" then fix county field and save qso again.
County information was fetch from Hamqth.com that has data as "County: KDR#1130 EPC#23109 RDRC#393" there for that callsign.

Should we protect "county" field so that it would cut string from first space, or take only length that database field can hold ?
In that case there should maybe be similar protect for all NewQso fields. (bigger job...)

Forums: 

Pages

Subscribe to RSS - CQRLOG - open discusion