Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Fri, 24 Jan 2020 07:55:38 -0800 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 00OFhA2A016203; Fri, 24 Jan 2020 10:45:56 -0500 Received: from outgoing-exchange-5.mit.edu (OUTGOING-EXCHANGE-5.MIT.EDU [18.9.28.59]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 00OFh8ml016199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 24 Jan 2020 10:43:08 -0500 Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 00OFjoDN013264 for ; Fri, 24 Jan 2020 10:45:51 -0500 Received: from oc11expo7.exchange.mit.edu (18.9.4.12) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Fri, 24 Jan 2020 10:40:25 -0500 Received: from oc11exhyb2.exchange.mit.edu (18.9.1.98) by oc11expo7.exchange.mit.edu (18.9.4.12) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Fri, 24 Jan 2020 10:42:55 -0500 Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.109) by oc11exhyb2.exchange.mit.edu (18.9.1.98) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Fri, 24 Jan 2020 10:42:55 -0500 Received: from SN2PR01CA0055.prod.exchangelabs.com (2603:10b6:800::23) by MN2PR01MB5775.prod.exchangelabs.com (2603:10b6:208:17a::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.20; Fri, 24 Jan 2020 15:42:54 +0000 Received: from DM3NAM03FT053.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e49::209) by SN2PR01CA0055.outlook.office365.com (2603:10b6:800::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.20 via Frontend Transport; Fri, 24 Jan 2020 15:42:54 +0000 Received: from mail-ot1-f53.google.com (209.85.210.53) by DM3NAM03FT053.mail.protection.outlook.com (10.152.83.181) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.18 via Frontend Transport; Fri, 24 Jan 2020 15:42:53 +0000 Received: by mail-ot1-f53.google.com with SMTP id 66so1981760otd.9 for ; Fri, 24 Jan 2020 07:42:53 -0800 (PST) Received: by 2002:a05:6830:20d4:0:0:0:0 with HTTP; Fri, 24 Jan 2020 07:42:51 -0800 (PST) From: Jason White To: Microcontroller discussion list - Public. CC: ApptechNZ Sender: "piclist-bounces@mit.edu" Date: Fri, 24 Jan 2020 07:42:51 -0800 Subject: Re: [EE] H-Bridge supply voltage spike only in "reverse" (not forward) Thread-Topic: [EE] H-Bridge supply voltage spike only in "reverse" (not forward) Thread-Index: AdXSzrk/UCwt2hppTb+XQb6/+tcoMw== Message-ID: References: List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of gmail.com designates 209.85.210.53 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.210.53; helo=mail-ot1-f53.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ovMzd5WPW70LyNxYwG3vqCzwlvyqHmeIgqfP84FetJQ=; b=RGw2Reha27lqmjcAuqCR8EOjjL04MmSNvnllTxUZRWtL2JZFx9QAG5nkiAhfBEL5Fp jBL3I1X65fDCelJVnQLQnQuwo+1JTjbz56pVi1Eidic9V9A0yTFEG202ytcZyJD1hR6E a3C1q86iPysCWAdGNmFc97Lna2vUskPV8esoEyJ3QOpjXAHEk1AJS9hoT8d4m+nUP9yr RUCZK6sC6SC0ODHkYFFqs348UP5O01Z/MTq+eEQLamFEtvJHXKaxaNCnSlx+DITxNfn3 HimDK1uWatdDwcM59KMBUbfijwXDt2IA7CIwj4XaKAlolX3p8PtHXWlUDuElisjYskNs B5aw== authentication-results: spf=pass (sender IP is 209.85.210.53) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=gmail.com;mit.edu; dmarc=pass action=none header.from=gmail.com;compauth=pass reason=100 errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-received: by 2002:a05:6830:1db3:: with SMTP id z19mr3242339oti.292.1579880572799; Fri, 24 Jan 2020 07:42:52 -0800 (PST) x-topics: [EE] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 The pwm alternates between "forward"/"backwards" and "braking". The lower two fets are supposed to be conducting during the off period. Is it correct to assume that the lower two fets being on should prevent dumping into the supply rail? If I get a chance I'll try bypassing D1 and S1. No internal diode that I know off. The problem follows the H-bridge, reversing motor leads has no effect. Also of note is the ground Of the waveforms is the bottom side of the bridge shunt resistor. On Thursday, January 23, 2020, RussellMc wrote: > 1. Given the lack of supply capacitor, the question MAY be "Why doesn't t= he > motor pump up the supply on motor overrun when the PWM is off ?" > > The MOSFET body diodes allow regeneration into the bus. > Voltage magnitude does not equal power - so a voltage similar to or above > that seen during bridge-on does not equal that during bridge-off. > > Do D1 and S1 play any role? > I assume that D1 is intended to prevent regenerated energy back feeding t= he > supply (in some cases magic smoke can happen (ask me how I know :-) )). > BUT what then should regenerated energy do? > > 2. Can you short S1 temporarily (as it is an overvoltage protector). > While it's not obvious why it would work in one motor direction and not t= he > other, what it DOES do is somewhat unknown. > > 3. Will the supply tolerate shorting D1? > > 4. I wondered if the motor may have an inbuilt parallel 'circulation' dio= de > - but, if so, it would get hardish to drive it backwards :-). > > Russell > > > > On Fri, 24 Jan 2020 at 08:09, Jason White < > whitewaterssoftwareinfo@gmail.com> > wrote: > > > Hello everyone, > > > > I am encountering the following. The supply voltage line to my > > H-Bridge is rising only when the H-Bridge is running a motor in > > "reverse." In forward the supply voltage is unaffected. > > > > Intuitively I am having trouble understanding why this should be. I > > lack a decoupling capacitor on the supply line, but do have a zener. > > > > I have attached a schematic of the circuit. > > > > I will send the forward and reverse waveforms in two follow up emails > > to avoid hitting the file size attachment limits.The waveforms will > > show supply voltage and voltage across the H-Bridge. > > > > -- > > Jason White > > -- > > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > > View/change your membership options at > > http://mailman.mit.edu/mailman/listinfo/piclist > > > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=20 Jason White --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .