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; Wed, 5 Feb 2020 12:23:24 -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 015KBmeK005479; Wed, 5 Feb 2020 15:15:14 -0500 Received: from outgoing-exchange-3.mit.edu (OUTGOING-EXCHANGE-3.MIT.EDU [18.9.28.13]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 015KBlJi005476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 5 Feb 2020 15:11:47 -0500 Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) by outgoing-exchange-3.mit.edu (8.14.7/8.12.4) with ESMTP id 015KB8jj023481 for ; Wed, 5 Feb 2020 15:11:18 -0500 Received: from w92expo12.exchange.mit.edu (18.7.74.66) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 5 Feb 2020 15:09:31 -0500 Received: from oc11exhyb3.exchange.mit.edu (18.9.1.99) by w92expo12.exchange.mit.edu (18.7.74.66) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 5 Feb 2020 15:11:25 -0500 Received: from NAM12-MW2-obe.outbound.protection.outlook.com (104.47.66.46) by oc11exhyb3.exchange.mit.edu (18.9.1.99) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 5 Feb 2020 15:11:24 -0500 Received: from BYAPR01CA0064.prod.exchangelabs.com (2603:10b6:a03:94::41) by SN2PR01MB2095.prod.exchangelabs.com (2603:10b6:804:a::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2707.21; Wed, 5 Feb 2020 20:11:23 +0000 Received: from CO1NAM03FT018.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e48::200) by BYAPR01CA0064.outlook.office365.com (2603:10b6:a03:94::41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.32 via Frontend Transport; Wed, 5 Feb 2020 20:11:23 +0000 Received: from mailscanner.virtbiz.com (208.77.216.252) by CO1NAM03FT018.mail.protection.outlook.com (10.152.80.174) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2707.21 via Frontend Transport; Wed, 5 Feb 2020 20:11:22 +0000 Received: from s18855546.onlinehome-server.com (s18855546.onlinehome-server.com [74.208.193.200]) by mailscanner.virtbiz.com (8.14.7/8.14.7) with ESMTP id 015KBHjp016906 for ; Wed, 5 Feb 2020 14:11:19 -0600 Received: from mai.hallikainen.org (localhost [127.0.0.1]) by s18855546.onlinehome-server.com (8.14.4/8.14.4) with ESMTP id 015KBDlw004583 for ; Wed, 5 Feb 2020 12:11:13 -0800 Received: (from apache@localhost) by mai.hallikainen.org (8.14.4/8.14.4/Submit) id 015KBDsg004580; Wed, 5 Feb 2020 12:11:13 -0800 Received: from 184.96.138.164 (SquirrelMail authenticated user harold) by mai.hallikainen.org with HTTP; Wed, 5 Feb 2020 12:11:13 -0800 From: Harold Hallikainen To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 5 Feb 2020 12:11:13 -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: AdXcYh5FABtRyDaqSeyUBfKIVJm/Iw== 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 mai.hallikainen.org designates 208.77.216.252 as permitted sender) receiver=protection.outlook.com; client-ip=208.77.216.252; helo=mailscanner.virtbiz.com; 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=AxyEqPzuHsSjBOfd4e0B65gpF8pOiLK8IPIpu695Ri0=; b=sv6LF1tsSZatlTAWgtJgWvP4Ai/7BBkQOMVa3Cv5Z0Qamemoj1g9IUXa4L4t86R2WD06h3/+SEjnt9GsSqYVUXQxCWONdmSj9mi3YMNS+eLTkVyXDSG7Dr+kjWsxQXawh+rxeHVR3mfMR3WW5L3FgxfiFlBRb7ceojAOrmMZEdk= authentication-results: spf=pass (sender IP is 208.77.216.252) smtp.mailfrom=mai.hallikainen.org; mit.edu; dkim=none (message not signed) header.d=none;mit.edu; dmarc=permerror action=none header.from=mai.hallikainen.org;compauth=pass reason=111 user-agent: SquirrelMail/1.4.22-5.el6 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-authentication-warning: mai.hallikainen.org: apache set sender to harold@mai.hallikainen.org using -f x-spam-status: No x-greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.6.2 (mailscanner.virtbiz.com [208.77.216.252]); Wed, 05 Feb 2020 14:11:19 -0600 (CST) x-topics: [EE] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I wonder if the overshoot could be due to the output capacitor. Is the input also dragged down in this condition? On input below output damaging the regulator, we used to put a diode between input and output to not let the input be more than 700 mV below the output. Harold > 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 them= .. > > They (and actually most PNP based regulators) can be damaged by the input > 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 th= e > same. There are more modern parts that are immune. > > -- > David VanHorn > Lead Hardware Engineer > > Backcountry Access, Inc. > 2820 Wilderness Pl, Unit H > Boulder, CO =A080301 USA > phone:=A0303-417-1345 =A0x110 > email:=A0david.vanhorn@backcountryaccess.com=A0 > > -----Original Message----- > From: piclist-bounces@mit.edu On Behalf Of Jaso= n > White > Sent: Wednesday, February 5, 2020 10:36 AM > To: Microcontroller discussion list - Public. > Subject: [EE] 78L05 (SO8) overshoot on removal of over-current event? > > Hello everyone, > > At a previous job I observed a failure mode where the 100mA current ratin= g > of a 78L05 type regulator (12->5V, SO8) was exceeded causing it to > saturate and then briefly overshoot to >7V when the load was removed > causing damage to 5V circuitry. (a micro-controller was driving a large > number of opto-isolators, all toggled on and off at the same time) > > Do anyone have any links to literature that documents this behavior? > > -- > 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 FCC Rules Updated Daily at http://www.hallikainen.com Not sent from an iPhone. --=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 .