I RECEIVED THE ICOM 7610 TODAY AND HAVE FOUND SETTINGS THAT WORK WITH THE 7610 AND CQRLOG. YES MY HAMLIB ETC IS UP TO DATE WITH THE IC-7610 AS RIG NUMBER 378 IN THE PULL DOWN MENU.

MY CQRLOG SETTINGS WERE:
RIG 378 Icom IC-7610
DEVICE /dev/ttyUSB0
POLL 2000
PORT 4532
EXTRA COMMANDS -r /dev/ttyUSB0 -m 378
SERIAL SPEED 19200
ALL OTHERS DEFAULT

THE ICOM 7610 SETTINGS ARE IN TWO SCREEN CAPTURE PHOTOS AND I CAN NOT PASTE THEM ON THIS PAGE. I CAN EMAIL THEM IF CONTACTED AT K5KV@ARRL.NET.

Hi,
I'm a new cqrlog user. Version: 2.5.2 on Linux Mint 20.1
Reading data from wsjtx does not work.
- wsjtx and cqrlog running on two PC's LAN connectet
- UDP server ports are set in wsjtx and IP address in cqrlog and ports are correct (wsjtx interface)
- starting remote mode for wsjt always reports: Offline with red color

what is going wrong?
Any help are welcome.
73 Hans

Greetings to this community.

I have recently installed CQRLOG, I have completed all my QSO's and little by little I am getting the hang of this good tool.

I have already managed to export to eQSL, but now I have problems exporting to LoTW. I have installed TQSL completing all the process including the certificate.

The question is: I use different QTH profiles. This is because nowadays I never transmit from home, it is always in portable mode, in different locations in the region.

Hi

I am using CQRLOG (001) under Ubuntu 20.04 successfully since quite long but today I updated Ubuntu with the usual sudo apt-get update ..... and I realised that both mariadb server and client had new versions.
Since the update, CQRlog does not work. Afater starting it all screens appears but is blocked, no interaction with any menu can be made.

I was searching through the filter options and saw that there are many options, but there is no filter by distance. I have distance display working where distance is calculated by grid square and shown when I click on a QSO in the log window. It would be a nice feature to be able to sort or search by distance (for example, filter all QSO over 8000 km).

Doug W1DH

I have realised that cqrlog is not showing all records in the database.

The records shown by a SQL query are, by date and id_cqrlog_main:
2021-05-08 1160
-
2020-10-20 770

2020-02-23 002
-
2019-05-03 123

2019-04-29 124
-
2000-05-19 769

The log is only showing qso's in the date range from today back to 2019-05-03.
Records with the id's in the range 124-769 are not shown.

Hi all,
I'm new to CQRlog and running it on Ubuntu 20.0.4.2.

I've exported my logbook from Log4OM, on Win7, in both ADIF 2 & 3 formats but CQRlog wont import more than 960 entries of the 5500 entries in the ADIF.

I've opened the ADIF's in a text editor to check that all the records are there ( they are ) and I've checked to make sure the ADIF is UTF8.

I've double checked the band edges in frequencies and adjusted them to region 3, just-in-case that was affecting it but it still wont import all my records :(

Any help appreciated.

The reason for the timeout is the MySQL server timing out on "wait_timeout". This is a parameter in the

/etc/mysql/my.cnf

under

[mysqld]
wait_timeout=28800

It is set to the above value in the normal case. That is why it times out after eight hours. To make it easier to debug the timeout it can be set to e.g. 300 which is five minutes. Note that this change affect all sessions on the MySQL / MariaDB server.

Of the 5 threads setup in src/dData.pas the four last ones time out for me:

I tried compiling the CQRLOG in a Docker-image using the existing master branch.

Unfortunately the Dockerfile needs to be updated for the Docker compilation to work due to that the existing Dockerfile uses

FROM ubuntu:eoan

With that version you get a number of missing release files when you try to build the CQRLOG according to the instructions.
FYI also using ubuntu:latest (=focal) will currently not work due to tzdata problems.

Hello everybody,

I encounter problems when I log several QSOs. After every 3 or 4 QSOs cqrlog stucks for up to 3 minutes with increased cpu usage before letting me continue to do the log. After restart of cqrlog everything starts all over again.
A few days ago I discussed that with Petr and it looked like QRZ.com would be the problem. So I switched to hamQTH and it worked for a while. But today I encouter that problem no matter which service I use.

Does anyone else have that issue with version 2.5.2 on a raspberry pi 4?

Hi, all!

A friend of min is running CQRLOG 2.5.2 on Xubuntu 18.04.

After an update he got the following error message in mysql.err. Any solution? Thanks a lot in advance!

73 de SM0RUX Pontus

mysql.err:
-------------
2021-04-20 21:37:05 139720063814976 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.