Hi George-

My experience lately is  the usage of :

KF2T RRTU73

Which seems to satisfy the Roger part and includes a parting 73.
The other side knows who they are talking to so sending your call is
redundant.

Bill W2PKY




On Tue, Apr 5, 2016 at 11:15 AM, George J Molnar <[email protected]> wrote:

> A modest proposal to shorten JT-mode QSO’s without compromising their
> integrity or cadence.
>
> Example:
> CQ KF2T DM25
> KF2T KX7XX -16
> KX7XX KF2T R-12
> KF2T KX7XX 73
> KX7XX KF2T 73
>
> Cuts the time required for a valid QSO by a minute, which could be helpful
> in certain situations, and may help alleviate congestion on the bands.
> Of course, greater adoption of JT9 and “fast modes” would make this less
> necessary, but perhaps it could help?
>
> Dropping the caller’s grid makes sense to me since we are using computers
> for this mode anyway, and almost everyone is connected to the internet, so
> QTH information is readily available without needing to be sent. It could
> be dropped from the CQ as well, but since it does no harm there, and may be
> useful for quick decision-making on whom to call, no reason to remove it.
>
> RRR seems to be the exchange that gets most people’s goat, and often gets
> replaced with RR73 or something else, which can disrupt cadence,
> particularly if automatic sequencing takes hold. I suspect few will mourn
> its loss. By advancing to the next message, the QSO partner implicitly
> acknowledges the previous step.
>
> In the interest of efficient standardized usage, I’m wondering if we
> should take the free text option out of the TX5 slot and make it a separate
> option below the CQ/TX6 slot? So it only really comes into play when
> there’s a special need?
>
> Something to think about, and probably not something to rush into “today.”
> Just my two cents for the modes I’ve really come to enjoy.
>
> 73,
>
>
>
> *George J Molnar*KF2T | AFA9GM
> Twitter: @GJMolnar
>
> SUPPORT HR-1301 & S-1685
> http://www.arrl.org/amateur-radio-parity-act
>
>
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> wsjt-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to