I ordered 1750 bullet WS2811 pixels from Ray a few weeks ago as well as 160 35mm UCS2903 based pixels. I was assured by Ray that the UCS2903 is WS2811 controller compatible and based on my research here and elsewhere, that appeared to be the case. For my project I am using ESPixelsticks. I have had no issues with the WS2811 pixels and other than a few issues with 3 dead pixels (bad wiring), The quality has been excellent. Unfortunately I haven't had as much success with the UCS2903 pixels. The pixels I am working with are from the link below:
To start I am simply trying to get them to work individually for use in "Really Big Light" conversions. When I first apply power (12v), the lights come on full white. When I try to control them, I don't get any change whatsoever. I have tried several different lights and even switched inputs (thinking maybe they were wired up backwards) but no change. I tried different firmware with the ESPixelStick (both the stable and the latest release) and it didn't make any difference. I have reached out to Ray and he confirmed they were compatible and had me check the normal things such as wiring, voltage, etc which I have checked, double-checked and triple-checked.
I am not new at all to animated lighting and have a lot of experience working with electronics in general. That being said, I cannot get these to work despite my best efforts and I was hoping someone here might help me figure out what I am doing wrong (if anything). I am running out of time and my fallback plan would be to use 3 bullets per RBL which wouldn't be nearly as bright and work with a much smaller display than planned.
Has anyone else had any problems with UCS2903 pixels?
thanks
Joey
Joey,
In my original conversion for the RBLs on Youtube I used a 24v version of UCS1904 (I think it was) and ran them from ESPixelsticks. I had no issue.
If you have them turning on solid white right off the bat something doesn't seem right (dah.. right?) Try powering one up without data input but tie the data input to ground via a 1k or 10k resistor. It should remain off. (the resistor might be optional). It that lights I would suggest maybe a wiring issue, like maybe they didn't give you the correct wire colors.. Just a thought. I know when I originally received samples the IN/OUT had the wrong connectors and I blew up a couple while testing. At some point I did have some that stayed on but I don't remember the reason.. could have been the wiring.. that is where I would start.
The UCS-based pixels seem to power up in an on state (for a reason I cannot determine). I asked a vendor about it when I first observed that behavior myself (in my case, full blue on power-up) and was assured that is normal operation of those chips. In fact, he stated that is one way to determine if your pixels are using the WS or UCS chips.
So, powering on in a lit state is normal, and doesn't indicate that you have any data signal getting to the pixels.
ags0000 wrote:The UCS-based pixels seem to power up in an on state (for a reason I cannot determine). I asked a vendor about it when I first observed that behavior myself (in my case, full blue on power-up) and was assured that is normal operation of those chips. In fact, he stated that is one way to determine if your pixels are using the WS or UCS chips.So, powering on in a lit state is normal, and doesn't indicate that you have any data signal getting to the pixels.
Wow.. that's weird.
Hi, I think you have a cable connection issue. The timing for the UCS2903 is different to the WS2811 but as far as I can see if this was the problem it would turn the pixels off (a ‘1’ would be seen as a ‘0’ and then all data would be ‘0’s which is off).
It might be worth noting that I think you will need to keep the cable from the ESPixelstick to the first UCS2903 as short as possible after the first you should be fine and don’t mix WS2811’s and UCS2903’s on the same string.
For reference:
Both are 800kHz.
Both have data ‘0’ as 0.25uS high followed by 1.0uS low.
UCS2903 data ‘1’ is 1.0uS high followed by 0.25uS low.
WS2811 data ‘1’ is 0.6uS high followed by 0.65uS low (in theory too short a high).
I’m sure I read that Shelby’s ESPixelstick code has what is described as a ‘long 1 bit’ i.e. the ratio isn’t 0.6uS to 0.65uS its more like 0.75uS to 0.5uS. It appears from other posts that or though this doesn’t meet the UCS2903 spec of 1.0uS to 0.25uS it is close enough to run these pixels.
UCS2903 reset is greater than 24uS.
WS2811 reset is greater than 50uS (old type) and greater than 280uS (new type).
This should be fine as both WS2811 reset times are greater than the UCS2903.
The reason not to mix WS2811’s and UCS2903’s on the same string is that whilst the ESPixelstick has a data timing that works with both types of pixel once it is regenerated by a pixel of which ever type the timing becomes specific to that pixel type and unlikely to be recognised by the other. That said WS2811’s may run on UCS2903’s data but not the other way round.
I wouldn’t be surprised if the UCS2903 didn’t run on the WS2811 setting of other pixel controllers. Other controllers may support the UCS2903 by type but don’t assume that using WS2811 will work without the ‘long 1 bit’ that the ESPixelstick uses.
http://diychristmas2.org/vb1/showthread.php?8369-ESPixelStick-and-UCS2903-Pixels
I have a strand of what turned out to be UCS2903s. Do not try to mix these with WS2811s! Yes mine are blue on startup too. It has nothing to do with the ESPixelstick. I had the same issue running off an arduino last yr. Keep them separate and make a star or something out of em. The seem very unstable as most likely the timing is just a slight bit different from the WS2811s
