Wrong mode in my log

2 posts / 0 new
Last post
dl1yar
Wrong mode in my log

Hi om and yl,
in my system is a bug. It's the is a new mode called "Main". My rig is a FTDX3000d.The debug txt is this:
##########################
Settings:
-----------------------------------------------------
RigCtldPath:/usr/local/bin/rigctld
RigCtldArgs:-m 1037 -r /dev/FTDXs -t 4532 -s 19200
RunRigCtld: TRUE
RigDevice: /dev/FTDXs
RigCtldPort:4532
RigCtldHost:localhost
RigPoll: 999
RigSendCWR: FALSE
RigId: 1037

Starting RigCtld ...
rigProcess.Executable: /usr/local/bin/rigctld
Parameters:
-m
1037
-r
/dev/FTDXs
-t
4532
-s
19200

rigctld started!
Connected to rigctld @ localhost:4532
Sending: ‡ 1

Sending: fmv

Sending: fmv

Msg from rig: RPRT 0
7062500
Msg from rig: LSB
1800
Msg from rig: Main
Msg from rig: 7062500
Msg from rig: LSB
1800
Msg from rig: Main
Sending: fmv
################################
I think the problem is the :"Msg from rig: Main" !
how can i solved this?

vy73 de Winfried

oh1kh
Wrong mode in my log

HI Winfried!

It seems tha you have quite new Hamlib, but older cqrlog.
It is very important to include the debug file header wo that we can see what version, and specially version date, of cqrlog is used.

In 2021 I made a fix to cqrlog to "survive" with new versions of Hamlib (rigctld). I think it could resolve this problem too.
If you set "show communication with TRX in console" at preferences/TRXcontrol and start cqrlog from command console:

[saku@hamtpad ~]$ cqrlog

Cqrlog Ver:2.5.2 (118) QT5 Date:2022-01-24
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=NR PARAMETER ****
*** Parameter -h or --help for details ***

OS:
Linux version 5.15.14-200.fc35.x86_64 (mockbuild@bkernel01.iad2.fedoraproject.org) (gcc (GCC) 11.2.1 20211203 (Red Hat 11.2.1-7), GNU ld version 2.37-10.fc35) #1 SMP Tue Jan 11 16:49:27 UTC 2022

Settings:
-----------------------------------------------------
RigCtldPath:/usr/local/bin/rigctld
RigCtldArgs:-m 2 -t 4532
RunRigCtld: FALSE
RigDevice:
RigCtldPort:4532
RigCtldHost:127.0.0.1
RigPoll: 1500
RigSendCWR: FALSE
RigChkVfo TRUE
RigId: 2

Not started rigctld process. (Run is set FALSE)
Connected to rigctld @ 127.0.0.1:4532
Poll Sending: \chk_vfo

Msg from rig: 1
"--vfo" checked:1

Poll Sending: +f currVFO +m currVFO +v

Msg from rig: GET_FREQ: CURRVFO
FREQUENCY: 7013700
RPRT 0
GET_MODE: CURRVFO
MODE: CW
PASSBAND: 500
RPRT 0
GET_VFO: CURRVFO
RPRT -11

There you can see that in fixed version the polling and responses from rig are different.

If you can compile from source it is most recommended to to so to get latest cqrlog.
At least following messages have instructions how to compile cqrlog from source:

Raspberry PI 4 and cqrlog https://www.cqrlog.com/node/3124
New Ubuntu and latest cqrlog https://www.cqrlog.com/node/2984
Mint 20 Cinnamon and new cqrlog https://www.cqrlog.com/node/2998

If you can not compile by yourself, or do not want to do so, you can try to update your cqrlog by using my ready compiled files from
https://github.com/OH1KH/cqrlog/tree/loc_testing/compiled
Operation is very easy. Just download "newupdate.zip" extract it to get "newupdate.sh" and start it in command console.
It will do the rest of job for you.
Please read the page's README.md before starting operation.

If version upgrade does not help I am very interested in to hear more about this so that I can do better fix to work also with Yaesu rigs (that I do not have here for testing).

--
Saku
OH1KH