Envelope-to: dave@picks.force9.co.uk Delivery-date: Wed, 25 May 2005 12:35:25 +0100 Received: by pih-mxcore05.plus.net with spam-scanned (PlusNet MXCore v2.00) id 1DauAV-000531-T0 for dave@picks.force9.co.uk; Wed, 25 May 2005 12:35:24 +0100 Received: from post.thorcom.com ([193.82.116.20]) by pih-mxcore05.plus.net with esmtp (PlusNet MXCore v2.00) id 1DauAV-00051r-FW for dave@picks.force9.co.uk; Wed, 25 May 2005 12:35:23 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1Dau9l-0000cR-Tq for rs_out_1@blacksheep.org; Wed, 25 May 2005 12:34:37 +0100 Received: from [193.82.116.30] (helo=relay.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1Dau9l-0000cI-9F for rsgb_lf_group@blacksheep.org; Wed, 25 May 2005 12:34:37 +0100 Received: from smtpout18.mailhost.ntl.com ([212.250.162.18] helo=mta10-winn.mailhost.ntl.com) by relay.thorcom.net with esmtp (Exim 4.43) id 1Dau9j-0002wf-Rg for rsgb_lf_group@blacksheep.org; Wed, 25 May 2005 12:34:37 +0100 Received: from aamta04-winn.mailhost.ntl.com ([212.250.162.8]) by mta10-winn.mailhost.ntl.com with ESMTP id <20050525113430.BOTC20297.mta10-winn.mailhost.ntl.com@aamta04-winn.mailhost.ntl.com> for ; Wed, 25 May 2005 12:34:30 +0100 Received: from mikedennison ([80.4.116.83]) by aamta04-winn.mailhost.ntl.com with ESMTP id <20050525113430.NCPO29369.aamta04-winn.mailhost.ntl.com@mikedennison> for ; Wed, 25 May 2005 12:34:30 +0100 From: "Mike Dennison" To: rsgb_lf_group@blacksheep.org Date: Wed, 25 May 2005 12:34:23 +0100 MIME-Version: 1.0 Message-ID: <429470CF.10995.5AB276@localhost> In-reply-to: <001301c56115$24ef57c0$6401a8c0@JAYTERMINAL> X-mailer: Pegasus Mail for Windows (4.21c) Content-description: Mail message body X-SPF-Result: relay.thorcom.net: domain of ntlworld.com designates 212.250.162.18 as permitted sender Subject: LF: Reception with multiple antennas Content-type: text/plain; charset=US-ASCII; format=flowed Content-transfer-encoding: 8bit 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-PN-SpamFiltered: by PlusNet MXCore (v2.00) I have been following this interesting discussion, but I have some perhaps naive observations which could do with some expert answers. Combining the output from two stations will give double the noise and double the signal - so no advantage there. I presume the fix is to make sure the two outputs are in phase, thus producing an improvement as the signals will be coherent but the noise will not. Plainly, there will be phase differences between the two receiving stations because of the different path lengths, and I suppose there would need to be compensation for this at the combining station. I can see this being useful for point to point ground-wave links, where the relative phase between the two received signals can be predicted and is constant. But how can it work when the incoming signal is from an unpredictable direction, and the path length (and hence phase) of a sky-wave signal is varying all of the time? At best you will have diversity reception (as described by Mal), but how do you keep two sky-wave signals in synch? Mike, G3XDV ==========