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, 20 Aug 2021 05:21: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 17KC9wfG025799; Fri, 20 Aug 2021 08:11:11 -0400 Received: from outgoing-exchange-1.mit.edu (OUTGOING-EXCHANGE-1.MIT.EDU [18.9.28.15]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 17KC9uCA025796 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Fri, 20 Aug 2021 08:09:56 -0400 Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 17KC9oBP032306 for ; Fri, 20 Aug 2021 08:09:56 -0400 Received: from w92exhyb2.exchange.mit.edu (18.7.71.32) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Fri, 20 Aug 2021 08:09:56 -0400 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by w92exhyb2.exchange.mit.edu (18.7.71.32) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Fri, 20 Aug 2021 08:09:33 -0400 Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.106) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1497.23 via Frontend Transport; Fri, 20 Aug 2021 08:09:33 -0400 Received: from BN9PR03CA0120.namprd03.prod.outlook.com (2603:10b6:408:fd::35) by SN6PR01MB3917.prod.exchangelabs.com (2603:10b6:805:1a::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4415.16; Fri, 20 Aug 2021 12:09:50 +0000 Received: from BN8NAM11FT030.eop-nam11.prod.protection.outlook.com (2603:10b6:408:fd:cafe::cb) by BN9PR03CA0120.outlook.office365.com (2603:10b6:408:fd::35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4436.19 via Frontend Transport; Fri, 20 Aug 2021 12:09:50 +0000 Received: from mail-pl1-f181.google.com (209.85.214.181) by BN8NAM11FT030.mail.protection.outlook.com (10.13.177.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4436.19 via Frontend Transport; Fri, 20 Aug 2021 12:09:50 +0000 Received: by mail-pl1-f181.google.com with SMTP id e15so5840318plh.8 for ; Fri, 20 Aug 2021 05:09:50 -0700 (PDT) From: Jason White To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Fri, 20 Aug 2021 05:09:12 -0700 Subject: Re: [EE] Amplifying a motor driver output Thread-Topic: [EE] Amplifying a motor driver output Thread-Index: AdeVvecmUHQypVNmRIy3Pdarl7uwGA== 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.214.181 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.214.181; helo=mail-pl1-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=QryI5DyhrsYMzugUcAowFA2FYprTwik8uI5NgDJHFho=; b=fRNGu34rkwMNLn0QG80mV1a+BeJuu2lE73QN692rpKUENhe8WuuIxEpSMatTOU3eJy Wet9rHG1jRSzq9blIIQnL21CFg8tBH+eeamaFRLKXwn5KMLWXEOTbzNrOKetrtt1ZzyL EHEoNWmYiy6QUVpjoIXwsnf2Gq5nxV4NbKvSUcT/KLWONBBnXFJwwxU4M4oInHvBqPBI aNqawsixeYyuAeF40w+i886tmTVLv3tr0iT0CeAVhWB2cYizcz68z1p21O9XOC4Lrnhm Fv9Y8zAedxBZkAMPeZLZsaepL4BXR9SGv2bsEyFcynNcqKnKYKIU0bHgUX3iXNhSzS4E mfDA== authentication-results: spf=pass (sender IP is 209.85.214.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:a17:90a:c003:: with SMTP id p3mr4302001pjt.14.1629461389388; Fri, 20 Aug 2021 05:09:49 -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 The specifics depend on the type of motor. But yes, that method would be essentially foolproof. I was going to say, "no need for load resistors or microcontrollers - simply have the motor terminal output serve as the input to an H-Bridge". But that assumes a bunch of things including brushed DC motors. I bet that open source open source joysticks might exist, but reengineering one of those to work with modified hardware might be more costly than what you were planning to do. On Thu, Aug 19, 2021 at 8:11 PM Neil wrote: > I need a force-feedback joystick such as a Microsoft Sidewinder FFB 2, > but with (much) more powerful motors. > I'm wondering if I can start with a MSFFB 2, replace the motors with > dummy loads (resistors), measure the voltage across those resistors, > filter/condition it, and have that control motor drivers with more > powerful motors. Is this practical? > Or any better (simple, not too costly) way to achieve 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 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 .