Hi All, >I think it would be helpful for the called station to return a 73 message in >response my RR73. As things are now, if I received nothing after sending >RR73, I do not know if the other station received my RR73 or if I could no >longer copy the other station due to band conditions or QRM. If the other >station started a new CQ, I took that as confirmation.
Let's assume that all stations follow principle stated in 'The FT4 Protocol for Digital Contesting': 'FT4 is presently configured so that a station operating in Search-and-Pounce (“S+P”) mode logs a QSO when RR73 is transmitted, and the CQing (“Run”) station logs a QSO when RR73 is received.' So after sending RR73 you may receive: - 'R-nn', if the other end missed your 'RR73'. It is his interest to complete QSO as you are already 'happy'. - CQ by the other end. He has received your 'RR73' and logged the QSO or is no more interested in to complete this QSO with you. - The other end is calling somebody else. As previous case. - No signal on the other end frequency. As previous two cases or a deep QSB (see no decode). - A signal on the other end frequency, but no decode. This is an interesting case as the missed message may be any of the three first cases or a third party is now on that frequency (QRM). Only 'R-nn' is relevant to you as you may miss a multiplier (or a new head). You may resend 'RR73' or perhaps '73'. For that you may already during reception cycle restart TX and select M4 or M5 as Next and place your pointer to M6 or Halt Tx ready to click on the missed decode. Well, this issue is not fully black and white; it is a matter of taste how to behave in a contest in order to get best total result, hi! Actually message with '73' is not really a part of minimum contest QSO and a sending of it should not be forced in automatic steps or by users. It's polite, not a part of a minimum QSO. How much of the above should be a part of automatic program steps is another issue. 73, Reino, oh3ma _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
