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; Sun, 14 Mar 2021 18:55:22 -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 12F1k4nq012104; Sun, 14 Mar 2021 21:46:43 -0400 Received: from outgoing-exchange-3.mit.edu (OUTGOING-EXCHANGE-3.MIT.EDU [18.9.28.13]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 12F1k2ZZ012098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Sun, 14 Mar 2021 21:46:02 -0400 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-3.mit.edu (8.14.7/8.12.4) with ESMTP id 12F1joWl030315 for ; Sun, 14 Mar 2021 21:46:02 -0400 Received: from oc11expo21.exchange.mit.edu (18.9.4.52) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 14 Mar 2021 21:45:32 -0400 Received: from w92exhyb1.exchange.mit.edu (18.7.71.12) by oc11expo21.exchange.mit.edu (18.9.4.52) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 14 Mar 2021 21:45:29 -0400 Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.173) by w92exhyb1.exchange.mit.edu (18.7.71.12) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Sun, 14 Mar 2021 21:45:29 -0400 Received: from MWHPR1701CA0003.namprd17.prod.outlook.com (2603:10b6:301:14::13) by BL0PR01MB5122.prod.exchangelabs.com (2603:10b6:208:61::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3933.32; Mon, 15 Mar 2021 01:45:27 +0000 Received: from CO1NAM11FT031.eop-nam11.prod.protection.outlook.com (2603:10b6:301:14:cafe::12) by MWHPR1701CA0003.outlook.office365.com (2603:10b6:301:14::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3933.31 via Frontend Transport; Mon, 15 Mar 2021 01:45:27 +0000 Received: from mailscanner.virtbiz.com (208.80.15.114) by CO1NAM11FT031.mail.protection.outlook.com (10.13.174.118) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3933.31 via Frontend Transport; Mon, 15 Mar 2021 01:45:25 +0000 Received: from s18855546.onlinehome-server.com (s18855546.onlinehome-server.com [74.208.193.200]) by mailscanner.virtbiz.com (8.14.7/8.14.7) with ESMTP id 12F1jJOG004539 for ; Sun, 14 Mar 2021 20:45:22 -0500 Received: from mai.hallikainen.org (localhost [127.0.0.1]) by s18855546.onlinehome-server.com (8.14.4/8.14.4) with ESMTP id 12F1jJEe018419 for ; Sun, 14 Mar 2021 18:45:19 -0700 Received: (from apache@localhost) by mai.hallikainen.org (8.14.4/8.14.4/Submit) id 12F1jJmG018416; Sun, 14 Mar 2021 18:45:19 -0700 Received: from 50.206.186.194 (SquirrelMail authenticated user harold) by mai.hallikainen.org with HTTP; Sun, 14 Mar 2021 18:45:19 -0700 From: Harold Hallikainen To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Sun, 14 Mar 2021 18:45:19 -0700 Subject: {Spam?} Re: {Spam?} Re: {Spam?} Re: [PIC] 1 Controller and 18 Peripheral PICs Thread-Topic: {Spam?} Re: {Spam?} Re: {Spam?} Re: [PIC] 1 Controller and 18 Peripheral PICs Thread-Index: AdcZPkMeVCEc+XSmRCyACmgpkmWW7g== Message-ID: <3160a2eedc536e9d2a881c7fb3e8a0d3.squirrel@mai.hallikainen.org> References: <24a1eea7-dbb8-da98-309e-cd4fb87bd4d4@gmail.com> <6d88a2e449f9c633a0ca57efdc178c97.squirrel@mai.hallikainen.org> <800f35305a98ce5ec4f53efcb9a8f057.squirrel@mai.hallikainen.org> <20210315001710.7583ac81@raspberry> <9375cb0d292938db417acf8523e39fa5.squirrel@mai.hallikainen.org> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <9375cb0d292938db417acf8523e39fa5.squirrel@mai.hallikainen.org> 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 mai.hallikainen.org designates 208.80.15.114 as permitted sender) receiver=protection.outlook.com; client-ip=208.80.15.114; helo=mailscanner.virtbiz.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitprod.onmicrosoft.com; s=selector2-mitprod-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=F/C77m7pU8z18GmF0Szu6uKxjj/D8eganKskDne035A=; b=rAw+Ovw0dIM6dwyNdRMhU7ctegXtcKZ9OUBhFgdN7FUgNhrGDaKKJcPBik8upLNO+LmgDJ72GFuyipmPXf7Us2Qs23Yu5ZEEzdh823DgG0E6NO/YYa8UaA0MV6WQAEjGTBVyFK6cjcmlJ50bvPkhr91ApKrwb40q0S4KVpsMbWw= authentication-results: spf=pass (sender IP is 208.80.15.114) smtp.mailfrom=mai.hallikainen.org; mit.edu; dkim=none (message not signed) header.d=none;mit.edu; dmarc=permerror action=none header.from=mai.hallikainen.org; user-agent: SquirrelMail/1.4.22-5.el6 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-authentication-warning: mai.hallikainen.org: apache set sender to harold@mai.hallikainen.org using -f x-spam-status: Yes x-greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mailscanner.virtbiz.com [208.77.216.252]); Sun, 14 Mar 2021 20:45:22 -0500 (CDT) x-topics: [PIC] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 > >>> Another approach that would be interesting to try is to have + supply >>> go to an inductor, then to the LED, then to a FET to ground. Place >>> another LED across the inductor. When the FET is on, the first LED >>> lights as the inductor current ramps up. When the FET opens, the >>> second LED (the one across the inductor) lights as the inductor >>> current ramps down. The inductor saturation current has to be kept >>> high enough and the pulse duration slow enough to ensure the inductor >>> does not saturate. But, this would be efficient (no resistive losses) >>> and pretty minimal on the parts count. You could use a small PIC to >>> drive the FET (maybe even an 8 pin part). >> >> Some careful design would be required. The LED across the inductor >> would need to be wired so that while the FET was conducting the voltage >> across the LED was in reverse direction, so that when the FET stops >> conducting the LED is lit by the 'flyback' current. However it would >> also require some thought about the inductor value to ensure the >> voltage across the inductor is not greater than the max reverse voltage >> of the LED - which would limit the supply voltage to less than the max >> reverse LED voltage. Thinking about this further, we could just have a diode from the bottom of the LED (FET drain) to + supply. When the FET is on, current through the inductor ramps up through the LED and the FET. When off, the current ramps down through the LED and the diode to + supply. Harold --=20 FCC Rules Updated Daily at http://www.hallikainen.com Not sent from an iPhone. --=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 .