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 x1OCGGIB016253 for ; Sun, 24 Feb 2019 13:16:22 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gxsbD-00066U-AG for rs_out_1@blacksheep.org; Sun, 24 Feb 2019 12:09:39 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gxsZp-00066H-Pc for rsgb_lf_group@blacksheep.org; Sun, 24 Feb 2019 12:08:13 +0000 Received: from 576e.8172.0000.0000.0210.4001.0d0f.7062.ip6.static.sl-reverse.com ([2607:f0d0:1004:120::2718:e675] helo=mx1.lylix.net) by relay1.thorcom.net with esmtp (Exim 4.91) (envelope-from ) id 1gxsZl-00032O-Ih for rsgb_lf_group@blacksheep.org; Sun, 24 Feb 2019 12:08:10 +0000 Received: from no3m.local (dynamic-acs-24-144-206-160.zoominternet.net [24.144.206.160]) (Authenticated sender: eric@lylix.net) by mx1.lylix.net (Postfix) with ESMTPSA id 40C4E1A408BE for ; Sun, 24 Feb 2019 07:08:02 -0500 (EST) To: rsgb_lf_group@blacksheep.org From: Eric NO3M Message-ID: <043bec62-8144-5ff3-98a6-9f04699f6a4c@no3m.net> Date: Sun, 24 Feb 2019 07:08:01 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 MIME-Version: 1.0 Content-Language: en-US X-Spam-Score: 2.0 (++) 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: 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 [...] Content analysis details: (2.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_PASS SPF: sender matches SPF record 2.0 KHOP_DYNAMIC Relay looks like a dynamic address X-Scan-Signature: 739d4fb39bd02fc5a2de5437a39bb056 Subject: LF: Class D current spikes Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 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