Thanks Bill!
I have not touched Settings/general ... I cannot remember when was the
last time. Perhaps it was some day in stone age. :-)
Both "monitor off..." and "monitor returns ..." were unchecked. Checked
now the "monitor returns to last used frequency" and it helps for "OOB"
problem. Assume it has appeared at some time since version 2.3.1 as It
did not need to check that before.
I think that wsjtx should get the current frequency from rig. Checking
"monitor returns to last used frequency" just hides the actual problem
by setting the rig.
That is because if starting wsjtx it sets now 6m frequency without "OOB"
but wsjtx cannot notice if I set 20m using rig buttons. It just shows
still 6m, I.E. it does not poll rig like it did before. With last used
ver2.3.1 manual change with vfo did affect also to wsjtx frequency display.
And that is also what "monitor returns to last used frequency"'s popup
help text claims, too.
Same thing continues if I change band from wsjtx band selector. Rig
changes frequency, but if I after that change frequency with vfo wsjtx
does not notice that. Rig poll rate is 5s, but I have used to wait for
the change a bit.
I have to test what happens in real qso as I sometimes drop dial -200Hz
with vfo to get free TX space from under 200Hz of waterfall.
-------------
I did downgrade back to wsjtx-2.4.0-1.fc34.x86_64 and noticed it has the
same problem. Frequency display does not follow rig if vfo is turned
while cqrlog, accessing the same rigctld daemon, notices frequency
changes. ;-(
-------------
grep says:
[RIGCTRL][2021-08-03 12:04:34.582825][00:00:00.186587][info] Hamlib
version: Hamlib 4.3~git Sun Jul 25 23:51:03 2021 +0000 SHA=67b787
--
Saku
OH1KH
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
