Return-Path: Received: from rly-me05.mx.aol.com (rly-me05.mail.aol.com [172.20.83.39]) by air-me04.mail.aol.com (v121.5) with ESMTP id MAILINME042-9ba48286647246; Mon, 12 May 2008 11:46:43 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-me05.mx.aol.com (v121.5) with ESMTP id MAILRELAYINME056-9ba48286647246; Mon, 12 May 2008 11:46:17 -0400 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1JvaDs-0007OG-Dq for rs_out_1@blacksheep.org; Mon, 12 May 2008 16:45:56 +0100 Received: from [193.82.59.130] (helo=relay2.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1JvaDr-0007O7-Oy for rsgb_lf_group@blacksheep.org; Mon, 12 May 2008 16:45:55 +0100 Received: from [62.24.128.231] (helo=smtp.talktalk.net) by relay2.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1JvaDo-0007km-Hn for rsgb_lf_group@blacksheep.org; Mon, 12 May 2008 16:45:55 +0100 X-Path: TTSMTP X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhNVAFMDKEhOlr7VPGdsb2JhbAATgiQ0hVuBWQuBJ4YzAQEBAS2QG4ga Received: from unknown (HELO g3kev) ([78.150.190.213]) by smtp.talktalk.net with SMTP; 12 May 2008 16:45:46 +0100 Message-ID: <029c01c8b447$3f08d400$0301a8c0@g3kev> From: "mal" To: References: <002101c8b40f$0fe78780$0201a8c0@home> Date: Mon, 12 May 2008 15:45:44 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 0.3 (/) X-Spam-Report: autolearn=disabled,AWL=0.312,HTML_MESSAGE=0.001 Subject: LF: Re: Becons etc. Content-Type: multipart/alternative; boundary="----=_NextPart_000_0299_01C8B447.3D5E0A30" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_20_30,HTML_MESSAGE autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-AOL-IP: 193.82.116.20 X-AOL-SCOLL-AUTHENTICATION: listenair ; SPF_helo : n X-AOL-SCOLL-AUTHENTICATION: listenair ; SPF_822_from : n ------=_NextPart_000_0299_01C8B447.3D5E0A30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello Chris Beacons can be useful the odd time but some are left on continuously for day= s. One weekend there was a chorous of beacons and some remained on for over=20= a week just generating qrm. GI3PDN, GI4DPE, GM4SLV, GW4HXO and a G3 in Norfolk, cannot remember his call= . I cannot see the necessity for this when they are all capable of working a= two way QSO on CW, then leaving the frequencies clear for others. I only wo= rk two way QSO mode and QSX on 3533/7033 khz for replies from those without=20= a NOV for the band plus some EU dx. I get lots of emails from others about beacons and some even advocate contac= ting OFCOM to have them stopped because of the QRM caused. I have not encour= aged this approach, hoping that it will go away eventually. I have a couple of large antennas for 500 and 137 khz and these pick up the=20= weakest signals and although good in qso mode I get all the beacon qrm as we= ll hi 73 for now and I hope you now see my point of view. de Mal/G3KEV =20 ----- Original Message -----=20 From: Chris=20 To: RSGB lf Group=20 Sent: Monday, May 12, 2008 9:03 AM Subject: LF: Becons etc. Hello Mal, G3KEV, I don't have NOV for 500kHz but enjoy listening. Happy to discuss by e-mai= l direct. I agree there is a problem with 'beacons'. Yesterdays long S9+ beacon sign= al was a nuisance to me, but I guess this was because the source was relativ= ely close. Chris, G4AYT, Whitstable, Kent. ----------------------------------------------------------------------------= -- Internal Virus Database is out-of-date. Checked by AVG.=20 Version: 7.5.524 / Virus Database: 269.23.8/1413 - Release Date: 03/05/200= 8 11:22 ------=_NextPart_000_0299_01C8B447.3D5E0A30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello Chris
Beacons can be useful the odd time but some= are=20 left on continuously for days. One weekend there was a chorous of beacons an= d=20 some remained on for over a week just generating qrm.
GI3PDN, GI4DPE, GM4SLV, GW4HXO and a G3 in=20= Norfolk,=20 cannot remember his call. I cannot see the necessity for this when they are=20= all=20 capable of working a two way QSO on CW, then leaving the frequencies clear f= or=20 others. I only work two way QSO mode and QSX on 3533/7033 khz for=20 replies from those without a NOV for the band plus some EU dx.
I get lots of emails from others about = ;beacons=20 and some even advocate contacting OFCOM to have them stopped because of the=20 QRM caused. I have not encouraged this approach, hoping that it wi= ll=20 go away eventually.
I have a couple of large antennas for=20= 500 and=20 137 khz and these pick up the weakest signals and although good in qso=20= mode=20 I get all the beacon qrm as well hi
73 for now and I hope you now see my point=20= of=20 view.
de Mal/G3KEV
 
----- Original Message -----
Chris
To: RSGB lf Group=20=
Sent: Monday, May 12, 2008 9:03 AM<= /DIV>
Subject: LF: Becons etc.

Hello Mal, G3KEV,
I don't have NOV for 500kHz but enjoy lis= tening.=20 Happy to discuss by e-mail direct.
I agree there is a problem with 'beacons'= .=20 Yesterdays long S9+ beacon signal was a nuisance to me, but I guess this w= as=20 because the source was relatively close.
Chris, G4AYT, Whitstable, Kent.

Internal Virus Database is out-of-date.
Checked by AVG.
Vers= ion:=20 7.5.524 / Virus Database: 269.23.8/1413 - Release Date: 03/05/2008=20 11:22
------=_NextPart_000_0299_01C8B447.3D5E0A30--