News:

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

+-+-

+-User

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

+-Site Stats

Members
Total Members: 16520
Latest: tanyadai
New This Month: 8
New This Week: 0
New Today: 0
Stats
Total Posts: 133087
Total Topics: 16541
Most Online Today: 83
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 1
Guests: 35
Total: 36

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

LED Panel issue after upgrade to v8 by k6ccc
September 06, 2024, 05:54:33 PM

Leave eth0 Gateway blank by colonelcline
September 06, 2024, 09:19:53 AM

FPP After Hours Music Plugin has been updated by ckuhner
September 06, 2024, 07:58:54 AM

HELP - Panels Blown or PocketScroller messed up by DaSarge
September 06, 2024, 07:38:55 AM

PiCap-V2 String port webpage display issue by JonD
September 06, 2024, 06:00:13 AM

Recent update broke ArtNet Advanced Plugin on RasPi only by k6ccc
September 05, 2024, 04:28:51 PM

REST API: Start playlist and set repeat flag to true by Pweazle
September 05, 2024, 02:46:33 AM

Overlaying 2 or 3 videos in falcon player by darylc
September 05, 2024, 01:05:52 AM

Control lights directly from the GPIO of a PI by tbone321
September 04, 2024, 12:40:13 AM

FPP 8.0 Released! by dkulp
September 03, 2024, 07:05:20 PM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod