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 x1PFwFIj024871 for ; Mon, 25 Feb 2019 16:58:21 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gyIWm-0003Ql-4x for rs_out_1@blacksheep.org; Mon, 25 Feb 2019 15:50:48 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gyIUK-0003QP-7o for rsgb_lf_group@blacksheep.org; Mon, 25 Feb 2019 15:48:16 +0000 Received: from mail-wr1-x436.google.com ([2a00:1450:4864:20::436]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gyIUG-0006Fb-7q for rsgb_lf_group@blacksheep.org; Mon, 25 Feb 2019 15:48:13 +0000 Received: by mail-wr1-x436.google.com with SMTP id o17so10491850wrw.3 for ; Mon, 25 Feb 2019 07:48:11 -0800 (PST) X-DKIM-Result: Domain=gmail.com Result=Good and Known Domain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:reply-to:message-id:to:subject:in-reply-to:references :mime-version:content-transfer-encoding; bh=/xlURw0Ms102NNQ9GEtAB95T4OVNuNBt/RyVWWNaLAw=; b=u+HriAWSHAspV+0X0RskvsmorENA6GaYLpB0ATQlM66Job9e7jPSGSE+epkFXkDXCr UPEWsIlQ3aJHxFyfCoPaHUjRwUJYaeiO9A31RTNwMbXgeORuvsmh3jeOpCrYDN70ZZYk yG7+ACDh1neE2fb1EJ07zoerOGVk3CTql3GjravOKbAoWyBVaIYr7ezEneIl1zdqtGMG Jf6yAYKw9vu5xfq2VP6dbn62IgY27zmeyUQ/AG1pMlgeQ3AtJ1UXqFuxdHcaaM4e9lKb OwLta0DGaCtyAIi+6EhaE3L1NPH1oeGTVw1zVYjACPty8hsjSRtwkN3cuaIPBKHcQxEJ tXmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-transfer-encoding; bh=/xlURw0Ms102NNQ9GEtAB95T4OVNuNBt/RyVWWNaLAw=; b=iMMVqXRrypx0w0DPhGCVrmsL/OkW2SJiQ+0rogztLUaNU6hIVYDD4r/k5dbVog7aqQ zpDqtBxbKJq/z6MVQyySq9tNqE2hbfHgpwyLGXyCk642jEiI9Adej9MgVJmOXe8jU8xt xzWMGPDkfASMRZJQRyyS5k3GPzoOylR+KSm0G5pnXXaATFAjn9yP60x5+DJFb7yWiw1c pOw14K69/0Hpg5yu5sQL0XbxV3907Tse4h6X2sqVHCfgO+z565bBxRQWH47kzd4aJ5k0 ZNhMEOv8v5FFeILgHLzFAfZ9wnJ5oJqJ5hYBrffa/a7fzzPxWO+E+RZ3RqnDNz7aRWg/ e5dg== X-Gm-Message-State: AHQUAubtKTxonfacqcYh22qUbF3k3aFAQTU0A500FwQK3lEyOWJ+QZMk UsHPtfe42Xzru6vp7oX+08UqbXiS X-Google-Smtp-Source: AHgI3IZTuwVGsnZeVEI6UHcMuqOpxG294p/CR+iZdsiyn/5wlUqu7K51jogGrLg900t5NQ1L+usCyA== X-Received: by 2002:a5d:6983:: with SMTP id g3mr13509020wru.286.1551109690726; Mon, 25 Feb 2019 07:48:10 -0800 (PST) Received: from OfficeWin7.lan (82-70-254-222.dsl.in-addr.zen.co.uk. [82.70.254.222]) by smtp.gmail.com with ESMTPSA id h13sm8263020wrs.42.2019.02.25.07.48.09 (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 25 Feb 2019 07:48:10 -0800 (PST) Date: Mon, 25 Feb 2019 15:48:08 +0000 From: Chris Wilson X-Priority: 3 (Normal) Message-ID: <1516612920.20190225154808@gmail.com> To: Rik Strobbe In-Reply-To: <1551107358099.3307@kuleuven.be> References: <043bec62-8144-5ff3-98a6-9f04699f6a4c@no3m.net>,<5C73F86B.8080201@posteo.de> <1551107358099.3307@kuleuven.be> MIME-Version: 1.0 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: Hello Rik, Monday, February 25, 2019, 3:09:18 PM, you wrote: > Hi Stefan, Eric, Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [2a00:1450:4864:20:0:0:0:436 listed in] [list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (dead.fets[at]gmail.com) X-Scan-Signature: 118b9e608370528226a3c3b3aedcdda0 Subject: Re: LF: Class D current spikes Content-Type: text/plain; charset=us-ascii 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.8 required=5.0 tests=PRIORITY_NO_NAME 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 Hello Rik, Monday, February 25, 2019, 3:09:18 PM, you wrote: > 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 >> >> I have a series of scope captures from my W1VD amp showing huge voltage spikes on the FET drains at the end of WSPR and especially OPERA TX sequences. I suspected inductance was the cause. In fact I try not use OPERA at high power as i am pretty sure to kill a FET after a few sessions... Oddly (although I hope msomeone more knowlegeable has the answer), using WSPR from my U3S direct from CLK0 of th Si535a or whatever it is never causes these spikes... Or at least they are well contained. -- Best regards, Chris mailto:dead.fets@gmail.com