In file included from C:\Program Files (x86)\Arduino\libraries\FastLed\FastSPI_LED.cpp:11:
C:\Program Files (x86)\Arduino\libraries\FastLed/FastSPI_LED.h:143: error: ‘Hide’ does not name a type
C:\Program Files (x86)\Arduino\libraries\FastLed\FastSPI_LED.cpp:364: warning: ‘spihl1606’ appears to be a misspelled signal handler
C:\Program Files (x86)\Arduino\libraries\FastLed\FastSPI_LED.cpp:395: warning: ‘spi595’ appears to be a misspelled signal handler
C:\Program Files (x86)\Arduino\libraries\FastLed\FastSPI_LED.cpp:437: warning: ‘spilpd6803’ appears to be a misspelled signal handler
C:\Program Files (x86)\Arduino\libraries\FastLed\FastSPI_LED.cpp: In member function ‘void CFastSPI_LED::show()’:
C:\Program Files (x86)\Arduino\libraries\FastLed\FastSPI_LED.cpp:534: warning: comparison between signed and unsigned integer expressions
C:\Program Files (x86)\Arduino\libraries\FastLed\FastSPI_LED.cpp:549: warning: comparison between signed and unsigned integer expressions
C:\Program Files (x86)\Arduino\libraries\FastLed\FastSPI_LED.cpp: In member function ‘void CFastSPI_LED::setup_hardware_spi()’:
C:\Program Files (x86)\Arduino\libraries\FastLed\FastSPI_LED.cpp:649: warning: comparison between signed and unsigned integer expressions
C:\Program Files (x86)\Arduino\libraries\FastLed\FastSPI_LED.cpp:664: warning: unused variable ‘x’
Beauty! Thanks much! I’m not sure how I ended up with the old code as I followed the old link to the new site. at any rate, I just “talked” to the strip, so I’m off to a good start. Thanks much!
Cripes! Although the LEDs responded, they didn’t respond as desired. Heck, I’m just trying the BLINK sample and I get a spool of random colors. It’s a 2811 and I unremarked the addleds line of code calling for the 2811. Here’s what I have: http://www.amazon.com/gp/product/B00MHUK83K/ref=oh_aui_detailpage_o03_?ie=UTF8&psc=1
I can see 3 pads where the wires are soldered, so I assume, D0, +V and GND. The LEDs do respond but not as desired.
I changed the colors in this simple loop to Black to try to get the LEDs to turn off with no luck
I believe I’m on the correct side. I was looking on the futher side of the LED, where it has D0 silk screened, but the next LED shows DI on the same side of the LED where I’m connected. I just can’t see it on the side where I’m connected because the wires cover it.
Arduino is 1.06. I’m using an Arduino UNO board and the corresponding board is selected in the Audrio software.
I’ve tried messing with the power a while back…
I’m powering the LEDs off a seperate 7.5V supply and tried common ground.
I am also able to power everything from the Arduino, so I tried that by plugging the supply into the Vin on the Arduino and then running the LED strip off of the GND & 5V header on the arduino. I was suprised how bright the strip lit up, even without the external power supply when only powering the arduino from USB.
Not sure what else could be going on here…?
1.0.6 just passed all the FastLED examples on a string of LPD8806 as well as WS2802. Neither one of those are clockless chips though. Things may be different with those.
I tried 1.0.5 with no luck. I remarked out the loop in “firstlight” and just kept the “FastLED.show();” call. I seem to get the same results–a strange mess of color–whether it performs the FOR loop, or it just calls “FastLED.show();” The exact same funky string of colors.
Wait - you’re running 7.5v into the led strip? Don’t do that, you should be giving it 5v.
Also, can you put the entirety of the output from a build into a pastebin/gist - I want to see what your build is doing.
Finally - make sure you have a delay after the call to FastLED.show() - for now, until you get this stuff worked out, put
delay(100);
after the call to show (the reason for this is some led chipsets, like the WS2811 glitch out if you update them too quickly - I want to eliminate that as a possibility for what you have going on here).
Also - can you provide a close up picture of how you have everything wired up?
@Ashley I’m just using the “firstlight” example that comes with the library.
I’ve even tried to directly address an LED, like this:
leds[5] = CRGB::Black;
FastLED.sho();
It’s almost as if the .sho() procedure can’t talk to the LED strip correctly…maybe the strip IS hosed. @Daniel: 7.5V was just a test to see if the USB couldn’t push what’s needed. It just made the LEDs burn a little brighter. I don’t think it harmed them or the processor. It doesn’t matter which LED strip I select, I get the same results, the same random color band ie; NEOPIXEL, 2811, 2812, 1903, etc.
The 7.5 may have been enough to fry something. (I’ve been told, by someone who does manufacturing of things w/WS2812’s, that he’s seen them able to take up to 6V, but randomly start having problems if given higher).
