Return-Path: Received: from rly-dc06.mx.aol.com (rly-dc06.mail.aol.com [172.19.136.35]) by air-dc07.mail.aol.com (v121_r4.4) with ESMTP id MAILINDC074-b28495144d7b2; Tue, 23 Dec 2008 15:06:57 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-dc06.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINDC064-b28495144d7b2; Tue, 23 Dec 2008 15:06:49 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LFDWT-0006kz-3G for rs_out_1@blacksheep.org; Tue, 23 Dec 2008 20:06:33 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LFDWS-0006kq-D4 for rsgb_lf_group@blacksheep.org; Tue, 23 Dec 2008 20:06:32 +0000 Received: from smtp-out-3.talktalk.net ([62.24.128.233] helo=smtp.talktalk.net) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1LFDWR-0006dG-DH for rsgb_lf_group@blacksheep.org; Tue, 23 Dec 2008 20:06:32 +0000 X-Path: TTSMTP X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEALPTUElOlrIG/2dsb2JhbACEVbo6WJF0hkM Received: from unknown (HELO mal769a60aa920) ([78.150.178.6]) by smtp.talktalk.net with SMTP; 23 Dec 2008 20:06:23 +0000 Message-ID: <00a201c96539$eed9c440$0301a8c0@mal769a60aa920> From: "mal hamilton" To: References: <000701c962f1$b79b04c0$4201a8c0@home> <016901c963c8$1c543720$8d01a8c0@JAYDELL> <494EE0A8.5040607@telus.net> <004501c963cf$24a20db0$8d01a8c0@JAYDELL> <000701c96492$04944b00$4201a8c0@home> <002201c96495$a77afe10$8d01a8c0@JAYDELL> <000b01c9649c$6066dec0$4201a8c0@home> <000501c96533$75ad5100$4201a8c0@home> Date: Tue, 23 Dec 2008 20:06:24 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: LF: Re: Re: WSPR Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit 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=none 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 Tnx Jim for the info but in actual fact 200 hz is required and not only 6 hz as some have specified, in other words if there was other acty within the 200 hz bandwidth it would corrupt the target signal. mal/g3kev ----- Original Message ----- From: "James Moritz" To: Sent: Tuesday, December 23, 2008 7:19 PM Subject: LF: Re: WSPR > Dear Mal, LF Group, > > The transmited WSPR signal has a bandwidth of about 6Hz. > > SSB mode is used for transmission in order to translate the soundcard > audio > to the appropriate RF frequency. But the signal bandwidth remains 6Hz > > At the receiver, a 200Hz bandwidth is extracted from the receive audio by > the DSP routines in the PC. This allows the transceiver to switch from TX > to > RX without changing modes. (In my case, I have configured the rig to use > the 250Hz CW filter as the "narrow SSB" filter, so the RX bandwidth is > only > 250Hz anyway). > > This 200Hz of bandwidth is then sub-divided into numerous narrow 6Hz > sub-channels, that can be simultaneously processed to receive lots of WSPR > beacons operating simultaneously on slightly offset frequencies within the > overall 200Hz range. That's the beauty of DSP. > > Overall, this means one transceiver can alternately transmit a WSPR beacon > signal and then receive many different WSPR signals within a 200Hz range, > during different 2 minute time slots. > > Cheers, Jim Moritz > 73 de M0BMU > > -------------------------------------------------------------------------------- No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.0/1861 - Release Date: 12/22/2008 11:23 AM