Since the new GA version 2.3.0 is out, and JT-Alert is now ast 2.16.17, try updating to the new versions to see if this still occurs. Trying to troubleshoot a superseded version is probably not practical at this point in time.
Neil, KN3ILZ On 2/12/2021 9:31 PM, M Bo wrote:
Dear friends, I am running wjst-x 2.2.2 with jtalert 2.16.13 on a windows 10 OS. I was answering a CQ from F4CZV on FT8. F4CZV was at 1861 Hz when he responded, and then I confirmed and sent SNR. At the next dwell, G0TSM on 1317 Hz was in my receive window sending RR73 to W1BS. Then, my FT8 called G0TSM instead of sending 73 to F4CZV. This occurred at 134630 and again during another event at 135745, with G0TSM sending on 1317 Hz while I was trying to QSO with PJ4NX on 2103 Hz. I have attached screen shots of these two events plus the wsjt-x log excerpts. This is a non-frequent but recurring event with v2.2.2, that I never experienced with the previous version(s) of wsjt-x. 73, mike n2mn
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
