Return-Path: Received: from mtain-mj01.r1000.mx.aol.com (mtain-mj01.r1000.mail.aol.com [172.21.164.85]) by air-dd04.mail.aol.com (v129.4) with ESMTP id MAILINDD042-86324cdfc8f42bd; Sun, 14 Nov 2010 06:33:08 -0500 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mj01.r1000.mx.aol.com (Internet Inbound) with ESMTP id B416B380000B5; Sun, 14 Nov 2010 06:33:06 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1PHao8-000300-8e for rs_out_1@blacksheep.org; Sun, 14 Nov 2010 11:31:40 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1PHao7-0002zr-Ml for rsgb_lf_group@blacksheep.org; Sun, 14 Nov 2010 11:31:39 +0000 Received: from out1.ip09ir2.opaltelecom.net ([62.24.128.245]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1PHao5-0003Zd-Gh for rsgb_lf_group@blacksheep.org; Sun, 14 Nov 2010 11:31:39 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ak4DAE1X30xcHYQp/2dsb2JhbACQaoMxDjGNf3G8T4VKBIFcjCE X-IronPort-AV: E=Sophos;i="4.59,195,1288569600"; d="scan'208,217";a="456985756" Received: from unknown (HELO xphd97xgq27nyf) ([92.29.132.41]) by out1.ip09ir2.opaltelecom.net with SMTP; 14 Nov 2010 11:31:30 +0000 Message-ID: <005301cb83ef$7bcf32b0$0401a8c0@xphd97xgq27nyf> From: "mal hamilton" To: References: <4CDEC5B8.17075.79A05A@mike.dennison.ntlworld.com> <4CDF089E.4090604@gmx.de> <66F8CECD4B354C5AA7B08F237E2577AB@White> Date: Sun, 14 Nov 2010 11:31:30 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: Re: LF: XDV QRSS60 137k Content-Type: multipart/alternative; boundary="----=_NextPart_000_0050_01CB83EF.7BA69C10" 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_40_50,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-global-disposition: G x-aol-sid: 3039400c89a24cdfc8f23645 X-AOL-IP: 195.171.43.25 ------=_NextPart_000_0050_01CB83EF.7BA69C10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Markus I agree with your point of view especially if some stations are churni= ng out Beacon mode and not listening. Qso mode is different where the frequency is being monitored all the= time for acty and evasive action can be taken if qrm becomes a proble= m. For those in Beacon mode stick to 136.320 E to W and 137.777 W to E al= so TA qso's use this procedure. This has worked well in the past. 73 de mal/g3kev ----- Original Message -----=20 From: Markus Vester=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Sunday, November 14, 2010 10:30 AM Subject: Re: LF: XDV QRSS60 137k Dear LF, again, I would very much favour to stay with the separation of trans= atlantic slots, ie. around 137.777 kHz for West-to-East and around 136= .320 for East-to-West.=20 On LF, the problem is not only related to a lack of dynamic range in= the receiver backend. Here in Central Europe, DCF39 keying sidebands= spill out a lot of in-band energy, which can only be effectively remo= ved by blanking. These periodic cutouts then modulate onto all in-band= signals, creating a set of nasty 0.1 Hz spaced sidelines around stron= g (but otherwise clean) amateur signals.=20 Kind regards, Markus=20 From: Hartmut Wolff=20 Sent: Saturday, November 13, 2010 10:52 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: XDV QRSS60 137k In the past EU QRSS beacons were transmitting in the 137.32 range.= Did this changed? I think I missed something. --=20 73 Hartmut www.h-wolff.de Locator: JO52hp ------=_NextPart_000_0050_01CB83EF.7BA69C10 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Markus
I agree with your point of view espec= ially if some=20 stations are churning out Beacon mode and not listening.
Qso mode is different where the frequ= ency is being=20 monitored all the time for acty and evasive action can be taken if qrm= becomes a=20 problem.
For those in Beacon mode stick to 136= .320 E to W=20 and 137.777 W to E also TA qso's use this procedure. This has worked= well in the=20 past.
73 de mal/g3kev
 
----- Original Message -----
Sent: Sunday, November 14, 20= 10 10:30=20 AM
Subject: Re: LF: XDV QRSS60= 137k

Dear LF,
 
again, I would very much favour to= stay with the=20 separation of transatlantic slots, ie. around 137.777 kHz for West-to-East and around 136.320= for East-to-West.=20
 
On LF, the problem is not only=  related=20 to a lack of dynamic range in the receiver backend. H= ere in=20 Central Europe, DCF39 keying sidebands spill out a lot of in-band en= ergy,=20 which can only be effectively removed by blanking. These periodic cu= touts then=20 modulate onto all in-band signals, creating a set of nasty= 0.1 Hz=20 spaced sidelines around strong (but otherwise clean) amateur si= gnals.=20
 
Kind regards,
Markus 
 
 
Sent: Saturday, November 13, 2010 10:52 PM
Subject: Re: LF: XDV QRSS60 137k
=
In the past=20 EU QRSS beacons were transmitting in the 137.32 range. Did this chan= ged? I=20 think I missed something.

--
73
Hartmut
www.h-wolff.de
Locator:= =20 JO52hp

------=_NextPart_000_0050_01CB83EF.7BA69C10--