N times could be 0 or 1 after called person responds to someone else.
If it is more, it is useless as if called is using RR73 qso lasts just
2 periods (getting R-report and 73 of opponent station)
This is, in a way, against the golden idea of wsjt-x program that
operator should be present all the time.
If I put WD timer to big value, then answer to rare station's CQ using
split TX and do not get answer at first stage I can leave wsjtx trying
and go to kitchen and have a cup of coffee. If rare station at some
point picks me up (within the WD time slot) wsjtx will handle qso to end
and I can just log it when I come back to shack.
If TX would be halted also when using split TX for answering to CQ, just
like it does when you answer on callers frequency, it would prevent this
kind of semi-automated qsos. And of course the unnecessary QRM.
--
Saku
OH1KH
Al Pawlowski kirjoitti 11.05.2018 klo 18:22:
An option setting, to call/send “n” (maybe 1 - 3) times after called
person responds to someone else and you are not on their frequency,
seems like a worthwhile idea to me.
Al Pawlowski, K6AVP
Los Osos, CA USA
Date: Fri, 11 May 2018 14:29:46 +0000
From: Tom M0LTE <t...@m0lte.uk <mailto:t...@m0lte.uk>>
To: WSJT software development <wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>>
Subject: Re: [wsjt-devel] FT8 auto seq suspected bug with audio split
…………….If there are people in both camps surely this should be an
option? Does
the WSJT-X team take pull requests?
------------------------------------------------------------------------------
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
