Yes.5 second default socket_wait_time on line#14 in HRDTransceiver.cpp which
I changed to 10 seconds

 

If I start WSJT-X with HRD Logbook running the menu is greyed out.  It still
decodes and runs.just can't use the menu to bring up settings for example.

With the timeout at 5 seconds I never see the retry exhausted message.

 

So I'm going to spend some time comparing the traffic between all these
applications to see what I can learn.

 

Mike W9MDB

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Friday, September 05, 2014 10:52 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] HRD tcp bug

 

On 05/09/2014 16:29, Michael Black wrote:
Hi Mike,

Still having problems with the HRD tcp bug.

What's of interest to me is that I can run HRD Logger and DM780 both of
which use port 7809 too and they don't seem to have any problems.  So I'm
going to try and compare these to hopefully figure out what's going on.  If
you want I can capture the network traffic with all 3 of these things
running and send it to you along with a trace log.

 

This packet dump shows an example of the problem.

After HRD died I clicked on "retry" so this is the sequence that followed.

11:28:27.460700  The first command "get context" goes out

11:28:32.460910  retransmit of "get context" after timeout

11:28:32.592923 HRD responds to first attempt

11:28:32.592923 WSJTX moves on to "get id"

11:28:35.770041 HRD responds to 2nd attempt

 

I do get rather significant pauses in HRD.especially when switching
frequencies.

So I bumped up the socket_wait_time to 10000 and now I hit the max # of
retries error which I've never seen before..during which menu operations on
WSJTX are pretty much hosed sionce timeout takes a minute or so with 5
retries.

 

Is that the socket wait time in WSJT-X?

This is an interesting observation, all the CAT activity in WSJT-X should be
asynchronous as it is running in a separate dedicated thread and the main
GUI doesn't block waiting for responses. I need to find out why you are
seeing this problem as it may be an error in the message queuing to and from
the transceiver control thread. 

Mike W9MDB

73
Bill
G4WJS.

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to