Fill out above information andin all cases attach yourklippy.logfile (use zip to compress it, if too big). Pasting yourprinter.cfgis not needed Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
Hello,
i know there are a lot issues related to MCU Shutdown/communication. But my printer completely shuts down during prints. I just goes off, and i’m not able to reach it anymore. I have to toggle the main power switch for it to reboot. I have disconnected all USB devices. It seems to get better (less frequent) when i decrease print acceleration, but i’m not sure with that. Could have been a coincidence the few times i tried since the problem occurs. There was no particular event i remember, that started the problem.
Klippy.log was downloaded after reboot. I can’t read any error messages from it, but i also don’t know what to look for. I would really appreciate some help
I found this post: Random Shutdown , but i would like to have an opinion before trying all these steps, which would mean at least bying a new host board and spending a lot of time.
Be careful with the power input connectors of BTT pi 1.2 and pi 2. It happened to me that both the soldering was deteriorated (it was barely visible) and I had a loss of power supply. Be careful with the power input connectors of BTT pi 1.2 and pi 2. It happened to me that both the soldering was deteriorated (it was barely visible) and there was a loss of power. Curiously, this also happened to me on the BTT skr mini E3 V3, but with significant deterioration in the welding due to the high input amperage.
When there are bad contacts, the correct power supply is not received with micro cuts. When there are bad contacts, the correct power supply is not received with micro power cuts that are imperceptible but the system fails to send or receive data.
Yes, i actually have read it, but i didn’t even now what dmesg was and i think i havn’t quite understood it yet.
I’ve attached the output from a “dmesg” command (right after startup of printer) as a txt. I hope this is the right way to do this. I am quite confident with the mechanical parts and klipper configuration, but am lacking the software/linux basics.
The system is running on the eMMC storage. If no obvious other problem raises from the dmesg.txt, i will get myself a high quality SD Card and do a fresh install, just to be sure.
I am now logging the cb2’s temperature, but it has a heat sink and is getting fresh air from a fan. Temperatures are fine.
The cb2 sits directly on my Manta M8P, so power supply shouldn’t be a problem, as long as it isn’t for the M8P. I checked multiple times, that it is fitted correctly. I do not have an oscilloscope, so if there is a way to measure the input voltage (with a high enough frequency), i’d be happy to do so.
It just happened once again and klipper was able to report the following error:
Can not update MCU ‘mcu’ config as it is shutdown
Once the underlying issue is corrected, use the
“FIRMWARE_RESTART” command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer
Normally it just stays off, but as the problem is most likely the same, i am happy to have at least a message
I did a “dmesg” directly after the shutdown. I’ve added it to the original post. It has a lot more “red” in it. There seem to be some w-lan connectivity problems, followed by i2c errors… does that make any sense? I do have a relatively weak w-lan signal, but as soon as the gcode is uploaded, this shouldn’t be relevant, should it?
