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 x1OERIFl016929 for ; Sun, 24 Feb 2019 15:27:19 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gxugZ-0006sN-4b for rs_out_1@blacksheep.org; Sun, 24 Feb 2019 14:23:19 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gxugX-0006sE-2e for rsgb_lf_group@blacksheep.org; Sun, 24 Feb 2019 14:23:17 +0000 Received: from rhcavuit04.kulnet.kuleuven.be ([2a02:2c40:0:c0::25:137]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gxugU-0003Mq-LD for rsgb_lf_group@blacksheep.org; Sun, 24 Feb 2019 14:23:15 +0000 X-KULeuven-Envelope-From: rik.strobbe@kuleuven.be X-KULeuven-Scanned: Found to be clean X-KULeuven-ID: BF76E12000A.A41E8 X-KULeuven-Information: Katholieke Universiteit Leuven Received: from icts-p-smtps-2.cc.kuleuven.be (icts-p-smtps-2e.kulnet.kuleuven.be [134.58.240.34]) by rhcavuit04.kulnet.kuleuven.be (Postfix) with ESMTP id BF76E12000A for ; Sun, 24 Feb 2019 15:23:12 +0100 (CET) Received: from ICTS-S-EXMBX18.luna.kuleuven.be (icts-s-exmbx18.luna.kuleuven.be [10.112.11.49]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by icts-p-smtps-2.cc.kuleuven.be (Postfix) with ESMTPS id B3D6520006 for ; Sun, 24 Feb 2019 15:23:12 +0100 (CET) Received: from ICTS-S-EXMBX26.luna.kuleuven.be (10.112.11.61) by ICTS-S-EXMBX18.luna.kuleuven.be (10.112.11.49) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 24 Feb 2019 15:23:12 +0100 Received: from ICTS-S-EXMBX27.luna.kuleuven.be (10.112.11.62) by ICTS-S-EXMBX26.luna.kuleuven.be (10.112.11.61) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 24 Feb 2019 15:23:12 +0100 Received: from ICTS-S-EXMBX27.luna.kuleuven.be ([fe80::291a:cc4f:6953:698a]) by ICTS-S-EXMBX27.luna.kuleuven.be ([fe80::291a:cc4f:6953:698a%25]) with mapi id 15.00.1395.000; Sun, 24 Feb 2019 15:23:12 +0100 X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Rik Strobbe To: "rsgb_lf_group@blacksheep.org" Thread-Topic: LF: Re: Class D current spikes Thread-Index: AQHUzDqCt8U6/kU7w0aNBM6ZXdfQC6Xu3vTJgAAPLXf///KdgIAAA4qAgAAGCgCAABHD2A== Date: Sun, 24 Feb 2019 14:23:12 +0000 Message-ID: <1551018171015.45843@kuleuven.be> References: <043bec62-8144-5ff3-98a6-9f04699f6a4c@no3m.net> <1551011916482.41235@kuleuven.be> <1551014480338.17397@kuleuven.be> ,<27248150-3565-aeb8-9b66-53a9089fd4ab@n1bug.com> In-Reply-To: <27248150-3565-aeb8-9b66-53a9089fd4ab@n1bug.com> Accept-Language: nl-BE, en-GB, en-US Content-Language: nl-BE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.112.50.1] MIME-Version: 1.0 X-Spam-Score: -2.3 (--) 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 the administrator of that system for details. Content preview: Hello Paul, Eric, Andy, AC coupling with a large C will not solve the problem. At "key up" one of the driver outputs will remain high thus the gate of theFET connected to that output will remain high (and the FET conducting) [...] Content analysis details: (-2.3 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, medium trust [2a02:2c40:0:c0:0:0:25:137 listed in] [list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record X-Scan-Signature: 3b8620872b19e25fb6f4dfaf1256edc3 Subject: Re: LF: Re: Class D current spikes Content-Type: text/plain; charset="iso-8859-1" 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=TO_ADDRESS_EQ_REAL 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by klubnl.pl id x1OERIFl016929 Hello Paul, Eric, Andy, AC coupling with a large C will not solve the problem. At "key up" one of the driver outputs will remain high thus the gate of theFET connected to that output will remain high (and the FET conducting) during a time depending on RC constant of the driver / gate network. For 0.22uF and 4.7kOhm the RC constant is 1 millisecond. So for a driver running on 12V iit will take about that time for the gate voltage to drop below the treshold. During that 1ms the FET is more or less shortcircuiting the powersupply. One of them will die sooner ot later ;-) 73, Rik ON7YD - OR7T ________________________________________ Van: owner-rsgb_lf_group@blacksheep.org namens N1BUG Verzonden: zondag 24 februari 2019 15:03 Aan: rsgb_lf_group@blacksheep.org Onderwerp: Re: LF: Re: Class D current spikes I will be watching this discussion closely. Mine is a W1VD kilowatt deck: http://w1vd.com/137-500-KWRev3.0.pdf It has blown FETs several times. The problem always occurs at the end of the RF envelope. To further confuse this issue, I have lost only one FET while running with my U3S exciter in hundreds of hours of operation. I have lost many FETs when driving it with HF transceiver and down converter. I have also lost FETs driving it with a phasing exciter. It seems using it with either of the latter exciters almost guarantees one or more dead FETs within a few minutes. I was running at about 300 watts output during all of these failures. 73, Paul On 2/24/19 8:42 AM, Eric NO3M wrote: > The driver and FET gates in mine are AC coupled (0.22u, SB560 > schottky shunt, 10 ohm series, 4.7k shunt) and the problem still > exists. Apparently same thing Paul N1BUG was having problems with. > The spike on the end of the RF envelope is what seems most ominous > and results in my 48v switcher going into fault mode.