Return-Path: Received: from rly-mb12.mx.aol.com (rly-mb12.mail.aol.com [172.21.131.170]) by air-mb02.mail.aol.com (v126.13) with ESMTP id MAILINMB022-d444b2248e224a; Fri, 11 Dec 2009 08:28:25 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-mb12.mx.aol.com (v125.7) with ESMTP id MAILRELAYINMB128-d444b2248e224a; Fri, 11 Dec 2009 08:28:04 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1NJ5WV-0007BK-Nj for rs_out_1@blacksheep.org; Fri, 11 Dec 2009 13:27:07 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1NJ5WV-0007BB-6v for rsgb_lf_group@blacksheep.org; Fri, 11 Dec 2009 13:27:07 +0000 Received: from mail-fx0-f217.google.com ([209.85.220.217]) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1NJ5WT-0008S2-Mt for rsgb_lf_group@blacksheep.org; Fri, 11 Dec 2009 13:27:07 +0000 Received: by fxm9 with SMTP id 9so1022539fxm.30 for ; Fri, 11 Dec 2009 05:27:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=YjNy5gtUe/Hb2dqT9Q2iHhGsfogqNgLvKVrCvk3Uv+k=; b=c5MCdZx1yV7YJCZ8G7ENvf7AK6WdioRIpJeHbQHCSXNkkGeSLEEUHRXFaRJsH/UCSJ /k4W3NId3JsLHEMG7Aaq43aBtVxde6TqgNqgNifhsuB8qIHZHkxasc+5O0zqBalqesfC zxg1QYxZHQbYLxf49vu0CNi07ZXOm/w11NkPg= 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:content-transfer-encoding; b=LYc0HIIN8fkaJW7hMm5Se2dL+hxt4SCO8Ppfl4MeBwPSigVO7kzfLfrqgeQyW16i+o WSz+eq18foYaVOXwOYgKZJN4sZboi9+k9Tz5XFmD4Ddg5P0FjlOaKtr/XHOuvngz3sw4 jDGpD5VUqGgQ7TS/0yIwrTrHgvPOsyBSDEIJk= MIME-Version: 1.0 Received: by 10.239.190.69 with SMTP id w5mr135974hbh.143.1260538019932; Fri, 11 Dec 2009 05:26:59 -0800 (PST) In-Reply-To: <4B22410F.1000306@telia.com> References: <38A51B74B884D74083D7950AD0DD85E828AC12@File-Server-HST.hst.e-technik.tu-darmstadt.de> <4B22410F.1000306@telia.com> Date: Fri, 11 Dec 2009 13:26:59 +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,none Subject: Re: LF: "Gain" between qrss3 and qrss10? Content-Type: text/plain; charset=ISO-8859-1 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=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 X-AOL-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-m263.2 ; domain : googlemail.com DKIM : pass X-Mailer: Unknown (No Version) On this matter... For the recent talk I gave on weak signals at a Microwave Roundtable ( http://www.g4jnt.com/MartleSham.htm ) I made some simulated CW in Noise using accurately calibrated S/N levels. An interesting finding came to light, if you normalise the signal rate to the S/N, so making bandwidth irrelevent, most of the 'fuzzy' modes end up with a similar capability. In other words, Aural CW, QRSS, SMT Hell all need a similar S/N at their respective bandwidths to work. The actual normalised S/N for readability is subject to the operator's experience togther with Temperature/Time of day/mood/Age/Gender/Alcohol intake/Hunger/Weather or any other similar parameter, but there's no massive differences between any of them. So its all down to bandwidth. Even machine modes without error correction manage a not-too-dissimilar performance once their data rates have been normalised. However, if you spread the signal, intentionally, by adding FEC, the improvements can be enormous. As I think we all know only too well when comparing QRSS etc with WSPR, Wolf and other modes with heavy FEC. At least on microwaves we have the luxury of virtually unlimited bandwidth, so can operate in a true Shannon power limited channel to make the most of band spreading. Incidently, the usually quoted signal efficiency used on one axis of the Shannon curve "Bits/second/Hz" sounds uninspiring. But if, instead of Hz, you use the old term 'cycles per second', it becomes Bits/cycle. Which puts a whole new meaning and explanation to the axis on the Shannon curve, and elicited an "Oh Wow, yes, that IS an interesting way of putting it" when told to an experienced comms engineer. The term was actually used in Shannon's original paper of 1948, but seems to have got lost Andy www.g4jnt.com This email has been scanned for damaging side-effects by the health and safety police 2009/12/11 Johan H. Bodin : > Hi Stefan, > >> Or isn't it possible to give such a relation? > > Yes, it is not only possible, it is in fact quite simple: > When the speed is reduced by a factor K, the information bandwidth is > also reduced by the same factor. This allows you to use a receiver > bandwidth which is K times narrower without missing any information. The > nice thing is that the noise power passing through this bandwidth is > also K times smaller - The S/N ratio has improved K times (or 10*log(K) > dB if you prefer). In other words, you can reduce the TX power by the > same factor K and still enjoy the same SNR (if RX BW is is also made K > timer narrower). > > In visually received QRSS, the receiver bandwidth is equal to the RBW, > the "resolution bandwidth", which is approximately equal to the FFT bin > width (one pixel on Argo). > > QRSS30 is 10dB more efficient than QRSS3, in theory at least. > > 73 > Johan SM6LKM > > ---- > > Stefan Sch=E4fer wrote: >> Dear LF, >> Does anybody know about the "gain" between QRSS3 and QRSS10 or QRSS30?= I mean, if the noise in both cases is equal, how much can I reduce my tx= pwr when switching from qrss3 to qrss10? Or isn't it possible to give suc= h a relation? >> And: Was there ever a TA QSO in QRSS3? >> I am new on the reflector, sri ;-) >> >> Stefan / DK7FC >> >> > >