y, 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:g4...@classdesign.com]
Sent: Wednesday, September 14, 2016 2:58 AM
To: wsjt-devel@lists.sourceforge.ne
Bill, I'm building hamlib3 independently using JTSDK.
Dan
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Wednesday, September 14, 2016 2:58 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X patches
On 14/09/2016 04:31, Dan
Hi Dan,
> I have also added QRA to the psk reporter.
>
> How should I share the code patches?
Has this item fallen through the cracks? If so, send me the patch and
I'll commit it.
-- Joe, K1JT
--
_
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
Sent: Tuesday, September 13, 2016 2:49 PM
> To: WSJT software development
> Subject: Re: [wsjt-devel] WSJT-X patches
>
>> On Sat, 2016-09-10 at 19:53 -0500, Dan Bates wrote:
>> Hi Bill,
>>
>> I see the failures when a second client is polling the rigctld
>>
Bill,
Let me know if you want help testing?
Dan
-Original Message-
From: Rik van Riel [mailto:r...@surriel.com]
Sent: Tuesday, September 13, 2016 2:49 PM
To: WSJT software development
Subject: Re: [wsjt-devel] WSJT-X patches
On Sat, 2016-09-10 at 19:53 -0500, Dan Bates wrote:
>
On Sat, 2016-09-10 at 19:53 -0500, Dan Bates wrote:
> Hi Bill,
>
> I see the failures when a second client is polling the rigctld
> socket.
>
> The current code, in the failure routine just toggles a bool variable
> for a single retry before throwing the error. Other apps (example
> fldigi) ha
Bill,
Rig is K3.
Also, fldigi will not run through hamlib3 on the Ubuntu build. Watching the
exchange via -v fldigi disconnects after one exchange. Works fine on w10.
Dan
ARRL, QCAW, CW Ops
First licensed 1962
> On Sep 12, 2016, at 2:18 AM, Bill Somerville wrote:
>
>> On 12/09/2016 0
On 12/09/2016 04:17, Dan Bates wrote:
> The error thrown is: protocol error trying to update current vfo frequency.
Hi Dan,
thanks for that. I believe that the protocol error can only occur at the
back end interface to the radio which is interesting. I was expecting it
to be some error in the
Bill,
The error thrown is: protocol error trying to update current vfo frequency.
This only happens on the Ubuntu build when an additional client is attached.
W10 no issues.
I'll try the json file when I get a chance.
Dan n5tm
ARRL, QCAW, CW Ops
First licensed 1962
> On Sep 11, 2016, at
On 09/11/2016 06:14 PM, Bill Somerville wrote:
Hi Bill,
> I am trying to improve Hamlib such that those options are not necessary,
> they have mostly been added to work around low level issues with the
> serial port communications rather than any specific rig issues.
Transceivers can be strang
On 11/09/2016 16:19, Claude Frantz wrote:
> Such options are e.g. timeout,
> retry, write_delay, post_write_delay.
HI Claude,
I am trying to improve Hamlib such that those options are not necessary,
they have mostly been added to work around low level issues with the
serial port communications
On 09/11/2016 01:16 AM, Bill Somerville wrote:
Hi Bill,
> Also there is a n undocumented feature in WSJT-X to read extra Hamlib
> configuration parameters from a JSON configuration file, this should
> allow you to do these sort of things without modifying any code.
In some circumstances, it be
On 11/09/2016 15:13, Dan Bates wrote:
> Bill could it be a timing issue? Seems to happen on my Ubuntu build more
> frequently that the W10 build, and the Ubuntu is slower computer.
Hi Dan,
quite possibly but it should not be getting as far as an error in WSJT-X
if it is something that can be fi
Ok Bill will see what I can find.
Dan
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Saturday, September 10, 2016 8:34 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X patches
On 11/09/2016 01:53, Dan Bates wrote:
> I see
@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X patches
On 11/09/2016 01:53, Dan Bates wrote:
> I see the failures when a second client is polling the rigctld socket.
>
> The current code, in the failure routine just toggles a bool variable for
a single retry before throwing the error. O
On 11/09/2016 01:53, Dan Bates wrote:
> I see the failures when a second client is polling the rigctld socket.
>
> The current code, in the failure routine just toggles a bool variable for a
> single retry before throwing the error. Other apps (example fldigi) have a
> user configurable variabl
Hi Bill,
I see the failures when a second client is polling the rigctld socket.
The current code, in the failure routine just toggles a bool variable for a
single retry before throwing the error. Other apps (example fldigi) have a
user configurable variable for retry count.
Dan. N5tm
Sen
On 10/09/2016 23:43, Dan Bates wrote:
> One increases the number of retrys on rigctld as under certain
> conditions I see the failure dialog when another retry would fix it.
Hi Dan,
I would be interested to know what those circumstances are?
Also there is a n undocumented feature in WSJT-X to
Hi Mike,
I have a couple of patches.
One increases the number of retrys on rigctld as under certain conditions I see
the failure dialog when another retry would fix it.
I have also added QRA to the psk reporter.
How should I share the code patches?
Dan n5tm
ARRL, QCAW, CW Ops
First licens
If anybody is running a "dirty" version of WSJT-X with your own patch how about
letting us know what patch you're using and why?I'd like to think we can make
everybody happyand maybe somebody has something useful the rest of us could
benefit from...
I'm running a patch the allow the logging
21 matches
Mail list logo
