Il 15/07/22 02:12, Reino Talarmo ha scritto:
>Hopefully, in an ideal world, it should be that WSJT-X waits for a
second RR73 (hypothetical answer confirmation sequence I mean) from
the remote station, before to definitely close and log the QSO.
Hi Marco,
I am not sure what you mean by the “second RR73”. There seems to be a
generic misunderstanding how the protocol is assumed to work. User
Guide sections 7.1. and 7.4. provide a nice advice. For a minimum QSO,
where locator information is exchanged:
CQ K1ABC FN42 #K1ABC calls CQ
K1ABC G0XYZ IO91 #G0XYZ answers
G0XYZ K1ABC –19 #K1ABC sends report
K1ABC G0XYZ R-22 #G0XYZ sends R+report
G0XYZ K1ABC RR73 #K1ABC sends RR73
K1ABC G0XYZ 73 #G0XYZ sends 73
The last message (73) is optional.
Relevant issue is that in none of the examples a station that receives
RR73 is sending back RR73, but 73 or nothing more for that call.
73, Reino OH3mA
Yes Reino,
WSJT-X dialog sequence is clear and it performs like you explained here,
however often my WSJT-X sends RR73 to the remote station and opens up
the LOG QSO window for me to click on its OK label.
Unluckily due a series of reasons, if the remote station has not
received back my RR73 then it sends again the latest sequence to me and
in this case some times I manually hit again on my RR73 sequence to
confirm the QSO to the remote station.
This scenario is causing from time to time I collecting dupes QSOs in my
CQRLOG which I need to delete manually.
Regards,
---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
