Could the station calling be in NA contest mode? That starts with TX2.
Alan G0TLK
On 04/08/2021 20:43, Martin Davies G0HDB via wsjt-devel wrote:
On 4 Aug 2021 at 9:46, j...@comcast.net wrote:
This sounds like it is related to the "WSJT-X 2.5.0-rc3 RST_RCVD logging
issue" that I reported on this reflector on Fri 7/16/2021 10:45 PM. In the
brief JA-to-NA 6m FT8 openings, it is typical for the JA station to start
with the Tx2 message.
Ed N4II.
Thanks for the reply, Ed. Unfortunately I don't recall having seen your
posting; if I had I
would have added my input to your issue report.
I've just found that there's also a (short) thread about this topic on the
WSJT-X groups.io
forum; the posting that started the thread was from 5H1FF on 6th June and is at:
https://wsjtx.groups.io/g/main/message/25555.
Unfortunately the thread is now locked, because I'd like to have been able to
contribute to the
discussion.
Two of the responses to the issue report from 5H1FF suggest the solution is not
answering
or working stations that call with the Tx2 message, or removing the option to
call using Tx2.
In my opinion these are not at all helpful or sensible suggestions because
there can be many
occasions when it's highly desirable to minimise the duration of a QSO and
using the Tx2
message to call a station helps achieve this (IMO).
--
73, Martin G0HDB
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
