On Tue, 8 May 2018, Joe Taylor wrote:
Yes, it might help. What would help, even more, is finding a way to get
potential Hounds to read what's already there.
Even after reading the doc, it's hard to know exactly what you're
talking about until you run the program in the mode. It's quite
Hi Jim,
On 5/8/2018 2:24 PM, Jim Brown K9YC wrote:
I think it would help a lot if details like these of the process, which
is clearly quite well designed, were to be part of user doc for Hounds.
Yes, it might help. What would help, even more, is finding a way to get
potential Hounds to read
Hi Joe,
I think it would help a lot if details like these of the process, which
is clearly quite well designed, were to be part of user doc for Hounds.
73, Jim K9YC
On 5/8/2018 10:37 AM, Joe Taylor wrote:
In Fox mode WSJT-X maintains several queues.
A specified Hound callsign stays in
Ok...
So, at 153115 I sent my last call, sent to the Fox at 153130. 2.5min later (or
less), the Fox queued me for the “available to call” list. Then, one of 2
scenarios played out: 1) I have a missing Fox attempt at 153500; or 2) I have a
missing Fox attempt at 153630. And, the delay on the
Gene --
On 5/8/2018 1:25 PM, Gene Marsh W8NET wrote:
I understand. But, look closely at this pic. The last time I called
the Fox was at 153115. The Fox responded at 153530. The Fox had my
call in queue for 4:15?
In Fox mode WSJT-X maintains several queues.
A specified Hound callsign
Hi Gene,
On 5/8/2018 1:01 PM, Gene Marsh W8NET wrote:> What it the time for
“staying in the queue?> I took a “bio break”, and missed the
first try (first pic). The > lag was 4:15. Second pic is my
successful QSO:
From the *FT8 DXpedition Mode User Guide*, item #19 on p8:
FYI to folks on this list
Forwarded Message
Subject: Re: [wsjtgroup] DX Mode Test Bug Report
Date: Tue, 8 May 2018 10:51:05 -0400
From: Joe Taylor j...@princeton.edu [wsjtgroup]
Reply-To: Joe Taylor
To: