X-GM-THRID: 1216846436157086534 X-Gmail-Labels: rsgb lf X-Gmail-Received: 2db303a0dac1682c52dc2d8daeea8a167d6a964c Delivered-To: daveyxm@gmail.com Received: by 10.78.205.5 with SMTP id c5cs12753hug; Tue, 10 Oct 2006 03:13:13 -0700 (PDT) Received: by 10.67.29.12 with SMTP id g12mr8061389ugj; Tue, 10 Oct 2006 03:13:13 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by mx.google.com with ESMTP id 24si2457862ugf.2006.10.10.03.13.12; Tue, 10 Oct 2006 03:13:13 -0700 (PDT) Received-SPF: neutral (google.com: 193.82.116.20 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1GXEVt-00027k-BP for rs_out_1@blacksheep.org; Tue, 10 Oct 2006 11:07:05 +0100 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1GXEVs-00027b-VI for rsgb_lf_group@blacksheep.org; Tue, 10 Oct 2006 11:07:04 +0100 Received: from smarthost4.mail.uk.easynet.net ([212.135.6.14]) by relay1.thorcom.net with esmtp (Exim 4.62) (envelope-from ) id 1GXEVp-0003uO-A6 for rsgb_lf_group@blacksheep.org; Tue, 10 Oct 2006 11:07:04 +0100 Received: from tnt-13-103.easynet.co.uk ([212.134.22.103] helo=captbrian) by smarthost4.mail.uk.easynet.net with smtp (Exim 4.10) id 1GXEVn-000NVv-00 for rsgb_lf_group@blacksheep.org; Tue, 10 Oct 2006 11:07:00 +0100 Message-ID: <00a301c6ec53$d54be780$721686d4@captbrian> From: "captbrian" To: References: <7D653C9C42F5D411A27C00508BF8803D06EFE514@mail.dstl.gov.uk> Date: Tue, 10 Oct 2006 11:06:04 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 0.1 (/) X-Spam-Report: autolearn=disabled,AWL=0.051 Subject: LF: Re: RE: Re: Re: erp eirp - bluff Content-Type: text/plain; charset="iso-8859-1" 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 Status: O X-Status: X-Keywords: X-UID: 4243 Aha I wasn't so stupid then..... Now , you asked for this.......what is the polarity of an 'isotropic ' radiator .? Bryan ----- Original Message ----- From: "Talbot Andrew" To: Sent: 10 October 2006 08:04 Subject: LF: RE: Re: Re: erp eirp - bluff > It should be, but the 'rule makers' way-back-when in their infinite wisdom > decided that dipoles were easier for the humdrum public to visualise so > defined ERP as being relative to a perfect dipole. > > As it is difficult to make dipoles at high frequencies (actually it is a lot > wasier easier, but... Never mind) ERP there was defined as being relative to > isotropic. So... > > Below 1000MHz ERP is defined as being realitive to a dipole, above 1GHz ERP > is defines as being the same as EIRP. > > Its just a matter of semantics. I fell into this trap and queried the ERP > limits when 50MHz was first introduced several decades ago. 50MHz requires > EDRP, so the actual maximum RF power could be more than would be needed for > an isotrope. > > Andy G4JNT/G8IMR (still lurking) > > > > -----Original Message----- > From: owner-rsgb_lf_group@blacksheep.org > [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of captbrian > Sent: 10 October 2006 03:13 > To: rsgb_lf_group@blacksheep.org > Subject: LF: Re: Re: erp eirp - bluff > > Then why isn't ERP called EDRP ? > > eg EIRP, EMRP, EDRP ......s'obvious innit.? > > > ----- Original Message ----- > From: "James Moritz" > To: > Sent: 09 October 2006 21:56 > Subject: LF: Re: erp ierp - bluff > > > > Dear Bryan, LF Group, > > > > >< snip >> > > > Cheers, Jim Moritz > > 73 de M0BMU > > > > (BTW, it is EIRP, not ierp) > > > > > > > > > > > G3GVB/ Bryan > > > > > "This e-mail is intended for the recipient only. If you are not the > intended recipient you must not use, disclose, distribute, copy, print, > or rely upon this e-mail. If an addressing or transmission error has > misdirected this e-mail, please notify the author by replying to this e-mail." > > "Recipients should note that all e-mail traffic on MOD systems is > subject to monitoring and auditing." > >