News:

Server migration complete, Welcome to version 2.1.1

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 15659
Latest: PaulDzRGB
New This Month: 9
New This Week: 3
New Today: 1
Stats
Total Posts: 128430
Total Topics: 15791
Most Online Today: 68
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 3
Guests: 25
Total: 28

How to detect a Ws2811 bad pixel

Started by MikelMD, October 23, 2018, 10:33:54 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

MikelMD

Hi all, I have a string of 23 WS2811 pixels and after number 13, no pixels light up.  I have confirmed it is not a configuration issue, I used a spare set of lights and all 23 light up.  So, how do I figure out which pixel is the culprit?

Bwinter

It could either be pixel 13 (it lights up okay, but failing to send out data to pixel 14) or it could be pixel 14.  On the rare occasions I've encountered, this, I've snipped out both pixels and the rest of the strip has been fine.

jnealand

I usually cut after the last pixel and then using my test rig I use alligator clips to connect to the first pixel not lighting up and see if the string works from that point on.  If the cutoff part works then it would be the last pixel lighting up that is not sending data forward.   Also in many cases a real close inspection of the wire between the working and non working part may reveal a bad connection/loose wire.  Found two of those just last week as I was testing some of my older lights before putting them up.  Actually these were lights that I have used the last 5 years so got pretty good used out of them.
Jim Nealand
Kennesaw, GA all Falcon controllers, all 12v Master Remote Multisync with Pi and BBB P10 and P5

rstehle

On every Pixel failure I have ever had, the culprit has always been the first pixel that doesn't light.

algerdes

I follow the same procedure as Jim.  Break the line before the first one that does not light up.  Connect a "test" string of pixels (with alligator clips) and see if they light correctly. If so, the first one that doesn't light is the culprit.  If not, the last of the lit pixels is not sending, and it goes into the bin.


One thing I found handy was to make a "test" string of at least 4 or 5 pixels. 


Of course, if it is cold enough - or there isn't enough time to do troubleshooting - both the last lit and the first not-lit go to the bin. 
Sequencers: Vixen3 and xLights
Players: FPP and xSchedule Controllers:  Renards - SS24/SS16; E1.31 - San Devices E682 - Falcon F16, F4, F48 - J1Sys - DIYLEDExpress E1.31 Bridges.  Much more!

Support FPP

+- Recent Topics

F16V3 with 2 expansion boards at 40 fps MAX PIXELS per output? by tbone321
Today at 10:51:55 AM

F48V4-NS at 40 fps using all 48 pixel output ports? by Poporacer
Today at 10:27:09 AM

Unable to update RPi 5.5 to latest version by JonB256
February 05, 2023, 07:23:16 PM

help getting started, next step? by rayster
February 05, 2023, 04:24:09 PM

Warning/Error: Network incomplete frames hit 250. by darylc
February 05, 2023, 04:06:58 PM

F48v4NS - Pi or No Pi? by joeyblasko
February 05, 2023, 09:15:33 AM

Huidu Controllers LED matrix by CaptainMurdoch
February 04, 2023, 10:18:47 AM

FPP6.2 universes by darylc
February 03, 2023, 08:48:57 PM

F16v4 Ports vs Universe Configuration Question by k6ccc
February 03, 2023, 09:32:48 AM

Need Expert Advise on F16v4 Ports vs Universe Configuration by Kairus
February 03, 2023, 09:32:33 AM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod