CQRLOG - bugs

"Callbook -> Database update" hangs...

Submitted by N9KT on

Ubuntu 20.04
CQRLOG 2.4.0 (001)
Using HamQTH.com for Callbook support

When I run "Callbook -> Database update" it hangs on the call MQ2JBS. I was hoping it would timeout and move on, but I have left it for hours on three different occasions and it just sits there on that call.

What can I do? Is there any way to help debug this?

Thanks!
-David, N9KT

Forums: 

Access violation. Rpi4 CQRLOG WSJT-X

Submitted by NM2R on

PC Rpi 4 2m ram
OS Rasbain buster
CQRLOG 2.3.0 (001) 2018-06-17
rig 1 Hamlib Dummy
WSJT-X V2.1.2

I am working on a Rpi4 for logging and digital for my truck. I have a very nice ft891 with builtin usb conection. But it is easier to test my setup on my bench in shack with my dx1200. I tested cat control with ft8 on ft891 and it worked great.

I brought the Pi back in house loaded cqrlog ( no issues at all loading). set radio on wsjt to none and ham lib dummy on cqrlog. All i really wanted to do is confirm logging of qso with ft8.

Forums: 

Propagation type RPT (repeater) should not be uploaded to LoTW

Submitted by PE4KH on

I'm one of those people who logs all radio contacts, including those via a repeater. Thanks to the cool and upgraded features in cqrlog I can now set propagation type RPT (repeater) correctly on the Satellite tab for the contact.

But that will make the next upload to LoTW fail. tqsl will not accept the contact (which matches the LoTW rules: repeater contacts don't count). So tqsl ends with status code 9 "some QSOs suppressed" which means cqrlog will mark none of the contacts as uploaded and the problem continues.

Forums: 

rigctld, TRX Control, WSJTX etc logic makes no sense

Submitted by VE3YDK on

In CQRLog the handling of rigctld is nonsensical at best and problematic in some use cases.

There are two main issues.
1. rigctld is not auto launched when TRX control window is opened. This means that TRX control is non-functional.
2. rigctld is not auto closed when TRX control window is closed.

In the case that "Run rigctld when program starts" is enabled in settings, TRX Control is not closed (along with rigctld) when WSJT-X or FLDigi modes are enabled, causing a conflict between rigctld and WSJT-X or FLDigi.

Forums: 

RBN-Monitor settings, bug and wishlist

Submitted by DL2KI on

Hi,

in the settings of the RBN monitor, under "Bands", "All", the 60m band is missing. I can't determine if the 60m band is processed in the software at the moment.

An "autoconnect" of the RBN monitor and an addition "Callsign alert" would also be good.

Because of the large empty space in the "New QSO" window, the arrangement of the windows is difficult when using the RBN monitor. Why a contest area in the "New-QSO" window, if there is already a separate window for this.

Forums: 

CQRLOG 2.4.0 - Telnet DX cluster does not work

Submitted by DL2KI on

Hi,

after upgrading from Kubuntu 19.10 to 20.04 another problem occurs.

The DX-Cluster Window "Telnet" does not work or stops after a few lines. The telnet connection in the Linux console works fine.

After a restart of CQRLOG spots appear in the "telnet" window. After some time, however, the window freezes. After a restart the "telnet" window works again, but then freezes again after some time.

The DX-Cluster Window "Web" in CQRLOG works as well.

73, Wolfgang
DL2KI

Forums: 

CQRLOG 2.4.0 - "ClubLog: Upload failed! Check Internet connection"

Submitted by DL2KI on

Hi,

after the update from Kubuntu 19.10 to 20.04 the clublog upload does not work again. It seems to be the same problem as here: https://www.cqrlog.com/node/2346

In CQRLOG 2.4.0 this message appears.

ClubLog: Upload failed! Check Internet connection

Internet connection is available and working. "mariadb" was and is installed.

73, Wolfgang
DL2KI

28.05.2020:
A compilation of the current source code does not change the behaviour.

Forums: 

K3NG CW Interface

Submitted by VA3KOT on

CQRLOG's K3NG CW interface does not work unless I have opened Minicom or Arduino Serial Port Monitor first. Then it works just fine. In order to use the K3NG CW interface I have to leave Minicom running on the same port (in my case /dev/ttyUSB1) at the same time. If I close Minicom CQRLOG's K3NG CW interface stops responding. Is this a bug?
John, VA3KOT

Forums: 

Fedora 32 - Cqrlog daily - error witch rigctld

Submitted by sp6ina on

Hi.
I have problem witch connect radio DX3000 to cqrlog. Cqrlog can't automatic start rigctld. Cqrlog don't send command to rigctld and i can't manually in terminal open connect when cqrlog is open. I can only on terminal open connect witch rigctld and after that open cqrlog - everything work ok.

i open cqrlog from terminal:
cqrlog

Cqrlog Ver:2.4.0 (118) Date:2020-04-20
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****

Forums: 

Unsecure passwords for eQSL

Submitted by OE6PAD on

Hi,

It seems CQRLOG forces to choose unsafe passwords for eQSL. The password field in the settings only allows passwords with a lenght of 8 and only digits and numbers. The field seems to accept special characters like $%_&, but the password (e.g. like %24_dhj8) will not work. There be an error message, when you try to upload your log.

Forums: 

Pages

Subscribe to RSS - CQRLOG - bugs