Replies: 1 comment 2 replies
-
Oops. Sorry about that. The holiday wreath project uses Neopixels connected to pin 10. Because the RPi Neopixels Editor doesn't allow entering pin 10, so I change the node's source code. I shouldn't have committed that. We're working on a Neopixels Node editor designed for Node-RED MCU Edition, so it does not have this limitation. That will avoid this problem in the future. (Cool to see external Neopixels working on a Grove connector. I haven't tried that myself.) |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@phoddie
config.gpio in flows.json is commented out with this commit.
3978cd2
FROM:
if (globalThis.lights) // for compatibility with hosts that create the NeoPixel driver (M5Atom-Matrix)
this.#np = globalThis.lights;
else
this.#np = new NeoPixel({length: config.pixels, pin: parseInt(config.gpio), order: config.rgb.toUpperCase()});
TO:
if (globalThis.lights) // for compatibility with hosts that create the NeoPixel driver (M5Atom-Matrix)
this.#np = globalThis.lights;
else
this.#np = new NeoPixel({length: config.pixels, pin: 10 /* parseInt(config.gpio) */, order: config.rgb.toUpperCase(), timing: Timing_WS2812B});
It previously works on Grove port of M5Stick CPlus and Core2 with NeoPixel, but not worked now because of fixed pin number 10.
I'm not sure the reason why the pin number is fixed number 10, and what about to change configurable?
Beta Was this translation helpful? Give feedback.
All reactions