Notifications
Clear all

Pixel Burn In

6 Posts
5 Users
0 Reactions
2,637 Views
Posts: 126
Topic starter
(@thechief96)
Estimable Member
Joined: 11 years ago
[#41050]

I have seen a mention or two on burning in pixels. Can someone give me the reason why and the procedure to do it?


5 Replies
Posts: 335
(@cdanna77)
Reputable Member
Joined: 12 years ago

Better to find failures before they go out into the display. Easier to repair this way.


Reply
Posts: 126
Topic starter
(@thechief96)
Estimable Member
Joined: 11 years ago

Thanks for the reason, which makes perfect sense, now how is it done?
Thanks


Reply
TazChaLet
Posts: 3042
(@tazchalet)
Famed Member
Joined: 13 years ago

depends on what controller you are using some have built in test patterns I used xlights test and ran it let it run for hours in a rbgw test and see if anything goes wrong I did this for several days before I built my tree


Reply
jchuchla
Posts: 8698
(@jchuchla)
Illustrious Member
Joined: 15 years ago

Burn in is just a slang term we use to refer to a testing and inspection process. All mass produced products have a potential for DOA units or problems related to inconsistent human assembly. The cheaper the product the higher the failure rate. So burning in is just a process of discovering these problems so that they can be fixed before you put them in a place where you don't want to work on them.
The most common failures happen in the more extreme regions of the operating range. When I test them, I like to hang them out by their own wires and run them at full white for a period, and also at full strobe for a while. Hanging them tests the physical wire connections to the pixels. If there's going to be a strain related issue, this will help reveal it. Full white tests the power handling at max load. This will make them run as hot as they'll get. This will usually get the single color failures to show up.
Strobing is a way to reveal data integrity problems. This creates a ton of line noise. If there's going to be a data integrity problem, it will most likely show up on fast transitions and when they're regularly repetitive, it's easier to see the problems.
Other good tests are for waterproofing and temperature. I've heard of some people testing pixels by running them in a bucket of water. I've also seen them frozen into a block of ice. I don't do these tests because I'm not really equipped to freeze them. But I do think it's a great idea. Many of my problems can be traced down to water and thermal cycling issues.
As to the testing duration, you need to make sure the test is long enough to actually create the conditions to reveal the problems. This is generally measured in days. I run my all white tests for usually over a week. Just plug them in and put them back in the box running and come back in a week to mark the bad bulbs so they can be fixed before using them. Then right before assembly I'll do the hanging and physical stress tests if it applies.

--Jon Chuchla--

Sent from my iPhone using Tapatalk


Reply
Posts: 486
(@uncledan)
Honorable Member
Joined: 11 years ago

Learn something new everyday. I tested everything but never went to this extreme. I think I had maybe 5 failures out of 10,000+ pixels and dumb rgb. Guess I'll find out next year when they all fail lol


Reply
Share: