HI Brian,
that is true but it isn't quite the same and doesn't change the
following assumptions.
1) If a "full" exchange is completed with one station sending an "RRR"
message until they receive a "73" message then the former station need
not send any more messages, although on a very sparse propagation
channel like MS on VHF sending a 73 back after receiving 73 is courteous
if no other back channel like PJ or ON4KST chat is available to close
down the QSO.
2) there is no point deviating from (1) unless you do not expect a reply
from your "RRR" substitute message "RR73", otherwise you may as well
just use "RRR" and wait for a "73", and there is no point using "RR73".
Therefore there must be an assumption that the "RR73" will be received
first time since there is no mechanism to request a repeat.
Agreed that if the first station repeats their R+SNR message then you
know you need to repeat the "RR73" message or revert to RRR but given
that third station could assume you are done and call over the first
station's repeated R+SNR then the first QSO is potentially incomplete.
If there is any chance that your QSO partner might not copy your "RR73"
message then you are better off sending "RRR" and waiting for a "73"
reply, hoping that others will wait too.
With a popular DX-pedition, others will not wait regardless but the
fox/hound protocol has some guards by having some protection for the fox
Tx frequencies thereby trying to maximize the chance of all their
transmissions being copied. It's not really different from an
experienced DX-pedition op running split and sending TU once they
receive their report, the QSO is done and the pile-up resumes. there too
there is an assumption that the DX station is copied first time every time.
73
Bill
G4WJS.
On 29/01/2018 21:15, Brian Moran wrote:
OK, but to me that seems slightly at (conceptual) odds to the
always-short-circuited pending DXpedition mode, which so far uses RR73
exclusively.
On Mon, Jan 29, 2018 at 12:22 PM, Bill Somerville
<g4...@classdesign.com <mailto:g4...@classdesign.com>> wrote:
On 29/01/2018 20:10, Brian Moran wrote:
Is it envisioned that the RR73 mode will be promoted into a
setting that is preserved as part of the configuration in the
future (depending on the preconditions of not having a type2
callsign)?
If it was a setting, would it move to the configuration tab,
would it stay a double-click option on tx4, or would it be
BOTH, with the double-click action changing it until the next
program restart (or unspecified other condition)?
-Brian N9ADG
HI Brian,
that is already the case. The "unspecified other condition" is
changing frequency. Using RR73 assumes that the message will be
received first time, you can only assume that when you have
assessed the band conditions and occupancy. Don't forget that
compound callsign holders also want to have QSOs and if there is
one of those on the band that you want to work then you have a
much better chance if you use the full message exchange without
trying to short cut the process.
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
