-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pi RGBW NeoPixel support incomplete? #56
Comments
hmm thats odd - it does work with normal RGB neopixels right? |
@ladyada Unfortunately I don't have any RGBs to test. I'll edit issue to add example code and the resulting color sequence here in a sec. |
I will add that I did try rpi_ws281x's Python examples, notably SK6812_strandtest.py, which does solid color fills, including white, and that was working as expected. |
oh ok you know i know what happened, i can fix it |
does this need updating to sync up with latest RGBW tweaks? |
no i think its just the way the raspi neopixel driver expects data, if i set it to RGBW i think i have to shift data in differently. im getting an RGBW ring to do a proper test |
I'd be happy to test a fix on my strip when you have one. I prototyped a fix (changed the |
i believe its now fixed in a PR |
I was working through https://learn.adafruit.com/neopixels-on-raspberry-pi/python-usage, adding https://learn.adafruit.com/circuitpython-essentials/circuitpython-neopix to understand how to add the W component (using bpp=4), with a Raspberry Pi Zero W and the RGBW Neopixel strip.
It didn't seem to work correctly. The result of this script:
was a repeating pattern of red, blue, unlit, green down the strip. I expected them to all be red (or at least all the same color.)
I took a look at the code and eventually got to 1f9263a, which implies RGBW is supported, but it didn't appear the W bits were being shifted in for the call to
ws.ws2811_led_set
, which would explain the behavior I saw.The text was updated successfully, but these errors were encountered: