What version of fldigi are you running and on what OS?
Add if you run rigctl with -vvvvv what does the tail end of that show? Should
indicate whether it's hamlib or fldigi with the problem.
de Mike W9MDB
From: Dan Bates <[email protected]>
To: 'WSJT software development' <[email protected]>
Sent: Wednesday, September 14, 2016 10:02 AM
Subject: Re: [wsjt-devel] WSJT-X patches
Bill, I'm building hamlib3 independently using JTSDK.
Dan
-----Original Message-----
From: Bill Somerville [mailto:[email protected]]
Sent: Wednesday, September 14, 2016 2:58 AM
To: [email protected]
Subject: Re: [wsjt-devel] WSJT-X patches
On 14/09/2016 04:31, Dan Bates wrote:
> I cannot get fldigi to work with rigctld at all. It closes the socket
after one exchange. Maybe I need to build a newer version of fldigi.
HI Dan,
the public interface and behaviour of Hamlib should not have changed since
v2 apart from defect fixes so applications that used to talk to it should
still do so. If a newer build of fldigi does fix it then I probably need to
find out what made that happen.
Are you using the rigctld that is packaged with WSJT-X (rigctld-wsjtx)?
73
Bill
G4WJS.
----------------------------------------------------------------------------
--
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
