Return-Path: Received: from rly-ma02.mx.aol.com (rly-ma02.mail.aol.com [172.20.116.46]) by air-ma06.mail.aol.com (v125.7) with ESMTP id MAILINMA062-8954b0703a02e4; Fri, 20 Nov 2009 16:01:56 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-ma02.mx.aol.com (v125.7) with ESMTP id MAILRELAYINMA027-8954b0703a02e4; Fri, 20 Nov 2009 16:01:22 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1NBaal-0001cC-B0 for rs_out_1@blacksheep.org; Fri, 20 Nov 2009 21:00:31 +0000 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1NBaak-0001c3-TB for rsgb_lf_group@blacksheep.org; Fri, 20 Nov 2009 21:00:30 +0000 Received: from cavuit01.kulnet.kuleuven.be ([134.58.240.43]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1NBaak-0002oH-92 for rsgb_lf_group@blacksheep.org; Fri, 20 Nov 2009 21:00:30 +0000 Received: from smtps01.kuleuven.be (smtpshost01.kulnet.kuleuven.be [134.58.240.74]) by cavuit01.kulnet.kuleuven.be (Postfix) with ESMTP id AFF827B802A for ; Fri, 20 Nov 2009 22:00:20 +0100 (CET) Received: from webmail6.cc.kuleuven.be (webmail6.cc.kuleuven.be [134.58.242.53]) by smtps01.kuleuven.be (Postfix) with ESMTP id 925C531E702 for ; Fri, 20 Nov 2009 22:00:20 +0100 (CET) Received: by webmail6.cc.kuleuven.be (Postfix, from userid 48) id 752CA18056; Fri, 20 Nov 2009 22:00:20 +0100 (CET) Received: from 65.13-180-91.adsl-dyn.isp.belgacom.be (65.13-180-91.adsl-dyn.isp.belgacom.be [91.180.13.65]) by webmail6.kuleuven.be (Horde MIME library) with HTTP; Fri, 20 Nov 2009 22:00:20 +0100 Message-ID: <20091120220020.zn8j8euh7os4wgk8@webmail6.kuleuven.be> Date: Fri, 20 Nov 2009 22:00:20 +0100 X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Rik Strobbe To: "rsgb_lf_group@blacksheep.org" References: <20091120141648.8WGQY.1557635.root@mp17> <007f01ca6a1b$34a0b8d0$0401a8c0@xphd97xgq27nyf> <009a01ca6a22$07a90470$0517aac0@desktop> In-Reply-To: <009a01ca6a22$07a90470$0517aac0@desktop> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Internet Messaging Program (IMP) H3 (4.1.2) X-Originating-IP: 91.180.13.65 X-KULeuven-Information: Katholieke Universiteit Leuven X-KULeuven-Scanned: Found to be clean X-KULeuven-Envelope-From: rik.strobbe@fys.kuleuven.be X-Karma: unknown: X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: Re: LF: WSPR a QSO mode not just beacon Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=TO_ADDRESS_EQ_REAL 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-Mailer: Unknown (No Version) Jim, I agree. This is far more than the information that is exchanged in a =20 DX-pedition pile up, where the exchange is often limited to (a part =20 of) the calls and the obligatory 59(9) report. 73, Rik ON7YD - OR7T Quoting James Cowburn : > Dear All, > > According to the ARRL, WSPR contacts, if verified as two way, will quali= fy > towards DXCC awards as they consider these to be a QSO mode and not simp= ly a > beacon. > > As there is an exchange of callsign, locator and signal strength then th= at > was deemed sufficient by the ARRL to qualify for DXCC and as a QSO in a= data > mode much like RTTY or PSK31 for example. > > This was discussed at the recent RSGB conference in a session on WSPR. > > With best regards > > > Jim > > > > -----Original Message----- > From: owner-rsgb_lf_group@blacksheep.org > [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of mal hamilton > Sent: 20 November 2009 19:54 > To: rsgb_lf_group@blacksheep.org > Subject: Re: LF: Re: WD2XES WSPR 136.0 > > Recently there has been an upsurge in wspr BEACON appliance operators an= d > your suggested frequency area is not the place for them. The bottom end > would keep Beacon acty out of the way. There would still be room for the= odd > EU qrs operator, can't say I have heard many in recent years. The freq= area > 137 - 138 k/cs is frequently occupied by Russian and other EU dxers for > inter Country working using CW and QRS and 136.5 - 137 for local CW > working. > NA stns wishing to work EU would still use 137 - 138 on CW and QRS and= not > be clobbered by wspr carriers going ON/OFF. > I hope you see the logic > G3KEV > > ----- Original Message ----- > From: > To: > Sent: Friday, November 20, 2009 7:16 PM > Subject: Re: LF: Re: WD2XES WSPR 136.0 > > >> Thanks for the suggestion, but I doubt it will cause you any more > interference than it has for the last 5 years. From our perspective, the > lower end of the band has long been reserved for EU to NA operation. >> >> John, W1TAG >> >> ---- mal hamilton wrote: >> > om I woud suggest you Beacon at the extreme bottom end of the band an= d > not >> > in the middle of the CW and QRS DX portion. >> >> > > > >