

4:15 am

July 3, 2019

In playing with the XIAO/Neopixel sequences (for 4th of July RWB holiday lights) I noticed two oddities
that may be note worthy.
I don't believe these are compiler problems.
~~
[1] Tested some holiday lights sequences on a Seeeduino XIAO and noticed that the blue channel fails to
address the last pixel of any sequence. I've tested my programs on arduino mega, nano, nano-every and
seeeduino XIAO and have only observed this oddity with the XIAO. Thus far I haven't found a fix.
~~
[2] While working on a fast refreash twinkle effect I found that updating too quickly results in random
"splatter" that will trigger many more pixels than declared. In example, I've had a 16 pixel sequence
fire over 200 pixels. I've found that adding a delay of ~200 micro seconds between writes solves the
problem. I haven't checked on an oscilloscope so don't know if it's a level, jitter, or other issue.
[2a] Note, I have not observed the "splatter" with WS2811 LED light strings.
~~
Tech Info:
Arduino IDE 1.8.13
Neopixel Library 1.0.2
ALITOVE WS2812B Addressable 300 Pixels RGB LED Strip
ALITOVE WS2812B Individually Addressable RGB LED Flexible Panel Matrix Screen 16x16
I've attached test program/vi
4
1 Guest(s)
