Reino is correct – in the example I experienced (reported in the archives at https://sourceforge.net/p/wsjt/mailman/message/37321504/ ) the JAs were not calling in NA contest mode, either. Since the received signal reports were displayed correctly in the WSJT-X Rx Frequency window (and reported correctly in the ALL.TXT file), the problem was only noticed when I copied the wsjt_log.adi file into my shack log (Logger32). When one sees:
-- 4 consecutive -12 dB entries, followed by -- 4 consecutive -08 dB entries, followed by -- 4 consecutive -14 dB entries, followed by -- 11 consecutive -12 dB entries, followed by -- 10 consecutive -17 dB entries . . . in the RST_RCVD column in your log, it’s pretty clear that there’s a logging problem. I suspect it occurs when a station “tail-ends” a completed QSO by calling with a Tx2 call, but that remains to be confirmed. Ed N4II. From: Reino Talarmo via wsjt-devel <[email protected]> Sent: Thursday, August 5, 2021 4:22 AM To: [email protected]; 'WSJT software development' <[email protected]> Cc: Reino Talarmo <[email protected]> Subject: Re: [wsjt-devel] 'Rpt Rcvd' not being correctly populated >Could the station calling be in NA contest mode? That starts with TX2. Alan, That’s not the case as NA VHF contest mode Tx2 contains locator, not signal report. 73, Reino OH3mA
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
