Return-Path: Received: from rly-dc01.mx.aol.com (rly-dc01.mail.aol.com [172.19.136.30]) by air-dc08.mail.aol.com (v123.4) with ESMTP id MAILINDC082-b004a0d99f43cc; Fri, 15 May 2009 12:36:28 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-dc01.mx.aol.com (v123.4) with ESMTP id MAILRELAYINDC014-b004a0d99f43cc; Fri, 15 May 2009 12:36:05 -0400 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1M50NZ-0007il-J6 for rs_out_1@blacksheep.org; Fri, 15 May 2009 17:35:25 +0100 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1M50NZ-0007ic-2h for rsgb_lf_group@blacksheep.org; Fri, 15 May 2009 17:35:25 +0100 Received: from cavuit02.kulnet.kuleuven.be ([134.58.240.44]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1M50NX-0008O5-Mx for rsgb_lf_group@blacksheep.org; Fri, 15 May 2009 17:35:24 +0100 Received: from smtps02.kuleuven.be (smtpshost02.kulnet.kuleuven.be [134.58.240.75]) by cavuit02.kulnet.kuleuven.be (Postfix) with ESMTP id D24B651C004 for ; Fri, 15 May 2009 18:35:14 +0200 (CEST) Received: from webmail2.cc.kuleuven.ac.be (webmail2.cc.kuleuven.ac.be [134.58.242.4]) by smtps02.kuleuven.be (Postfix) with ESMTP id 97763F3863 for ; Fri, 15 May 2009 18:35:14 +0200 (CEST) Received: by webmail2.cc.kuleuven.ac.be (Postfix, from userid 65534) id E6E335B9F; Fri, 15 May 2009 18:35:14 +0200 (CEST) Received: from 131.38-201-80.adsl-dyn.isp.belgacom.be (131.38-201-80.adsl-dyn.isp.belgacom.be [80.201.38.131]) by webmail4.kuleuven.be (Horde MIME library) with HTTP; Fri, 15 May 2009 18:35:14 +0200 Message-ID: <20090515183514.mt168ada0ug4k4c4@webmail4.kuleuven.be> Date: Fri, 15 May 2009 18:35:14 +0200 X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Rik Strobbe To: rsgb_lf_group@blacksheep.org References: <4A0D91E3.9040602@btconnect.com> In-Reply-To: <4A0D91E3.9040602@btconnect.com> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Internet Messaging Program (IMP) H3 (4.1.2) X-Originating-IP: 80.201.38.131 X-KULeuven-Information: Katholieke Universiteit Leuven X-KULeuven-Scanned: Found to be clean X-KULeuven-Envelope-From: rik.strobbe@fys.kuleuven.be X-Karma: unknown: X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: Re: LF: Aerial current Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" 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-Mailer: Unknown (No Version) Hello Richard, is you antenna matched to 50 Ohm ? If you just bring it to resonance (loading coild adjustment) the =20 antenna impedance can be anything between 10 and 100 Ohm. And some 10m's length of coax can cause some odd impedance =20 transformations, even on 500kHz. As I started on 500 I just tuned the loading coil to bring the antenna =20 to resonance at 502.5kHz. At the antenna feeding point I measured 40 =20 Ohm what comes down to a SWR of 1.25. Fair enough I thought, my PA =20 would handle such an SWR without a problem. But when I fired the PA I =20 got less output current than expected and far more input power than =20 expected, so the PA seemed not so happy. Next I measured the impedance at the TX end of the coax (40m long) and =20 found out that resonance was at 490kHz instead of 502.5kHz. I went back outside to measure the impedance at the antenna feeding =20 point: still 40 Ohm at 502.5kHz resonance. It is common knowledge: if the antenna impedance is different from 50 =20 Ohm then the coax act as an impedance transformer. But I did not =20 expect such significant effect. 73, Rik ON7YD - OR7T Quoting Richard Newstead : > After my success in getting more current into the aerial yesterday I > decided to measure the RF current in the link (link coupled ATU) with a > proper RF ammeter. I was somewhat surprised that the current pinned my > 1 Amp RF meter. How can that be? I can think of some possible reasons: > > 1) The meter is wrong (it must be nearly 70 years old) > 2) The impedance is not 50 Ohms which is odd because I assume the TX is > designed to have a 50 Ohm output and I carefully adjusted the link for > maximum power transfer last night). > 3) The transmitter is giving out far more power than expected (seems > unlikely). > > Any ideas? > > Incidentally, am I best to measure current in the link or in the aerail wi= re? > > 73 > > Richard > > PS - beacon on again 501.6kHz.