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 x6PC0SNc016313 for ; Thu, 25 Jul 2019 14:00:29 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1hqc9V-0007bc-N0 for rs_out_1@blacksheep.org; Thu, 25 Jul 2019 12:43:17 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1hqc9H-0007bT-Hv for rsgb_lf_group@blacksheep.org; Thu, 25 Jul 2019 12:43:03 +0100 Received: from mail-wr1-x431.google.com ([2a00:1450:4864:20::431]) by relay1.thorcom.net with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hqc9C-00066D-RM for rsgb_lf_group@blacksheep.org; Thu, 25 Jul 2019 12:43:02 +0100 Received: by mail-wr1-x431.google.com with SMTP id p17so50393474wrf.11 for ; Thu, 25 Jul 2019 04:42:56 -0700 (PDT) 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:message-id:to:subject:in-reply-to:references:mime-version :content-transfer-encoding; bh=RF6YbDquieDY1GFUh9dyPYZTdyZPuBITSIBsnLkPFFk=; b=C0HncPtKRhEdGcN+S2C77dOFzVDkwLkcoMOQQdHDv7pbep2x19EcXqAWJJ5+eGOMWo UN7pWEa/wQoR1fyVIAEunwBTrU4jfaw4JKmXRu3PDWhyuo9yqiNR+OeA1DFGnmcgBMZQ Cif9m7rg7+O68HhOQLz+EWz1Utz/FzoCMrkgIqzYCsZkhv/apgJOBNHM5qUEP+sHdUC6 9ykp88AZNTWPJBz9sQDvLOhWWISQSTqeBvg8AZ3NwplL8Ig9yMZElMNbFk6nL4YwEDkK x4PJk1Bnoje1k7SI0GF4GsK1Vt0BmMbsvbEMr+Swu/uUFR04gs9JW/ELsbipSNTnnx2y jLZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:message-id:to:subject:in-reply-to :references:mime-version:content-transfer-encoding; bh=RF6YbDquieDY1GFUh9dyPYZTdyZPuBITSIBsnLkPFFk=; b=cEYsGVJ8SPOaL+3sbYrfPtRgWEEQOgn6WO1lxeeednptWSHBvtZWjPexdMZtKzM1WU LmPeFgdnaRVY3eIFS+fna3+I7CIvU9BztJioaiYityNWCUROrzJWl5AqzEW0fTEKdu10 gDTMl6nGlC1/fhL+w/GsYAgOKwIQ7PTFWq179gUO7FpszwNNmtU9Hs3akyk2dQuIMkcq ZjdGzLnrI9jPZoxgWX1Du7i7GQDdOkFd289WYpIULsD+x/b2BRR1agwqurS+92OVUhn+ EKrCaVRI/11WNVEIaU+WG60UXRH+MkNLcuFD+cEE4PQOqpy/HFqPO+aTQ7K5U47KTz35 jyFg== X-Gm-Message-State: APjAAAU+B99J2h/yK3NvzKBfNcgoIdu4+LGVrkMTGetXJCzYebXDMUmK 1Fgc8HWHTN2RdzcgoawuaYxfWuJkkpc= X-Google-Smtp-Source: APXvYqwpYzwbqVKUBZDNVP7NDJC0bpbfBUenS3e1XpnaCAsBRL7huMawwBTP3FbpI1o8Z/D+mIBDaw== X-Received: by 2002:a5d:4205:: with SMTP id n5mr86324848wrq.52.1564054976055; Thu, 25 Jul 2019 04:42:56 -0700 (PDT) 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 q10sm52606929wrf.32.2019.07.25.04.42.54 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 25 Jul 2019 04:42:55 -0700 (PDT) Date: Thu, 25 Jul 2019 12:42:53 +0100 From: Chris Wilson X-Priority: 3 (Normal) Message-ID: <1601026811.20190725124253@gmail.com> To: Andy Talbot In-Reply-To: References: <993240756.20190717143805@gmail.com> <5D2F677F.1090208@posteo.de> MIME-Version: 1.0 X-Spam-Score: -0.2 (/) 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 @@CONTACT_ADDRESS@@ for details. Content preview: Hello Andy and Stefan, Thanks for the replies, it's a lot clearer now, I appreciate your time! Wednesday, July 17, 2019, 7:50:39 PM, you wrote: Content analysis details: (-0.2 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:431 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) -0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain X-Scan-Signature: 47a967f57bae6380aac0a0062beb1b4e Subject: Re: LF: DC restoration Content-Type: text/plain; charset=utf-8 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by klubnl.pl id x6PC0SNc016313 Hello Andy and Stefan, Thanks for the replies, it's a lot clearer now, I appreciate your time! Wednesday, July 17, 2019, 7:50:39 PM, you wrote: > I assume we're talking about the series C from driver to gate, then > a high value leakage R from gate to ground, and a reverse biassed diode in parallel with this. > AC coupling without any DC restoration means the MEAN voltage on > the gate is zero.  For LF transmitter uses, where the drive has a > 50% duty cycle (or very close to) this is not too much of an issue > as there will still be a significant positive swing.  So provided > Vdd  / 2 of the driver stage is more than sufficient to fully > turn-on the FET than AC coupling with just a C and leakage R is OK.  > Transformer coupling - allowing galvanic isolation - works very well and that givs true AC drive. > The problem comes in SMPSUs where the duty cycle is not zero.  > Assume a 20% duty cycle and a drive waveform of 0/15V.   The mean > voltage on the gate still has to  0V, so the get this from a 0/15V > wavefomr means a positive excursion of 3/4 * 15V = 12V and a > negative excursion of 3V.  That will still work OK > But an 80% duty cycle is +3V and -12V that certainly won't. > By adding a DC restoration diode, the negative excursion is clamped > to around -0.6V (ish)) and the positive lifted to 14.4V (ish) WHATEVER the duty cycle.    > SO even at 50% the drive amplitude is doubled. > I think earlier IGBJT devices needed a negative voltage to turn off > properly - I doubt that is the case with later ones.   And IGBJTs > don't seem to have been adopted for LF transmitters anyway. > I remember learning about DC restoration when I was quite young and > being shown how TVs (monochrome at that time) worked.   It was a > simple way of getting a constant black level on AC coupled video > amps, by clamping the recovered sync pulses to 0V, then biassing to > get black level, whnere teh video signal have a varying DC > component.   Later designs clamped the back porch at true black > level.  Exactly the same circuit arrangement > Andy > www.g4jnt.com > On Wed, 17 Jul 2019 at 19:26, DK7FC wrote: > Hi Chris, > > Maybe it helps to show a concrete schematic together with your question. > I find reverse diodes quite useless, at least when MOSFETs are used. It > may be a different thing with bipolar transistors... > > 73, Stefan > > Am 17.07.2019 15:38, schrieb Chris Wilson: >> >> Hello  rsgb, >> >>    Some Class D LF / MF amps use a diode to DC restore the waveform >>    after the FET driver chip to the gates. Why do they do this, I am >>    thinking the negative part of the waveform would turn OFF the gate >>    harder, assuming the positive part is adequate to turn the gates ON >>    hard enough? Is there any point in using the modern FET's designed >>    to have a negative rail to turn the gates off hard? Cree do the >>    Wolfspeed ones with this feature. I have also noticed that with amps >>    where the input to the driver is capacitively coupled adding a DC >>    restoration diode makes the waveform pretty much exactly 50 / 50 >>    mark  space,  whereas without one this is not the case. Good idea to >>    use these restoration diodes there? Thanks. >> >>    > > -- Best regards, Chris mailto:dead.fets@gmail.com