When sending RR73 the other station doesn't have to reply with a 73. The reason is that the QSO is over at RR73. A lot of stations take as much and move on.
If you'd like your 73 just change the RR73 to RRR by double clicking Tx 4. Doing it this way it will not log until you receive the 73. This also might be a good idea as you stated you have a little station. Another thing you could do is to check Prompt me to log QSO on the Reporting tab. This pops up a box and it stays there until you feel the QSO is sufficient to log even if you send RR73. Of course this doesn't work if you are in a contest mode and you have Log automatically checked.
Fred
N2XK
On Jul 14, 2022 11:24 PM, Adrian via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:
It is a good point, wsjtx should not auto log until the 73 is received, not RR73 sent.
Case in point is the rejected eqsl's from stations in my log, but I am not in theirs.
This would save that problem.
In the meantime, in those situation's, my TX is set free to change, and I click a
vacant column on pan to better my chances of finishing the qso.
Many stations don't bother with the 73 because of this shortfall.
73
vk4tux
On 15/7/22 13:10, Marco Calistri via wsjt-devel wrote:
Il 14/07/22 23:18, jarmo ha scritto:
Thu, 14 Jul 2022 23:02:32 -0300 Marco Calistri via wsjt-devel <wsjt-devel@lists.sourceforge.net> kirjoitti:Hello,This occurrence causes that WSJT-X logging the QSO then I go to hit "OK" and QSO is getting saved on my CQRLOG app. (I'm using Linux).I'm using also, now question, why you hit OK, if qso is not complete? I hit again opposite stations report to give again RR73, some cases move couple Hz TX and hit again RR73. Normally I do this max 5 times and then hit CANCEL. Can't log unfinished qso.
Good point!
Yes probably I just have to discard the logged QSO offered by WSJT-X in cases like this one and click OK only when QSO get really completed.
The fact is that as soon as WSJT-X sends the RR73 to the partner then from a WSJT-X point of view the QSO is complete!
Thanks Jarmo for your comments. I believed that this process (logging QSO) would be totally managed by WSJT-X, without any human intervention.Normally this means, that someone qrm'ing so much, that opposite station can't hear anymore me.But I would like to know if I could adjust something into WSJT-X settings, to avoid closing QSO's "unilaterally".This could ba, as sending that RR73 so long yuo get /# or if not you cancel qso.. Jarmo, oh1mrr
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.
Regards,
---
73 de Marco, PY1ZRJ (former IK5BCU)
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
