You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running this Neopixel sketch from the examples: RgbStripSequence.ino
What I've noticed is that after several cycles (it seems to vary) all the LEDs will turn white, and the program freezes and stops changing the animation. Sometimes there is a faint colored sparkle effect superimposed on the white.
I thought it was a power supply problem, but it happens with multiple different supplies.
I thought it was the WS2812 strip - but it happens with two different strips.
Any suggestions? Is this a hardware problem I can't see?
I've now used two different Arduinos (both Leonardo), three different power supplies, and two different WS2812 strips - and the same thing happens. The program loops through the animation sequence for some period of time, then the whole string turns white.
Unless I'm missing something, could this suggest a problem with the software - memory leak, millis() timing, too many animation sequences?
The text was updated successfully, but these errors were encountered:
I'm running this Neopixel sketch from the examples: RgbStripSequence.ino
What I've noticed is that after several cycles (it seems to vary) all the LEDs will turn white, and the program freezes and stops changing the animation. Sometimes there is a faint colored sparkle effect superimposed on the white.
I thought it was a power supply problem, but it happens with multiple different supplies.
I thought it was the WS2812 strip - but it happens with two different strips.
Any suggestions? Is this a hardware problem I can't see?
I've now used two different Arduinos (both Leonardo), three different power supplies, and two different WS2812 strips - and the same thing happens. The program loops through the animation sequence for some period of time, then the whole string turns white.
Unless I'm missing something, could this suggest a problem with the software - memory leak, millis() timing, too many animation sequences?
The text was updated successfully, but these errors were encountered: