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; Sat, 13 Mar 2021 18:01:20 -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 12E1qNZF025252; Sat, 13 Mar 2021 20:53:05 -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 12E1qMC0025249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Sat, 13 Mar 2021 20:52:22 -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 12E1qI9c001634 for ; Sat, 13 Mar 2021 20:52:22 -0500 Received: from oc11expo16.exchange.mit.edu (18.9.4.47) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 13 Mar 2021 20:52:12 -0500 Received: from w92exhyb4.exchange.mit.edu (18.7.71.74) by oc11expo16.exchange.mit.edu (18.9.4.47) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 13 Mar 2021 20:52:18 -0500 Received: from NAM11-CO1-obe.outbound.protection.outlook.com (104.47.56.174) by w92exhyb4.exchange.mit.edu (18.7.71.74) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Sat, 13 Mar 2021 20:52:18 -0500 Received: from BN8PR15CA0039.namprd15.prod.outlook.com (2603:10b6:408:80::16) by PH0PR01MB6794.prod.exchangelabs.com (2603:10b6:510:75::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3933.32; Sun, 14 Mar 2021 01:52:17 +0000 Received: from BN8NAM11FT029.eop-nam11.prod.protection.outlook.com (2603:10b6:408:80:cafe::76) by BN8PR15CA0039.outlook.office365.com (2603:10b6:408:80::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3933.31 via Frontend Transport; Sun, 14 Mar 2021 01:52:16 +0000 Received: from mailscanner.virtbiz.com (208.80.15.114) by BN8NAM11FT029.mail.protection.outlook.com (10.13.177.68) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3933.31 via Frontend Transport; Sun, 14 Mar 2021 01:52:16 +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 12E1qBdo029577 for ; Sat, 13 Mar 2021 19:52:13 -0600 Received: from mai.hallikainen.org (localhost [127.0.0.1]) by s18855546.onlinehome-server.com (8.14.4/8.14.4) with ESMTP id 12E1qBBH005059 for ; Sat, 13 Mar 2021 17:52:11 -0800 Received: (from apache@localhost) by mai.hallikainen.org (8.14.4/8.14.4/Submit) id 12E1qAbx005056; Sat, 13 Mar 2021 17:52:10 -0800 Received: from 174.198.129.170 (SquirrelMail authenticated user harold) by mai.hallikainen.org with HTTP; Sat, 13 Mar 2021 17:52:10 -0800 From: Harold Hallikainen To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Sat, 13 Mar 2021 17:52:10 -0800 Subject: {Spam?} Re: [PIC] 1 Controller and 18 Peripheral PICs Thread-Topic: {Spam?} Re: [PIC] 1 Controller and 18 Peripheral PICs Thread-Index: AdcYde3vpxo5v7jLQGaDdFR8Mod/WQ== Message-ID: <800f35305a98ce5ec4f53efcb9a8f057.squirrel@mai.hallikainen.org> References: <24a1eea7-dbb8-da98-309e-cd4fb87bd4d4@gmail.com> <6d88a2e449f9c633a0ca57efdc178c97.squirrel@mai.hallikainen.org> 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: TempError 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=+LF5wSXj1RqLjOjbeW7qf8EZreQVJNIMV4JKsVByWZU=; b=GJbrv9yNTK44tEMK4YGemxN8xrWDBZUwFJNnpwjWgQgqwTiGwx+C2+iVYlOZZX6SobvcGredlGBa94ZtCC6Ehf0TQCLetwHfisfTsI2PHatNGgG1U/+cohtaBDwXfBBH4kLtmMUDy5sPAew+ePZks/xusPkWc20wsAeOgetJJdo= 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]); Sat, 13 Mar 2021 19:52:13 -0600 (CST) x-topics: [PIC] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Ah, I did not realize you needed 700 mA per LED. I think the TI part was good for 40 mA. I once did a strobe light system for motorcycles where I used an LM317 as a constant current generator then had several series strings of LEDs with a FET to ground on each string. The PIC drove the FET to light the appropriate string. These were high power camera flash LEDs. Is the voltage source and LED drop constant enough that you could just use a series current limit resistor? Not very efficient, but any linear regulation method is going to also be inefficient. In another project (a dental composite curing light), I used a switching boost converter. The LED took something like 7V at 1.5A. I added a current sense amplifier and fed the output of that back into the boost converter feedback pin. The LED current could be varied by adjusting the reference pin voltage. 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). The internal RC oscillator is definitely good enough for SPI since SPI provides a clock. Also, I think the internal RC oscillators are generally good for 1%, which is good for many applications (but not USB). Besides SPI, you might consider using the UART. That requires only one wire for one way transmission. You could send packets that address individual PICs. As with reflections on a clock line, reflections on a UART line could be an issue. I'd use a separate driver (with series source termination) at the master to drive the lines to all the other PICs. Good luck! Harold https://w6iwi.org --=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 .