If I have a string of 500 bullet nodes and only the first 42 nodes work, that means more than likely that pixel #43 is bad, correct? (As long as my controller is configured to light up the entire string, which it is.) I am power injecting at all points and when I'm not, I still get voltage at all points (and of course it drops as I get further from the source). Just want to make sure there's not something else that I might be missing before I start chopping up the string... Thanks!
It could be pixel 42 not passing data . Could be broken v- or v+ between 42 and 43 also .
Or you are/have not configured beyond 42 pixels .
Typically I would cut #42 AND #43 out and replace them.
I replaced what i thought was a bad pixel under similar circumstances last year. But it was a configuration issue. Double check your configuration before replacing pixels.
What controller are you using? How have you tested?
It was the pixel. I cut it after #42 and the rest of the string works fine. Sounds like what Angus said, #42 was not passing data.
Glycerine wrote:It was the pixel. I cut it after #42 and the rest of the string works fine. Sounds like what Angus said, #42 was not passing data.
Hmmm . If #42 was not passing the data , the pixels should not be working if you did not remove it .
It appears that #43 receiving data was the issue if all is well now .
I would dissect that pixel to see if it was actually a bad board, ic or just a bad solder on the data line.
Either way good to hear you fixed .
angus40 wrote:Hmmm . If #42 was not passing the data , the pixels should not be working if you did not remove it .
It appears that #43 receiving data was the issue if all is well now .
I would dissect that pixel to see if it was actually a bad board, ic or just a bad solder on the data line.Either way good to hear you fixed .
What I did was cut the string in "half" after #42, so that I have 2 separate strings, one that has 42 pixels and one that has 458 pixels. #43 of the original string is now #1 of the new string. When I say the rest of the string works fine, I mean they work as a new string. All of the pixels are working as two separate strings and I even added the original 42 pixels to the END of the new string and they all work. I cut the output wires of the bad pixel off right at the pixel, so I won't forget later down the road and try to add any more pixels after it.
That is a very creative way of salvaging the poor pixel 🙂
kev wrote:I replaced what i thought was a bad pixel under similar circumstances last year. But it was a configuration issue. Double check your configuration before replacing pixels.What controller are you using? How have you tested?
Oh, to answer your questions, I was using an ESPixelStick for testing and just used the "effects" tab to test. I did change the number of pixels to 500 in the "Device Setup" tab as well. I also had several more strings that I had already tested, so I was fairly sure it was configured correctly before testing that string.
angus40 wrote:That is a very creative way of salvaging the poor pixel 🙂
I'm going to be chopping these strings up for a mega tree build anyway, so who knows, that short string will probably end up not being used. At least not now.
