#mcu shutdown, Timer too close

9 messages · Page 1 of 1 (latest)

devout dove
#

Hello forum,
I have to join the bandwagon as I received the message now a few times.

Background: New build, SKR pico, RPI zero 2w connected over UART, new SD card.

I have checked the klippy.log onto the sineos git and it seems at any random time the usage and memory spike but I have no clue why.
System is all up to date, no webcam. Only extra installed: Klipper screen but nothing connected so far...

could you please help out?
Thank you, Misael

#

Also interesting: after the shutdown I reset the mcu and started the print fresh, and it printed no problems.

devout dove
#

Another thing that might be the culprit: for my communication with the pi I use a mobile hotspot on my phone and when the printer shut down the first time the mobile hotspot went out.
After reprinting it with no problems the second time (hotspot on all the time) I printed same gcode again and shut off the hotspot and 10 minutes into the print or so it has the same error.
I have another printer on a Rpi3+ that never gave me that message. Could the absence of network cause that error?
I'll print the gcode again and will report...

devout dove
#

sadly missing Wifi wasn't the issue.... 😕

bleak pulsar
#

I don't know exactly where this came from, but iirc there was something about problems when changing it too fast or setting is multiple times without any move in between

devout dove
#

thanks for the pointers - I'll change the config and retest. Since posting I have also found a poor connection from the Pi to the board (UART)....

mental galleon
#

any luck? @devout dove

mental galleon