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 what's already there.
-- 73, Joe, K1JT
On 5/8/2018 10:37 AM, Joe Taylor wrote:
In Fox mode WSJT-X maintains several queues.
A specified Hound callsign stays in Fox's "available to be selected"
list for up to 2.5 minutes after the most recent decode of that Hound.
When the Fox operator selects a Hound call is goes into a
"to-be-called" queue, a FIFO list. When it reaches the top and a slot
is available, it will be sent a report. The time spent waiting can be
some minutes, and depends on many factors: NSlots, the number of calls
in the FIFO, and the number of repeats necessary for QSOs already in
progress.
Fox considers a potential QSO to have started when he first calls a
particular Hound. That potential QSO "times out" and is aborted if
more than 3 minutes elapses without receiving "R+rpt" and sending RR73.
------------------------------------------------------------------------------
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
