Skip to content
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

In RGB+W Mode, showColour() lights an extra LED, and clear() ignores it. #28

Open
nbogie opened this issue Jun 10, 2018 · 0 comments
Open

Comments

@nbogie
Copy link
Contributor

nbogie commented Jun 10, 2018

Simplest repeatable failing test: https://makecode.microbit.org/_YmYf9i6AzAxA

Note: This behaviour isn't visible in the simulator (perhaps because the simulator is only showing the number of LEDs configured by the create() call). In the real world this would only be noticed if neopixel.create() was called with a lower number of pixels than actually contained on the physical strip.

let lightStrip: neopixel.Strip = null
lightStrip = neopixel.create(DigitalPin.P0, 3, NeoPixelMode.RGBW)
basic.pause(1000)
lightStrip.showColor(neopixel.colors(NeoPixelColors.Red))
basic.pause(1000)
lightStrip.clear()
lightStrip.show()

Expected Behaviour (on real strip): Should see pixels 0,1,2 all red, only

Actual Behaviour (on real strip): As expected except pixel 3 is lit green and stays on after the clear()

rgbw extra unclearable pixel issue

Notes: I've tested with various configured lengths, whether 3, 15, or 60 pixels, the library call will always light this extra (last + 1) LED green. This discounts the possibility that the issue is simply a bad pixel in my hardware.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant