lost communnication with MCU 'toolboard_t0'
during long printing i often come across this problem, 1 or 2 days after the start of the print having to throw away everything...
i thought this may happen because of a loose usb-c connection, however i have zip tied it pretty well
19 Replies
does anyone have any idea on how i should reliably trouble shoot this?
thank you in advance
you need to capture the log right after it happens and before restarting. The klippy.log you uploaded is useless as it doesn't have the error
okay, i'll try starting another print then, any other suggestions?
Have you double checked all of your custom crimps and made sure all of the connections are tight inside the electronics enclosure? I had a loose ground connection on the PS and I was getting all kinds of different random errors. I would start by wiggling all of the crimped connections on the toolhead and see if you can reproduce the error manually. Pay special attention to the red and black in the large white connector in upper right of EBB. That is power for the EBB. If you see the lights go out on the board when you wiggle, that is your issue for sure.
Here i am, with the error repeated after 2 days of straight printing...
tried to recreate the error manually and ointentionally but couldn't, any help would be appreciated, thank you
same thing, this log is from after a restart and doesn't have the error in it
=============== Log rollover at Thu Jan 2 00:00:00 2025 ===============
The error just occurred, I downloaded it just after the notification came… what should I do?
there should be more klipper logs, grab one of the older ones
Ok, I’ll check in a minute
i'll send the zipped file
this should be the error isn't it?
@blacksmithforlife 🇺🇸 other than this i wouldn't really know what to do
I also see this in the debug zip
Write g-code response Traceback (most recent call last): File "/home/pi/klipper/klippy/gcode.py", line 459, in _respond_raw os.write(self.fd, (msg+"\n").encode()) BlockingIOError: [Errno 11] Resource temporarily unavailablehow old is your SD card?
not sure, it should be new, but may be i've used an old one
could it be just overheating or should i just copy it on a new one to not loose any data and see if that solves the problem?
i first tried to disk copy, still had corrupted data... so i formatted that second sd card, started the first print and now i'm still getting the same error, any thoughts o. what this could be?
just noticed that this has today's logs and the error occoured yesterday