Currently, FastLED supports standard WS2812B timings. However, I have encountered a WS2812 variant that requires a different timing specification:
- T0H: 0.3µs
- T0L: 0.6µs
- T1H: 0.6µs
- T1L: 0.3µs
This variant does not work correctly with the current timing parameters in FastLED, resulting in incorrect colors or no output.
I would like FastLED to support this new timing profile. Ideally, this could be implemented by adding a new chipset definition (e.g., WS2812_FAST or a similar name) that uses these specific timings. Alternatively, providing a way for users to define custom timings would be a more flexible solution.
I have considered manually adjusting the timing in the platform-specific drivers, but this is not portable and would be overwritten by library updates. Using other libraries is not an option as I rely on FastLED's feature set.
I use atmega8 au 16Mhz, arduino IDE.
35277587662020幻彩WS2812C-X款HXG.pdf
Currently, FastLED supports standard WS2812B timings. However, I have encountered a WS2812 variant that requires a different timing specification:
This variant does not work correctly with the current timing parameters in FastLED, resulting in incorrect colors or no output.
I would like FastLED to support this new timing profile. Ideally, this could be implemented by adding a new chipset definition (e.g.,
WS2812_FASTor a similar name) that uses these specific timings. Alternatively, providing a way for users to define custom timings would be a more flexible solution.I have considered manually adjusting the timing in the platform-specific drivers, but this is not portable and would be overwritten by library updates. Using other libraries is not an option as I rely on FastLED's feature set.
I use atmega8 au 16Mhz, arduino IDE.
35277587662020幻彩WS2812C-X款HXG.pdf