Actually, if you are the originator of the RR73 message, the only messages that you should be expecting is either a 73 confirming your RR73 (part of auto seq) completing the QSO, or a retransmission of the SNR message (also part of auto seq), in which case you should retransmit the RR73 message by re-enabling TX with TX4 containing the said RR73. If you receive neither, while you may still log the QSO, you really don't know if the other party logged the QSO on their end. 73, Sam W2JDB
-----Original Message----- From: Alex via wsjt-devel <wsjt-devel@lists.sourceforge.net> To: WSJT software development <wsjt-devel@lists.sourceforge.net> Cc: Alex <a...@kr1st.com> Sent: Mon, Oct 4, 2021 12:39 pm Subject: Re: [wsjt-devel] Question, FT8 Yes, that was exactly my point. Thanks for setting me straight. How could I have been so stupid to miss that. 73, --Alex KR1STOn Oct 4, 2021, at 9:33 AM, Neil Zampella via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote: It's currently optional ... When you send RR73, when the Tx Enable turns off, the operator has the OPTION to click it back on, select the Tx5 message, and have it go out. See ... already implemented. Just takes TWO clicks. Neil, KN3ILZ On 10/4/2021 7:21 AM, Alex wrote: Hi Jim, Hence the suggestion to make it optional. Perhaps there should be a penalty for not being courteous on the bands. I can live with that. I always had to laugh when I read the discussions on the RTTY lists after a contest. It's full of complaints about operators sending a character too many here and there. We're in a bad place if sending a 73, which is done in almost every other mode (including RTTY contests back when I participated), is too much to ask for. One can hardly argue that fully automatic operations (including logging) is a bad thing if sending a 73 is too much to ask for. 73, --Alex KR1ST On Oct 4, 2021, at 2:43 AM, Jim Brown via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote: On 10/3/2021 7:50 PM, Alex via wsjt-devel wrote: No 73, no QSO. I really don't care if that means my log will be a few Q's short. The world is already rude enough as it is. We can take a few moments to be courteous. Not when there's short band opening for DX, and not in a contest. :)When the other station sends RRR or RR73 and I immediately call CQ, heshould know that I copied it. If I didn't, I'd send R-10 again. And ifyou re-send R-10, I know you didn't get my RRR or RR73, so I re-send it.This stuff is LOOONG established practice on the HF bands, especiallyfor contesting and DX pileups. Indeed, the most discourteous thing wecan do with working a contest (or in a DX opening) is to make thecontact take longer to complete -- it slows the other station down!Contest rules penalize you if a QSO in your log is not in the otherstation's log, and it's often the loss of ANOTHER QSO. Failing tounderstand these issues has driven RTTY contesters crazy when FT8 andFT4 were added to RTTY Roundup, and when those same RTTY contestersworked to set up a pure digital contest.73, Jim K9YCwsjt-devel mailing listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
