I'm attempting to write to two different strings of Pixels using the library,

Archive FastLED Archive
,
1

I’m attempting to write to two different strings of Pixels using the library, using separate functions for each (in regards to my previous question on referencing arrays, I’ll get back to that once I can get this working).

Each string has it’s own array and output pin. Yet, when I test this, I’m not seeing any output. Am I implementing this correctly?
(I posted this earlier, but I’ve cleaned up the code and double-checked it)
http://pastebin.com/yBqVzUU9

2

For a quick test (away from anywhere I can poke with code for a while) - swap the pins in your addLeds lines. Does the same physical strip light up as did before? Possible wiring problem. If which strip is working flips as well, likely a code issue.

3

I’m going to be away from the bench for the weekend, but I will take a look on Monday. I’m hoping I can work this out, because managing all my pixels on a single array/pin is going to be messy and involve a lot of ‘repeater’ pixels strung around.

4

An Update: I hadn’t really looked closely at the code I posted, I’ve been working with a few versions of this at once and I’ve been sloppy. Here is the code that will actually compile. I currently have one array commented out for testing, but on upload, this has caused two arduino micros to fail to show up in the Serial Menu - I’m a bit concerned about that. Anyhow, this is the one that should be experimented with:
http://pastebin.com/Pzk3nMfW

5

Ah! In this case it is simple - you are running out of ram. With two 300 element arrays of CRGB objects, you’re using 1800 bytes of ram (300 * 3 * 2) - and with only 2k on the arduino, there’s not enough left for, well, much else.

6

Change:

CRGB leds2[ARRAY1_SIZE];//Create array for RGB LED Control

to

CRGB leds2[ARRAY2_SIZE];//Create array for RGB LED Control

which will cut your ram usage for led data down to 1092 bytes.

7

Ah crud. Again - sloppy code

I tried it out today, and I actually got it to work - My problem actually came down to a physical error. When I’ve been experimenting, I haven’t been using the recommended resistor on the data in port, and I haven’t had a problem (with one prior exception).

When I tried doing two arrays again, I had the same problem -one of my strips’ first pixel failed. I Added in the resistor on each array of pixels, and the problem disappeared. Lesson learned: follow the guides…