News:

LATEST RELEASE:  FPP 6.3 - Download from here - https://github.com/FalconChristmas/fpp/releases/tag/6.3

+-+-

+-User

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

+-Site Stats

Members
Total Members: 15736
Latest: richardrons076
New This Month: 3
New This Week: 3
New Today: 1
Stats
Total Posts: 129006
Total Topics: 15889
Most Online Today: 127
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 2
Guests: 126
Total: 128

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

Raspberry PI 4 b fan by JonB256
June 07, 2023, 09:30:09 AM

Advatek Vortex 48 channel DC controller by k6ccc
June 06, 2023, 09:31:41 AM

RS485 CAN HAT for DMX by MikeKrebs
June 05, 2023, 09:18:04 PM

colorlight 5a-75b not working with raspberry pi4B fpp by Kensington Graves
June 05, 2023, 10:09:36 AM

Multi Channel Audio by dkulp
June 05, 2023, 09:30:24 AM

Wifi help by dkulp
June 04, 2023, 12:24:56 PM

MMAL error 2 "ENOSPC" by MikeKrebs
June 03, 2023, 09:34:36 PM

Dmx by MikeKrebs
June 03, 2023, 08:53:35 PM

F48V4-NS at 40 fps using all 48 pixel output ports? by MikeKrebs
June 02, 2023, 09:36:11 PM

EEEPROM Files by shanebou24
June 01, 2023, 01:27:06 PM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod