Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+N1MM\s+Auto\-spotting\s+Change\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+N1MM\s+Auto\-spotting\s+Change\s*$/: 4 ]

Total 4 documents matching your query.

1. [CQ-Contest] N1MM Auto-spotting Change (score: 1): Author: David Siddall <hhamwv@gmail.com>; Date: Thu, 29 Oct 2015 21:45:59 -0400; I updated N1MM+ today, and indeed it includes the revision to spotting. The notes explain it thusly: "For each Entry Window, do not auto spot QSOs if successive QSOs are on the same frequency. This i; /archives//html/CQ-Contest/2015-10/msg00264.html (8,686 bytes)
2. Re: [CQ-Contest] N1MM Auto-spotting Change (score: 1): Author: W0MU <w0mu@w0mu.com>; Date: Fri, 30 Oct 2015 12:35:00 -0600; Why would the program not figure out that it was in run mode if two contacts were made on the same frequency back to back? Forgetting to set run mode is a pretty common issue. "For each Entry Window,; /archives//html/CQ-Contest/2015-10/msg00279.html (9,847 bytes)
3. Re: [CQ-Contest] N1MM Auto-spotting Change (score: 1): Author: Jim Brown <k9yc@audiosystemsgroup.com>; Date: Fri, 30 Oct 2015 12:20:16 -0700; It is if you don't call CQ with an F-key CQ message. I use three CQ messages -- a very short (TEST K9YC) on F1, a slightly longer one on F8, and a longer one on F9. Since F1 is the designated CQ mess; /archives//html/CQ-Contest/2015-10/msg00284.html (8,177 bytes)
4. Re: [CQ-Contest] N1MM Auto-spotting Change (score: 1): Author: Steve London <n2icarrl@gmail.com>; Date: Fri, 30 Oct 2015 13:48:16 -0600; It is very common for two stations to be running within the tuning tolerance you have set in N1MM Logger. You S&P the first one. Good. Now you S&P the 2nd one. With your proposed implementation, work; /archives//html/CQ-Contest/2015-10/msg00285.html (11,127 bytes)

Current List: 1 - 4
Page: [1]