Return-Path: Received: from rly-da01.mx.aol.com (rly-da01.mail.aol.com [172.19.129.75]) by air-da04.mail.aol.com (v125.7) with ESMTP id MAILINDA042-a4f4b070db3d9; Fri, 20 Nov 2009 16:44:40 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-da01.mx.aol.com (v125.7) with ESMTP id MAILRELAYINDA017-a4f4b070db3d9; Fri, 20 Nov 2009 16:44:20 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1NBbGB-0001l6-Hl for rs_out_1@blacksheep.org; Fri, 20 Nov 2009 21:43:19 +0000 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1NBbGA-0001kx-Vq for rsgb_lf_group@blacksheep.org; Fri, 20 Nov 2009 21:43:18 +0000 Received: from mail-bw0-f221.google.com ([209.85.218.221]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1NBbGA-00032P-0l for rsgb_lf_group@blacksheep.org; Fri, 20 Nov 2009 21:43:18 +0000 Received: by bwz21 with SMTP id 21so3998151bwz.4 for ; Fri, 20 Nov 2009 13:43:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=02zOBoCLReazA/UmKYxPihsZ9d80pRswF5ipH+rEQtQ=; b=kvobNcRs9AWYS/mj0ZR50n0gzts1ZaflJn0C/j7tAwzEtTDJI4lgR0M+N3i375tZ0s IEvG4D3xMhz3hTdqwM1PANSJ9WOSRj4h1uF5M8RLeYuQJxKjOU1eS11PyGEQna2HsXo1 7koz+Xrla+qI/fL6IuPlMhzT4zF6KFieLYwSQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=hAAYhh5X+DaWUP+XhDvUZvtf2OPnrFhlIk70Qq+pHL5wM4m8S3Px1nup9cQUZqCu6L idVk3mgxtAb8jgQRERzH8zlMjYovye5tICFVNOok6Pivow7KhJ6VIQN/x1W/wBmfKe2M IbTVNE4Qd7Q76tuhp6FloBD9HzbqjFpYapRiw= MIME-Version: 1.0 Received: by 10.204.157.24 with SMTP id z24mr1864875bkw.208.1258753391117; Fri, 20 Nov 2009 13:43:11 -0800 (PST) In-Reply-To: <009a01ca6a22$07a90470$0517aac0@desktop> References: <20091120141648.8WGQY.1557635.root@mp17> <007f01ca6a1b$34a0b8d0$0401a8c0@xphd97xgq27nyf> <009a01ca6a22$07a90470$0517aac0@desktop> Date: Fri, 20 Nov 2009 21:43:11 +0000 Message-ID: <9afca2640911201343q6330c05cxbc250a456fc61952@mail.gmail.com> From: Roger Lapthorn To: rsgb_lf_group@blacksheep.org X-Karma: unknown: DomainKey-Status: good (testing) X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: Re: LF: WSPR a QSO mode not just beacon Content-Type: multipart/alternative; boundary=0015175d0640bcc78c0478d45c4b 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=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: mail_rly_antispam_dkim-d248.1 ; domain : gmail.com DKIM : pass X-Mailer: Unknown (No Version) --0015175d0640bcc78c0478d45c4b Content-Type: text/plain; charset=ISO-8859-1 Now I am unclear what *really* constitutes a WSPR QSO. Does me getting a WSPR database report from XX3XXX and he getting on from me at much the same time on the same database constitute a QSO? Or does it have to be a "real" QSO a bit like JT6m? I agree with Rik that an HF contest exchange contains less (mutually useful) data than either of these. 73s Roger G3XBM 2009/11/20 James Cowburn > Dear All, > > According to the ARRL, WSPR contacts, if verified as two way, will qualify > towards DXCC awards as they consider these to be a QSO mode and not simply > a > beacon. > > As there is an exchange of callsign, locator and signal strength then that > 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 and > 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 and > not > > > in the middle of the CW and QRS DX portion. > > > > > > > > -- ------------------------------------------------------------- http://g3xbm-qrp.blogspot.com/ http://www.g3xbm.co.uk G3XBM GQRP 1678 ISWL G11088 --0015175d0640bcc78c0478d45c4b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Now I am unclear what really constitutes a WSPR QSO. Does me gettin= g a WSPR database report from XX3XXX and he getting on from me at much the= same time on the same database constitute a QSO? Or does it have to be a= "real" QSO a bit like JT6m?

I agree with Rik that an HF contest exchange contains less (mutually= useful) data than either of these.

73s
Roger G3XBM

2009/11/20 James Cowburn <james.cowburn@virgin.net>=
Dear All,

According to the ARRL, WSPR contacts, if verified as two way, will qualify=
towards DXCC awards as they consider these to be a QSO mode and not simply= a
beacon.

As there is an exchange of callsign, locator and signal strength then that=
was deemed sufficient by the ARRL to qualify for DXCC and as a QSO in a da= ta
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_l= f_group@blacksheep.org] On Behalf Of mal hamilton
Sent: 20 November 2009 19:54
To: rsgb_lf_group@blackshe= ep.org
Subject: Re: LF: Re: WD2XES WSPR 136.0

Recently there has been an upsurge in wspr BEACON appliance operators and<= br> 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 =A0 =A0 QRS and 136.5 - 137 for local= CW
working.
NA stns wishing to work EU would still use 137 - 138 on CW and =A0QRS and= not
be clobbered by wspr carriers going ON/OFF.
I hope you see the logic
G3KEV

----- Original Message -----
From: <w1tag@charter.net> To: <rsgb_lf_group@blac= ksheep.org>
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 <g3kevm= al@talktalk.net> wrote:
> > om I woud suggest you Beacon at the extreme bottom end of the ba= nd and
not
> > in the middle of the CW and QRS DX portion.
>
>






--
----------------------= ---------------------------------------
http://g3xbm-qrp.blogspot.com/
http://www.g3xbm.co.uk
G3XBM =A0 =A0GQRP 1678 =A0 =A0 =A0ISWL G11088
--0015175d0640bcc78c0478d45c4b--