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; Sat, 23 May 2020 10:28:28 -0700 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 04NHJWI7007097; Sat, 23 May 2020 13:19:44 -0400 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 04NHJVjW007094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sat, 23 May 2020 13:19:32 -0400 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 04NHJaVa010941 for ; Sat, 23 May 2020 13:19:37 -0400 Received: from w92expo33.exchange.mit.edu (18.7.74.45) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Sat, 23 May 2020 13:19:23 -0400 Received: from oc11exhyb8.exchange.mit.edu (18.9.1.113) by w92expo33.exchange.mit.edu (18.7.74.45) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Sat, 23 May 2020 13:19:31 -0400 Received: from NAM11-BN8-obe.outbound.protection.outlook.com (104.47.58.169) by oc11exhyb8.exchange.mit.edu (18.9.1.113) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Sat, 23 May 2020 13:19:31 -0400 Received: from MWHPR1601CA0017.namprd16.prod.outlook.com (2603:10b6:300:da::27) by MWHPR01MB2430.prod.exchangelabs.com (2603:10b6:300:3f::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3021.23; Sat, 23 May 2020 17:19:30 +0000 Received: from CO1NAM03FT034.eop-NAM03.prod.protection.outlook.com (2603:10b6:300:da:cafe::7) by MWHPR1601CA0017.outlook.office365.com (2603:10b6:300:da::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3021.23 via Frontend Transport; Sat, 23 May 2020 17:19:30 +0000 Received: from mail-ej1-f45.google.com (209.85.218.45) by CO1NAM03FT034.mail.protection.outlook.com (10.152.80.177) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3021.23 via Frontend Transport; Sat, 23 May 2020 17:19:29 +0000 Received: by mail-ej1-f45.google.com with SMTP id yc10so16406655ejb.12 for ; Sat, 23 May 2020 10:19:29 -0700 (PDT) Received: by 2002:a54:3107:0:0:0:0:0 with HTTP; Sat, 23 May 2020 10:19:26 -0700 (PDT) From: Jason White To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Sat, 23 May 2020 10:19:26 -0700 Subject: Re: [EE] MOSFET Gate Voltage Thread-Topic: [EE] MOSFET Gate Voltage Thread-Index: AdYxJ5MnZrg90LuTRVy8d4Xe82OtRQ== 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.218.45 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.218.45; helo=mail-ej1-f45.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=qqfjVik6cp00hT+22qvpOPCRyfjctJXLDI7BRBTqQDk=; b=ijYveWxjjZH+ItRl8eLmVt69ihPomIHFB+esWOwg2M00ErnWlHBwokr4Zh+0oRC4Z8 GhrHtqWczwpHSoac8v66vHI2N9UOeAggwHnUkEsQQC2u/C4DeqEExCZ47s4Ckp3I/sq0 lclSzB3tNnXt6ht7oyMaq/Wvu5uft9Z+qQxaeN2QZgqowrIz4MLaEtO2gvRq4YPULlXp TMyNNx+eosppvDEXe3YvgsvCjaxANxE87YR1g3S0x9FWAiqOmyzXYoiZcXgPKRCF3o65 slz7T8oC4iDtBdnvIp2rzXx4MuWcaM+BERqrL/IUOFJfnDLbj8R0anRAxjib7TsI3A5r AtFQ== authentication-results: spf=pass (sender IP is 209.85.218.45) 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:a17:906:e211:: with SMTP id gf17mr12696816ejb.495.1590254367449; Sat, 23 May 2020 10:19:27 -0700 (PDT) x-topics: [EE] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I'd advise reducing the control signal to 3.3 volts. Without more information it's hard to say what might (or might not) happen. On Saturday, May 23, 2020, Josh Koffman wrote: > Hi all, > > I'm modifying an existing battery powered LED lamp. I haven't fully > completed my investigation, but I believe I have identified a MOSFET > that is responsible for controlling the LEDs. I want to hijack that > MOSFET and inject my own control signal. If my current theories are > correct, this shouldn't be too hard. > > However, the circuit is running off a battery at 3.3V. The control > signal I plan on using is going to be 5V. So that means the gate of > the MOSFET will have more voltage on it than across D-S. Will this > work, or will this end badly for the MOSFET? > > Thank you! > > Josh > -- > A common mistake that people make when trying to design something > completely foolproof is to underestimate the ingenuity of complete > fools. > -Douglas Adams > -- > 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 .