Marco Calistri kirjoitti 29.9.2021 klo 16.49:
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!
HI Marco!
Cqrlog does not have influence to A=B needs, but it is related to this.
To get rid of pushing A=B after band change with wsjtx rigctld that
access rig needs starting parameter "--vfo" if you start rigctld outside
of wsjtx and use "Hamlib Net rigctld" as rig in wsjtx configuration.
That helped at least me with Icom IC7300.
As reminder:
You can not start wsjtx with your rig model and serial port as rig in
configuration(F2/radio) if you also start cqrlog with your rig model and
serial port in preferences/TRXControl.
This will cause two programs trying to share same serial port to access
to your rig at same time and that will not work.
You have to start rigctld with rig parameters separately and then make
your programs call that rigctld with "Hamlib net rigctld" as rig in
programs.
(
https://github.com/OH1KH/cqrlog/blob/loc_testing/compiled/setting_rigctld_for_all_programs.pdf
)
But when "--vfo" is used to get wsjtx happy problem arise with cqrlog
that does not like "--vfo" parameter at rigctld start at all.
And the reason is, as said, rigctld one letter commands need additional
parameter about vfo (VFOA, VFOB, currVFO etc...) for almost all commands.
This makes it not being backward compatible any more with older rigctld
commands.
So making wsjtx happy with "--vfo" makes cqrlog unhappy because it uses
legacy one letter commands for accessing rigctld that then do not work
any more.
If you try latest hamlib 29 10:46:53 2021 +0000 SHA=a2b3a8 you could
also try my fix for cqrlog at
https://github.com/OH1KH/cqrlog/tree/hamlib_vfo
It has a new checkbox at preferences/TRXcontrol called "Use \chkvfo". It
is default checked and then tries to find out has user started rigctld
with or without "--vfo" parameter. With that information it changes
command format for accessing rigctld from cqrlog.
When unchecked it acts like previous cqrlogs. I.E: disables this fix.
It seems to work with IC7300 when "--vfo" parameter is used and both
cqrlog and wsjtx become happy.
--
Saku
OH1KH
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
