Hey Folks,

Hope everyone had a wonderful holidays! I love cqrlog. I use it every single day!

I've got 2.4.0 running with hamlib 3.3. I'm able to:

/usr/bin/rigctl -m 221 -r /dev/ttyUSB0 -vvv
Opened rig model 221, 'K2'

Rig command: f
rigctl_parse: input_line: f
Frequency: 3540550

Rig command: m
rigctl_parse: input_line: m
Mode: CW
Passband: 500

Rig command: v
rigctl_parse: input_line: v
VFO: VFOA

Yet, when I run cqrlog, with show communications in TRX console selected in the preferences, or in debug, I don't see that any rig state is reflected in cqrlog.

Cqrlog Ver:2.4.0 (001) Date:2019-10-27
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****

OS:
Linux version 5.4.74-1-MANJARO (builder@b3a61a533317) (gcc version 10.2.0 (GCC)) #1 SMP PREEMPT Sun Nov 1 13:43:13 UTC 2020

Settings:
-----------------------------------------------------
RigCtldPath:/usr/bin/rigctld
RigCtldArgs:-m 221 -r /dev/ttyUSB0 -t 4532 -s 4800
RunRigCtld: TRUE
RigDevice: /dev/ttyUSB0
RigCtldPort:4532
RigCtldHost:localhost
RigPoll: 500
RigSendCWR: FALSE
RigId: 221

Starting RigCtld ...
rigProcess.Executable: /usr/bin/rigctld Parameters: -m
221
-r
/dev/ttyUSB0
-t
4532
-s
4800

rigctld started!
Connected to localhost:4532
Sending: fmv

So, I see that rigctl seems to be working...but CQRlog isn't reflecting anything. Now, I tested with yfktest, and, I have the same effect. In both cases rigctld starting up causes the filter/mode flashes on the K2 as it walks through, but, nothing reflected. This makes me think that hamlib has changed?

I happen to run arch and I'm current.

73!

Joe