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:50:46 -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 015Kc19m009166; Wed, 5 Feb 2020 15:41:45 -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 015KbxgA009163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 5 Feb 2020 15:37:59 -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 015KbUI9024841 for ; Wed, 5 Feb 2020 15:37:30 -0500 Received: from oc11expo18.exchange.mit.edu (18.9.4.49) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 5 Feb 2020 15:35:42 -0500 Received: from oc11exhyb7.exchange.mit.edu (18.9.1.112) by oc11expo18.exchange.mit.edu (18.9.4.49) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 5 Feb 2020 15:37:36 -0500 Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.173) by oc11exhyb7.exchange.mit.edu (18.9.1.112) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 5 Feb 2020 15:37:36 -0500 Received: from BL0PR0102CA0058.prod.exchangelabs.com (2603:10b6:208:25::35) by BYAPR01MB5095.prod.exchangelabs.com (2603:10b6:a03:1e::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.27; Wed, 5 Feb 2020 20:37:34 +0000 Received: from DM3NAM03FT010.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e49::207) by BL0PR0102CA0058.outlook.office365.com (2603:10b6:208:25::35) 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:37:33 +0000 Received: from mail-oi1-f176.google.com (209.85.167.176) by DM3NAM03FT010.mail.protection.outlook.com (10.152.82.65) 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:37:33 +0000 Received: by mail-oi1-f176.google.com with SMTP id p125so2161589oif.10 for ; Wed, 05 Feb 2020 12:37:33 -0800 (PST) From: Jason White To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 5 Feb 2020 12:36:57 -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: AdXcZfDR/xs4Rs6NQ52fXQ+mNEHgrg== 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.167.176 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.167.176; helo=mail-oi1-f176.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=8wtMlYjvZJMKaLijBs+mmJ18eacfumxSP0en/dQjqhA=; b=CkV4ajvl4yQX1RCoUWKZ9B0+J+2kjIyvsXD9WCBn54xCuB6wtY/59RJEmcC9FKWWsI HPCNUrQp86VKmNC+6l0qngpcHhbgUigBuScEtY0Oy7y7DnzEvEE3EGA/lu/m6Mfha9co HJVxAvF8JNyUb7bN4ZUATxS+m7ZFynIhgaN/fYTKvADh5C9Eqte7/4crJkbrjSdsr9x6 2CDPuxciFSJgmQHu5vbAm/k44HghPPeQDs8UfutRR31AoaR1v1v0WbnNI04ZosGy+YUP ZxSk/IFa2J3gAOHyfn+XizaPUDN5Od766ooLwF8AAe0D7cfx+2swXDE7CjbveDp3R317 9P/g== authentication-results: spf=pass (sender IP is 209.85.167.176) 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:aca:5150:: with SMTP id f77mr4294040oib.52.1580935052287; Wed, 05 Feb 2020 12:37:32 -0800 (PST) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 While it is definitely possible, I don't recall it being damaged. We went from a 28V transformer to 24V to 12V to 5V - big capacitors at each linear regulator stage. Back then we fixed it just by putting a higher current regulator for the 12V->5V on the PCB. As soon as the larger regulator was wired in by a technician the micro-controller (which was not touching any high voltage stuff) stopped getting holes blown through it. We were able to reproduce the issue on the two prototype boards we had. On Wed, Feb 5, 2020 at 3:15 PM Harold Hallikainen wrote: > > 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 th= em. > > > > They (and actually most PNP based regulators) can be damaged by the inp= ut > > 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. > > > > -- > > David VanHorn > > Lead Hardware Engineer > > > > Backcountry Access, Inc. > > 2820 Wilderness Pl, Unit H > > Boulder, CO 80301 USA > > phone: 303-417-1345 x110 > > email: david.vanhorn@backcountryaccess.com > > > > -----Original Message----- > > From: piclist-bounces@mit.edu On Behalf Of Ja= son > > 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 rat= ing > > 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 > > > > > -- > FCC Rules Updated Daily at http://www.hallikainen.com > Not sent from an iPhone. > -- > 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 .