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; Tue, 7 Jan 2020 15:38:54 -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 007NRA5t016700; Tue, 7 Jan 2020 18:29:55 -0500 Received: from outgoing-exchange-7.mit.edu (OUTGOING-EXCHANGE-7.MIT.EDU [18.9.28.58]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 007NR9b3016697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 7 Jan 2020 18:27:09 -0500 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 007NR3ST027278 for ; Tue, 7 Jan 2020 18:27:03 -0500 Received: from OC11EXPO27.exchange.mit.edu (18.9.4.98) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 7 Jan 2020 18:25:48 -0500 Received: from oc11exhyb2.exchange.mit.edu (18.9.1.98) by OC11EXPO27.exchange.mit.edu (18.9.4.98) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 7 Jan 2020 18:27:08 -0500 Received: from NAM12-DM6-obe.outbound.protection.outlook.com (104.47.59.172) by oc11exhyb2.exchange.mit.edu (18.9.1.98) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 7 Jan 2020 18:27:07 -0500 Received: from BL0PR0102CA0008.prod.exchangelabs.com (2603:10b6:207:18::21) by BYAPR01MB5141.prod.exchangelabs.com (2603:10b6:a03:7a::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2623.9; Tue, 7 Jan 2020 23:27:06 +0000 Received: from CO1NAM03FT003.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e48::205) by BL0PR0102CA0008.outlook.office365.com (2603:10b6:207:18::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2623.9 via Frontend Transport; Tue, 7 Jan 2020 23:27:06 +0000 Received: from mail-ed1-f53.google.com (209.85.208.53) by CO1NAM03FT003.mail.protection.outlook.com (10.152.80.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2623.9 via Frontend Transport; Tue, 7 Jan 2020 23:27:05 +0000 Received: by mail-ed1-f53.google.com with SMTP id cy15so1052140edb.4 for ; Tue, 07 Jan 2020 15:27:05 -0800 (PST) From: Ryan O'Connor To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Tue, 7 Jan 2020 15:26:48 -0800 Subject: Re: [EE]: LTSpice Question Thread-Topic: [EE]: LTSpice Question Thread-Index: AdXFs6BgyklDK8YZQQGuQwLvnEYuQw== Message-ID: References: <20200107125557.06a56fd6300ec2bfca6379d4e10ab8d2.0d7b2e735f.wbe@email27.godaddy.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <20200107125557.06a56fd6300ec2bfca6379d4e10ab8d2.0d7b2e735f.wbe@email27.godaddy.com> 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.208.53 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.208.53; helo=mail-ed1-f53.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=b5AIzfRbO2DgLh41Jq4hh1oBdGQAYehbbJtr26TNiTM=; b=T9DqmpJtT/+NeloTWKWT3UcuVvL6zRNdi+AN/s1yuy0q9YrHZfuTvGqfh7J/Q0toyp mYbOOKSImOFDWtpc6FmFJsQynZyJcCR2OzSiO3eDh7kdKmmwjLO6AqdThxGqIwLKihNW cmTxcR5vs3qKl6XpLt8jRBZ9lbX0DAxsZBvJei7xUNwShephlpi7lw9xaA7vIDPIPFVt zdnnFXdMLQdF+g1gHRQ0jCaF7ARlgT/ZmHh0Qn9/2OaGu2LmJ9OyDAgg3ozAphMYSL2R akyOJP9kEmhsT38hLdf9TLsD1e1A6yDPttV3vz9xkbWzRdCars+YkgydkqV2AJ32K89L Br6g== authentication-results: spf=pass (sender IP is 209.85.208.53) 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:a50:ed18:: with SMTP id j24mr2527570eds.124.1578439623850; Tue, 07 Jan 2020 15:27:03 -0800 (PST) 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 Looking forward to later hearing about a practical reason to use depletion mode mosfets! Ryan On Wed, 8 Jan 2020 at 09:00, Jim wrote: > > All, > > I have a need to simulate a circuit using a Depletion Mode MOSFET using > LTSpice. > I have looked at the list of MOSFETs included in the application, but I > don't see any Depletion Mode FETs. > Does anyone have any idea what part number in LTSpice could be a > Depletion Mode MOSFET? Or does anyone have a model of > an N Channel Depletion Mode MOSFET that will run under LTSpice? > The parameters of the particular part number aren't an important issue > at this time. I just need a functional model > for a quick proof of concept for a new circuit for a new product at > work. I can't elaborate on this further at the > moment, but later, if all works out, I'll let everyone know that is > interested what the circuit is intended to do, and > if it does what it's supposed to. > > Anyway, if anyone knows if any of the MOSFET part numbers listed in > LTSpice are Depletion Mode FET's, please let me > know. > > > Thanks and Regards, > > Jim > > > -- > 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 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .