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 w3EA4euw012170 for ; Sat, 14 Apr 2018 12:04:43 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1f7HxW-0003un-I4 for rs_out_1@blacksheep.org; Sat, 14 Apr 2018 10:59:02 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1f7HxU-0003ue-Pb for rsgb_lf_group@blacksheep.org; Sat, 14 Apr 2018 10:59:00 +0100 Received: from mail-wr0-x22d.google.com ([2a00:1450:400c:c0c::22d]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1f7HxR-0002TC-1U for rsgb_lf_group@blacksheep.org; Sat, 14 Apr 2018 10:58:59 +0100 Received: by mail-wr0-x22d.google.com with SMTP id u46so13777773wrc.11 for ; Sat, 14 Apr 2018 02:58: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=wUwvuNWkTVE2n0HLiXar0ZCQFwdOXQMualoYIc++8hY=; b=gIwowJf1zye+gASB76GISowOKYZkoECeC0Kl0etZCTKHLhVPwh5mdgw5sP65auG9FA HwlJ9ONrQB8/zuWgCF4Z0uwWDUbmG0VlEPoIgDTBdQ+rw9PX8eT7nvJVOj2rZE+Q2DpB lg9X1VMhqYG6dQR+mzpfEDPTp91UcL6klcOTmwdTbTB64NGmMXElJluBW382Oac9RZg2 3oPfibHKOtXms7i8Cju8hkjWZkOcnJmdQv+smIqaaMNAPmHkVQZFi5GWDboCwNuZcFcY BwhfHf9qqkcUOwMo16AG3bN71wYrpI204heSakpJGVqX3FzQOgKyEr+2TmXZoT/G6hQV 4H1A== 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=wUwvuNWkTVE2n0HLiXar0ZCQFwdOXQMualoYIc++8hY=; b=C+5e25YpGqVaywUh2mhaBUjYMsJtz2swZAVTQMw7ErXgDQZaIBI+DRq/UVeGHLNd4I 3cWrHeRHyZgvjFctfjp5lMxNGlDAlO1f4SSmqbunTGTu2eSXRIQNGnoDiXbPO3ZxW5pO En88EmMq3TDN7oO3IEY/ct9ZIvL2O0im3d80x5IjNWgvt5y7IwUntndG5UvNyb2irre5 vbh3dEr110wUE60VsXrQS0QQNqq9GPPYLY/6oO7s9O2x0TWHBkEbYDLcC48pWSeAIT2g c2l0eF7gZ9iEpvsRvS+vLLuHnKL08yr9DShkgEtTdbvmd1ikIqgyAMkvY89SZoaT2iOZ rrfA== X-Gm-Message-State: ALQs6tDIVFBgIr4uGX6t7LAAZkeUPAHC+Oe4rfGBm260EvBFNK9j4jIz meOspIZE0byOGQOXzbqsaw82TA== X-Google-Smtp-Source: AIpwx48BThvdEXFrybkcTP7X+0kJDXIOEXsetmzIxNMsi5lgdcAiHqcwhlSvtWpHKNyHGR6lbNxxqw== X-Received: by 10.28.19.193 with SMTP id 184mr5416432wmt.158.1523699935120; Sat, 14 Apr 2018 02:58:55 -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 d8sm1640855wrb.72.2018.04.14.02.58.53 (version=TLS1 cipher=AES128-SHA bits=128/128); Sat, 14 Apr 2018 02:58:54 -0700 (PDT) Date: Sat, 14 Apr 2018 10:58:52 +0100 From: Chris Wilson X-Priority: 3 (Normal) Message-ID: <699259072.20180414105852@gmail.com> To: N1BUG In-Reply-To: <0a8d5855-2891-d2e9-42c6-713895e91146@n1bug.com> References: <1UQRRBrZ33.5N62o0UWd72@optiplex980-pc> <1b2b034a-404d-8b95-220c-5568950a1918@n1bug.com> <1523452469895.92892@kuleuven.be> <8c1acac6-e271-6398-2768-481298344387@n1bug.com> <1523457751831.88599@kuleuven.be> <612685899.20180411225537@gmail.com> <968686644.20180411232838@gmail.com> <7950E881690348FB8A48C42DD2735F8D@StevePC> <1UQRSH98Tx.2IrTZ1ue7L6@optiplex980-pc> <7FBAA3A0B6C84158BA005CFF09A5A7EA@DELL4> <4d214d82-a112-84c7-f9ab-c71941f6689a@n1bug.com> <277967114.20180412191941@gmail.com> <8D5E7536EB86447B920A6B0C99E2BA88@gnat> <124C5670D5484E89A084985970CDE55C@gnat> <6DB8451D7F3D3947A5918808A59621EA04F0DC@servigilant.vigilant.local> <0a8d5855-2891-d2e9-42c6-713895e91146@n1bug.com> MIME-Version: 1.0 X-Spam-Score: 0.8 (/) 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 Paul, I just took some photos of one of my spare driver boards that should be detailed enough to copy or peruse usefully. not sure if this type of board is available out there, but I can send you some, or a ready to populate board, or even a populated one! [...] Content analysis details: (0.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (dead.fets[at]gmail.com) 0.1 URIBL_SBL_A Contains URL's A record listed in the Spamhaus SBL blocklist [URIs: n1bug.com] 0.6 URIBL_SBL Contains an URL's NS IP listed in the Spamhaus SBL blocklist [URIs: n1bug.com] 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 24b65a258fa7a3a87cfdaa03bb2f3176 Subject: Re: LF: W1VD amp help - finally some progress! 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 Paul, I just took some photos of one of my spare driver boards that should be detailed enough to copy or peruse usefully. not sure if this type of board is available out there, but I can send you some, or a ready to populate board, or even a populated one! http://www.chriswilson.tv/board.jpg Saturday, April 14, 2018, 1:14:21 AM, you wrote: > Jay, > At least now I've seen some real evidence the gate drive overlap > issue and ringing are related, if not cause and effect. Agreed mine > is slow to turn on as well as off, though arguably being slow to > turn on might not be such a bad thing when one is fighting overlap. > ;-) I think we can safely say now that my driver board simply > doesn't work. See below. > My twisted pairs are now about 1.75 inches of #18. 'Traces' on the > board are built up solder rows that are roughly the cross sectional > area of #12 wire. There are ground buses like this down each long > edge of the board, terminating in solder lugs which ground it to the > chassis when the screws are tightened. Currently only the two near > the IR2110 are grounded in this manner since I stood the board on > end to reduce gate twisted pair length. I think you are right that > the board layout and construction is at fault. Originally pins 2 and > 5 of the IR2110 were grounded through a thick solder trail to the > ground bus on just one edge of the board. Pin 13 was run to the > ground bus on the opposite edge. This evening I modified it so that > pins 2, 5, and 13 are all tied together as close to the chip as > possible and to a 'trace' that goes all the way across the width of > the board to the ground buses along each long edge, taking the > shortest possible route. Doing this made the drain ringing > significantly *worse*! There's not much room left on that board for > adding ground plane pads. > I'm clearing this off the bench as I have some other things that > need to get done. I will have to consider the future of the project > at this point. Thanks for all your help Jay. Thanks to everyone else > who contributed also. Whatever the future holds I have learned a lot > from this endeavor. > Paul > On 04/13/2018 05:57 PM, jrusgrove@comcast.net wrote: >> Paul >> >> So ... we're still stuck at solving the gate drive overlap issue. Your's seems to be slow to turn on >> and to turn off. >> >> Think I questioned back a while ago the driver circuit board 'trace' widths. Since you're using perf >> board I wonder if there are long runs using small gauge wires for the +V and ground connections. If >> you look at my driver board, the top (component side) is a complete copper ground plane ... which >> makes for a very low impedance ground. Screws through the four mounting holes makes an excellent >> connection between the board ground plane and the amplifier chassis. Perhaps you can come close to >> replicating this with pieces of copper flashing on the bottom of your perf board. The IR2110 is >> charging and discharging a realtively high gate capacitance ... so if the IR2110 connections to the >> + and - 'rails' and ground aren't reasonably stout the charging and discharging process could be >> slowed ... maybe enough to cause the problem. For the record, I used #20 for the twisted pairs ... >> but the ground connection also exists through the chassis. >> >> Jay W1VD >> >> >> ----- Original Message ----- >> From: "N1BUG" >> To: >> Sent: Friday, April 13, 2018 1:09 PM >> Subject: Re: LF: W1VD amp help - finally some progress! >> >> >>> Today I verified board connections again, including power to the >>> driver IC (tnx Luis). With the scope I checked +5v and +12v power at >>> IC pins while operating to be sure it is clean. All looked OK. >>> >>> I replaced the timing capacitors with recommended ones (tnx Jay). No >>> change. >>> >>> I replaced resistors in the timing circuit with closely matched ones >>> of a different type or at least different manufacturer. No change. >>> >>> I added bypass capacitors at all +5v and +12v pins on the ICs. No >>> change. >>> >>> I replaced the 10 ohm resistor / diode on each gate lead with 20 ohm >>> / diode. Finally some change! First peak of the ringing is down from >>> 62V to 45V. This is with 12.5V drain supply. Current consumption and >>> power output are down about 5% but efficiency remains the same as >>> before. >>> >>> Looking very carefully at my scope patterns and the one Jay provided >>> a few days ago, I still believe my gate voltage drops much more >>> slowly than his. I don't know why. If my gate voltage would decay as >>> fast as Jay's, I think the FETs would not cross conduct. >>> >>> I don't know what to do next. Is there any way I can speed up the >>> gate turn off? Can it be the 1N4148 diodes? Mine are of unknown age >>> from a large batch I got quite some years ago. >>> >>> Paul >>> -- Best regards, Chris mailto:dead.fets@gmail.com