Comments below .
73, Ed W0YK From: Andy Durbin <a.dur...@msn.com> Sent: 22 July, 2019 14:37 To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Contest confusion " This thread is about "Contest confusion" " when a contester is sending only the required exchange of a Grid Square and his QSO partner is a non-contester using standard FT messages which include SNR. The non-contester may be confused if she doesn't receive an SNR from the contester. " No, I think you have missed the point. The point of the OP was that if a contester replies to a CQ clearly from a non-contester then that person, if not confused, should use the exchange expected by the person who called CQ. [Ed Muns] Agree. To me it's the same "point". I'm advocating that the contester should take responsibility in either case-calling a non-contester or being called by a non-contester. It's in the contester's best interest, as well as the interest of the non-contester, to use an exchange flow that the non-contester expects. The cost to the contester is (1) he has to take action to initiate a different message sequence from his contest messaging, and (2) the alternate messaging takes more time. The benefit is that the contester gets another QSO in the log and the non-contester has the normal QSO he expected. The person calling CQ becomes frustrated and goes QRT because the confused contesters are not able to follow the established protocol for a standard non-contest QSO. [Ed Muns] Yes. It benefits contesters to avoid that. If you don't want to follow standard QSO protocol then don't answer a CQ from a non-contest station. [Ed Muns] Agree. At least part of the problem is caused by WSJT-X itself because it auto-sequences to "RRR" in response to "R grid" even though that instance of the application is not selected to contest mode. If the received message is not "R report" WSJT-X should continue to send the report and not auto-sequence to RRR. [Ed Muns] The operator is responsible for the appropriate messages being sent. If Auto Seq doesn't accomplish that in certain instances, then the operator should manually intervene. Andy, k3wyc
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
