Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+Band\s+Change\s+Violation\s*$/: 3 ]

Total 3 documents matching your query.

1. [CQ-Contest] Band Change Violation (score: 1)
Author: Ed K1EP <k1ep.list@xxxxxxxxx>
Date: Thu, 1 Jun 2017 09:07:57 -0400
I received my UBN report for 2016 CQWW CW contest. Several QSOs were flagged as band change violations. We were operating as Multi-Single with one transmitter (no mult station). The QSO at 1145Z was
/archives//html/CQ-Contest/2017-06/msg00000.html (7,712 bytes)

2. Re: [CQ-Contest] Band Change Violation (score: 1)
Author: "Paolo, IK3QAR" <ik3qar@xxxxxxxxx>
Date: Thu, 1 Jun 2017 16:26:26 +0200
I've figured out what your actual log is... and looking at it (it's publicly available), I see no reason for that QSO being a band change violation. 73 Paolo IK3QAR On 01/06/2017 15:07, Ed K1EP wrote
/archives//html/CQ-Contest/2017-06/msg00001.html (9,066 bytes)

3. Re: [CQ-Contest] Band Change Violation (score: 1)
Author: "Walter J. Legowski" <sue.walt@xxxxxxxxxxxx>
Date: Thu, 01 Jun 2017 19:27:00 +0000
The sponsors are apparently still using the same flawed log-checking software that they were using many years ago. The software is unable to attribute which transmitter is running and which is mult-h
/archives//html/CQ-Contest/2017-06/msg00002.html (9,934 bytes)


This search system is powered by Namazu