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; Mon, 6 Apr 2020 23:27:04 -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 0376HW9q010643; Tue, 7 Apr 2020 02:18:02 -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 0376HUc8010631 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 7 Apr 2020 02:17:31 -0400 Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 0376HG8V004946 for ; Tue, 7 Apr 2020 02:17:16 -0400 Received: from w92expo9.exchange.mit.edu (18.7.74.63) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 7 Apr 2020 02:16:41 -0400 Received: from oc11exhyb3.exchange.mit.edu (18.9.1.99) by w92expo9.exchange.mit.edu (18.7.74.63) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 7 Apr 2020 02:17:30 -0400 Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.172) by oc11exhyb3.exchange.mit.edu (18.9.1.99) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 7 Apr 2020 02:17:29 -0400 Received: from DM5PR16CA0027.namprd16.prod.outlook.com (2603:10b6:4:15::13) by DM5PR0102MB3573.prod.exchangelabs.com (2603:10b6:4:9e::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.21; Tue, 7 Apr 2020 06:17:29 +0000 Received: from DM3NAM03FT029.eop-NAM03.prod.protection.outlook.com (2603:10b6:4:15:cafe::d5) by DM5PR16CA0027.outlook.office365.com (2603:10b6:4:15::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.15 via Frontend Transport; Tue, 7 Apr 2020 06:17:29 +0000 Received: from mail-ed1-f44.google.com (209.85.208.44) by DM3NAM03FT029.mail.protection.outlook.com (10.152.82.194) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.15 via Frontend Transport; Tue, 7 Apr 2020 06:17:28 +0000 Received: by mail-ed1-f44.google.com with SMTP id i16so2551339edy.11 for ; Mon, 06 Apr 2020 23:17:28 -0700 (PDT) From: David C Brown To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Mon, 6 Apr 2020 23:17:15 -0700 Subject: Re: [EE]: Bi-Colour status LED Thread-Topic: [EE]: Bi-Colour status LED Thread-Index: AdYMpY4bhQFyzE8LT4m9/12s98jU0A== Message-ID: References: <5E8BF616.17802.639BB839@brent.eds.co.nz> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <5E8BF616.17802.639BB839@brent.eds.co.nz> 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 gmail.com designates 209.85.208.44 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.208.44; helo=mail-ed1-f44.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=0JBc/AzaBjvYnfRnSHAg1Oq0TW7nq9r3DDMcnMsFSog=; b=PyWvDt0QfYDEkACP+fST9O8KCGtSadiJwuwp7sJ+qvQ/0uwjtK63DUoXpfz8tJ/e3e RZoKDjj1gKXPtv8MwuH6apW8ASbeH1S9ee1pe70H+adEC8iFj8qJLffSVSriKbyjK5io CfRZwYpZKk66l6EBa5/iCMDqFeuvEyN8KIJShqsHX2dp20B70VsRnCOCGnYqajiQHvCT sVSJS2dQ6K6kS9ZkKkSGpSjAkU1HSn58Emz7slsxtJRckFGq6Kz1zEk+iHui2Fz+VZxt tYxXpfyDkWa+kx6RUngEtk0pBT7JBRTZXZ8PhDENDuvJvJKkmHDJiTdP5YD8XjGAdc1t Anqw== authentication-results: spf=pass (sender IP is 209.85.208.44) 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;compauth=pass reason=100 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:906:3f88:: with SMTP id b8mr516814ejj.301.1586240247388; Mon, 06 Apr 2020 23:17:27 -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 Or, without the capacitor you could have shades of yellow. __________________________________________ David C Brown 43 Bings Road Whaley Bridge High Peak Phone: 01663 733236 Derbyshire eMail: dcb.home@gmail.com SK23 7ND web: www.bings-knowle.co.uk/dcb *Sent from my etch-a-sketch* On Tue, 7 Apr 2020 at 04:41, Brent Brown wrote: > Interest only, I must have too much time on my hands... > > Todays brain exercise was how to add a red/green status indicator to an > existing > product. There is an available RS232 port, and firmware mods are feasible= .. > The > LED is required to be off when the power is off, green when functioning > correctly, > and flashing red when there is a fault. > > Attached circuit is I think about as simple as it can be. The LED is on > solid Red > when the power is on but no data is being transmitted, i.e. during bootup= , > due to the > idle state of TxD being -ve. Could flip the LED and make the default Gree= n > if that > were desired. LED can be set to red/green/off simply by changing the data > being > sent. Flashing shouldn't be too difficult. For extra marks dimming is > possible. > > -- > 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 .