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 11:28:42 -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 01QJJmF9029354; Wed, 26 Feb 2020 14:20: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 01QJJkFA029347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 26 Feb 2020 14:19:46 -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 01QJMcZS001467 for ; Wed, 26 Feb 2020 14:23:05 -0500 Received: from w92expo8.exchange.mit.edu (18.7.74.62) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 26 Feb 2020 14:16:58 -0500 Received: from oc11exhyb4.exchange.mit.edu (18.9.1.100) by w92expo8.exchange.mit.edu (18.7.74.62) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 26 Feb 2020 14:19:32 -0500 Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.169) by oc11exhyb4.exchange.mit.edu (18.9.1.100) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 26 Feb 2020 14:19:32 -0500 Received: from MWHPR13CA0037.namprd13.prod.outlook.com (2603:10b6:300:95::23) by SN6PR01MB4509.prod.exchangelabs.com (2603:10b6:805:e2::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.21; Wed, 26 Feb 2020 19:19:28 +0000 Received: from CO1NAM03FT044.eop-NAM03.prod.protection.outlook.com (2603:10b6:300:95:cafe::64) by MWHPR13CA0037.outlook.office365.com (2603:10b6:300:95::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2793.5 via Frontend Transport; Wed, 26 Feb 2020 19:19:28 +0000 Received: from mail-qk1-f170.google.com (209.85.222.170) by CO1NAM03FT044.mail.protection.outlook.com (10.152.81.108) 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 19:19:27 +0000 Received: by mail-qk1-f170.google.com with SMTP id 11so642016qkd.1 for ; Wed, 26 Feb 2020 11:19:27 -0800 (PST) Received: from [192.168.0.138] ([189.63.53.85]) by smtp.gmail.com with ESMTPSA id o3sm1597982qkk.87.2020.02.26.11.19.25 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Feb 2020 11:19:26 -0800 (PST) From: Isaac Marino Bavaresco To: "piclist@mit.edu" Sender: "piclist-bounces@mit.edu" Date: Wed, 26 Feb 2020 11:19:23 -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: AdXs2vSKg78HcxvPTTqD1HErbJGilw== Message-ID: References: List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US Content-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: x-antivirus-status: Clean x-antivirus: Avast (VPS 200225-0, 25/02/2020), Outbound message received-spf: Pass (protection.outlook.com: domain of gmail.com designates 209.85.222.170 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.222.170; helo=mail-qk1-f170.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=vdxP1pnveUfjEyLIC2T1LiB0NbqHAv9GLR+JnfrMZxU=; b=toTWr5k7TCSHEUFMD/FYfcaYwOb3r6VN7f3AmASoxmT/fcf7p8rB6tsMb+ol99ytow ukYIsCjSEkXegcBefjPe/aAlKeJDbAjZSN+A0ENqc2I2ALHHssAt21yK+KaBOC28uNMP BquyjFkVaQOQeqjCfGtDW5lW4bOdaKZk+3S3JJAOxXJ61VsfeRdWgws3VgeZ05y+6j0o azOFX+EhyXsF3LqqdVkk2r86WgJY2N77bt/LU7JZEPDovtBTN8HlJxPjxcQ9WBjzYlWV CYIBKvmJZInS7AWC18PgCS60sA0k43mVh2A4DmFCSfwtunKSFq8Ebl/MdCOy/JL2mnYV aM0g== authentication-results: spf=pass (sender IP is 209.85.222.170) 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 user-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 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:a37:9bd5:: with SMTP id d204mr742067qke.252.1582744766593; Wed, 26 Feb 2020 11:19:26 -0800 (PST) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Those LVC devices are 5V tolerant, which means that they don't have a diode to VCC. What you are planning is not safe, because the voltage will not be limited. use a Zener diode outside the device. Cheers, Isaac Em 26/02/2020 16:04, Jason White escreveu: > 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? > --=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 .