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, 3 Aug 2020 17:09:21 -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 07400rso025244; Mon, 3 Aug 2020 20:01:04 -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 07400qG2025232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 3 Aug 2020 20:00:52 -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 073NxPuk026046 for ; Mon, 3 Aug 2020 19:59:25 -0400 Received: from w92exhyb8.exchange.mit.edu (18.7.71.113) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Mon, 3 Aug 2020 20:00:15 -0400 Received: from oc11exhyb7.exchange.mit.edu (18.9.1.112) by w92exhyb8.exchange.mit.edu (18.7.71.113) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 3 Aug 2020 20:00:51 -0400 Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.171) by oc11exhyb7.exchange.mit.edu (18.9.1.112) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Mon, 3 Aug 2020 20:00:51 -0400 Received: from MW2PR16CA0018.namprd16.prod.outlook.com (2603:10b6:907::31) by MN2PR01MB6031.prod.exchangelabs.com (2603:10b6:208:17b::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.18; Tue, 4 Aug 2020 00:00:49 +0000 Received: from CO1NAM03FT015.eop-NAM03.prod.protection.outlook.com (2603:10b6:907:0:cafe::79) by MW2PR16CA0018.outlook.office365.com (2603:10b6:907::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.18 via Frontend Transport; Tue, 4 Aug 2020 00:00:49 +0000 Received: from mail-ej1-f45.google.com (209.85.218.45) 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.3239.20 via Frontend Transport; Tue, 4 Aug 2020 00:00:49 +0000 Received: by mail-ej1-f45.google.com with SMTP id a26so14664452ejc.2 for ; Mon, 03 Aug 2020 17:00:49 -0700 (PDT) From: RussellMc To: Microcontroller discussion list - Public. CC: ApptechNZ Sender: "piclist-bounces@mit.edu" Date: Mon, 3 Aug 2020 17:00:10 -0700 Subject: Re: [EE] "Sunlight" brand LEDs Thread-Topic: [EE] "Sunlight" brand LEDs Thread-Index: AdZp84EUrQhH3NpTThGP0Wo67Q7Quw== Message-ID: References: <5F28A038.9060203@narwani.org> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <5F28A038.9060203@narwani.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 gmail.com designates 209.85.218.45 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.218.45; helo=mail-ej1-f45.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 :cc; bh=iTvzLnSKDWKVqoTpu25NJ0qYhUkCDxNg5djHmYMsW4Y=; b=TdJGF3itqH3gPi0aDsXIRn5JTaZFAwAVXRMveFoIKO9xliWtfrQ0BMQVI3PVpIDSWQ ds29xZlGI2bH0osmm9E2tFUXiZwAL8OroaSE0Vtav4VRuReqeERCNbQ9R9Yw0zZERGTO Fs/3KiiVnqjsw23FM+jS5QrPZXTH92Zrt2ze3uzYdHt/n8nrKRc+cI143xJEftuGNJ9r wGab/2+UUN6DlszOsZTHciuSzFALupzfQsTEQEZ9ePRM+5xZCRYw6whXEKfrcar00do3 ZLn5glXjqtPc5G5Ery9KfL2sbJNYM1oVerBd3SgwjA085TyiEQqZcHp3/dXZixu8r3+i 9RlA== authentication-results: spf=pass (sender IP is 209.85.218.45) 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:906:4c97:: with SMTP id q23mr5907360eju.11.1596499247483; Mon, 03 Aug 2020 17:00:47 -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 On Tue, 4 Aug 2020 at 11:41, Neil wrote: > Anyone have any mid-to-long-term experience with "Sunlight" brand > 7-segment LED displays? > Looking at these for a long product as the Lite-On LEDs I've used to > date are in short supply, being discontinued. And the ones I found from > a broker were counterfeits, which have cost me considerably. > Hence, looking for any reviews anyone can provide. > > I have NO experience of them. Chinese LEDs seem to generally be of substantially higher longevity in most cases than when I used them in largish volume around 10 years ago. However, if Lite-On fakes are problematic then other names also may be. Depending on what the issues are and what time you have available you may be able to carry out longevity testing yourself. At 168 hours/week, ~ 700 hrs/month you may start to get lifetime indications in a useful time period when operated at top end currents. Output often rises initially. I placed LED strings in series with a constant current source (say 10 LEDs) plus a switchable reference in series - usually shorted out. Occasional output checks using a lashup "integrating cone" and light meter and multiple strings allowed early degradation to easily be seen. Russell _SNS _LED --=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 .