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, 26 Feb 2020 14:03:06 -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 01QLsoYg019529; Wed, 26 Feb 2020 16:55:00 -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 01QLsm1I019524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 26 Feb 2020 16:54:48 -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 01QLvsC1013536 for ; Wed, 26 Feb 2020 16:58:07 -0500 Received: from oc11expo21.exchange.mit.edu (18.9.4.52) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 26 Feb 2020 16:51:44 -0500 Received: from oc11exhyb3.exchange.mit.edu (18.9.1.99) by oc11expo21.exchange.mit.edu (18.9.4.52) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 26 Feb 2020 16:54:18 -0500 Received: from NAM11-BN8-obe.outbound.protection.outlook.com (104.47.58.173) by oc11exhyb3.exchange.mit.edu (18.9.1.99) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 26 Feb 2020 16:54:18 -0500 Received: from MWHPR15CA0029.namprd15.prod.outlook.com (2603:10b6:300:ad::15) by SN6PR01MB5135.prod.exchangelabs.com (2603:10b6:805:c5::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.14; Wed, 26 Feb 2020 21:54:17 +0000 Received: from CO1NAM03FT004.eop-NAM03.prod.protection.outlook.com (2603:10b6:300:ad:cafe::f1) by MWHPR15CA0029.outlook.office365.com (2603:10b6:300:ad::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.15 via Frontend Transport; Wed, 26 Feb 2020 21:54:17 +0000 Received: from mail-oi1-f180.google.com (209.85.167.180) by CO1NAM03FT004.mail.protection.outlook.com (10.152.80.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.14 via Frontend Transport; Wed, 26 Feb 2020 21:54:16 +0000 Received: by mail-oi1-f180.google.com with SMTP id r137so1151060oie.5 for ; Wed, 26 Feb 2020 13:54:16 -0800 (PST) From: Jason White To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 26 Feb 2020 13:53:39 -0800 Subject: Re: [EE] 74LVC1G332 input clamping current only specified for VI < 0 V Thread-Topic: [EE] 74LVC1G332 input clamping current only specified for VI < 0 V Thread-Index: AdXs8IZ7MWJTaQUJR8aBegGL6NWm1A== Message-ID: References: <20200226164620.14640af0czl2y8to@webmail.ca.inter.net> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <20200226164620.14640af0czl2y8to@webmail.ca.inter.net> 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.180 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.167.180; helo=mail-oi1-f180.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=RQTZ1JnMpSjcr0eA5RZHYfpDloVM1HxktCYTzAKHJzk=; b=DB4JZq7F1Lzx1721lnCATbsjRvuxSXRr95lGg69BWr3nu2u+ZuTeoAFyub4tHqOdkm vsGq68qmvY3v6JmvGfv2+exT/xFsNbbT5uBn6FvsfXn33XVAAhBPiW990HD2d7te/dJ9 mdEJ0rQL/kNInBO9/EnEZeuMpmSIAqO1VjI0tFQD/79TL8aM4bFTY8dO+0e7G2ieD1aC +pB0AmMNLz+qHoQbs//+al+rMIh4F6S0W6Hb44sIHNOkE1X4pcIHPh3WCSEz45rUdEK2 HJo5yCwh5dBqTEkm5EqUBA40blBQTpBKklld7/SiGE6n4UHhcBVTpPAyHfKxmqBMv1Bs zcTw== authentication-results: spf=pass (sender IP is 209.85.167.180) 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:b9c2:: with SMTP id j185mr879569oif.112.1582754055586; Wed, 26 Feb 2020 13:54:15 -0800 (PST) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Thanks everyone! I will design accordingly On Wed, Feb 26, 2020 at 4:47 PM wrote: > > Quoting Jason White : > > > Hello, > > > > I am considering subjecting the input of a 74LVC1G332 to 12 to 48V > > though a resistor and relying upon the internal clamping diodes. > > > > Problem is, this device only specifies clamping diode current for VI < > > 0 V (and not for VI > VCC). However, it does specify that it passes > > various EMI certifications. > > > > I know I could use an Zener diode, but I am curious: what is going on > > here with the datasheet specification? > > > > Hi, Jason: - > > That's a 5V-tolerant part, so does not have a clamping network to Vcc. > There's no doubt some kind of zener like structure inside for ESD. > > It's not the best to rely on the diodes during normal operation as > they can result in excessive current draw or other strange behavior. > A BAT54S dual Schottky will clamp to both rails before any diode in the > gate gets a chance to conduct much. The clamping numbers are abs max. > > Best regards, > Spehro Pefhany > > -- > 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 .