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 x1ODdHTT016704 for ; Sun, 24 Feb 2019 14:39:18 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gxtwZ-0006XN-GQ for rs_out_1@blacksheep.org; Sun, 24 Feb 2019 13:35:47 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gxtwZ-0006XE-7I for rsgb_lf_group@blacksheep.org; Sun, 24 Feb 2019 13:35:47 +0000 Received: from mx1.lylix.net ([74.86.36.27]) by relay1.thorcom.net with esmtp (Exim 4.91) (envelope-from ) id 1gxtwW-0003FB-Pt for rsgb_lf_group@blacksheep.org; Sun, 24 Feb 2019 13:35:46 +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 A762B1A40CB1 for ; Sun, 24 Feb 2019 08:35:39 -0500 (EST) To: rsgb_lf_group@blacksheep.org References: <043bec62-8144-5ff3-98a6-9f04699f6a4c@no3m.net> <1551011916482.41235@kuleuven.be> From: Eric NO3M Message-ID: Date: Sun, 24 Feb 2019 08:35:38 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 MIME-Version: 1.0 In-Reply-To: <1551011916482.41235@kuleuven.be> Content-Language: en-US X-Spam-Score: -0.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: Rik Thanks for the reply.  This particular build is current mode (choke off center tap)... so I guess I'm dealing with voltage spikes.  I didn't notice voltage spikes while monitoring the envelopes when [...] Content analysis details: (-0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_PASS SPF: sender matches SPF record X-Scan-Signature: 0a4643e586472c13187d293ec5d096c2 Subject: Re: LF: Re: 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 Rik Thanks for the reply.  This particular build is current mode (choke off center tap)... so I guess I'm dealing with voltage spikes.  I didn't notice voltage spikes while monitoring the envelopes when sending dits from the exciter, but may not have had the scope adjusted to best visualize them. The driver outputs are AC coupled to the FETs using a 0.22u coupling cap, shunt schottky (SB560), series 10 ohm, and shunt 4.7k.  Should the same behavior with extended ON time be present? On 2/24/19 7:38 AM, Rik Strobbe wrote: > 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 > >