On 03/08/2021 11:41, Saku via wsjt-devel wrote:
Hi!
Just upgraded my Fedora from 33 to 34.
Removed all self compiled hamlib and wsjtx versions and installed
packages from repository:
wsjtx-2.4.0-1.fc34.x86_64
hamlib-4.1-1.fc34.x86_64
It seems to work. Only one question arises:
*Is it in purpose that every time I start wsjtx it shows yellow "OOB"
on red background and frequency display is filled with zeros.*
After band is selected frequency shows out ok and all works. Just
annoying that it does not get frequency at start by itself like before.
I use rigctrld started from script before wsjtx. Start line is:
/usr/bin/rigctld -m 3073 -r /dev/icom7300 -t 4532 -s 19200 -C
auto_power_on=0 &
(as you can see the rig is icom 7300)
Wsjtx settings use rig: Hamlib Net rigtcĺd, sever: localhost:4532,
split: rig
ldd /usr/bin/wsjtx | grep ham
libhamlib.so.4 => /lib64/libhamlib.so.4 (0x00007fd30f59e000)
-------------------------------------
After that I installed 2.5.0_rc4 from wsjtx web page package:
wsjtx-2.5.0_rc4-1.x86_64
Again every time wsjtx is started it shows yellow/red "OOB" with zero
frequency. When band is selected from selector frequency shows ok.
But every time I try to "Tune" or start tx from "Enable TX" the
yellow/red "OOB" and zero frequency returns and TX does not start.
Also following error appears:
Hamlib error: Feature not available
rig.c(5605):rig_has_vfo_op return(0)
rig.c(3790):rig_set_split_freq return(-11)
rig.c(4331):rig_set_split_freq_mode return(-11) while setting split TX
frequency and mode
If I return band back from band selector same repeats. But If I ignore
"OOB" and try again "Tune" or "Enable TX" transmitter starts and I can
keep qso. How ever at logging phase the "Band" column is empty as can
be expected when "OOB" is visible.
Perhaps rig timeout is too short in wsjtx (??) and it can not get
response from daemon running rigctld that have to ask it from rig.
But from where to adjust that?
If I go configuration/radio and test CAT and PTT everything works ok.
*So rc4 is unusable with "split"="rig". If I set "Fake it" all works
after I have cleared the start phase "OOB" like with 2.4.0*
--
Saku
OH1KH
Hi Saku,
do you have the "Settings->General->Monitor off at startup" checked?
What does the following command print:
grep SHA= ~/.local/share/WSJT-X/wsjtx_syslog.log
There is a known issue with recent Hamlib versions that cause problems
with using split mode in WSJT-X, for now I recommend using "Fake It"
split mode.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
