I recently switched from Marlin to Klipper and everything works fine besides I’m getting several mcu shutdowns. Everything, including the SD Card, is fairly new and worked on the Marlin setup without a charm.
When does this happen:
Usually with longer prints, but also random for short prints. Shortly after start of the print (10-15 minutes) as well as mid print or close to the end. Haven’t found a pattern yet.
What I also did:
Checked the Raspberrys Voltage (vcgencmd get_throttled gave me throttled=0x0)
Reflashed Firmware and updated everything
Try to find something in the Klipper log
Cried
Edited the background task like suggested here Link
Things I didn’t do
Unplugged the Webcam (since I need it for my monitoring and really won’t like to go without. Furthermore I actually want to upgrade to a touchscreen next month)
Bought new hardware (I want to make sure that there are issues with my hardware before trying to find another raspberry or sth similar)
Since I’m fairly new to Klipper I hope you can help me interpreting my scenario.
Your log indicate that you very often your system have communication issues,
your ready_bytes constantly recording some bytes are waiting for sending
also sometimes you have upcoming_bytes jumping - which indicate that some bytes are waiting in MCU for sending.
Usually they will go thru with next request and you don’t see ‘Timer too close’ issue, but sometimes they stuck for longer and you are getting ‘Timer too close’ error.
When this is happening Stats show that you don’t have some huge load on CPU.
As possible solutions you should try to replace your USB cable, USB-to-Serial adapter. It could be your USB port - you can try to plug USB to other port or introduce USB Hub with external power - sometimes this is helping.
Thanks for your suggestion!
I just had a failure without the webcam, but as you mention it there might be something wrong with my USB setup. I’m currently using a hub with an ethernet port (because I had WLAN issues in the past) maybe this mixture is really messing things up. I started a new run without that adapter so the connection from the PI and the printer won’t have any other interferences.
Maybe the best idea would be to move to a B variant with ethernet port as well as multiple usb ports
