“canbusload can0@1000000 -b -t” never reported +15% can bus usage
Describe your issue:
I have been dealing with this issue where klipper randomly shuts down in the middle of a print, can be printing for 6h all fine or shut down at 10 minutes.
Once it stops with the error message from the title klipper will fail to start with the message “mcu ‘can0’: Unable to connect Once the underlying issue is corrected” until I power cycle the printer, restart the PI or disconnect and reconnect the usb cable from the U2C
I’m totally lost as I have tried everything that I was able to find, thanks in advance for any help and please note that even If I’m not new to 3d printing this is my first time using a can bus.
What I have already tried with no results:
Increasing txqueuelen up to 2048 (128 → 512 → 1024 → 2048), I reverted this to 128 because it did not seem to help
New can cables
Re flashing EBB42 & U2C with the images available on BTT github
Re flashing U2C with the current version of candlelight
Re flashing U2C with the fork of candlelight that BTT has
I have not done any hardware/software changes since the post was made but I have printed a few things and seems like the error is still a random thing because I started a 5 hour print that failed with the error from the title at 2 hours so I cleaned the bed and sent the job back to the printer and it finished without errors.
The ifconfig I have added in the first post is from the same time that the log, just after the print failed.
Today I have been printing all day with that same ifconfig and by the moment the error has not appeared so I’m a bit concerned by the randomness of it as I can not find a way to force the error.
Do you provide enough current to the EBB?
Meaning are the cables for V+ and GND thick enough?
Depending on the used hotend and other attached components the used wires might be too thin for higher loads.
Otherwise did you check for bad soldering on the EBB?
Sorry for the late reply to everyone, I have been bussy for the past few weeks.
As an Update regarding this I have been printing and monitoring a few prints today and I have some data that can be useful but the possible fixes are out of my knowledge
This is the best dump that I was able to get:
Printer shuts down (seems like the error is different now)
21:40:25
Klipper state: Shutdown
21:40:42
Lost communication with MCU 'can0'
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
21:40:43
Lost communication with MCU 'can0