Since upgrading from Fly 2040 v1 to v2 I keep getting “MCU ‘sb2040’ shutdown: Timer too close” after a “Hold till temp is meet” command finishes. I am trying to print a temperature tower and it is consistently shutting down after the temperature is meet with this error. I have read other post where neopixle seems to be the issue, so on my last run (Line 12508) I stopped all LED effects to rule that out and it still occurred.
Lines 15844 is adjusting the temp and 15854 it reaches temp to then line 15870 where klipper shuts down.
I did re-flash everything twice, and updated my repo. not sure what else to look for.
My host computer peaks out at 2% utilization, so that isn’t the issue.
Non-Temp changing prints are completing with no issue.
I had a Pi in it before, but maxed out its bus with 2 1080P cameras running, so I needed something with a faster bus, and wanted native NVME. So this is what I settled on. I had my eye on another motherboard, but it was 300 more with less power, so I went the cheaper route and have a power house
It looks like you’ve customized the Klipper code. I’d recommend reproducing the error on the pristine Klipper code to see if the error persists. If it does, please attach the Klipper log file from that event. (Though, note, there are reports that the rp2040 code is not working properly in the very latest master Klipper code.)
i am using the most current from git, didn’t customize anything in klipper, just macros.
Unless you mean by customize I installed the canboot and klipper-led_effect, then yes its customized in that way, but i did not edit any source code.
do you know what code version is known to work properly with the rp2040 code?
Led_effects is not a part of mainline Klipper, and the screenshot notes that file as untracked in your local directory. That would need to be removed to do any further diagnosis.
