I'm running CQRlog 1.9.0 on a Raspberry Pi 3, OS is Jessie. I connect to Quisk 4.0.4 and an OmniaSDR radio, using the Hamlib rig 2.
Changing the frequency and/or band on Quisk is reflected correctly on the New QSO window in CQRlog and correctly the TRX Control window. Changing the mode in the TRX Control window is refelected correctly in Quisk, but no change happens on the New QSO window. Likewise, changing the mode in Quisk is reflected correctly on the TRX window, but again, not on the New QSO window. I can change the New QSO window mode manually, but I don't think this is how it is supposed to work. There is a checkbox labeled "Auto" above the mode field on the New QSO window, but it has no effect, nor is there any sort of mouseover text showing what it is for.
Is this a bug in my release, or is there a setting somewhere that I have incorrect?
Thanks, Jim / W6JHB
Hi Jim,
go to Preferences -> TRX control and on the bottom of the window is "Show communication with TRX in console". Check that option, click to OK, close the program and run it from a console. There should be more information what mode hamlib sends to CQRLOG.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Petr,
On my Preferences-> TRX control, there is no such check box. The bottom most thing on my panel is a "Change default frequencies" box.
73, Jim / W6JHB
Jim / W6JHB
Folsom, CA
Jim,
this option has been added in version 2.0.0.
Please run cqrlog from a terminal with --debug=1 parameter. It will show debug information including communication with the radio.
73 Petr
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Petr,
I ran it as you asked and the results are pasted below. The sequence of events: (1) started CQRlog with Quisk already running mode CW, (2) from the TRX Control window, I told CQR to change the mode to SSB and then to AM. In each case, Quisk obeyed and changed the mode of the radio. However, the New QSO window mode stayed the same. I do notice an error on startup: the line saying rig_open: error = Invalid configuration. Doesn't say what is invalid, though.
Question for you - should I try to upgrade to version 2.0.1 rather than have you debugging this older version that I have? If yes, then I assume I will have to assemble it, unless there is a package already built for the ARM processor in my Raspberry Pi. Is there a list of steps required to do the assembly? I am very far from being an expert with Linux, but I have compiled Hamlib and WSJT-X quite a few times in the past six months, so I may be able to get through it...
Here is the console log from my test:
pi@raspberrypi:~ $
pi@raspberrypi:~ $
pi@raspberrypi:~ $ cqrlog --debug=1
**** DEBUG LEVEL 1 ****
Loading libssl:
Loading libcrypto:
Loading libmysqlclient:
**************************
MySQL version: 5.5
**************************
**********************************
MySQL version assigned: 5.500000000000000000E+00
**********************************
Loaded 93636 LoTW users
Loaded 98114 eQSL users
Loaded 48268 SCP calls
IniFile:/home/pi/.config/cqrlog/cqrlog.cfg
LocalIniFile:/home/pi/.config/cqrlog/local.cfg
*
User home directory: /home/pi/
Program home directory: /home/pi/.config/cqrlog/
Data directory: /home/pi/.config/cqrlog/database/
Memebers directory: /usr/share/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/
TConnection to MySQL: 5.5
*
Trying to connect to database
160511 9:10:51 [Note] /usr/sbin/mysqld (mysqld 10.0.23-MariaDB-0+deb8u1) starting as process 12306 ...
Server connect failed.
Trying:1
select * from tables where table_schema = 'cqrlog_common'
SELECT log_nr,log_name FROM cqrlog_common.log_list order by log_nr
use cqrlog001
use cqrlog001
use cqrlog001
use cqrlog001
SELECT * FROM cqrlog_config
IniFile:/home/pi/.config/cqrlog/1cqrlog.cfg
LocalIniFile:/home/pi/.config/cqrlog/1local.cfg
LocalSections:
select * from db_version
select * from cqrlog_common.db_version
SELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIF
SELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIF
Settings:
-----------------------------------------------------
RigCtldPath:/home/pi/hamlib-3/bin/rigctld
RigCtldArgs:-m 2 -r -t 4575
RunRigCtld: TRUE
RigDevice:
RigCtldPort:4575
RigCtldHost:localhost
RigPoll: 500
RigSendCWR: FALSE
RigId: 2
Starting RigCtld ...
/home/pi/hamlib-3/bin/rigctld -m 2 -r -t 4575
rig_open: error = Invalid configuration
rigctld started!
Connected to localhost:4575
Settings:
-----------------------------------------------------
RotCtldPath:/usr/bin/rotctld
RotCtldArgs:
RunRotCtld: FALSE
RotDevice:
RotCtldPort:4533
RotCtldHost:localhost
RotPoll: 500
RotId: 1
rotctld started!
Connected to localhost:4533
CW init
SELECT * FROM profiles WHERE visible > 0 ORDER BY nr
SELECT * FROM profiles WHERE visible > 0 ORDER BY nr
Sending: M LSB 2000
Sending: M AM 3000
OnCloseQuery - NewQSO
1
2
3
4
5
6
select count(*) from cqrlog001.cqrlog_config
Saving ini file to database
select count(*) from cqrlog001.cqrlog_config
Saving ini file to database
1
2
3
4
5
6
Closing DXCluster window
Closing TRXControl window
Closing GrayLine window
Closing dDXCC
Deleting config file: cqrlog.cfg
Invalid file handle
Deleting config file: 1cqrlog.cfg
Closing dData
/home/pi/.config/cqrlog/database/raspberrypi.pid
Command:
kill 12306
(cqrlog:12300): GLib-CRITICAL **: Source ID 12 was not found when attempting to remove it
(cqrlog:12300): GLib-CRITICAL **: Source ID 11 was not found when attempting to remove it
(cqrlog:12300): GLib-CRITICAL **: Source ID 44 was not found when attempting to remove it
(cqrlog:12300): GLib-CRITICAL **: Source ID 43 was not found when attempting to remove it
(cqrlog:12300): GLib-CRITICAL **: Source ID 49 was not found when attempting to remove it
(cqrlog:12300): GLib-CRITICAL **: Source ID 48 was not found when attempting to remove it
Closing ini file ...
pi@raspberrypi:~ $
Jim / W6JHB
Folsom, CA
Jim,
I wrote it to the FAQ: https://www.cqrlog.com/faq#source-code but you have to has Lazarus 1.6 and fpc-3.0. Ubuntu 16.04 for Raspberry Pi has these versions in the repository.
73 Petr
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
OK - that is the way I will proceed. Will let you know how it goes.
Thanks & 73, Jim
Jim / W6JHB
Folsom, CA
Ran into a problem. Trying to do part of the install - how to fix this and move on?
Here is the error:
pi@raspberrypi:~/cqrlog $
pi@raspberrypi:~/cqrlog $ sudo apt-get install mysql-server libmysqlclient-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
mysql-server : Depends: mysql-server-5.5 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
pi@raspberrypi:~/cqrlog $
Tnx & 73, Jim / W6JHB
Jim / W6JHB
Folsom, CA
Hi Jim,
please try apt-get update, first. Maybe the repositor is broken.
73 Petr
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Hi Petr,
Just ran the sudo apt-get update, followed by the attempt to install those two packages - same failure. I have no idea how to proceed from here. I can continue using the older version of CQRlog, as that mode problem is not a big deal - I do the vast majority of my QSOs on CW. I just thought it would be nice to get it fixed. The other issue is that sooner or later I probably will have to go to a newer version of CQRlog, so if we can get by this package install problem it would be helpful.
73, Jim / W6JHB
Jim / W6JHB
Folsom, CA
Ran into a problem. Trying to do part of the install - how to fix this and move on? Here is the error:
pi@raspberrypi:~/cqrlog $
pi@raspberrypi:~/cqrlog $ sudo apt-get install mysql-server libmysqlclient-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
mysql-server : Depends: mysql-server-5.5 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
pi@raspberrypi:~/cqrlog $
Tnx & 73, Jim / W6JHB
Jim / W6JHB
Folsom, CA