Il 29/09/21 03:34, Saku via wsjt-devel ha scritto:
Hi Marco!
Sounds familiar, hi...
As you use #2 Net Hamlib rigctld as cqrlog's rig you have to start
rigctld elsewhere with rig parameters. I guess that happens via bash
script.
There you should use "--vfo" to get wsjtx work with split=rig.
Unfortunately that causes problems with cqrlog. It does not work if
parameter "--vfo" is used as using it changes the format of rigctld
short (one letter) commands. They are no more backwards compatible
because almost every command needs vfo stated as first parameter when
start parameter "--vfo" is used.
There is a workaround to start rigctld with rig parameters and "--vfo"
via bash script. That makes wsjtx happy with rig #2 Hamlib Net rigctld
configured there, but then you need to start another rigctld without
"--vfo" for cqrlog and that 2nd rigctld accesses the 1st rigctld that
then accesses your rig.
For doing this:
With bash script start rigctld with your normal rig parameters and "--vfo"
wsjtx:
rig #2 Net Hamlib rigctld selected, server localhost:4532
cqrlog/trxcontrol:
"Run rigctld when program starts" checked
rig #2 Hamlib Net rigctld selected
localhost
Port 14532 !!! Note the port number !!!
Extra command line arguments <empty> I.E. do not write anything there
Other settings do not affect with rig #2 no need to set them
Instead of "localhost" I prefer using 127.0.0.1 because sometimes
IPv6, if enabled, causes troubles when "localhost" is used directing
connects to IPv6 that may not been supported by all programs.
I'm working with fix for cqrlog, it is under testing and Mike has done
good work at Hamlib side to get this issue solved.
Specially Icom rigs that can not report vfo with "v" command have
caused extra work.
As soon as I have tested it properly I will make pull request to
cqrlog's GitHub
Another way to resolve this is leave the "--vfo" parameter away from
bash started rigctld and then set wsjtx split=fake it. Then it is
happy without "--vfo" and also cqrlog works as always before.
For the audio issue I can not give help. All I know that pulse audio
(pipewire) does not work properly. It has been so always, at least
with Fedoras. Alsa is the only one that works.
And when you change band and press Tune there as the first thing to do
the first period transmit after that is always without audio. So do
not use Tune button for tuning the new band first, just start transmit
immediately and let the first transmit period activate autotuner (just
wondering what the Tune button is for...)
--
Saku
OH1KH
Marco Calistri via wsjt-devel kirjoitti 29.9.2021 klo 0.51:
Il 28/09/21 18:08, Black Michael ha scritto:
#1 Does the rig behave when NOT running cqrlog?
#2 Please run rigctld like this, duplicate the problem, and send me
the log.txt file
rigctld -m 1021 --vfo -vvvvv -Z >log.txt 2>&1
Mike W9MDB
Hi Mike,
Yes, CQRLOG is not affecting at all in these behaviors.
In attachment the two logs:
1 - *rigctld.usb.log.txt *produced when selecting "NET rigctl" into
WSJT-X: result is that no AFSK is generated and FT-100 just switch
the PTT on/off.
2 - *FT-100ctld.usb.log.txt* produced when selecting FT-100 as Rig
into WSJT-X. In this case I tried to change band from 10 to 17 meters
and going back to 10 meters and the result is that *_only_* the
receiving VFO changes correctly though WSJT-X commands, while the
transmitting VFO holds on 10 meters initial frequency.
So yes, both issues are still present independently of CQRLOG and as
I told, they are news issues since the newer software versions
(hamlib/wsjt-x) has been released.
Regards,
--
*73 de Marco, PY1ZRJ (former IK5BCU)*
**
Hi dear Saku 😁
I was hopefully waiting a feedback from your side as being one member of
the CQRLOG developers team as well as a WSJT-X user.
However, sorry to say this, but your reply doesn't sounds pretty clear
to me... Despite this I will try to follow your suggestion about
starting rigctld by a separate session.
I demonstrated though my answer to Mike that CQRLOG has not any
influence on the anomalies I faced (minor issue 1: no AFSK using NET
rigctl and minor issue 2: radio split issue).
I could keep using my current settings on both CQRLOG and WSJT-X since I
feel that Hamlib will not works anymore as it was before (using NET
rigctl) but at least I would like to get rid of the need to manually
push VFO A=B button on my FT-100 every time I switch the band from WSJT-X.
Thanks and best regards!
---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
