I’ve just switched my code over to 2.1 in the hope of using the new power management functions, but it seems to have broken everything.
Even the basic blink example no longer works… Instead of blinking one light it lit up every led on the strip one by one, even when set to Black.
I’m using a Teensy 3.1 with an LPD8806 strip, FastLED 2.1 and Arduino 1.0.5. I have DATA_PIN as 11 and CLOCK_PIN as 12.
It all works fine on FastLED 2.0.
Ah - yeah, there’s a recently identified problem with the teensy 3.1 and SPI chipsets that I haven’t checked in a fix for yet - go into ledsysdefs.h and change the line that says:
#define CLK_DBL 1
to
#define CLK_DBL 0
(that is not the correct long term fix, but it should be a stopgap)
Bingo! That’s fixed it, thanks!
However, in possibly related issues, the code is working under 2.1 however there is some very strange behaviour…
Even without using any of the power management functions (ie, still using FastLED.show()) some LED’s just aren’t lighting up, or some are lighting up the wrong colour.
I’m using a 30x8 matrix, and if I try to set them ALL on solid red it skips over the first 6 or 7, and a few of the other random ones are more green than red.
Switching back to FastLED 2.0 makes the problem go away.
Very strange.
Hmmm… two questions:
what happens if you slowly scale back the number of LEDs - e.g. peel off one row at a time, is there a point where it stops behaving like that?
it is possible that I’m still driving the leds too fast, and you can change this by making your addLeds line look like:
addLeds<LPD8806,RGB,DATA_RATE_MHZ(15)>(leds, NUM_LEDS);
try 15 and try 10.
I have had issues where the longer the strip of leds was, the slower I needed to run the SPI clock 
Ok, I’ve just done a brief test… at 16mhz data rate everything is fine… at 17 things start to go weird with my strip of 240 LED’s.
I need to alter a little more code to work out what the maximum number of LEDs is at the default rate… I’ll get back to you on that one.