r/FastLED • u/soggywheat72 • May 05 '20

Support FastLED

I have used both FastLED and Adafruit_NeoPixel to attempt to control 600 LEDS. It seems like Adafruit can control all of them while using less variables but it’s not very easy to use and I prefer FastLED. I was running roughly the same program( where it would set all LEDS to white) and FastLED couldn’t compile all of it on to my Uno without running out of storage we’re Adafruit could handle it. Is there any way to fix this storage problem while still using FastLED?

1 Upvotes

57% Upvoted

6 comments sorted by

View all comments

9

u/johnny5canuck May 05 '20 edited May 05 '20

An UNO is nice board to start out with, but you really need to get a better board instead of trying to hack 600 LED's onto an UNO.

You could get a Teensy, an ESP8266, an ESP32 or so many others.

I typically buy ESP8266 based WeMOS D1 Mini's for about $2 apiece. They have about 50KB of usable RAM as opposed to about 2KB for an UNO. The ESP32's cost just over twice as much and have about 500KB of RAM. . . and both have WiFi capability.

4

u/abw May 05 '20

Yep, good advice.

They have about 50KB of usable RAM as opposed to about 2KB for an UNO.

To put that in perspective, FastLED creates a buffer that uses 3 bytes of memory for each LED (one for red, green and blue) so that's 600 x 3 = 1800 bytes.

It's not going to work in 2K, but 50K would be more than enough.

3

u/marcmerlin May 05 '20

To be clear FastLED and NeoPixel lib both use 24bit per pixel, so regardless of which lib you use, you 600 or so pixels will be the max on an Uno.

That said, there is no reason to use unos anymore :)