I poisoned my Pixelblaze

I know what I did wrong. I was creating a map and used Math.Cos instead of Math.cos.

The Pixelblaze is now in a permanently unhappy state. Despite resetting & power-cycling, on each power-up, I get the message:

The controller has restarted from repeated errors and has loaded fail-safe settings. Proceed with caution - using this interface may persist fail-safe settings.

Is there a way to do a complete factory reset?

[edit] The replacement Pixelblaze is now in the same state, so my typo was not the root cause. I’ll check on power issues tomorrow. Worth noting the original board had been driving pixels for a few days.

(FWIW: not my first Pixelblaze installation by a long shot.)

Sounds like a bad pattern that is crashing. Try pressing the button once it powers up and starts to draw stuff on the LEDs, hopefully you can switch it to another pattern and get in the ui

Apologies for the delayed response. Most likely the problem was due to inadequate power. Both devices worked perfectly on the bench.

We were trying to install a second controller in the middle of a strip, where it would just tap power to run a second strip. Admittedly a hack.

Running separate power supply fixed the issue.
Initially quite perplexing that they would both exhibit the same issue, but I would bet it was NVS-related behavior.

1 Like