-
Notifications
You must be signed in to change notification settings - Fork 121
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
Neopixel issue #110
Comments
Also having the same issue. |
This is firmware (Micropython port) related not hardware. The driver was rewritten 15 mins before the opening ceremony and pretty sure this is an issue where the pixels are picking up an extra edge at the start of the pulse output from the timer.
Of no one gets to it before me I’ll look with the scope next week.
Matt
… On 2 Sep 2018, at 21:49, Jake Walker ***@***.***> wrote:
Also having the same issue the left one is perfectly fine though.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This seems to make things better but it still ocassionally needs several attempts before the data is latched correctly: emfcamp/Mk4-micropython-board#4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I may have a bad neopixel.The Neopixel closest to the end button doesn't work properly:Appreciate if someone could check.The text was updated successfully, but these errors were encountered: