On 19/07/2017 00:05, Tim Carlson wrote:
I don’t think its about what I consider complete, I’m concerned about what the
software considers complete. If sending an “RRR” completes the exchange, then
I think one of two things should happen:
1. The Auto Sequenced software should not repeat the RRR if no 73 is received,
or
2. The other end should automatically resend the 73 if an RRR is repeated.
Hi Tim,
option 1 is very propagation dependent, for example an MS QSO or a
marginal EME QSO would almost certainly repeat the RRR message until a
73 is received unless a back channel was in use to say thanks you can
stop now.
option 2 makes more sense except what happens if the RRR is lost in QSB
or QRM, resending the 73 message still makes sense if you are assuming
that an RRR message was due. this is particularly the case with MS for
example where blank periods are the norm.
The problem here is that ending a QSO is not deterministic unless both
sides keep sending 73 messages until they get bored or some other
subjective decision is made. Fortunately ending the QSO is not the same
as both parties being able to log the QSO as complete. It is not
possible to automate a non-deterministic process.
WSJT-X gives you two options at the extremes. Stop after one 73 message
or keep sending 73 messages until the watchdog intervenes. Both can be
overridden by the operator by clicking "Enable Tx" or "Halt Tx"
respectively.
73
Bill
G4WJS.
------------------------------------------------------------------------------
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
