This repo now contains experimental support for parallel data output on ESP32; currently (01/19/18) hardcoded out put for pins 12-19,0,2,3,4,5,21,22,23 OR YOU CAN USE IT WITH THE PINS YOU WANT !!!! STILL UP TO 16
based from https://github.com/eshkrab/FastLED-esp32
The strip 1 will be wired to pin 12 The strip 2 will be wired to pin 13 .... The strip 16 will be wired to pin 23
For esp32 I Suggest you use the code done by Sam Guyer https://github.com/samguyer it avoids flickering
// -- The core to run FastLED.show()
FASTLED_USING_NAMESPACE
/*THIS IS THE NEW POINT THIS MASK REFER TO THE PIN O(lowest bit) TO 31 (significant bit) if you want 5 STRIPS on pins 2 6 12 16 19 the MASK will look like THIS 0b1001000100000100010 set NUM_STRIPS to 11
*/
CRGB leds[NUM_LEDS];
// -- Task handles for use in the notifications static TaskHandle_t FastLEDshowTaskHandle = 0; static TaskHandle_t userTaskHandle = 0;
void FastLEDshowESP32() { if (userTaskHandle == 0) { const TickType_t xMaxBlockTime = pdMS_TO_TICKS( 200 ); // -- Store the handle of the current task, so that the show task can // notify it when it's done userTaskHandle = xTaskGetCurrentTaskHandle();
// -- Trigger the show task xTaskNotifyGive(FastLEDshowTaskHandle);
// -- Wait to be notified that it's done ulTaskNotifyTake(pdTRUE,portMAX_DELAY); userTaskHandle = 0; } }
void FastLEDshowTask(void *pvParameters) { const TickType_t xMaxBlockTime = pdMS_TO_TICKS( 500 ); // -- Run forever... for(;;) { // -- Wait for the trigger ulTaskNotifyTake(pdTRUE,portMAX_DELAY);
// -- Do the show (synchronously) FastLED.show();
// -- Notify the calling task xTaskNotifyGive(userTaskHandle); }
} //Then add code to initialize the task in your setup() function:
void setup(){ // -- Create the FastLED show task xTaskCreatePinnedToCore(FastLEDshowTask, "FastLEDshowTask", 2048, NULL, 2, &FastLEDshowTaskHandle, FASTLED_SHOW_CORE);
//-- Initiate the Leds.
/ two choices use the PORT_MASK or use the hardcoded FOR Harcoded just PORT_MASK=0 it's a bit faster because i have hardcoded the way the bit are encoded when you use the PORT_MASK it's a bit slower bit still good you can use two setups WS2811_PORTA (less artifacts with hardcoded pins) or WS2812B_PORTA a new one a bit slower i have better result for non hardcoded up to you to test the different combination. /
FastLED.addLeds<WS2811_PORTA,NUM_STRIPS,PORT_MASK>(leds, NUM_LEDS_PER_STRIP); //
//OR
FastLED.addLeds<WS2812B_PORTA,NUM_STRIPS,PORT_MASK>(leds, NUM_LEDS_PER_STRIP); //
}
//Finally, call the new show function in place of regular show:
void loop(){
static uint8_t hue = 0; for(int i = 0; i < NUM_STRIPS; i++) { for(int j = 0; j < NUM_LEDS_PER_STRIP; j++) { leds[(iNUM_LEDS_PER_STRIP) + j] = CHSV((32i) + hue+j,192,255); } }
// Set the first n leds on each strip to show which strip it is for(int i = 0; i < NUM_STRIPS; i++) { for(int j = 0; j <= i; j++) { leds[(i*NUM_LEDS_PER_STRIP) + j] = CRGB::Red; } }
hue++;
// send the 'leds' array out to the actual LED strip FastLEDshowESP32(); // FastLED.show(); }
Here are the performances:
IMPORTANT NOTE: For AVR based systems, avr-gcc 4.8.x is supported and tested. This means Arduino 1.6.5 and later.
This is a library for easily & efficiently controlling a wide variety of LED chipsets, like the ones sold by adafruit (Neopixel, DotStar, LPD8806), Sparkfun (WS2801), and aliexpress. In addition to writing to the leds, this library also includes a number of functions for high-performing 8bit math for manipulating your RGB values, as well as low level classes for abstracting out access to pins and SPI hardware, while still keeping things as fast as possible. Tested with Arduino up to 1.6.5 from arduino.cc.
Quick note for people installing from GitHub repo zips, rename the folder FastLED before copying it to your Arduino/libraries folder. Github likes putting -branchname into the name of the folder, which unfortunately, makes Arduino cranky!
We have multiple goals with this library:
If you need help with using the library, please consider going to the google+ community first, which is at http://fastled.io/+ - there are hundreds of people in that group and many times you will get a quicker answer to your question there, as you will be likely to run into other people who have had the same issue. If you run into bugs with the library (compilation failures, the library doing the wrong thing), or if you'd like to request that we support a particular platform or LED chipset, then please open an issue at http://fastled.io/issues and we will try to figure out what is going wrong.
How quickly can you get up and running with the library? Here's a simple blink program:
#include "FastLED.h"
#define NUM_LEDS 60
CRGB leds[NUM_LEDS];
void setup() { FastLED.addLeds<NEOPIXEL, 6>(leds, NUM_LEDS); }
void loop() {
leds[0] = CRGB::White; FastLED.show(); delay(30);
leds[0] = CRGB::Black; FastLED.show(); delay(30);
}
Here's a list of all the LED chipsets are supported. More details on the led chipsets are included TODO: Link to wiki page
LPD6803, HL1606, and "595"-style shift registers are no longer supported by the library. The older Version 1 of the library ("FastSPI_LED") has support for these, but is missing many of the advanced features of current versions and is no longer being maintained.
Right now the library is supported on a variety of arduino compatable platforms. If it's ARM or AVR and uses the arduino software (or a modified version of it to build) then it is likely supported. Note that we have a long list of upcoming platforms to support, so if you don't see what you're looking for here, ask, it may be on the roadmap (or may already be supported). N.B. at the moment we are only supporting the stock compilers that ship with the arduino software. Support for upgraded compilers, as well as using AVR studio and skipping the arduino entirely, should be coming in a near future release.
What types of platforms are we thinking about supporting in the future? Here's a short list: ChipKit32, Maple, Beagleboard
Wait, what happend to FastSPI_LED and FastSPI_LED2? The library was initially named FastSPI_LED because it was focused on very fast and efficient SPI access. However, since then, the library has expanded to support a number of LED chipsets that don't use SPI, as well as a number of math and utility functions for LED processing across the board. We decided that the name FastLED more accurately represents the totality of what the library provides, everything fast, for LEDs.
Check out the official site http://fastled.io for links to documentation, issues, and news
TODO - get candy