Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id wB1Gllxj004870 for ; Sat, 1 Dec 2018 17:47:49 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gT8NT-0006Vp-BX for rs_out_1@blacksheep.org; Sat, 01 Dec 2018 16:44:23 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gT8NS-0006Ve-UN for rsgb_lf_group@blacksheep.org; Sat, 01 Dec 2018 16:44:22 +0000 Received: from smtp-out-3.talktalk.net ([62.24.135.67]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91_59-0488984) (envelope-from ) id 1gT8NQ-0007CK-Q3 for rsgb_lf_group@blacksheep.org; Sat, 01 Dec 2018 16:44:21 +0000 Received: from mal ([88.104.1.72]) by smtp.talktalk.net with SMTP id T8NQgWLvDAGVrT8NQgoV7w; Sat, 01 Dec 2018 16:44:20 +0000 X-DKIM-Result: Domain=talktalk.net Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=talktalk.net; s=cmr1711; t=1543682660; bh=H6r5ab3L29V/vNXpKGqvQvwMBy1SMghyVRMDpDQPxDk=; h=From:To:References:In-Reply-To:Subject:Date; b=QJ3Jnmw45xWdWEeAXTy0PUi7Fne8QupXM9aE03HaxkcjYDEHgIfuUYjgHY8mdk39I EGHqUxoBd20VMCyXVsfA2fApTiCvgY2FCCagcx1po2SW6ewZlxBwqMvjJF7VrDPU7k a738NWN4M+FEh1YyAUkavOrONz6WcOcLayh3szzI= X-Originating-IP: [88.104.1.72] X-Spam: 0 X-OAuthority: v=2.3 cv=DtN4Bl3+ c=1 sm=1 tr=0 a=oLFlnT8c2Bb0h2QgbgxInQ==:117 a=oLFlnT8c2Bb0h2QgbgxInQ==:17 a=IkcTkHD0fZMA:10 a=F3M5lZpKAAAA:8 a=wV9FcBFsAAAA:8 a=51i0XUUpjgvynjf00nAA:9 a=q9BBUQHSMI5bUgOe:21 a=mWiqcGfSC9C0W2KO:21 a=QEXdDO2ut3YA:10 a=slCku8JSH3TyizEDQ3pD:22 a=S9tSBiJD-_FMqjcyfT7e:22 Message-ID: From: To: References: <2133457080.64533.1543584595217@mail2.virginmedia.com> <27270b29-dde1-1207-1158-becc1e4de123@n1bug.com> <1382885588.67051.1543589445229@mail2.virginmedia.com> <530677a9-52b1-0280-128f-4afc58f94536@n1bug.com> <911f1e76-a994-c5d2-ef25-c4f7fde7d46f@n1bug.com> In-Reply-To: <911f1e76-a994-c5d2-ef25-c4f7fde7d46f@n1bug.com> Date: Sat, 1 Dec 2018 16:44:19 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3528.331 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331 X-CMAE-Envelope: MS4wfCylWQIujKifuDhOGHGV5pS73N3WHeGk6hjrf4SRLjU01jje6CKzMHx244MUoA0v/ZCxjA7hUi3cVdYl+dM0qc95aJBdkEQW1B969tg7dYCl+1Z6brfe 18lHmwiMDxiJPFuuhMK5jBxIy6R8d8UPIo0gLDnei4sxwPX/dKqmmjen X-Spam-Score: 0.2 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Paul Use the DECCA 5501 bridge cct and you will not have a problem, no ringing, singing or dancing. 73 gl de mal/g3kev Content analysis details: (0.2 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [62.24.135.67 listed in list.dnswl.org] 0.2 STOX_REPLY_TYPE No description available. -0.0 SPF_PASS SPF: sender matches SPF record 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 195b836cb7437e99aa05107459888659 Subject: Re: [Lowfer] LF: Re: FET change, hmmm Content-Type: text/plain; format=flowed; charset="utf-8"; 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.4 required=5.0 tests=MISSING_OUTLOOK_NAME, NO_REAL_NAME 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 Paul Use the DECCA 5501 bridge cct and you will not have a problem, no ringing, singing or dancing. 73 gl de mal/g3kev -----Original Message----- From: N1BUG Sent: Friday, November 30, 2018 8:50 PM To: rsgb_lf_group@blacksheep.org Subject: Re: [Lowfer] LF: Re: FET change, hmmm All I know is this amp had very little drain ringing and worked well with FQA34N20 FETs but it is not happy with FQA32N20. I slowly increased drain voltage but at 200W out (of a kilowatt deck), there were obvious issues related to the ringing. I've gone back to my old faithful 200W output Class E amp for now. I am running WSPR-2 33% 137.437. Paul On 11/30/18 3:25 PM, Andy Talbot wrote: > Cross conduction spikes can also be dealt with by inserting a bit of > inductance between top and bottom FETs of a totem pole, or in each leg of > a > push-pull pair. As done in the old Decca transmitters, and I cribbed for > my 700 Watt 137 design. > The inductor absorbs the short spike and returns the energy via clamp > diodes to the supply > See http://www.g4jnt.com/137tx.pdf > > A lot simpler than worrying about generating a special drive waveform with > gaps > > Andy > www.g4jnt.com > > > > On Fri, 30 Nov 2018 at 20:19, Hans-Albrecht Haffa wrote: > >> Dear OMs, dear Paul, >> >> To prevend current spikes by cross conduction of both fets it is necesary >> to use a gate drive circuit with dead time, as used in power supplies. >> But >> in this case there is a no current flow time in both transistors, what >> may >> cause spikes in the drain circuit. Damping of oscillations in the drain >> circuit may also reached by quiescent current, not used for class D PAs. >> To >> load the spikes to the load is not possible in an LW-PA, like in an >> flyback-transformer of an switch mode power supply, as the load is an >> LP-Filter that filters by reflections of the applied voltage.