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; Tue, 21 Apr 2020 07:11:04 -0700 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 03LE0dqA013318; Tue, 21 Apr 2020 10:01:13 -0400 Received: from outgoing-exchange-1.mit.edu (OUTGOING-EXCHANGE-1.MIT.EDU [18.9.28.15]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 03LE0cMO013315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 21 Apr 2020 10:00:38 -0400 Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 03LE0GhW027458 for ; Tue, 21 Apr 2020 10:00:24 -0400 Received: from oc11exhyb7.exchange.mit.edu (18.9.1.112) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 21 Apr 2020 09:59:54 -0400 Received: from oc11exhyb3.exchange.mit.edu (18.9.1.99) by oc11exhyb7.exchange.mit.edu (18.9.1.112) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 21 Apr 2020 10:00:05 -0400 Received: from NAM04-SN1-obe.outbound.protection.outlook.com (104.47.44.53) by oc11exhyb3.exchange.mit.edu (18.9.1.99) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 21 Apr 2020 10:00:05 -0400 Received: from DM5PR21CA0030.namprd21.prod.outlook.com (2603:10b6:3:ed::16) by BYAPR01MB5238.prod.exchangelabs.com (2603:10b6:a03:91::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2921.29; Tue, 21 Apr 2020 14:00:04 +0000 Received: from DM3NAM03FT016.eop-NAM03.prod.protection.outlook.com (2603:10b6:3:ed:cafe::cd) by DM5PR21CA0030.outlook.office365.com (2603:10b6:3:ed::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2958.2 via Frontend Transport; Tue, 21 Apr 2020 14:00:04 +0000 Received: from mail-oo1-f46.google.com (209.85.161.46) by DM3NAM03FT016.mail.protection.outlook.com (10.152.82.198) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2921.25 via Frontend Transport; Tue, 21 Apr 2020 14:00:03 +0000 Received: by mail-oo1-f46.google.com with SMTP id t12so2529883oot.2 for ; Tue, 21 Apr 2020 07:00:02 -0700 (PDT) From: Mike Rigby-Jones To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Tue, 21 Apr 2020 06:59:49 -0700 Subject: Re: [EE] LDO reg keeps failing. Looking for suggestions. Thread-Topic: [EE] LDO reg keeps failing. Looking for suggestions. Thread-Index: AdYX5rJhGG/vavn8QCmNioDL7HksXA== Message-ID: References: <35716fec-1512-6e55-8b3c-d4fe3e9b10aa@gmail.com> 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.161.46 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.161.46; helo=mail-oo1-f46.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Mh/Gkwas1yJvNmiL/3quXJ/Ny/Udbdv7b4o0XCgGHhQ=; b=uesPwWNRQd83ubfwrAywwZsqmRDeUnnfPtLE52WIXIuL/Juxwf3xJjhFr84iQFEyAZ kOtc0z0e3dUA28Dmz6O+xB7o8mK44GF6z7N95DE3RO2X8QXx2XMVpCqmLID01LEJCGuZ i2w7qnCKOuSAL5vJG5YNgp0Fm/exCc/oeXkIVT4DaxFY2oKJXP+EZTkg0ov4tnrclSsG dYHXCKbv1ZbQNw9Bv4eOBNFPFTrQ0lp1LG6IRpGLxEn+pWdJTnlKINDLypv8Qe2iJY/t Uz12lC8h0nbDamnio0DKd4QARLoNz6RnLbC6rEAwqdY4NDxEgcwh8SWR4A3EVfmh86/U EGDA== authentication-results: spf=pass (sender IP is 209.85.161.46) 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:a4a:5482:: with SMTP id t124mr16437704ooa.92.1587477599825; Tue, 21 Apr 2020 06:59:59 -0700 (PDT) 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 problem is not Vout rising, but rather Vin falling below Vout (which is held up through decoupling capacitance) due to current transients etc. I would have D8 cathode connected to the input pin of the regulator however. As drawn a dip in the supply rail could cause the micro to brown out, negating the usefulness of the input diode. Mike On Tue, 21 Apr 2020, 08:32 Sean Breheny, wrote: > On Mon, Apr 20, 2020 at 9:33 PM David Van Horn < > david.vanhorn@backcountryaccess.com> wrote: > > > I disagree. > > The failure mechanism is well documented, where Vout > Vin. > > The point of D8 is to prevent the input pin from being more than a diod= e > > drop below Vout in that situation. > > But the problem mechanism here isn't Vin falling, it's Vout rising. > > > > Why do you say that the problem is Vout rising? It appears to me that > Vout > only powers the microcontroller, not the motors. Any regeneration from th= e > motors should go directly into the battery. > -- > 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 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .