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, 8 Nov 2021 16:56:04 -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 1A90hp2N002058; Mon, 8 Nov 2021 19:44:53 -0500 Received: from outgoing-exchange-3.mit.edu (OUTGOING-EXCHANGE-3.MIT.EDU [18.9.28.13]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 1A90hn3b002054 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Mon, 8 Nov 2021 19:43:49 -0500 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-3.mit.edu (8.14.7/8.12.4) with ESMTP id 1A90hm4Z008994 for ; Mon, 8 Nov 2021 19:43:49 -0500 Received: from oc11expo31.exchange.mit.edu (18.9.4.104) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1497.24; Mon, 8 Nov 2021 19:43:17 -0500 Received: from w92exhyb5.exchange.mit.edu (18.7.71.110) by oc11expo31.exchange.mit.edu (18.9.4.104) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Mon, 8 Nov 2021 19:43:48 -0500 Received: from NAM11-BN8-obe.outbound.protection.outlook.com (104.47.58.171) by w92exhyb5.exchange.mit.edu (18.7.71.110) with Microsoft SMTP Server (TLS) id 15.0.1497.24 via Frontend Transport; Mon, 8 Nov 2021 19:43:48 -0500 Received: from CO2PR04CA0121.namprd04.prod.outlook.com (2603:10b6:104:7::23) by BL0PR01MB4340.prod.exchangelabs.com (2603:10b6:208:81::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4669.13; Tue, 9 Nov 2021 00:43:42 +0000 Received: from CO1NAM11FT042.eop-nam11.prod.protection.outlook.com (2603:10b6:104:7:cafe::c) by CO2PR04CA0121.outlook.office365.com (2603:10b6:104:7::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4669.10 via Frontend Transport; Tue, 9 Nov 2021 00:43:42 +0000 Received: from mail-yb1-f181.google.com (209.85.219.181) by CO1NAM11FT042.mail.protection.outlook.com (10.13.174.250) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4669.10 via Frontend Transport; Tue, 9 Nov 2021 00:43:42 +0000 Received: by mail-yb1-f181.google.com with SMTP id d10so48450485ybe.3 for ; Mon, 08 Nov 2021 16:43:41 -0800 (PST) From: Justin Richards To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Mon, 8 Nov 2021 16:43:29 -0800 Subject: Re: [EE]: Sony LED TV repair update KD-60X6700E. 50 backlight LEDs in series. Thread-Topic: [EE]: Sony LED TV repair update KD-60X6700E. 50 backlight LEDs in series. Thread-Index: AdfVBJNDixbcjA2fSuW7MS8UkarTuA== Message-ID: References: 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: Pass (protection.outlook.com: domain of gmail.com designates 209.85.219.181 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.219.181; helo=mail-yb1-f181.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ivKKkYtV+gtaUpuZeZfxgwiE8X4IMulNzU454I20kbw=; b=cWI1m/6CB+z8VQvJad1nECb7jy21be2nKY3DBZk9a3yEiFF7RmD6Z1xaIEBdyCmpFi EeWMt5ASKrJx9zUMF+4BA1OxNT+HIWR5qYYfSayl6RKeTNvgXjUGIXQFG+4s/pF0MCWQ UnDc9zd4WOO7llCZShPDpUT1cWl0ptvBO/NHu2TBV70vu/NJCOT7QNhX8UNiPKZRBgNN xqFKEEbkJZhG1k6mDYTdLn30IRzxY+RCF1bauFfAfSZt9xZvSZgG7ghFVcvpEcnLItxd K9GrCXr4ROLjcqvmtgRX9Rm2dAG1LCPMFw/mxVjNgyOf9XGnNfGN9kyCdFo5RnN508rm p6Hg== authentication-results: spf=pass (sender IP is 209.85.219.181) 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:a25:4290:: with SMTP id p138mr3606437yba.498.1636418620859; Mon, 08 Nov 2021 16:43:40 -0800 (PST) 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 Sean, Interesting results from your experiment, It adds a little weight to my suspicions particularly that they heal but not permanently. The failure within hours of each other is also curious. Its $50 to find out and in the meantime I am going to setup a bench PSU to continuously cycle on/off individual strips and monitor for failures. I know the current the TV drives them at, but I am curious what rating the manufacturer has given them. For what could be considered a simple two legged device they do have a spectrum of failure modes. At work we have several that fail flashing. They were ordained as suitable low RF noise incandescent replacements but I suspect they might not pass if they are in one of their many and varied failure modes. Justin On Tue, Nov 9, 2021 at 3:16 AM Sean Breheny wrote: > Interesting problem! > > I suspect you are correct about capacitance causing the flash. > > I once worked on a product which used blue LEDs as indicators and it was > important that they had a consistent brightness (so that they didn't look > different from each other when all were on, which was the normal state - > off indicated a problem). We had a problem with these LEDs either failing > entirely or going dim after some time in service. In the end it turned ou= t > to be an ESD problem during assembly but before we knew that, we had a > question about whether the problem could have been caused by temporary > overcurrent on the LEDs because we had a problem early-on where we had be= en > running them at too high a current before we swapped out the driver board= - > and this had affected hundreds of units in the field so we couldn't just > preemptively replace the LEDs themselves. > > To answer whether the observed misbehavior could have been caused by > overcurrent, we set up an experiment where we ran 10 LEDs each at 5 > different current levels (from my memory): 100% nominal, 150% nominal, 20= 0% > nominal, 300% nominal, and 400% nominal. Nominal was the maximum > recommended continuous current. We continued to run the experiment for > about a year - even after we had solved the fundamental problem with ESD > precautions. 100% never failed. 400% all failed completely within hours o= f > each other after about 3 or 4 days. But the really interesting thing was > the tremendous variation in the fate of the intermediate units. Some even > up to 200% never failed. But some failed open. Some stopped producing lig= ht > but still drew current (I don't recall what the voltage drop was). Some > became dim while still drawing the same current. Some became intermittent > where wiggling the leads would cause them to flicker (surprising that > stress could be so easily transmitted through the epoxy body). Some were > intermittent where no external influence seemed to start or stop the > intermittency - it was something purely internal. > > I will say that I don't think we ever saw one with any type of failure > which "fixed" itself permanently. Some stopped producing light and then > started making light again, but there was always intermittency later, too= .. > > Sean > > > On Mon, Nov 8, 2021 at 1:55 AM Justin Richards > wrote: > > > Thought this may be interesting or someone may have experienced > > similar with self repairing LED's > > > > Has anyone experienced strange failure modes of LED's where they > > randomly open circuit but then randomly behave like normal LEDs after > > perhaps welding the bond wires short again. > > > > I initially expected to find shorted LEDs but after doing a complete te= ar > > down all the LED's are now operating normally with volt drops ranging > from > > 2.98v - 3.45v. And purposely shorting out LEDs has no effect. i.e. T= he > > system continues to work fine, the compliance voltage simply drops by 3= v > > each time implying the PSU is doing a good job as a const curr source. > > > > I think there is a LED or two that has failed open but when hit with a > > sudden voltage rise from 0 - ~200v welds itself shut then after some > > heating/cooling cycles it or another one fails. > > > > Is that plausible? Many videos doing similar repair only ever seem to > find > > failed LED strips and works fine once they have been replaced. > > > > Another interesting observation is after disconnecting one of the strip= s. > > As mentioned they are all in series, however, in this mode they briefly > > flash when powered on which should not be possible. I am guessing the > > capacitive effect of the cabling provides for a small current to flow > with > > such a high dv/dt. This brief flash looks very similar to the flash wh= en > > the TV fails to power on and hence the reason for my crazy theory. > > > > Other info .. > > > > The TV worked for a short time with a NTC thermistor in series with the > > LEDs. > > > > As it failed again I have dis-ssembled expecting to find some failed > LEDs. > > However, during testing it randomly powered on and has since been rock > > solid. > > > > I have taken many measurements but here are the key parameters while it= s > > running ok > > > > 50 LEDs all in series with a compliance voltage of 165VDC and a current > of > > 540mA. > > > > The compliance voltage increases and current is roughly stable at aroun= d > > 540mA.taking measurements while increasing a variable resistor in seri= es > > with the LEDs. > > > > Justin > > -- > > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > > View/change your membership options at > > http://mailman.mit.edu/mailman/listinfo/piclist > > > -- > 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 .