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; Thu, 16 Sep 2021 09:46:02 -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 18GGZChW027703; Thu, 16 Sep 2021 12:35:57 -0400 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 18GGZAeU027678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Thu, 16 Sep 2021 12:35:10 -0400 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 18GGYp7I020751 for ; Thu, 16 Sep 2021 12:35:10 -0400 Received: from oc11expo18.exchange.mit.edu (18.9.4.49) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Thu, 16 Sep 2021 12:34:40 -0400 Received: from oc11exhyb8.exchange.mit.edu (18.9.1.113) by oc11expo18.exchange.mit.edu (18.9.4.49) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Thu, 16 Sep 2021 12:34:23 -0400 Received: from NAM11-CO1-obe.outbound.protection.outlook.com (104.47.56.169) by oc11exhyb8.exchange.mit.edu (18.9.1.113) with Microsoft SMTP Server (TLS) id 15.0.1497.23 via Frontend Transport; Thu, 16 Sep 2021 12:34:23 -0400 Received: from DM5PR17CA0053.namprd17.prod.outlook.com (2603:10b6:3:13f::15) by BYAPR01MB3637.prod.exchangelabs.com (2603:10b6:a02:82::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4523.14; Thu, 16 Sep 2021 16:34:44 +0000 Received: from DM6NAM11FT054.eop-nam11.prod.protection.outlook.com (2603:10b6:3:13f:cafe::29) by DM5PR17CA0053.outlook.office365.com (2603:10b6:3:13f::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4523.14 via Frontend Transport; Thu, 16 Sep 2021 16:34:44 +0000 Received: from mail-qk1-f172.google.com (209.85.222.172) by DM6NAM11FT054.mail.protection.outlook.com (10.13.173.95) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4523.14 via Frontend Transport; Thu, 16 Sep 2021 16:34:44 +0000 Received: by mail-qk1-f172.google.com with SMTP id p4so8282709qki.3 for ; Thu, 16 Sep 2021 09:34:44 -0700 (PDT) From: Denny Esterline To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Thu, 16 Sep 2021 09:34:32 -0700 Subject: Re: [EE] Current mode / Torque mode motor driver Thread-Topic: [EE] Current mode / Torque mode motor driver Thread-Index: AderGlX3aLQvct74Qc+vLEMOSPhTSA== 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.222.172 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.222.172; helo=mail-qk1-f172.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=vdpOKuzUvJJcJQd9jgD15MkMWl/bjmyhm6tml9Nz3Fc=; b=Ls+bCYQKwYzucrBkc7mTQzYD4czNWjI12dQjFnDf5pK6MH7N2nMFlNY3uHPyjbFi8X VQRmfx4qz/dKKUUfzNLi42lGD7pcxUyba9II4eghLSAwMx9Vap169SYmSDp22I8OKiOx LajGXE054q4/cyd0Mtaacf7lycxnJns16YLwe5YcxBeMsXQVobBrkxXLG2mhoXTo52rF Csm8ADvjz8kwHxf+2uKeZASzIBNHriEWGJB8FYOHKbc1CCq0IyrzVUA9nxZaSFeerQMM OpKzr6FFm2Ie575YgYERlO5uJ1Q3i6u4G6jg+8S7SaPkvN3eCmkpoC5LHNrUhs5iEvVw oKEA== authentication-results: spf=pass (sender IP is 209.85.222.172) 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:a37:8747:: with SMTP id j68mr5893125qkd.165.1631810083492; Thu, 16 Sep 2021 09:34:43 -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 High level, yes. But as they say, the fun is in the details. No doubt you want to output PWM, then you have to sync the AD to the PWM. If it's a three-phase motor, then you have to run a commutation algorithm and then consider how your current sensor(s) are connected to the phases. (multiple sensors are common for different control algorithms) Then there's a bunch of corner-cases you need to consider. Reach MIN/MAX control output without reaching goal current? Can you be more specific about the motor? There really are a lot of existing driver options out there that can do this already, depending on the details of your application. -Denny On Thu, Sep 16, 2021 at 8:52 AM Neil wrote: > I'm having a hard time finding a current-mode / torque-mode motor driver > and thinking it's time I DIY something. > High-level thought is to add a small resistor to the ground side, buffer > and measure that with a microcontroller and dynamically > increase/decrease the motor output signal from the microcontroller to > get a specific current. > Is it as simple as this? > > Cheers, > -Neil. > > -- > 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 .