I'm trying to create a new log but having difficulty. If i select "create or open a log" menu option, I get taken to the MySql connect dialogue box where the only options available to me is to open my existing log. I could go in the back end i suppose and create my new log using MySql, but shouldn't i be able to do that via CQRLog? This issue is not related to the current new version of CQRLog I noticed it with the previous version also.

Well Both Mysql and Postgresql are great databases for the use of local and remote servers thats no problem at all.
if your hosting a webpage to the outside world i always recomended both of them on a local server and local port to shut down the outside world port connecting to it.

But theres also SQLITE database also great for local fullly grown database stored in one file,
thats why i request sqlite to the wishlist of cqrlog.

73's PD1SR, Roel

Hi Petr,

i have the impression that no dx-cluster spots from the 60m band appear in the band map.

Is my impression correct, or am I doing something wrong?
For the DX cluster settings, 5MHz is selected.

73, Wolfgang
DL2KI

Hello,

only as a wish : a new updated built for RaspberryPI will be strongly appreciated, also if the current 1.8 runs quite well

Thank-you for your effort
Regards
IU1IPB Ugo

Heloo,

New to Linux, new to CQRLOG. I backed up my log in adif (adI) format and can only get about 200 QSO's imported. I have over 8900 Q's in the log. I can provide my log if you like.
73
K5RHD
/randy

Hi Petr,

i would like to use another program with CAT in addition to CQRLOG.

With "socat" I had so far no success. Access to "/dev/pts/x" is obviously not possible. Do you know another solution.

73, Wolfgang
DL2KI

Hi Petr,
having trouble starting CQRLOG on a fresh install of debian 9 64 bit.
First I had to install libmariadb-dev-compat package but after that I now get:

Error during connection to database: TMySQL56Connection can not work with the installed MySQL client version: Expected (5.6), got (5.5.1).

Any ideas?

Thanks & 73

Log follows:

vittorio@ik1rac:~$ cqrlog --debug-1

(cqrlog:4127): Gtk-WARNING **: Impossibile trovare il motore del tema in module_path: «adwaita»,

If you want to be alert when a desired callsign appears in cluster, add this command (Linux) in Preferences -> DXCluster.
You should install zenity first.

zenity --info --text='Callsign $CALLSIGN detected at $FREQ $MODE' --title=Info

Also you may set display duration in 5 seconds (Thanks DL2KI). After the window closes automatically.
KDE
kdialog --title=Spot-Info --passivepopup "Callsign $CALLSIGN detected at $FREQ $MODE" 5

Right after starting to accept FT8 eQSL decided to upgrade their mode definitions to those of ADIF 3.0.4, so the mode is now "PSK (PSK31)" and not PSK31.

eQSL offers the option to upgrade your outbox, but it seems cqrlog currently is not ready for this change as it does not recognize new PSK (PSK31) contacts at the moment. I saw no announcements from eQSL so I guess they surprised all software developers.

From the eQSL_error.txt file:

I have had intermittent problems in getting CRQLog to talk to my FT2000 for quite some time now, it's always been a battle. I have periods of it working then periods when it wont.

I have recently rebuilt my PC and now run Linux Mind KDE.
Reinstalling CQRLOg onto my new environment saw a brief period where CQRLog would talk to my FT2000, but now it persistently refuses.

I recently installed TR4W contesting software on my KDE PC and even though its running under WINE, per performs flawlessly connecting to my FT2000 every time!

Hi,

During last week a new mode FT8 is introduced as a part of wsjt-x. FT8 is faster. TX periods only 15sec, but also that's why it is a bit less sensitive mode mainly planned for ES openings on 6m and up, but it is usable also in HF. too. It is a bit wider than JT9, but narrower than JT65.
You can get this wsjt-x 1.7.1-devel only by compile it from source at the moment.
There was some growing activity yesterday on 14.079Mhz .