Last Bullet Pixel in 270 pixel String Won't Light Up With Xlights But Will With Baldrickboard Software.

Yep, those pesky four strings, like the above posters say, swap the two data cables around, if that doesn't fix it, I'm happy to jump on zoom and see if we can work it out rather than have another 20 replies :)

I've just checked the source code and made sure that we deleted the disable pixel 270-271 functionality a few months ago..
 
While I cannot comment on swapping the two data lines, I would really like to see how your controller is setup even if the data lines fix the issue. From the one screenshot it looks like the Baldrick might be setup as a generic controller which might cause issues later on.
 
Joining the party late...
After re-pushing all configs, the first thing in my "diagnostic tree" for the last pixel not lighting is to check whether the first pixel lights or not (if the first is white, and the rest are orange, say). This will let you know if the data is shifted by 1, or just cut off at the end.
(Yes, this off by 1 happens to me, the first batch of 3->4 pin adapters I got in 2023 was wired incorrectly and did not ground the backup data. I think I got them all binned by now, but...)
 
SUCCESS!
My 3 -> 4 core adaptors are configured incorrectly as @merryoncherry stated above.
I made my own adaptor up and retested, now the last pixel lights up when told to.
Tried this on my other bullet pixels and also the seed pixel strings and all light up when contolled.
My thanks to all for your replies and comments.
These 4 cores with data backup are fun to learn on. Ha Ha.
Cheers
 
You must log in or register to reply here.
Back
Top