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; Fri, 4 Dec 2020 10:10:57 -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 0B4Hw6xK017975; Fri, 4 Dec 2020 12:58:41 -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 0B4Hw5gr017972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 4 Dec 2020 12:58:05 -0500 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 0B4HvfPc010055 for ; Fri, 4 Dec 2020 12:58:05 -0500 Received: from w92expo15.exchange.mit.edu (18.7.74.69) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Fri, 4 Dec 2020 12:57:14 -0500 Received: from oc11exhyb1.exchange.mit.edu (18.9.1.60) by w92expo15.exchange.mit.edu (18.7.74.69) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Fri, 4 Dec 2020 12:57:56 -0500 Received: from NAM11-BN8-obe.outbound.protection.outlook.com (104.47.58.169) by oc11exhyb1.exchange.mit.edu (18.9.1.60) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Fri, 4 Dec 2020 12:57:56 -0500 Received: from DM5PR06CA0074.namprd06.prod.outlook.com (2603:10b6:3:4::12) by SA0PR01MB6284.prod.exchangelabs.com (2603:10b6:806:e2::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3611.22; Fri, 4 Dec 2020 17:57:55 +0000 Received: from DM6NAM11FT011.eop-nam11.prod.protection.outlook.com (2603:10b6:3:4:cafe::9e) by DM5PR06CA0074.outlook.office365.com (2603:10b6:3:4::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3632.17 via Frontend Transport; Fri, 4 Dec 2020 17:57:55 +0000 Received: from mail-pf1-f181.google.com (209.85.210.181) by DM6NAM11FT011.mail.protection.outlook.com (10.13.172.108) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3632.17 via Frontend Transport; Fri, 4 Dec 2020 17:57:55 +0000 Received: by mail-pf1-f181.google.com with SMTP id b26so4258500pfi.3 for ; Fri, 04 Dec 2020 09:57:55 -0800 (PST) From: Manu Abraham To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Fri, 4 Dec 2020 09:57:35 -0800 Subject: Re: [EE] Piezo driver Thread-Topic: [EE] Piezo driver Thread-Index: AdbKaNDtpYMIUy0STu6NhS/haR87Ow== 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.210.181 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.210.181; helo=mail-pf1-f181.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=ranjvtIpQqYH9YfZViYB1DyrjluuxU8aZryo2+6TgTo=; b=Q/MEJozzyYW6bWr8jnplfD9Wskdhao+UsPVFsmuui6jh9DZvNi9HBTDhiSDpbXdqnL vngYYt+AY2Ki7OeWKEJOql3213wq52nh54eIdCXqRA7MXOrdOYUh8+qq5Os2skcoGyIt ovRmOFcMB/0bBo7PQc4nrFjFnHsivT+dXqX6xb2H0VMvK9DdMEbWbWZFGKRM4P6LMfz6 FYy0r/4tbwh0ZZ1Gr90MYpv6JTKD1CbfPAr3GmhYmdwu0UyAIXoagcu/72vlWmXZbDVF CjUqdO7GWPlYpGENPqd8ubsWf+N5TazMfKlRE93iio3eOn48Cjy5AXqrR8LDcdVrQKjW QD+Q== authentication-results: spf=pass (sender IP is 209.85.210.181) 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; 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:a62:7b85:0:b029:198:11e5:596 with SMTP id w127-20020a627b850000b029019811e50596mr4918475pfc.40.1607104673995; Fri, 04 Dec 2020 09:57:53 -0800 (PST) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 On Wed, Dec 2, 2020 at 12:48 AM Jason White wrote: > > Discrete solution: N channel FETs in H-bridge configuration plus beefy ga= te > driver. 1-2Mhz switching frequencies are pretty commonly in SMPS design. > You might find an SMPS controller with integrated FETs and make it do you= r > bidding by altering the voltage at the feedback pin. Regarding the discrete solution, what gate driver/MOSFET do you have in min= d ? A SMPS controller cannot work for the simple reason is that the frequency is fixed internally by the controller. Simple controllers such as the SG3524 do have external RC components to set the frequency, but such legacy controllers run at relatively lower frequencies. Thanks, Manu --=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 .