Im running MX Linux 21.x XFCE and all of a sudden CQRlog isn't getting the frequency from FLRIG unless i open JTDX /WSJT-X but then im locked in to FT modes i wanted to chase a SSB dx station can any one please help
Tue, 2023-01-10 15:21
#1
FLRIG suddenly stoped working
Hi!
Without knowing your setup I can just assume that you try to "talk" with your rig with flrig and cqrlog (using "start rigctld at program start")
If flrig is your main rig controlling program that is always running then you should set Cqrlog/preferences/TRXControl
to use rig model #4
See this picture:
https://www.cqrlog.com/sites/default/files/Screenshot_20200802_094904.png
You also should set same rig model and port parameters to JTDX/WSJTX if you use them together with flrig.
Otherwise your programs try to talk to rig all on their own and that causes chaos. All rig commands and requests shoud go via flrig,
if that is your main rig control program.
You can also see this, even when there is not question in flrig. How ever you can see the idea how rig communication needs to be done
https://github.com/OH1KH/cqrlog/blob/loc_testing/compiled/setting_rigctl...
--
Saku
OH1KH
i have configured CQRLog as per screenshot and still nothing coming up on CQRlog
https://gyazo.com/9489bfd933e4d0079a6573be4a046b73
OK!
Serial speed can also be default, but that should not matter.
Then you have selected "Show communication with trx in console". What can you see if you add to "Extra command line arguments" string -vvvvv (minus and 5 "v"s), stop Cqrlog, open command console and start Cqrlog by typing cqrlog in console?
You might get glue from console debug messages. Does rigctld get connectd to flrig xmlrpc server?
It might be handy to change poll rate from 500 to something between 1000-5000 while testing. You can also drop "v"s from 5 to 4 or even 3 if you are getting too much debug lines to follow.
You can also check that flrig / configuration /server has the Xmlrpc port as 12345 and that server is actually running.
--
Saku
OH1KH
adam@Main-pc:~/radio
$ cqrlog
Cqrlog Ver:2.6.0 (001) Gtk2 Date:2022-07-05
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=NR PARAMETER ****
*** Parameter -h or --help for details ***
OS:
Linux version 5.10.0-20-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.158-2 (2022-12-13)
/usr/bin/mysqld
2023-01-15 1:18:01 0 [Note] /usr/sbin/mysqld (mysqld 10.5.18-MariaDB-0+deb11u1) starting as process 8116 ...
Settings:
-----------------------------------------------------
RigCtldPath:/usr/bin/rigctld
RigCtldArgs:-m 4 -r 127.0.0.1:12345 -t 4532 -vvvvv -s 19200 --set-conf=serial_handshake=None
RunRigCtld: TRUE
RigDevice: 127.0.0.1:12345
RigCtldPort:4532
RigCtldHost:127.0.0.1
RigPoll: 2500
RigSendCWR: TRUE
RigChkVfo TRUE
RigId: 4
Starting RigCtld ...
rigProcess.Executable: /usr/bin/rigctld
Parameters:
-m
4
-r
127.0.0.1:12345
-t
4532
-vvvvv
-s
19200
--set-conf=serial_handshake=None
Recommend using --vfo switch for rigctld if client supports it
rigctl and netrigctl will automatically detect vfo mode
rigctld Hamlib 4.5.4
Last commit was Fri Dec 25 02:30:30 2020 +0000 SHA=519f82
Report bugs to
rig_check_rig_caps: p1=0x7f62c537f220, p2=0x7f62c53857a0, rig_model=0x7f62c537f220, macro_name=0x7f62c53857a0
initrigs4_dummy: _init called
rig_init: rig_model=FLRig FLRig
rig_init: rig does not have tx_range!!
rig_init: rig has VFO_A
rig_init: rig has VFO_B
1:flrig.c(616):flrig_init entered
flrig_init version 20221109.0
1:flrig.c(659):flrig_init returning(0)
rig_token_lookup called for serial_handshake
rig_confparam_lookup called for serial_handshake
rig_set_conf called
rig_confparam_lookup called for 0
Config parameter error: rig_check_rig_caps: p1=0x7f62c537f220, p2=0x7f62c53857a0, rig_model=0x7f62c537f220, macro_name=0x7f62c53857a0
initrigs4_dummy: _init called
rig_init: rig_model=FLRig FLRig
rig_init: rig does not have tx_range!!
rig_init: rig has VFO_A
rig_init: rig has VFO_B
1:flrig.c(616):flrig_init entered
flrig_init version 20221109.0
1:flrig.c(659):flrig_init returning(0)
rig_token_lookup called for serial_handshake
rig_confparam_lookup called for serial_handshake
rig_set_conf called
rig_confparam_lookup called for 0
Invalid parameter
rigctld failed to start!
Destroy rigctld
1
2
3
4
5
6
Done!
Warning: Can't find /home/adam/.config/cqrlog/xplanet/marker in
xplanet/markers
/home/adam/.xplanet/markers
/usr/share/xplanet/markers
Warning: Can't load marker file /home/adam/.config/cqrlog/xplanet/marker
WARNING: TGtk2WidgetSet.InvalidateRect refused invalidating during paint message: TStringGrid
Warning: Can't find /home/adam/.config/cqrlog/xplanet/marker in
xplanet/markers
/home/adam/.xplanet/markers
/usr/share/xplanet/markers
Warning: Can't load marker file /home/adam/.config/cqrlog/xplanet/marker
Warning: Can't find /home/adam/.config/cqrlog/xplanet/marker in
xplanet/markers
/home/adam/.xplanet/markers
/usr/share/xplanet/markers
Warning: Can't load marker file /home/adam/.config/cqrlog/xplanet/marker
VK2PWR_2023-01-15_01-18-18.adi
HI!
The reason is invalid parameter with rigctld and it is "--set-conf=serial_handshake=None"
Be sure to have all these as "Default". I just tested so and model #4 flrig works then:
Chek that and retry and keep on eye that debug text does not have his line:
That is the one that leads to this:
--
Saku
OH1KH
$ cqrlog
Cqrlog Ver:2.6.0 (001) Gtk2 Date:2022-07-05
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=NR PARAMETER ****
*** Parameter -h or --help for details ***
OS:
Linux version 5.10.0-20-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.158-2 (2022-12-13)
/usr/bin/mysqld
2023-01-16 13:45:42 0 [Note] /usr/sbin/mysqld (mysqld 10.5.18-MariaDB-0+deb11u1) starting as process 9014 ...
Settings:
-----------------------------------------------------
RigCtldPath:/usr/bin/rigctld
RigCtldArgs:-m 4 -r 127.0.0.1:12345 -t 4532 -vvvvv --set-conf=serial_handshake=None
RunRigCtld: TRUE
RigDevice: 127.0.0.1:12345
RigCtldPort:4532
RigCtldHost:127.0.0.1
RigPoll: 2500
RigSendCWR: FALSE
RigChkVfo TRUE
RigId: 4
Starting RigCtld ...
rigProcess.Executable: /usr/bin/rigctld
Parameters:
-m
4
-r
127.0.0.1:12345
-t
4532
-vvvvv
--set-conf=serial_handshake=None
Recommend using --vfo switch for rigctld if client supports it
rigctl and netrigctl will automatically detect vfo mode
rigctld Hamlib 4.5.4
Last commit was Fri Dec 25 02:30:30 2020 +0000 SHA=519f82
Report bugs to
rig_check_rig_caps: p1=0x7f3d81e00220, p2=0x7f3d81e067a0, rig_model=0x7f3d81e00220, macro_name=0x7f3d81e067a0
initrigs4_dummy: _init called
rig_init: rig_model=FLRig FLRig
rig_init: rig does not have tx_range!!
rig_init: rig has VFO_A
rig_init: rig has VFO_B
1:flrig.c(616):flrig_init entered
flrig_init version 20221109.0
1:flrig.c(659):flrig_init returning(0)
rig_token_lookup called for serial_handshake
rig_confparam_lookup called for serial_handshake
rig_set_conf called
rig_confparam_lookup called for 0
Config parameter error: rig_check_rig_caps: p1=0x7f3d81e00220, p2=0x7f3d81e067a0, rig_model=0x7f3d81e00220, macro_name=0x7f3d81e067a0
initrigs4_dummy: _init called
rig_init: rig_model=FLRig FLRig
rig_init: rig does not have tx_range!!
rig_init: rig has VFO_A
rig_init: rig has VFO_B
1:flrig.c(616):flrig_init entered
flrig_init version 20221109.0
1:flrig.c(659):flrig_init returning(0)
rig_token_lookup called for serial_handshake
rig_confparam_lookup called for serial_handshake
rig_set_conf called
rig_confparam_lookup called for 0
Invalid parameter
rigctld failed to start!
Destroy rigctld
1
2
3
4
5
6
Done!
still the same with the config change
HI!
Shouldn't do that.
Close Cqrlog, then open it again but do not open any log. If you have set "open recent log when cqrlog starts" you must take that OFF via NewQSO/File/Open or create new log"
When Database connection window is open select the log what you use, if not already selected. Do not open log but press utils button and navigate to configuration/export.
Give a file name for config export and press save.
After that find saved file with file manager and open it into text editor.
Search string "serial_handshake". You should find it from section [TRX1], I think.
Once you have found the line, checked that it has same string as in debug.txt, remove the line and save file.
Go back to Connect database window, press utils and navigate configuration/import.
Find the saved file and press open.
Once done open the selected log and see if you did get rid of that line from debug.
--
Saku
OH1KH
i have gone from a debian base MX Linux to Mint 21.1 fixed the clublog upload url so fair everything is working 100%