Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+Logging\s+quirks\s+with\s+WSJT\-X\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+Logging\s+quirks\s+with\s+WSJT\-X\s*$/: 3 ]

Total 3 documents matching your query.

1. [CQ-Contest] Logging quirks with WSJT-X (score: 1): Author: Terry Zivney <n4tz@arrl.net>; Date: Mon, 15 Jun 2020 17:06:25 +0000 (UTC); I operated the ARRL VHF QSO party sporadically this past weekend. I noticed some quirks in the logging process. I was justusing the barebones WSJT-X 2.10 program, as I'm suremany casual FT-8 contest; /archives//html/CQ-Contest/2020-06/msg00201.html (7,954 bytes)
2. Re: [CQ-Contest] Logging quirks with WSJT-X (score: 1): Author: <contesting@w2irt.net>; Date: Mon, 15 Jun 2020 15:01:42 -0400; I used N1MM+ with the special version of WSJT-x and it behaved mostly OK, but I did notice one problem. If I was called by a station or there was a belated reply where his grid square didn't populate; /archives//html/CQ-Contest/2020-06/msg00202.html (9,286 bytes)
3. [CQ-Contest] Logging quirks with WSJT-X (score: 1): Author: Bill Frede via CQ-Contest <cq-contest@contesting.com>; Date: Tue, 16 Jun 2020 14:25:27 +0000 (UTC); I experienced the same problem with the N1MM interface that you did. After losing 3 QSOs in the heat of battle I figured out how to get information entered correctly. The form that pops up requesting; /archives//html/CQ-Contest/2020-06/msg00204.html (10,182 bytes)

Current List: 1 - 3
Page: [1]