On Wed, Feb 1, 2017 at 1:27 PM Bill Somerville <[email protected]>
wrote:
> On 01/02/2017 18:07, Phil Frost wrote:
> > I'm using the "Hamlib NET" driver, and it's running and working enough
> > for fldigi and direct testing with telnet. Unfortunately, in WSJT-X
> > doesn't seem to like that the hamlib get/set mode commands are not
> > supported for this radio, even though I've set "Mode" to "None" in the
> > radio settings.
>
> WSJT-X should not be doing get or set mode Hamlib commands if
> "Settings->Radio->Mode" is set to "None" but there may be some
> complication when the "Hamlib NET rigctl" back end is involved.
>
Well, I'm happy to report I was able to get a local build from the most
current version in SVN, and it now rig control works. Previously, the
softrock rig wasn't available in the hamlib configuration (that's why I was
trying to use the net backend), but now it is and it works fine. It may be
because I built a fresher hamlib when building the fork as described in
INSTALL.
I do notice some new issues, unfortunately.
Firstly, wstjx would segfault at start. I traced this to the memset() in
main() which initializes the shared memory, around line 300 or so. It was
attaching to an existing shared memory segment at start, which I suppose
had a different size and so memset overran it. I "fixed" it by changing the
application key, but I'm not sure what led to this condition in the first
place.
Secondly, although decode works and the level meter in the lower-left shows
around 20dB, the waterfall is black.
[image: pasted1]
I've tried twiddling the range and zero adjustments to no avail. (You can
also see in this screenshot the "smashed" GUI, probably a consequence of my
HiDPI display settings.)
Lastly, the band hopping "Schedule..." button doesn't seem to open any
window when I click it. I had this problem with the previous build also,
which I got from a PPA:
1.7.0-r6626-1~ki7mt~wily 0
500 http://ppa.launchpad.net/ki7mt/wsjtx-next/ubuntu/ wily/main
amd64 Packages
Let me know if there's any additional information that would help. I'll
poke around the source and see what I can do on this end.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
