Cannot seem to get rig control working on CQRLog 2.5.1 running on Raspberry Pi Bullseye. Radio firmware is 1.41.
Not sure what other info you need. Thanks
Wed, 2022-04-27 02:27
#1
IC-7300 on RPi Bullseye
HI!
If you have configured your ic7300 at preferences/TRXControl, and you think it is ok, you should start by opening Cqrlog from command line console.
Type as below and then hit return:
cqrlog --debug=1 > /tmp/debug.txt
When cqrlog has started close it. You should have now text file /tmp/debug.txt. Show about 100 first lines of that file here.
That is good starting point.
--
Saku
OH1KH
Cqrlog Ver:2.5.1 (001) Date:2021-01-24
**** DEBUG LEVEL 1 ****
OS:
Linux version 5.15.32-v7l+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1538 SMP Thu Mar 31 19:39:41 BST 2022
SSL libraries:
libssl.so
libcrypto.so
Loaded 172537 LoTW users
Loaded 153661 eQSL users
Loaded 40941 SCP calls
*
User home directory: /home/pi/
Program home directory: /home/pi/.config/cqrlog/
Data directory: /home/pi/.config/cqrlog/database/
Memebers directory: /home/pi/.config/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/
*
56 us states loaded
Grid map created
/usr/bin/mysqld
MySQLProcess.Executable: /usr/sbin/mysqld Parameters: --defaults-file=/home/pi/.config/cqrlog/database/mysql.cnf
--datadir=/home/pi/.config/cqrlog/database/
--socket=/home/pi/.config/cqrlog/database/sock
--port=64000
Trying to connect to database
TMySQL57Connection : 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 cqrlog002
use cqrlog002
use cqrlog002
use cqrlog002
use cqrlog002
SELECT * FROM cqrlog_config
select * from db_version
[UpgradeMainDatabase] Old version: 18 cDB_MAIN_VER: 18
select * from cqrlog_common.db_version
SELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIF
SELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIF
SELECT * FROM cqrlog_common.bands
Settings:
-----------------------------------------------------
RigCtldPath:/usr/local/bin/rigctld
RigCtldArgs:
RunRigCtld: TRUE
RigDevice: /dev/ttyUSB0
RigCtldPort:4532
RigCtldHost:localhost
RigPoll: 500
RigSendCWR: FALSE
RigId: 1
1
2
3
4
5
6
Settings:
-----------------------------------------------------
RotCtldPath:/usr/bin/rotctld
RotCtldArgs:-m 1 -t 4533
RunRotCtld: FALSE
RotDevice:
RotCtldPort:4533
RotCtldHost:localhost
RotPoll: 500
RotId: 1
Not started rotctld process. (Run is set FALSE)
Connected to rotctld @ localhost:4533
FreqmemSql:select id,freq,mode,bandwidth,info from freqmem order by id
FreqmemNR:0=0
FreqmemFirst:0 FreqmemLast:0
SELECT * FROM profiles WHERE visible > 0 ORDER BY nr
SELECT * FROM profiles WHERE nr = 1
Hi !
Looks like rigctld does not start.
Open command console and type:
rigctld -m 3073 -r /dev/ttyUSB0 -vv
What does it say? Do you see any errors?
If you have older Hamlib your rig model may be 373 instead of 3073. Then change that and try again.
--
Saku
OH1KH
rigctld: symbol lookup error: rigctld: undefined symbol: debugmsgsave
Attached is a screenshot of my settings, my RIG model is always blank after i save a new log
File:
i did see this reply from Jason, KM4ACK, on another website with this reply to someone having a similar issue
That is the pain with installation packages.
If you remove Hamlib it removes Cqrlog.
Unless you have Fedora where you can say:
sudo rpm -e --nodeps hamlib
That will remove just Hamlib but leaves all others (no dependencies parameter, --nodeps). I do not know what is the corresponding Ubuntu apt's paramater (if any),
Cqrlog compile is easy.
See this: Raspberry PI 4 and cqrlog https://www.cqrlog.com/node/3124
--
Saku
OH1KH
Should i update my Hamlib?
Hi!
That is what I was expecting, but had to approach it by checking basics first.
It seems to be so that you have now two versions of Hamlib.
Usually the version that comes as dependency of some other program, like Cqrlog, installing and the other that comes when Hamlib is compiled from source.
By default package versions usually place rigctld as /usr/bin/rigctld . Compiled version by default goes to /usr/local/bin/rigctld.
To clear up what is the situation open command console and type:
whereis -b rigctld
You should get just one answer. If you have two rigctlds you have to remove the other Hamlib.
If you get one answer copy that to "preferences/TRXControl/Path to rigctrld" after closing preferences and reopening it again you should see list of rigs.
Let's do this first and see the result.
--
Saku
OH1KH
i do have two copies, one in /usr/bin/rigctld and one in /usr/local/bin/rigctld. I'm not sure how to delete it, as the OS won't let me move it to the wastebasket
Try first each one to preferences/TRXContol/Path to rigctld binary.
With luck the other one works without deleting the other.
That means using /usr/bin/rigctld is the one that may work. Then you should see Rig model list at TRXContorl and you can select your ic7300
--
Saku
OH1KH
I can now select my IC7300, but it continuously keys my rig when i open my log
I can now select my IC7300, but it continuously keys my rig when i open my log
Forgot to say:
At same go check also Connectors/CI-V:
CI-V Baud Rate = Auto
CI-V Address = 94h
CI-V Tranceive = OFF
CI-V USB->REMOTE Tranceive address 00h
CI-V Output (for Ant) = OFF (unless you need it)
CI-V USB Port = Link to [REMOTE]
As alternative for this it can also be:
CI-V USB Port = Unlink from [REMOTE]
But then following two are not grayed and must be set as:
CI-V USB Baud Rate Auto
CI-V USB Echo Back OFF
--
Saku
OH1KH
Fine !
Now you have to check your rig settings. I think the TX problem is because one of below settings is ON state.
Ic7300: Menu/Set/Connectors/Usb send/keying/
USB SEND OFF
USB Keying (CW) OFF
USB Keying OFF
--
Saku
OH1KH