Printer Model: RSE Core XY Printer
MCU / Printerboard: MKS PI
Host / SBC Klipper
klippy.log
…
Second time that printer is shutting down mid print.
I already consulted configuration reference and adjusted the “verify heater” section within my configuration.
Again same error occured. Please help me to understand how to read klippy log so next time I can understand whats going on.
klippy (3).log (88.8 KB)
Thanks mate.
Very useful post. Totally agree !
Obviously the bed heater is somehow not heating at expected rate. I really don’t know why because I set 60C temperature and the bed heats perfectly fine up to 120C.
Also wiring and installation is without flaw and usually looked and worked good.
I hope to narrow down the problem.
What did happen that triggered the shutdown?
Maybe something like?: Heater_Bed ran on 30% power. It waited 120 seconds to reach 60C coming from 58,5C. This took too long=shutdown
At this point I’m not able to read Klippy.log and try to get assistance. Please correct me if I forgot something fundamental. Thank you 
Unfortunately, the log you provided does not contain the event you are reporting. Without a log showing it, no further guidance can be provided.
Which log should I provide?
Is it not the standard klippy.log where all information should be contained?
Usually yes, but the log should include the occurrence of the issue.
So, try again to heat. When the issue kicks in, send a M112 from the terminal and then attach the klippy.log to your next post.
I‘m not able to set M112 command because the machine is shutdown and non responsive.
I didn’t update the machine for a couple of month. On my update info box I see several issues and available updates. And also „corrupted „ on the Klipper button.
Could a bad Setup somehow be responsible for this kind of sudden shutdown behavior ?
It happened again 
Would you mind check what the reason could be?
New klippy.log attached.
klippy.zip (1.7 MB)
More important is the line before:
Transition to shutdown state: Heater heater_bed not heating at expected rate
Something weird is going on with your bed:
Oh shit, actual temp is heavy away from target…
Is there also a timestamp? So I’m not sure if the drop occurred within minutes or maybe one hour…
There are timestamps but they are not immediately translatable to “human” time and in almost no case this is needed either.
Such sharp drops as shown by @EddyMI3D typically point to a defect temperature probe. Either the probe itself or its wiring / connectors.
Each stats line is 1 second and it is simply impossible for the temperature to change by 60 °C within 1 second.
Yes I agree. Will check the system thoroughly and order also new thermostat element.
I did many heat cycles today since morning. Just wanted to confirm that it’s not that and more something like a spiky tc.
