Here are the photos

Daniel, you should be able to find that code in the thread on the forum now.

Try replacing FastLED.delay with just delay for now - I’m wondering if there’s a bug in FastLED.delay on the teensy 3.1

Just tried that. It’s interesting, the flickering comes back, which I expected, but it starts MUCH more reliably. With FastLED.delay() it would only runn correctly after a power cycle about 1 in 10 times. Now it seems to run correctly about 9 out of 10 times. That definitely has something to do with it. I’ll post that info in the forum as well.

Thanks for the help. I’d rally like to get the reliability up to 100%.

= Ed =

As mentioned above - if you are going to run at a low frame rate (and 30 counts here), then turn off dithering to get rid of the flickering.

Daniel, yes. I did not mention that after I made the change to delay() from FastLED.delay() and saw that it improved the reliability significantly, I went ahead and added the setDither( 0 ) into setup as well.

Thanks again for all of the help. It still hangs occasionally, but much more reliable now. There must be some sort of timing bug in FastLED.delay(), but a cursory look through the code did not turn anything up - unless there is a point in time when CLEDController::head() returns a bogus value (unlikely) or possibly the linked list somehow becomes circular?? I’ll keep playing with this.

= Ed =

Ed- do you have a “decoupling” capacitor or some other more robust power isolation between the power going to the teensy and the power going to the LEDs?
I seem to recall having a couple of teensy lockup a due to sudden power changes (due in turn to sudden LED light/power changes).

Because FastLED disables interrupts for writing led data, it attempts to adjust the system timer after writing out data, I suspect the teensy bug is in there because without that, time doesn’t advance so the loop spins forever.

Mark, I do not have a decoupling capacitor. What ratings would you suggest for one?

Daniel, that sounds very reasonable. Is it possible to configure Teensy/Arduino/FastLED to run using an on board clock - if that would even alleviate the problem.