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; Thu, 6 Feb 2020 02:24:25 -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 016AC5Ur004838; Thu, 6 Feb 2020 05:15:30 -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 016AC4aW004832 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 6 Feb 2020 05:12:04 -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 016AEw3l007522 for ; Thu, 6 Feb 2020 05:15:01 -0500 Received: from w92expo22.exchange.mit.edu (18.7.74.76) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Thu, 6 Feb 2020 05:10:06 -0500 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by w92expo22.exchange.mit.edu (18.7.74.76) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 6 Feb 2020 05:12:00 -0500 Received: from NAM10-MW2-obe.outbound.protection.outlook.com (104.47.55.105) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Thu, 6 Feb 2020 05:12:00 -0500 Received: from SN2PR01CA0021.prod.exchangelabs.com (2603:10b6:804:2::31) by DM6PR01MB6090.prod.exchangelabs.com (2603:10b6:5:14d::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.32; Thu, 6 Feb 2020 10:11:59 +0000 Received: from DM3NAM03FT047.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e49::203) by SN2PR01CA0021.outlook.office365.com (2603:10b6:804:2::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2707.21 via Frontend Transport; Thu, 6 Feb 2020 10:11:58 +0000 Received: from mail-1.ca.inter.net (208.85.220.69) by DM3NAM03FT047.mail.protection.outlook.com (10.152.83.124) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.20.2707.21 via Frontend Transport; Thu, 6 Feb 2020 10:11:58 +0000 Received: from localhost (offload-3.ca.inter.net [208.85.220.70]) by mail-1.ca.inter.net (Postfix) with ESMTP id A216B2EA07E for ; Thu, 6 Feb 2020 05:11:57 -0500 (EST) Received: from mail-1.ca.inter.net ([208.85.220.69]) by localhost (offload-3.ca.inter.net [208.85.220.70]) (amavisd-new, port 10024) with ESMTP id Cfo94gdklWuJ for ; Thu, 6 Feb 2020 05:05:49 -0500 (EST) Received: from localhost (webmail.ca.inter.net [208.85.220.72]) by mail-1.ca.inter.net (Postfix) with ESMTP id 1EAF42EA169 for ; Thu, 6 Feb 2020 05:11:57 -0500 (EST) Received: from CPE688f2e2f19d3-CM688f2e2f19d0.cpe.net.cable.rogers.com (CPE688f2e2f19d3-CM688f2e2f19d0.cpe.net.cable.rogers.com [99.246.174.220]) by webmail.ca.inter.net (Horde Framework) with HTTP; Thu, 06 Feb 2020 05:11:56 -0500 From: "speff@interlog.com" To: "piclist@mit.edu" Sender: "piclist-bounces@mit.edu" Date: Thu, 6 Feb 2020 02:11:56 -0800 Subject: Re: [EE] 78L05 (SO8) overshoot on removal of over-current event? Thread-Topic: [EE] 78L05 (SO8) overshoot on removal of over-current event? Thread-Index: AdXc15u7hBBl9BEXTnqmIi5qhSFjlw== Message-ID: <20200206051156.11833yanpr1zlld8@webmail.ca.inter.net> 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 interlog.com designates 208.85.220.69 as permitted sender) receiver=protection.outlook.com; client-ip=208.85.220.69; helo=mail-1.ca.inter.net; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitprod.onmicrosoft.com; s=selector2-mitprod-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oL0LeWEVqTZLkgi/uoQLN580IFee+0cyWiYR+CRHrfY=; b=AEXb+EmVO9ZPDHgTKzHoEFXF7FiXBB1AbP7le0Socvz9w3+h82p6Dy4i88uIw1VWFa3WTFkK5h+Jw515e5r9p3/SPtHQw/BcyD/nf8jdMBR61PohUzholZrt8YYMJTyYxEQJ2Kk4U3iYLaFfZlu7wfYLebP0jHuSaolltFdO1Jo= authentication-results: spf=pass (sender IP is 208.85.220.69) smtp.mailfrom=interlog.com; mit.edu; dkim=none (message not signed) header.d=none;mit.edu; dmarc=bestguesspass action=none header.from=interlog.com;compauth=pass reason=109 user-agent: Internet Messaging Program (IMP) H3 (4.3.7) 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-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Quoting RussellMc : > On Thu, 6 Feb 2020 at 06:50, David Van Horn < > david.vanhorn@backcountryaccess.com> wrote: > >> I've not seen this exactly, but I have seen a lot of problems with the L >> version being defective in various ways. I generally wouldn't trust the= m. >> >> They (and actually most PNP based regulators) can be damaged by the inpu= t >> being shorted to ground, if the output capacitor is large. This is not >> well documented, you might have to go back to Motorola data sheets from = the >> 1980's to find it documented, but the output stages are still much the >> same. There are more modern parts that are immune. >> >> Normal method to protect against this is to place a reverse biased diod= e > across the regulator so that the output capacitor will discharge via the > diode if the input is shorted. Hi, Russell:- The old NS datasheets say "generally" no diode is required for 10uF or =20 less output capacitor on the 7805. That may be a relic of the =20 electrolytic capacitors of old, which would have enough ESR (1-2 ohms =20 maybe) to limit the current. Maybe a modern 10uF ceramic cap can ruin =20 the regulator given a direct short. > Worst case a power off event may qualify if there is a heavy load on the > input side from loads. > > I recall, but now not why in detail, that many decades ago we decided tha= t > the 78Lxx regulators were not worth using compared to the 'full spec' one= s. I picked 78Mxx many years ago for a whole series of applications where a 78L0x would function because they are superior electrically in just =20 about every respect, in particular the temperature coefficient, line =20 regulation, load regulation and PSRR are better. Less temperature rise =20 with a TO-252 on a bit of copper or a TO-220 too. Best regards, Spehro Pefhany > > Russell > -- > 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 .