Mail Archive Search: <+from:tree@kkn.net>

Results:

References: [ +from:tree@kkn.net: 849 ]

Total 849 documents matching your query.

141. Topband: Noise ID (score: 1): Author: Tree <tree@kkn.net>; Date: Sat, 31 Dec 2005 23:00:16 -0800; Anyone think they know what this might be? I think this noise has been around for years - but it sure comes up "out of the other noise" with my new JA Beverage. I have found the general area it is co; /archives//html/Topband/2006-01/msg00000.html (6,278 bytes)
142. Topband: Boring Report (score: 1): Author: Tree <tree@kkn.net>; Date: Tue, 3 Jan 2006 09:22:03 -0800; The waters went down and I was able to hook up the new European Beverage. Simply - it works. Last night, UU4JMG was heard all evening from my sunset until his sunrise. There was long and slow QSB on; /archives//html/Topband/2006-01/msg00020.html (6,781 bytes)
143. Re: Topband: Last Night - S9SS (the "Alligator") (score: 1): Author: Tree <tree@kkn.net>; Date: Thu, 12 Jan 2006 08:50:36 -0800; An excellent pointer Charles. The "sequence" of a QSO needs to be paid attention to so those tough QSOs can be made. Not sending the report until you are sure the DX station came back to you and you; /archives//html/Topband/2006-01/msg00168.html (8,573 bytes)
144. Re: Topband: 160 and other Contest Log verification (score: 1): Author: Tree <tree@kkn.net>; Date: Mon, 23 Jan 2006 12:26:47 -0800; I think the "feature" of being able to tell what your exchange would be based upon the previous QSO applies to all contests - and the subsequent QSO in most contests. That is - unless you are using; /archives//html/Topband/2006-01/msg00335.html (8,242 bytes)
145. Topband: Boring Report - 9N7JO (score: 1): Author: Tree <tree@kkn.net>; Date: Tue, 24 Jan 2006 12:08:55 -0800; This morning I had an appointment that enabled me to be on the radio at sunrise (or just before) and was amazed to tune in a signal on 1835 and find 9N7JO CQing! I didn't have the transmitter QRV yet; /archives//html/Topband/2006-01/msg00349.html (7,513 bytes)
146. Topband: More Boring zone 22 (score: 1): Author: Tree <tree@kkn.net>; Date: Wed, 25 Jan 2006 09:07:58 -0800; This AM - was seeing Spectran traces for 9N7JO (I think) and VQ9LA. VQ9LA peaked up and worked at least one west coast station. I was copying occasional bursts of letters around 1525 - the same time; /archives//html/Topband/2006-01/msg00362.html (6,495 bytes)
147. Re: Topband: CQWW160 (score: 1): Author: Tree <tree@kkn.net>; Date: Thu, 26 Jan 2006 06:49:36 -0800; I think it should be pointed out that the problem here wasn't the log checking. The log checking did determine that half of the log was "incorrect" and the QSOs were taken out. Perhaps K4JRB is guil; /archives//html/Topband/2006-01/msg00378.html (7,798 bytes)
148. Re: Topband: Calling without hearing (was CQ 160 WW) (score: 1): Author: Tree <tree@kkn.net>; Date: Tue, 31 Jan 2006 10:21:26 -0800; You are not alone Bob. In fact, that is why we have this rule in the Stew Perry contest: "Remote or Cluster spotting shall not be used." However, I believe there are other factors. Some of them are; /archives//html/Topband/2006-01/msg00420.html (10,249 bytes)
149. Re: Topband: Calling without hearing (was CQ 160 WW) (score: 1): Author: Tree <tree@kkn.net>; Date: Tue, 31 Jan 2006 16:23:43 -0800; Different people call CQ DX at different times - with different results. W7LR recently discovered that he should probably call CQ DX more often than he does. I occasionally do it under specific circ; /archives//html/Topband/2006-01/msg00439.html (7,989 bytes)
150. Re: Topband: CQ 160 WW experience (score: 1): Author: Tree <tree@kkn.net>; Date: Wed, 1 Feb 2006 08:42:41 -0800; i I have to share this story... back in the 1990 CQ 160, I found myself in Texas at the QTH of N5KO / WN4KKN. We had a spotlight European opening (putting about 50 of them in the log) and we worked; /archives//html/Topband/2006-02/msg00020.html (8,233 bytes)
151. Re: Topband: 160 m Propagation (score: 1): Author: Tree <tree@kkn.net>; Date: Wed, 1 Feb 2006 12:54:19 -0800; Was some great ducting from N8T to Oregon during the contest. Excellent signal. I would be interested in knowing more about the antenna used there. It sounded better than K9DX out here. Tree _______; /archives//html/Topband/2006-02/msg00033.html (7,039 bytes)
152. Re: Topband: fixed freq receiving beacons, remote radios, and awards (score: 1): Author: Tree <tree@kkn.net>; Date: Thu, 9 Mar 2006 18:17:16 -0800; If one calls CQ on the frequency, they might get DX calling them that they would otherwise not hear. There are technical solutions to this problem - like limiting the connection time to a minute or t; /archives//html/Topband/2006-03/msg00069.html (11,058 bytes)
153. Topband: Boring Report - VK6ABL (score: 1): Author: Tree <tree@kkn.net>; Date: Tue, 14 Mar 2006 09:04:19 -0800; This morning, turned on the radio and heard VK6ABL working W7AWA. After our QSO, he went into beacon mode for awhile. I also called some CQs and was rewarded with JA7MSQ calling me. I guess if we all; /archives//html/Topband/2006-03/msg00110.html (6,948 bytes)
154. Topband: Boring Morning Report (score: 1): Author: Tree <tree@kkn.net>; Date: Wed, 15 Mar 2006 09:44:50 -0800; Fellow topbanders This morning I was surprised to find quite a bit of activity from JA on the band around 1230-1300 UTC. I worked eight of them - about half for the first time on topband. It was enco; /archives//html/Topband/2006-03/msg00122.html (6,613 bytes)
155. Topband: Boring Report - EUROPE!! (score: 1): Author: Tree <tree@kkn.net>; Date: Thu, 16 Mar 2006 10:34:21 -0800; Spotlight conditions to Scandinavia last night - OZ1DD was coming through with lots of QSB - eventually peaking 589 - as strong as the USA stations working him. ES1QD was worked first, and OH3XR and; /archives//html/Topband/2006-03/msg00126.html (6,628 bytes)
156. Re: Topband: TY - 160 (score: 1): Author: Tree <tree@kkn.net>; Date: Mon, 20 Mar 2006 08:25:29 -0800; They finally peaked up around their sunrise on 80 meters and I was able to work them there. They seemed to be doing pretty well with the pileup on CW - so I am optimistic that they will be workable o; /archives//html/Topband/2006-03/msg00139.html (8,998 bytes)
157. Re: Topband: TY5MR (score: 1): Author: Tree <tree@kkn.net>; Date: Tue, 28 Mar 2006 19:23:09 -0800; Heard - the only night they stuck around after my sunset - but not worked. The guys down in the south had better luck. I know N7DD worked him along with some sixes. Tree N6TR/7 - Boring, OR _________; /archives//html/Topband/2006-03/msg00196.html (7,295 bytes)
158. Re: Topband: ty aftermath (score: 1): Author: Tree <tree@kkn.net>; Date: Fri, 31 Mar 2006 13:08:15 -0800; when you are one of them. Such is life when you live on the wrong coast. Sure - if the TY had spent a lot more time on 160 at their sunrise, we probably could have worked them, but it is impossible t; /archives//html/Topband/2006-03/msg00225.html (8,021 bytes)
159. Topband: Boring report - it's not dead yet (score: 1): Author: Tree <tree@kkn.net>; Date: Tue, 4 Apr 2006 08:16:27 -0700; The band has been pretty noisy during the past few days. We have been having some bad static from nearby storms (even hearing some thunder occasionally). Last night, I heard W2VJN calling CQ - which; /archives//html/Topband/2006-04/msg00008.html (6,763 bytes)
160. Topband: Radar last night? (score: 1): Author: Tree <tree@kkn.net>; Date: Tue, 4 Apr 2006 10:42:19 -0700; When I was working DF2PY and G3JMJ, I heard some really strange noise on the band. I didn't report it at first, because I thought it might have been due to a new video card I installed on my computer; /archives//html/Topband/2006-04/msg00011.html (7,117 bytes)

Current List: 141 - 160
Page: [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]