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, 4 Aug 2020 16:33:17 -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 074NNOnq026115; Tue, 4 Aug 2020 19:23:55 -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 074NNNdJ026092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 4 Aug 2020 19:23:23 -0400 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 074NKsat006409 for ; Tue, 4 Aug 2020 19:21:28 -0400 Received: from w92expo30.exchange.mit.edu (18.7.74.42) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 4 Aug 2020 19:22:24 -0400 Received: from oc11exhyb6.exchange.mit.edu (18.9.1.111) by w92expo30.exchange.mit.edu (18.7.74.42) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 4 Aug 2020 19:22:57 -0400 Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.106) by oc11exhyb6.exchange.mit.edu (18.9.1.111) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 4 Aug 2020 19:22:57 -0400 Received: from MWHPR04CA0070.namprd04.prod.outlook.com (2603:10b6:300:6c::32) by DM6PR01MB4778.prod.exchangelabs.com (2603:10b6:5:6d::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.21; Tue, 4 Aug 2020 23:22:55 +0000 Received: from CO1NAM03FT026.eop-NAM03.prod.protection.outlook.com (2603:10b6:300:6c:cafe::41) by MWHPR04CA0070.outlook.office365.com (2603:10b6:300:6c::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.16 via Frontend Transport; Tue, 4 Aug 2020 23:22:53 +0000 Received: from mail-ed1-f53.google.com (209.85.208.53) by CO1NAM03FT026.mail.protection.outlook.com (10.152.80.162) 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 23:22:53 +0000 Received: by mail-ed1-f53.google.com with SMTP id o18so16706449eds.10 for ; Tue, 04 Aug 2020 16:22:53 -0700 (PDT) From: RussellMc To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Tue, 4 Aug 2020 16:22:13 -0700 Subject: Re: [EE] "Sunlight" brand LEDs Thread-Topic: [EE] "Sunlight" brand LEDs Thread-Index: AdZqt6HYwODbUGZ1Th+3NnDSLigi/Q== Message-ID: References: <5F28A038.9060203@narwani.org> <5F296D3B.7010705@narwani.org> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <5F296D3B.7010705@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: 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.53 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.208.53; helo=mail-ed1-f53.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=LL0znxFt5wBf1hcdzIwdlX8R35wTiVEakmm5/PAc2Wk=; b=GV6V2fmU+M7oR9jifVYCIAWCEY6i0KkYUlriO3n0vmhcIRIZVqQsfm73S+hX4Wi31l RIGQhw2/9X99QsKK9ksF+MA+yOOOgXWmO7f6+1YDVmvGVE3VEqNlRisJDilaRge5wZ+i +lLv2m8Nu5C0PJL02oCrZ602ExITnm2chft8XfnYy0cBTCglDPuh8dz1x+FLB5DkaZMA 5uH3ZenPAWXYdNY7Uwy8lwuNShO1VpdezdNDyPwW5DxngrVmo21Bt5e6XmyHhNOmme7h U6l01hS+Hpa53QcaINM+VR/DZ/44Xbp/UjnhvPTqQWr+qJSPCMazy604IBM0B1f2YF3P qgbQ== authentication-results: spf=pass (sender IP is 209.85.208.53) 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:a05:6402:1d92:: with SMTP id dk18mr287738edb.206.1596583370834; Tue, 04 Aug 2020 16:22:50 -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 Wed, 5 Aug 2020 at 02:16, Neil wrote: > The failures I had with the counterfeits were random segments failing > within weeks, months or more, and replacing a 12-pin through-hole > display on a very tight PCB was a very difficult task, so the boards had > to be replaced. > 1. Possible source. May be about as reputable as any of the Asian sources https://lcsc.com/products 2. There are too many variables known only to you or not known at all to offer anything like certain advice. Depending on quantity involved, acceptability or possibility of redesign, time available, knowledge of failure environments my approach MIGHT include these semi random thoughts: Any possible clues from environment? - temperature cycling or extremes, vibration, hours of use, voltages, ... Soldering temperature or profile affected? Could torture test bad units to see if relevant. Are old "bad" versions available for comparison testing? Are mechanical aspects a factor - twisting or differential cooling or vibration or ... ? (Not directly relevant, but as an example, small slices from PV panel wafers have stress issues which many manufacturers seem unaware of). Test rig? High end currents? On off cycling? Whole power supply square wave? Hot cold cycling - maybe in and out of refrigerator every day or so while running? Vibration ? Doable "simply enough" if liable to be relevant. I can envisage a module with N displays, mounted on a woofer to provide vibration, cycled on and off grossly and powered on long enough wires to allow it to be moved in and out of a refrigerator easily. Mix of liteon (1 or 2), old bad units (few), Sunlight samples. Not overly "controlled"- but at 3 hours/day usual operation (if on time is relevant) that gives you 8 months per month. ANY segment failures are probably too many. Statistical rule of thumb is if you get no results in N samples then actual figure is - hmm - mind says either < 1 in N/3 or < 1 in 3N. If that sounds of relevance it can be checked. Russell > --=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 .