CQRLOG - Troubleshooting

WARNING! Backup your data often! BACKUP your log directory at the end of EVERY session! All that you need to backup and store in a safe place is the log database directory located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function in Preferences. This autobackup function creates an ADIF file with a backup of your log.

CQRLOG for LINUX by OK2CQR & OK1RR

Troubleshooting

My radio control (CAT) does not work

Check your ports. You must be a member of the user group, which has permission to use ttyS* or ttyUSB* devices.
Open command console and give "ls -l your serial port name" and "groups" commands.
There must be same group, usually "dialout" in both results.

[saku@hamtpad ~]$ ls -l /dev/ttyUSB0
crw-rw----. 1 root dialout 188, 0 13. 4. 09:39 /dev/ttyUSB0
[saku@hamtpad ~]$ groups
saku dialout lock
[saku@hamtpad ~]$

If not try google with "your_linux_distribution_name add user to dial group" to get information how to do the fix.

Check that your radio is properly set up (see here). Click the 'Settings' button and check the port settings - ttyS* or ttyUSB* number and all communication parameters.
Is the poll rate set too fast? Try a lower setting (higher number). Your qsos usually lasts longer than 5 seconds so even ẃith value 5000 the right frequency is there before you save your qso.

When I click on a spot in the DX cluster window it populates the log but it does not move the rig to the new operating frequency. I am using an Icom 756 (original nonPro model).

Set IF filters bandwidth to 0 (Preferences -> Modes tab).

I'm unable to autologin to the Cluster

Open the DX cluster window and click the 'Select' button. In the

DX Cluster List

The 'User name:' field must be filled with your call sign.

I have trouble with LoTW login getting the following error message:

PROGRESS shows:
NOT logged
Error: 0
Error: ssl_none

Solution: libssl-dev must be installed

CQRLOG is very slow or does not run at all

The accompanying problem is an abonormally high CPU load. The problem is instant polling of a non-existent (not responding) radio. Your radio setup is probably incorrect. Try to downoad a default cqrlog.cfg from the CQRLOG web site (www.cqrlog.com) and copy it into your /cqrlog/log_data folder. Backup your old cqrlog.cfg before if you want. The default cqrlog.cfg redirects all polling to the hamlib dummy radio (model=1] and the high CPU load should return to its normal values.

Then you should set up your radio again. Don't use too low a poll rate, a value of 300 is sufficient.

Disappearing fonts in the Radio Control Window

If your Radio Control Window looks like this

go to Preferences -> Fonts and uncheck the 'Use default settings' option

and set fonts manually. Choose any font of your preference which is present on your system (you will see it in the font choice pulldown dialog 'Select font'). This fixes this problem.