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; Tue, 7 Apr 2020 14:25:41 -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 037LFRn3008955; Tue, 7 Apr 2020 17:15:58 -0400 Received: from outgoing-exchange-5.mit.edu (OUTGOING-EXCHANGE-5.MIT.EDU [18.9.28.59]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 037LFPEp008935 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 7 Apr 2020 17:15:25 -0400 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 037LFQil011526 for ; Tue, 7 Apr 2020 17:15:30 -0400 Received: from w92exhyb8.exchange.mit.edu (18.7.71.113) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 7 Apr 2020 17:14:39 -0400 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by w92exhyb8.exchange.mit.edu (18.7.71.113) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 7 Apr 2020 17:15:04 -0400 Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.108) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 7 Apr 2020 17:15:04 -0400 Received: from MWHPR08CA0060.namprd08.prod.outlook.com (2603:10b6:300:c0::34) by BYAPR01MB4118.prod.exchangelabs.com (2603:10b6:a03:10::16) 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 21:15:03 +0000 Received: from CO1NAM03FT015.eop-NAM03.prod.protection.outlook.com (2603:10b6:300:c0:cafe::80) by MWHPR08CA0060.outlook.office365.com (2603:10b6:300:c0::34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.20 via Frontend Transport; Tue, 7 Apr 2020 21:15:03 +0000 Received: from mail-pg1-f171.google.com (209.85.215.171) by CO1NAM03FT015.mail.protection.outlook.com (10.152.80.167) 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 21:15:02 +0000 Received: by mail-pg1-f171.google.com with SMTP id c5so2315881pgi.7 for ; Tue, 07 Apr 2020 14:15:02 -0700 (PDT) Received: from [192.168.1.5] (118-93-176-83.dsl.dyn.ihug.co.nz. [118.93.176.83]) by smtp.gmail.com with ESMTPSA id l18sm13983466pgc.26.2020.04.07.14.14.59 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Apr 2020 14:15:00 -0700 (PDT) From: Brent Brown To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Tue, 7 Apr 2020 14:14:56 -0700 Subject: Re: [EE]: Bi-Colour status LED Thread-Topic: [EE]: Bi-Colour status LED Thread-Index: AdYNIxeGpllWPSdFTX2gWQQ8mAYwbw== Message-ID: <5E8CED50.406.676176A1@brent.eds.co.nz> References: <5E8BF616.17802.639BB839@brent.eds.co.nz>, 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: None (protection.outlook.com: eds.co.nz does not designate permitted sender hosts) dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eds-co-nz.20150623.gappssmtp.com; s=20150623; h=from:organization:to:date:mime-version:subject:message-id:priority :in-reply-to:references:content-transfer-encoding :content-description; bh=LuaKF3IDztouVBq4uevk/da1uMSUWtbyes4sJOa6gOc=; b=E7mpxjg3iOn3bHDbZN5KBKDAd6QJh0Kd+fSt2OAM2RT7Vwuv1EIVp8aZm8u6Y92hwq iw8WlCet8Qw8gioCBVh+HqSR1fr6iS04XJDqBcNCNg/zYTVyeESu5G9xTOYQlTb0u1dw hp05Px0/CtNZ4I4Ujb6qMYgomQNvTwUH76no4t5hdhhTxY/Gg8/hXAM6Uawx525G6ZnR AI9CCSfTIY/mYSX+yakvpYJnsfpThC34RYl2QAdFIF6Zki04YSiC3oxTtxBzs3qXZq9v yBBIr2ETCILrl79bE/svZkXw1YT53ei4A06Y41PdDj0qOBJGz5dycREkqXRUTZI5S2vv T4qw== authentication-results: spf=none (sender IP is 209.85.215.171) smtp.mailfrom=eds.co.nz; mit.edu; dkim=pass (signature was verified) header.d=eds-co-nz.20150623.gappssmtp.com; mit.edu; dmarc=none action=none header.from=eds.co.nz; 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:a62:52d7:: with SMTP id g206mr4584579pfb.286.1586294101636; Tue, 07 Apr 2020 14:15:01 -0700 (PDT) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Yes, good point. Without the cap only shades of orange/yellow are possible.= ... it=20 would be impossible to hold either LED off for longer than one character ti= me (start=20 and stop bits always illuminate one or other of the LEDs). In the no capacitor case you can loose the resistor too... LED current reli= es on the=20 RS232 driver current limiting (~10mA). Here I only had discrete red and green LEDs, not an actual Bi-Colour LED. A= iming=20 for fully Red, fully Green, and fully Off states I chose RC values to minim= ise flicker=20 and show no light at all from the off LED(s). Baud rate can be increased to decrease capacitor size/cost, but that means = less=20 time between UART characters so CPU overhead increases... may or may not be= =20 significant. On 7 Apr 2020 at 7:17, David C Brown wrote: > Or, without the capacitor you could have shades of yellow. > > On Tue, 7 Apr 2020 at 04:41, Brent Brown wrote: >=20 > > 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 feasib= le. > > 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 boot= up, > > due to the > > idle state of TxD being -ve. Could flip the LED and make the default Gr= een > > if that > > were desired. LED can be set to red/green/off simply by changing the da= ta > > being > > sent. Flashing shouldn't be too difficult. For extra marks dimming is > > possible. --=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 .