Once again a new feature!

4 posts / 0 new
Last post
Once again a new feature!

Found once again a new feature from cqrlog. I should have known it is there because I have looked the source code at point what makes it, but I newer think it in that way!

I downloaded cqrlog_2.5.0_amd64.tar.gz from download page and extracted only the "cqrlog" file from cqrlog-2.5.0/usr/bin folder. I normally use my test binary 2.4.0(135) that is so close to 2.5.0 that help files etc in /usr/share/cqrlog folder do not need refreshing.
So I got the "cqrlog" file, but because i all ready have "cqrlog" file in /usr/bin (that is the 2.4.0(135)) I renamed this extracted file to "cqrlog250" and moved it to /usr/bin folder.

Now I can start the 2.4.0(135) with command "cqrlog" and the official 2.5.0 with command "cqrlog250".

First start with "cqrlog250" was surprise. It claimed that "It seems that you have not used cqrlog before...."


After some checks I found out that the binary name in /usr/bin folder, this case /usr/bin/cqrlog250 makes the user directory to be "~/.config/cqrlog250" and because that did not exist there program was right by saying that I had never used it before.

After all these years and play with source this was again totally new feature to find!

So you can have many versions of cqrlog in same computer if you just make different name binary file copies into /usr/bin. and startup icons for them (if you do not want to start them from console).

They all make their own database to ~/.config/cqrlog[your_name_extension] if you use "Save log data to local machine".

Also they all can connect to same external sql server, but in that case be aware that if your cqrlog versions are very different they may change the settings saved to sql server. And maybe logs too if the difference in cqrlog version is very big. So you have been warned about common external database server usage with multiple copies of cqrlog binary!

Dear Saku,

Dear Saku,
Can I exploit this feature running two identical versions of cqrlog on the same computer at the same time, accessing the same log database on the computer?

At my home shack i use the SunSDR2-DX radio with independent CAT control on both receivers. Normally I connect cqrlog to receiver 1 using hamlib (rigctl), and connect JTDX to receiver 2 using rigctl (rigctl-jtdx). I then use the cqrlog "remote mode for wsjtx" to connect JTDX to cqrlog.

This setup works well, but my operating habit is to let JTDX run while I am looking for CW dx using receiver 1. As the call sign field is grayed out on New QSO windows using the remote mode for wsjtx, I tend to uncheck it working qsos on receiver 1, and forget to activate it when doing qsos using the JTDX.

This could be avoided by using two instances of cqrlog log database.

Alternatively, is it possible today to set up cqrlog to monitor changes in the wsjtx_log.adi file and add changes to the log? I can not find anything about this in the documentation.

73 de LB2EG Richard

Once again a new feature!

Hi Richard!

Interesting question. I have not tried that. You should try.
It seems that you use "save data to local machine" option and have log data in ~/.config/cqrlog/database folder.
Using "real" mysql/MariaDB server running at port 3306 would be easier in some way.

log in ~/.config/cqrlog/database using mysql_safe thread started by cqrlog:

- easy to backup all by copying whole folder structure to backup drive/stick
- when running two cqrlog the one that holds logs in ~/.config/cqrlog/database must be started always first and be running even if not in use and closed as last cqrlog

log in Mysql server running (always when PC is running) at port 3306:
- saving log data needs script that uses mysqldump. Backup should be made when neither one of cqrlogs is running.
- both cqrlogs can run at same time, or alone. Starting order does not matter.

Of course in both cases adf backup can be used but it saves just log data, not cqrlog settings.

First make another copy of cqrlog binary by:
sudo cp /usr/bin/cqrlog /usr/bin/cqrlogB
or give what ever name you want instead of cqrlogB

Test that second cqrlog runs ok.

With both cqrlogs open preferences/program push button Configuration settings. There you can select what settings are common and what are local for running cqrlog. I would start by setting all as local. Then thinking what settings could be common. Maybe some upload settings could use same setup.

Then decide the log database usage.
If you use cqrlog (the first one) ~/.config/cqrlog/database then yo do not need to change anything in that cqrlog.
At second cqrlog uncheck "save log data to local machine" and select server localhost, port 64000, user cqrlog, password cqrlog and try to connect. At that point cqrlog1 must be running already. Select checkbox remember me. You can also check autoconnect but remember that cqrlog1 must be running first.

If you use PC's running mysql server at port 3306 you have first set up user for cqrlog. You find examples by putting word "grant" to forum search box. Here is one of them https://www.cqrlog.com/comment/8110#comment-8110
When that is done you just set up cqrlog database connect same way in both cqrlogs.
Uncheck "save log data to local machine", server localhost, port 3306, user cqrlog, password cqrlog (must be same as used in GRANT command), check remember me and autoconnect.

If using second way you have to move your logs to 3306 database server. adif export/import is the easiest way as you have to make new cqrlog settings anyway for both cqrlogs using local-options.
BTW you can do utils/configuration/export at open database window from your current log and then use that file as configuration/import base settings for both cqrlogs. And when it is imported then change the local settings.

Cqrlog can not read wsjtx adif log and pick updates from it. Only way is to import it manually and at import stage check duplicate checking to prevent once imported qsos to be imported twice. Then it picks up just new qsos.


Once again a new feature!

Hello Saku,
thank you for your feedback!

I will try to find time to do the testing in the weekend. Maybe I will learn a bit more about databases doing this too.

73 de LB2EG Richard