Is there any timeline to support OCTOWS2811 for FastLED in the roadmap? I am beginning to design a custom chip for a large project and would like to use the Teensy LC with OCTO to get as many cycles as I can for the remaining code. If its coming up in the next 6 months, then I could work the Teensy LC into the design rather than Teensy 3.2 to save some money on the multiple chips.
The octows2811 driver is just a wrapper around the library - assuming octows2811, the library, is code compatible between the 3.2 and the LC, then the header file should be just copy able to the lc’s platform folder.
(I still don’t have a timeline for getting back into regular working on the library)
All the pins are the same, so it might be as easy as just that… any chance you know off the top of your head the file to find that info to copy?
The file literally has the name octows2811 in it 
(I’m traveling right now and on a poor internet connection on the phone at the moment)
I see octows2811_controller.h in the K20 folder… that would be the one? And I believe the Kl26 is the Teensy LC… just need to incorporate that into it then right? No clue what I am doing but willing to trip and fall through it…
Shout out to anyone on here who wants to help!
Ask @PaulStoffregen , he’ll know…
@Justin_Eastman Depending on what you want the octo for, and as awesome as the Teensy is and we all love to support it… the newer Esperif controllers might make a lot of that obsolete. Even the 8266 packs a ton of power and can be found for about $2-3 on aliexpress, and the ESP32 is in the $5-7 range, comes ready to go with bluetooth and wifi and 4mb of onboard memory, and @Sam_Guyer has just released a FastLED fork for it to natively support 8 way parallel output seamlessly in the code.
I’m actually curious if anyone has a strong opinion: with access to the ESP32 and Sam’s native 8 way parallel output… is there any reason to go with teensy and the octo board anymore?
@chad_steinglass So the ESP8266 support created uses a DMA as well? Just trying to maximize cycles… I have a few ESP8266 lying around, just have not gotten to them.
@Justin_Eastman I’ve only used 4 way parallel output on the 8266. it uses one of the SPI buses, I think its basically the same as the Teensy does it. You define your strips the way that the parallel example in the FastLED wiki specifies, using a PORT and a single array of size NUM_STRIPS*NUM_LEDS_PER_STRIP.
I haven’t tried it yet, but I believe that Sam updated a fork of FastLED so that on an ESP32, you can simply define up to 8 strips each of their own legnth on 8 separate pins, and behind the scenes it defaults to sending out the signals in parallel
The other thing that the octo gives you is a level shifter and data line resistors… but thats another thing you can do for yourself if you want to.
Unless I’m missing something, basically with the ESP chips and a few components (your own resistors and SN74HCT245 chip - about $0.20 on aliexpress, and maybe some RJ45 jacks or other connectors for your data lines) you should be able to put together a controller with tons of memory and 8 way parallel output for an all in cost of $8 or less each.
If you’re doing a large project or making lots of items, that seems a lot cheaper than $25 all in for a TeensLC and octo board, or up to $40 if you were to go with a 3.2 or 3.6
@chad_steinglass I am designing my own boards which will bring my cost way down compared to buying directly and save me a LOT of hours having to assemble multiple boards and components. I have done this with The Tunnel of Questionable Enlightenment (http://www.facebook.com/ttoqe) and just want to avoid that.
The Teensy LC processor is like $2 vs Teensy 3.2 processor which is $7 . When considering 100s of boards, $5 per board becomes a lot.
Thank you for sharing your input. You are certainly peaking my interest into at least looking into the capabilities of the ESP processors.