CQRLOG - bugs

Date and Time of QSO

Submitted by w7ck on

There is a problem how CQRlog logs QSOs that start prior to midnight GMT and end after midnight GMT.

If you start a QSO prior to midnight GMT (23:55 example) and end the QSO after midnight GMT (00:05 example) CQRlog will take log the entry as 23:55 with tomorrows date. Then for the next 24 hours all logged QSOs will be logged PRIOR to the example above.

How long has this been going on and no one has noticed?

This means the date will be tomorrow's date but will have a time of say 23:55.

Forums: 

Cannot connect to radio when using cqrlog remote wsjtx

Submitted by kd2sam on

Hi, total new guy to Ubuntu and Linux.i have the latest version on Cqrlog from the web site and a fresh install of Ubuntu 20. Cqrlog and wsjtx work fine alone. But when I use remote for wsjtx it will not connect to the radio. I have searched, but have not found anything that seems to help. Thanks in advance.

Dave
Kd2sam

Forums: 

Invalid Mode when uploading QSOs to eQSL and LoTW

Submitted by w7ck on

I'm running CQRlog v2.5.2, fldigi v4.1.20 along with fldigi xmlrpc.

I currently have CQRlog setup to start fldigi as remote.

The problem I'm having is the way the mode gets logged. As an example. When operating the digital mode Olivia, it will log as Olivia-8/500 or Olivia-32-1k.
At the end of the day when I upload my new QSOs to eQSL and LoTW, I get errors telling me that the mode is invalid. I then have to go into each and every log entry and change the mode to a valid entry such as: Changed Olivia-8/500 to OLIVIA, changed THOR8 to THOR.

Forums: 

Errors on building from source packages in Debain 11 arm64

Submitted by KK4SVR on

Currently running 64bit Debian GNU/Linux 11 (bullseye) on a raspberry pi 4 that has been updated as of last night and while the sourcing of the file does attempt to install the cqrlog package there are errors on the install; not sure if its related to 64 bit or not at this point.

Forums: 

WSJT-X CQ-monitor - Upper/lower case in FT4 reporting

Submitted by 9H1ZZ on

Hi Saku!
Possibly due to classing FT4 as mode MFSK, I notice that, per band, any previously logged FT4 stations calling CQ always appear in CQ-monitor in UPPER case. Normally they should be reported in lower case, as happens in all other modes. Not really a problem, but still a bit confusing!
Robin, 9H1ZZ

Forums: 

WSJT-X CQ-monitor - Upper/lower case in FT4 reporting

Submitted by 9H1ZZ on

Hi Saku!
Possibly due to classing FT4 as mode MFSK, I notice that, per band, any previously logged FT4 stations calling CQ always appear in CQ-monitor in UPPER case. Normally they should be reported in lower case, as happens in all other modes. Not really a problem, but still a bit confusing!
Robin, 9H1ZZ

Forums: 

Downloaded eQSL entry before start date shows up in error log as not in CQRlog

Submitted by WB0NRE on

Raspberry Pi 4 running Bullseye 32-bit
Cqrlog Ver:2.5.1 (001) Date:2021-01-24

I have over 1000 entries in eQSL, the vast majority of them from before I started using CQRlog in mid-February 2022.

When I download with the starting date set as 2022-02-15, I can successfully download any new QSLs; but I also get an annoying error message claiming that I have QSOs that are not in my log. When I check the eQSL_error.txt, the entries are clearly not after my CQRlog start date. And oddly enough they are both from the same call, but over a year apart.

Any thoughts?

Forums: 

Pages

Subscribe to RSS - CQRLOG - bugs