CQRLOG - open discusion

access violation

Submitted by kf4cq on

have cqrlog 2.1.0 (001) on 2 different computers one is linux mint 18.2 other ubuntu 16.04

on opening qso list and scrolling down a blank error window opens and program freezes at same point on both computers... here is dbug error...

"
select id_cqrlog_main from cqrlog_main order by qsodate,time_on LIMIT 1

select count(*) from cqrlog_main where (qsodate = '2015-10-08'and time_on <= '20:37') or qsodate < '2015-10-08' order by qsodate DESC, time_on DESC LIMIT 500

Forums: 

Mode mismatch on import from eQSL

Submitted by la9nka on

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.

Forums: 

RST sent/rcvd not set when using wsjtx remote

Submitted by DL7OAP on

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.

Forums: 

Pages

Subscribe to RSS - CQRLOG - open discusion