W9ET's 73 message was a QSL that he received N9UDO's report. It would have
been clearer had the default message of "RR73" been sent, but nonetheless,
W9ET's message was more than a "courtesy" because it served to tell N9UDO that
he received his report. That really is a requirement for a solid contact.
CW/SSB/RTTY contesting has long had the convention that both QSO partners QSL
the contact.
Yes, the appropriate action that N9UDO could have taken was to simply log the
contact once he received the 73 message from W9ET, which effectively QSL'd
N9UDO's report. BUT, what if N9UDO did not receive the 73 message? Then,
resending his Tx 3 message was exactly the right thing to do. W9ET should
continue to respond with his QSL message (73 in this case) until N9UDO stops
resending his report. That is W9ET's clue that N9UDO had not received the QSL
message.
Now, it is more likely that N9UDO had Auto Seq enabled and his PC was resending
Tx 3 (his report) because WSJT-X had not received the expected Tx 4 message
(RR73) from W9ET. But, W9ET can't know which case it is (N9UDO did receive his
QSL message OR N9UDO's Auto Seq function is running "unattended"). At some
point one or both QSO partners will give up ... if they want to try to complete
a QSO with someone else.
Ed W0YK
-----Original Message-----
From: CQ-Contest <cq-contest-bounces@contesting.com> On Behalf Of Stanley
Zawrotny
Sent: 29 July, 2019 14:18
To: Joe <nss@mwt.net>
Cc: Contest Reflector <cq-contest@contesting.com>
Subject: Re: [CQ-Contest] WWDIGI Contest Testing...
From a pure contesting perspective, receiving a 73 is not a requirement for
making a contact. The 73 is a curtesy. W9ET has done his part and is correct in
moving on. Why should he have to slow down his Q rate on the mere POSSIBILITY
that someone may not hear the curtesy?
N9UDO should manually log the QSO and continue with the contest unless he wants
to penalize himself AND W9ET for a missed contact. W9ET won’t work him again
because he thinks he is a dupe.
Stan, K4SBZ
"Real radio bounces off the sky."
> On Jul 29, 2019, at 9:40 AM, Joe <nss@mwt.net> wrote:
>
> I was testing my set up with a few locals for the Up-Coming WWDIGI Contest,
> and we discovered something, that is NOT a HUGE issue, but looking for a
> workaround.
>
> here is what happened.
>
> N9UDO calling CQ
>
> W9ET answers CQ with 'N9UDO W9ET EN43'
>
> N9UDO replies with 'W9ET N9UDO R EN53'
>
> W9ET responds by sending 73 round
>
> N9UDO does not hear the 73 and keeps re-sending 'W9ET N9UDO R EN53'
>
> W9ET is not aware that this is happening because it's TX has been turned off
> because the contact was logged. And W9ET is off looking for the next S&P to
> try to get.
>
> This is with the N1MM+ & WSJT-X set up. Running with the Auto Log box checked
> and the special contest with the NA VHF chosen.
>
> N9UDO can manually add the EN43 and manually log the contact,
>
> Thinking if the 73 is it a must have for a valid contact? if so, maybe the
> W9ET side should not shut off the TX enable button till it gets the 73?
>
> or how should this situation be handled?
>
> Joe WB9SBD
> --
> Sig
> The Original Rolling Ball Clock
> Idle Tyme
> Idle-Tyme.com
> http://www.idle-tyme.com
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|