OK, I've read the FAQ "6.

Archive FastLED Archive
,
1

OK, I’ve read the FAQ
“6. Why doesn’t FastLED support this random led chipset or that random MCU?”

Problem is, I already have a display built with 1500 pixels of a really obscure old part. I’m a pretty good coder, and I have written drivers for this part myself in C. How can I add my own chipset to the library? Does it have to be integrated into the code, or is there a way to use parts of the library but with a custom protocol?
I plan to use Teensy 3.2, or maybe the new Teensy 3.5 when I get mine from the kickstarter.

2

here is the display. the driving hardware is old and expensive, and I want to replace it. https://www.youtube.com/watch?v=Z6Jgz78a9t4

3

That’s a very impressive build

4

Woah, that is a sweet display!

5

Beautiful build! I’d love to see more details, if you have them and don’t mind sharing. :slight_smile:

As for adding chipset support, I think they’re all defined here: https://github.com/FastLED/FastLED/blob/master/chipsets.h You should be able to fork the library on GitHub and make your changes.

Teensy 3.2 is currently supported, but not the 3.5 or 3.6, although I’m hoping they’ll be added soon after they ship. :slight_smile:

6

OK, so this is a noob question… Do I need to rebuild the library? Are there any instructions for how to modify the FastLED library after I make changes to the code?

7

https://youtu.be/0QBFtsd9C00. The first video is made o metal and can’t be disassembled. The new one uses the same leds but was engineered to be assembled at Burning Man.