RNoble

as i no longer seem to be having this issue, i'm considering the problem resolved. i appreciate the assistance; thank you.

i have cut out a lot of things that i didn't understand the purpose of in that sketch and added things from other sketches that i was attempting to grok, so it's likely that's a problem i caused. that makes more sense. i'm not totally enamored...

but why would the board work with other sketches and the sketch work with other boards if it was a memory fault? i did the basic tests with Octo and WS2812 and everything works fine; even tried the WS2812 Cylon test which does the same thing as...

i had put this project away for a while and forgotten to link the power and board grounds together; the LEDs are no longer going bonkers. i managed to get the WS1812 basic test to operate using all 438 pixels. when i attempt the FastLED sketch...

had an error in the IDE and restarted it. the IDE is now outputting this: the verbose log is now producing this: and the LEDs are going bonkers. it seems the communication issue is resolved (partially?), but the sketch is misbehaving.

i'm a web guy. didn't change the meaning of anything in the code for me. but sure... here you go. /// /// /// @brief An animation that moves a single LED back and forth (Larson Scanner effect) /// @example Cylon.ino #include <FastLED.h>...

i don't have any setting that will change that. the system assigned it.

swapped that bit of code in to kill the serial read and got this: no change to the program running though.

power for programming is coming from USB. power to run the project after installation hasn't been decided. LEDs are 12V and being powered separately. i've run through 3 or 4 cables, but a lot of my cables are from unknown sources. tried a couple...

first, i'm new to C++ - my rudimentary background is in HTML/CSS/JS. my 8yo wanted to learn to program LEDs because i have them on my motorcycle and all over the house. now we are learning C++ and Arduino. there seems to be a communication...