Hello, I am trying to write a controller for an arduino pro mini to intelligently flash light patterns on RGB led strips placed on a multicopter arms.
I have the specific need to read the chipset type, pin assignment and RGB order for n strips of n less (all of these parameter read from eprom) and set up the led strips accordingly. The regular ways to setup FastLed requires chipset, rgb order and pins to be passed as constants. Is there a way to pass chipset type and data/clock pins to FastLed.addLeds as variables calling some of the internal classes in the library?
Thanks
No, not really at the moment. A lot of how the library gets its performance is hard coding low level io access at compile time.
Daniel. Thank you for the quick answer. Any plan to add this functionality in the future? It would make the library a lot more flexible
Not really - the library isn’t targeted for people making generalized, run-time re-arrangable controllers. To have both the compile time optimized code for performance and would require either significant re-working of the existing code or creating a parallel set of code (doubling my workload and what I have to test/maintain for what is a fairly niche edge case use of the library) - as it is, the backlog list of work for the library is long enough (and that’s not even including MCU/led chipsets that are likely to continue being released) that splitting off the time to do something like this is even less likely.
That said, take a look at the firmware for the allpixel - they do something like this - https://github.com/ManiacalLabs/AllPixel - though the pins are still chosen at compile, not run time - but the type of led used is chosen at runtime.
It seems he does not touch your library but rather add its own initialization. What it does may suffice for what I need to do. Thanks again