Hi Mike,
you may be correct. Of course Chris had the option not to use the
rigctld-wsjtx provided with WSJT-X, instead reverting to the older
rigctld provided in some other package. If that is the case then some
version incompatibility between Hamlib internal network rig control
protocols may be the case. Such a breakdown seems self-inflicted to me,
running the version of rigctld that works with the most applications
being the choice available. Rather ironic given that original complaint
was a wish to use the latest possible unreleased version of Hamlib from
the Hamlib web-site.
73
Bill
G4WJS.
On 07/06/2020 04:58, Black Michael via wsjt-devel wrote:
It sounds like SKCClogger was talking to WSJT-X rigctld-wsjtx....is
that possible?
Otherwise I don't see how it could have any effect.
As another test move the WSJT-X into a subdirectory in WSJT-X and then
move them back one at a time and see if any particular file breaks things.
Most likely to be rigctld-wsjtx.
Can you send a screen shot of SKCClogger's setup referring to hamlib?
Mike W9MDB
On Saturday, June 6, 2020, 10:53:26 PM CDT, Topher Petty
<[email protected]> wrote:
Apparently the statically linked WSJT-X with its own hamlib does...
Neither FLDIGI nor the SKCClogger does these things on startup..
As SKCClogger is written in Python and references my local copy of
hamlib, this shows that hamlib most likely isn't the issue.
But you're right... I should contact the hamlib team about symptoms
that only appear when I use a software that is statically linked to
hamlib and is the only place where the symptoms occur.
On Sat, Jun 6, 2020, 20:17 Bill Somerville <[email protected]
<mailto:[email protected]>> wrote:
On 07/06/2020 01:08, Topher Petty wrote:
> For example:
> I won't report that, for some reason, 2.2.1 seems to cycle my 7300
> from VFO A to VFO B and back to VFO A on startup, which makes me
need
> to press the "TUNE" button again to get the auto-tuner back in sync
> with the radio. I won't report that changing bands to a band 15m
and
> above using the dropdown in WJST-X automatically turns my preamp
on..
> sometimes it's Preamp1, others Preamp2, and sometimes not at all.
> I also won't report that both of these behaviors are undesirable.
> de AI8W
Chris,
I suggest you report all those issues to the Hamlib team, WSJT-X
doesn't
do any of that.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
