Return-Path: Received: from mtain-me05.r1000.mx.aol.com (mtain-me05.r1000.mx.aol.com [172.29.96.141]) by air-mb05.mail.aol.com (v129.4) with ESMTP id MAILINMB053-a5b94cd1ee08f6; Wed, 03 Nov 2010 19:19:37 -0400 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-me05.r1000.mx.aol.com (Internet Inbound) with ESMTP id 6ABAC380024FC; Wed, 3 Nov 2010 19:19:33 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1PDmam-0005w4-6w for rs_out_1@blacksheep.org; Wed, 03 Nov 2010 23:18:08 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1PDmal-0005vv-Pb for rsgb_lf_group@blacksheep.org; Wed, 03 Nov 2010 23:18:07 +0000 Received: from mail-gy0-f171.google.com ([209.85.160.171]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1PDmaj-0003K4-H1 for rsgb_lf_group@blacksheep.org; Wed, 03 Nov 2010 23:18:07 +0000 Received: by gyd12 with SMTP id 12so941419gyd.16 for ; Wed, 03 Nov 2010 16:17:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=sMQOZ/lg5E7F5cofDzB00Ujrc8ftDV3pL+jylbfdTTE=; b=iuzUKYmScq+le4WDztfr4C1F8yCEX0FlZOw6ZbqnBiKESJX/NbVpgxJ7Kjdpy1eBRh 2O8b4WMe1gRwMSI/PH9KPgKvKA5JLYjnXhocmGxto7VvEeibrutU86eJmLDMuzLMNU0q 8zPoHV/mdYEuSZDgvVfZr9lHtQIxZWjFkCVFg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=pMSfu3FC0UYCCE+mt4mbiCQWY7D9gTWuj9FZpxEFcWbw5100PhlrI8i7M8d6JAyVzj 6UAlrtsZ0NeSJQELGTMWrcEFboc9NnrUBx9cFhL5WiSNrF2kcdc5JhR7NdFWB4EEYRLP ZRWaHv31uEdqQpB1HRgkZTrdXb04B5iJddvBM= MIME-Version: 1.0 Received: by 10.42.221.137 with SMTP id ic9mr2539415icb.151.1288826278702; Wed, 03 Nov 2010 16:17:58 -0700 (PDT) Received: by 10.231.79.69 with HTTP; Wed, 3 Nov 2010 16:17:58 -0700 (PDT) In-Reply-To: <1288825676.4cd1eb4c162d3@imp.netikka.net> References: <4CD1CD51.2010103@kpnmail.nl> <1288819317.4cd1d275cc0bf@imp.netikka.net> <000f01cb7ba6$b2802040$8d01a8c0@JAYDELL> <1288825676.4cd1eb4c162d3@imp.netikka.net> Date: Wed, 3 Nov 2010 23:17:58 +0000 Message-ID: From: Andy Talbot To: rsgb_lf_group@blacksheep.org DomainKey-Status: good (testing) X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: Re: LF: WSPR window Content-Type: multipart/alternative; boundary=20cf3043475284f07c04942e40c7 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_20_30, HTML_FONTCOLOR_UNSAFE,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-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-m202.2 ; domain : googlemail.com DKIM : pass x-aol-sid: 3039ac1d608d4cd1ee0526ff X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none X-Mailer: Unknown (No Version) --20cf3043475284f07c04942e40c7 Content-Type: text/plain; charset=ISO-8859-1 Most transceivers can be operated in split mode now, isn't this a workable solution ? And anyone with separate Tx / Rx setups has got split frequency operation by default Andy www.g4jnt.com On 3 November 2010 23:07, Paul-Henrik wrote: > WSPR is a "party-line" mode by default, you have to receive where you > transmit. > This limitation can be overcome by running two WSPR setups and having the > receiver on a different frequency, or better still, receiving on two > frequencies as I do at the moment. > > Perhaps a future WSPR version will have an option of arranging split > frequency > operation where the user can specify separate transmit and receive windows? > > BR > > Paul-Henrik, OH1LSQ > > > Quoting jrusgrove@comcast > --20cf3043475284f07c04942e40c7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Most transceivers can be operated in split mode now, isn't this= a workable solution ?
And anyone with separate Tx / Rx setups has got split frequency opera= tion by default
=A0
On 3 November 2010 23:07, Paul-Henrik <phl@netikka.fi> wrote:
WSPR is a "party-line&quo= t; mode by default, you have to receive where you transmit.
This limita= tion can be overcome by running two WSPR setups and having the
receiver on a different frequency, or better still, receiving on two
fr= equencies as I do at the moment.

Perhaps a future WSPR version will= have an option of arranging split frequency
operation where the user= can specify separate transmit and receive windows?

BR

Paul-Henrik, OH1LSQ
--20cf3043475284f07c04942e40c7--