Adafruit_NeoPixel VS NeoPixelBus

// Support for Adafruit NeoPixel LED driver #define NEOPIXEL_LED #if ENABLED(NEOPIXEL_LED) #define NEOPIXEL_TYPE NEO_GRB // NEO_GRBW, NEO_RGBW, NEO_GRB, NEO_RBG, etc. // See https://github.com/adafruit/Adafruit_NeoPixel/blob/master/Adafruit_NeoPixel.h //#define NEOPIXEL_PIN 4 // LED driving pin //#define NEOPIXEL2_TYPE NEOPIXEL_TYPE //#define NEOPIXEL2_PIN 5 #define NEOPIXEL_PIXELS 2 // Number of LEDs in the strip. (Longest strip when NEOPIXEL2_SEPARATE is disabled.) //#define NEOPIXEL_IS_SEQUENTIAL // Sequential display for temperature change - LED by LED. Disable to change all LEDs at once. #define NEOPIXEL_BRIGHTNESS 255 // Initial brightness (0-255) #define NEOPIXEL_STARTUP_TEST // Cycle through colors at startup // Support for second Adafruit NeoPixel LED driver controlled with M150 S1 ... //#define NEOPIXEL2_SEPARATE #if ENABLED(NEOPIXEL2_SEPARATE) #define NEOPIXEL2_PIXELS 15 // Number of LEDs in the second strip #define NEOPIXEL2_BRIGHTNESS 127 // Initial brightness (0-255) #define NEOPIXEL2_STARTUP_TEST // Cycle through colors at startup #define NEOPIXEL_M150_DEFAULT -1 // Default strip for M150 without 'S'. Use -1 to set all by default. #else //#define NEOPIXEL2_INSERIES // Default behavior is NeoPixel 2 in parallel #endif // Use some of the NeoPixel LEDs for static (background) lighting //#define NEOPIXEL_BKGD_INDEX_FIRST 0 // Index of the first background LED //#define NEOPIXEL_BKGD_INDEX_LAST 5 // Index of the last background LED //#define NEOPIXEL_BKGD_COLOR { 255, 255, 255, 0 } // R, G, B, W //#define NEOPIXEL_BKGD_ALWAYS_ON // Keep the backlight on when other NeoPixels are off #endif

neopixel code is the strandtest: https://github.com/adafruit/Adafruit_NeoPixel/blob/master/examples/strandtest/strandtest.ino

Lookup NeoPixel library

adafruit/Adafruit_NeoPixel has assembly code for AVR. Plus ESP and Rpi which are a lot easier to read. And the protocol does look like inverted WS2812; it should be possible, although tedious, to modify the library to invert the pin.

I looked at the neopixel github and I couldn't find any functions that took floats as arguments, so I think you can get away without using floats because they're reinterpreted as ints and truncated anyway, but if what you have works then don't bother.

I'm not sure if that is the same thing. Back when I used it I got it from Adafruit which links to this Github.

The most important question first, the Adafruit NeoPixel Library does support the RP2040 since version 1.10.2. So make sure you are using the right version. To install the library please follow the steps explained here: Adafruit NeoPixel Installation.

The Adafruit Neopixel library is great, but uses 3 bytes of RAM per pixel....in my application that's nearly 3kB (for the pixels alone!), which rules out the M328/Uno, and basically all of the 8-bit chips. I have a prototype running well using Adafruit's Neopixel library on a Mega 2560, but those are hard to source in the current market. And it's overkill for my use case.

Using something like the Adafruit NeoPixel library there are commands to set intensity and to set color: setBrightness() setPixelColor()

This library (and some others) supports them: https://github.com/Makuna/NeoPixelBus

FastLED doesn't natively support RGBW addressable strips as of version 3.5.0 (October 2022). The alternate library NeoPixelBus does support RGBW strips, but handles animation in a completely different way than FastLED does.This snippet is an example of a way to shuttle data from FastLED RGB to NeoPixelBus RGBW, for folks (like me!) who prefer creating animations with FastLED.The additional library NPBColorLib is needed because NeoPixelBus doesn't (currently) use the white channel when converting RGB to RGBW -- see https://github.com/Makuna/NeoPixelBus/issues/323Tested with:FastLED, version 3.5.0 from https://github.com/FastLED/FastLEDNeoPixelBus, version 2.7.0 from https://github.com/Makuna/NeoPixelBusNPBColorLib, updated 2020-05-29 from https://github.com/jackjansen/NPBColorLib

I know it sounds insane, but it was an example script and I had issues with other example scripts too. Here's the example: https://github.com/Makuna/NeoPixelBus/blob/master/examples/NeoPixelBrightness/NeoPixelBrightness.ino

Do you mean https://github.com/Makuna/NeoPixelBus ?

One of the issues I ran into with LED chains (not the same kind of setup as this) was that some of the data pins on ESP8266 support hardware PWM and some don't. The LED library I used automatically did software PWM / bit-banging on the later pins. This bogged down the processor enough to make the wifi & IR-reception flakey when the number of LEDs was too high. https://github.com/Makuna/NeoPixelBus/wiki/ESP8266-NeoMethods has a bit on that - essentially only GPIO 1,2,3 support non-bit-banging. Depending on the board, you'll have different GPIO pins in different places, and some perhaps not available at all. I don't know how this LED panel is controlled, my guess is that some of the control pins need to be at high resolution, and that using hardware for that as much as possible will reduce the overhead needed, making it all run smoother.

That said, if you need RGBW support right now you could look at NeoPixelBus. It has very few of the capabilities of FastLED though...

Have you also tried Makuna's Neopixelbus for pushing out the RGBW pixels? Same thing with slower framerate?

Double-check that the outputs you chose will work for WLED (all of them will need "bit-banging" to generate the signal, which takes a bit of processing power - GPIO1,2,3 would be able to generate the signal directly). If you have a dev-board, this should be easy to check.