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 x1ODQGEp016625 for ; Sun, 24 Feb 2019 14:26:17 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gxtj0-0006MB-O8 for rs_out_1@blacksheep.org; Sun, 24 Feb 2019 13:21:46 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gxtiz-0006M2-Sw for rsgb_lf_group@blacksheep.org; Sun, 24 Feb 2019 13:21:45 +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 1gxtix-0003Bv-9P for rsgb_lf_group@blacksheep.org; Sun, 24 Feb 2019 13:21:44 +0000 X-KULeuven-Envelope-From: rik.strobbe@kuleuven.be X-KULeuven-Scanned: Found to be clean X-KULeuven-ID: E8312120013.A18B0 X-KULeuven-Information: Katholieke Universiteit Leuven Received: from icts-p-smtps-1.cc.kuleuven.be (icts-p-smtps-1e.kulnet.kuleuven.be [134.58.240.33]) by rhcavuit04.kulnet.kuleuven.be (Postfix) with ESMTP id E8312120013 for ; Sun, 24 Feb 2019 14:21:41 +0100 (CET) Received: from ICTS-S-EXMBX23.luna.kuleuven.be (icts-s-exmbx23.luna.kuleuven.be [10.112.11.58]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by icts-p-smtps-1.cc.kuleuven.be (Postfix) with ESMTPS id AFFB240B4 for ; Sun, 24 Feb 2019 14:21:41 +0100 (CET) Received: from ICTS-S-EXMBX27.luna.kuleuven.be (10.112.11.62) by ICTS-S-EXMBX23.luna.kuleuven.be (10.112.11.58) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 24 Feb 2019 14:21:41 +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 14:21:41 +0100 X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Rik Strobbe To: "rsgb_lf_group@blacksheep.org" Thread-Topic: Class D current spikes Thread-Index: AQHUzDqCt8U6/kU7w0aNBM6ZXdfQC6Xu3vTJgAAPLXc= Date: Sun, 24 Feb 2019 13:21:41 +0000 Message-ID: <1551014480338.17397@kuleuven.be> References: <043bec62-8144-5ff3-98a6-9f04699f6a4c@no3m.net>,<1551011916482.41235@kuleuven.be> In-Reply-To: <1551011916482.41235@kuleuven.be> 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: Addendum: 3 microseconds is for 472kHz, for a 136kHz PA it should be 10 microseconds. 73, Rik ON7YD - OR7T Van: owner-rsgb_lf_group@blacksheep.org namens Rik Strobbe Verzonden: zondag 24 februari 2019 13 [...] 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: 6be9408bcc63ba5aab6f1e66e2d5b7ce Subject: 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 x1ODQGEp016625 Addendum: 3 microseconds is for 472kHz, for a 136kHz PA it should be 10 microseconds. 73, Rik ON7YD - OR7T ________________________________________ Van: owner-rsgb_lf_group@blacksheep.org namens Rik Strobbe Verzonden: zondag 24 februari 2019 13:38 Aan: rsgb_lf_group@blacksheep.org Onderwerp: LF: Re: Class D current spikes Hello Eric, I had a similar problem: at "key up" one of the driver outputs will remain low and the other high. As a result the gate of one of the power MOSFETs is kept high for a time much longer that half a period. During that time this MOSFET is in ON-state (conducting) and thus drawing excessive current. I solved the problem by adding monostable multivibrators that disable the MOSFET driver when one of the driver outputs stays high longer than 3 microseconds. Assuming that you refer to the W1VD "500W RF-deck" (http://www.w1vd.com/137-500-500WTX.pdf): it is actually a voltage mode design (thus having current spikes). A current mode class D amp has a choke between the supply voltgae and the output transformer center tap, limiting the current (and causing voltage spikes). 73, Rik ON7YD - OR7T ________________________________________ Van: owner-rsgb_lf_group@blacksheep.org namens Eric NO3M Verzonden: zondag 24 februari 2019 13:08 Aan: rsgb_lf_group@blacksheep.org Onderwerp: LF: Class D current spikes I recently got a current mode (outp xfmr center tap not bypassed) Class D amp going on 136khz, basically modeled after the W1VD / G0MRF circuits. FETs are 59N25s, 4820p / 10ohm snubbers, 5t+5t / 21t 3C90 42mm output xfmr, 62uH (25t T157-26) choke. Output xfmr depends on the power supply in use: 30V linear supply: 5t+5t / 21t 3C90 42mm, 300W out 48V switching supply: 5t + 5t / 16t 3C90 51mm, 500W out I am also using the G0MRF keying circuit, ie. P-channel MOSFET (IRF9540) in the driver (MCP1404) supply line. If the driver is left active (key down), the beginning and end of the input RF envelope produces a "clicking" noise... assume this is from current spikes being developed and sunk by the FET body diodes? If the driver is keyed with input RF already applied, thereby interrupting the drive to the FETs, there is no such behavior. The keying is shaped, resulting in a ramping of the driver supply voltage and resultant gate waveforms to the FETs. These current spikes do not bother my 30V linear power supply, however, when I attempt to use a 48V switching supply (rated at 17.7A), it seems to be OK with the current spike generated on the beginning of the RF envelope, but not the spike at the end of the envelope and goes into fault mode. If the driver is keyed with continuous RF applied, it's happy and does not trip out. But keying the driver doesn't seem practical for digi modes without some exotic circuitry or engaging computer generated signaling to key down *after* RF drive is applied and key up *before* RF drive is removed.... again, this phenomena only happens at the beginning and end of the input RF envelope. Is there way to mitigate these current spikes, especially the one generated when RF is removed? 73 Eric NO3M