Hi Mike,
the history is that a bunch of HF operators thought that they could be
clever by using an extremely rare grid (RR73) as a short-form RRR+73 so
they could get on with the next QSO. Then I believe JTDX added support
for unilaterally it despite the obvious problems. Eventually Joe gave in
and we added support in WSJT-X. The rational has always been a way of
shortening QSOs, akthough in many cases that is not achieved.
73
Bill
G4WJS.
On 21/05/2020 14:58, Black Michael via wsjt-devel wrote:
Guess I was recalling the wrong reason for the RR73 then....
What is the history?
On Thursday, May 21, 2020, 08:55:50 AM CDT, Bill Somerville
<[email protected]> wrote:
On 21/05/2020 14:33, Black Michael via wsjt-devel wrote:
> The whole intent of RR73 was for meteor scatter QSOs which can take a
> really long time. So RR73 eliminates one exchange that can take
minutes.
>
>
> Mike W9MDB
Mike,
that's not correct. With MS the RRR then 73 is necessary so both
stations know when to stop transmitting. There may be many periods in an
MS QSO when nothing is copied. These days it is common to inform your
QSO partner via a back channel, Ping Jockey or ON4KST IRC for example,
so that everyone can stop. Once an RRR message has been received the QSO
is complete and it is allowed to confirm that by some other means than a
73 message on air. This breaks the potential loop of not knowing that a
73 message has been received, and so on ad infinitum.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
