New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repeated "Neopixel update did not succeed" error until klipper crashes #56
Comments
You have a lot of LEDs. Could be a bit too much, especially with only one MCU, which also has to control the motors. I would recommend using a separate MCU for the LEDs. You could also try reducing the frame rate or amount of LEDs active at the same time. |
@julianschill Understood, but this setup has worked fine for the past ~6 months until the most recent LED Module update? |
Ok, that's a different story then. But I am not sure if I can do anything about it as it might be due to changes to klipper. I will look into it. |
@julianschill I played with number of LEDs, issue appears to only happen when greater than 21 LEDs selected in chain and the greater the amount of LEDs included the more frequent the error exists. Not sure if that is helpful in anyway, but it's what I found. Also, MCU load is only 0.28 while this is happening according to Mainsail UI. |
@julianschill I take it this issue isn't going to be resolved? Loved the module until this started :( |
With any LED effects enabled klipper continuously gives "Neopixel update did not succeed" error until klipper overloads and crashes. Fresh install of klipper and LED control module installed did not resolve issue.
klippy (5).log
.
The text was updated successfully, but these errors were encountered: