Bill....it's up the the other operator to have the report, not you to make sure that your report has been received ok.

I've sent my report and if he hasn't got it he will ask again...

I have his call and report, for me the qso is ok. A lot of contacts are "not in log" or with wrong reports and doesn't count for Contest and award rules. This is because of the other operator not me or the transmission protocol. It happens frequently.

I don't think that this is either a problem of a transmission protocol. In fact in "DXPEDITION MODE" (TX1 and TX3 only )   there is no RR73 but qso's are valid.

But this is just an accademic discussion...what is useless is (TX6) also in normal (not Contest or DxPedition) qso's.

Anyway I would keep the RR73 (TX5) (although I don't think it's necessary) but with a maximum repeat of two...then it shoud pass over and prompt the log enter, and don't send any 73 (TX6) . This will stop all the 73 request that I can see on the HF causing only qrm  ( 3 or 4 or more periods make 1 minute and just to get  a 73 while your qso has already ended?).

73 de Carlo IK1HJS


Il 15/10/2018 22:58, Bill Somerville ha scritto:
On 15/10/2018 21:30, W0MU Mike Fatchett wrote:
I don't need to see rr73 or 73.  I prefer making contacts instead of finding reasons not to have contacts.  On CW or SSB working rare dx you never get a 73 so why do you need it here? You don't!  Have fun and log it.
W0MU

Mike,

if you don't wait for an RR73 or RRR message (they serve the same purpose as conformations or receipt of a key piece of QSO information) then you don't know that your report to your QSO partner has been received, that is not a complete two-way QSO by any reckoning. No contest rules or award rules would accept such a QSO as valid. A 73 message is not the same as a RR73 message, they are very different.

73
Bill
G4WJS.



_______________________________________________
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