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 x1PFYua2024721 for ; Mon, 25 Feb 2019 16:35:03 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gyIC4-0003Gs-Gh for rs_out_1@blacksheep.org; Mon, 25 Feb 2019 15:29:24 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gyIBx-0003Gj-0F for rsgb_lf_group@blacksheep.org; Mon, 25 Feb 2019 15:29:17 +0000 Received: from mout02.posteo.de ([185.67.36.66]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gyIBv-0006D1-B5 for rsgb_lf_group@blacksheep.org; Mon, 25 Feb 2019 15:29:15 +0000 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 873F92400FD for ; Mon, 25 Feb 2019 16:29:14 +0100 (CET) X-DKIM-Result: Domain=posteo.de Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1551108554; bh=xjtXkfe/i6Lv31KJPoDgRRSAujyLSS1Fg2jJ6hyWzgk=; h=Date:From:To:Subject:From; b=OaTj/NkhXL1666YdxCNW58+d/9rvdc//2cM8WO9SGGAeRexg+Aam9+LxVmlBZRDGk ifR7rHIcdlvvPFtghd9whHt8xbgwIlug+PAg7WKrS8rMWbeAe+DdACt9jr/u/Xdwuy dnboArEz/GYD9qTdJg++yzZvU4eLdhxQdm/fe8QbyHhxOjJax65VwmurQvKCFdkPTm jFjp8ZYay4+6IiANSIjWhR5dcAKrNJhBZpt5X8er7xcFSYFrUsqwd4BJ4bGdzkHxGq a5QcNpPXjnkdaLYE4UCR2VCWllrszcF8ae3a5rlg1ZK+UUKoKhJuxghdCVFcsMF81a TdUBgjm8ZsFIQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 447Qpd6rFWz9rxP for ; Mon, 25 Feb 2019 16:29:13 +0100 (CET) Message-ID: <5C7409C9.9000803@posteo.de> Date: Mon, 25 Feb 2019 16:29:13 +0100 From: DK7FC User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <043bec62-8144-5ff3-98a6-9f04699f6a4c@no3m.net>,<5C73F86B.8080201@posteo.de> <1551107358099.3307@kuleuven.be> <5C740794.1040902@posteo.de> In-Reply-To: <5C740794.1040902@posteo.de> 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: PS: In a current mode call-D PA i would rather expect an overvoltage issue rather than an overcurrent issue (at the power supply). Maybe the sudden stop of the current consumption (100% to 0%) is to f [...] 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 [185.67.36.66 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record X-Scan-Signature: 118b9e608370528226a3c3b3aedcdda0 Subject: Re: LF: Class D current spikes Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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.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 PS: In a current mode call-D PA i would rather expect an overvoltage issue rather than an overcurrent issue (at the power supply). Maybe the sudden stop of the current consumption (100% to 0%) is to fast for the regulator of the SMPS, so it does not regulate the duty cycle fast enough and produces its own overvoltage. Or, a voltage peak across the terminals due to the high di/dt across the L of the cable between SMPS and PA. Such problems could be minimised easily by some additional C near the SMPS... 73, Stefan Am 25.02.2019 16:19, schrieb DK7FC: > ...yes, might. > But also it might not, especially when the critical event happens only > once per minute. > > 73, Stefan > > Am 25.02.2019 16:09, schrieb Rik Strobbe: >> Hi Stefan, Eric, >> >> this might solve the PS tripping problem, but on the other hand it >> might also provide the MOSFET the draincurrent it needs to die ;-) >> >> 73, Rik ON7YD - OR7T >> >> ________________________________________ >> Van: >> owner-rsgb_lf_group@blacksheep.org >> namens DK7FC >> Verzonden: maandag 25 februari 2019 15:15 >> Aan: rsgb_lf_group@blacksheep.org >> Onderwerp: Re: LF: Class D current spikes >> >> Hi Eric, >> >> What happens to the supply behaviour if you just switch some Cs parallel >> to the output, say 4x 4700 uF (low ESR) rated at 63V ? >> Maybe it solves the problem of the supply going into fault mode, >> although it is no the perfect solution. >> >> 73, Stefan >> >> Am 24.02.2019 13:08, schrieb Eric NO3M: >>> 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 >>> >>> >>