Basic Information:
Printer Model: Highly customized Anycubic Chiron
MCU / Printerboard: BTT Manta M8P v2(mcu), BTT EBB42 v1.2 (EBB_X, EBB_Y, EBB_E)
Host / SBC: BTT CB2
klippy.log (9.9 MB)
The printer is a testbed printer. The hardware and config changes frequently, but the CAN network failures have persisted in every configuration since installing the M8P/CB2. I am using the M8P as the CAN adapter and do not have a separate CAN board.
The CAN network will randomly fail. I get a connection failure from one of the devices on the CAN, usually the standard timeout failure. The error will usually come from the main “mcu” MCU not the “EBB_X”, “EBB_Y”, or “EBB_E” device, although it can come from any of them. The error has also occurred when there were no EBB42 boards connected and the only MCU was the M8P itself. No matter which MCU generateds the initial error, when the firmware is restated I get a connection error on the “mcu” MCU. As this MCU is physically on the same board as the CAN adapter this should be impossible. The problem can only be corrected by a power cycle. None of the reboot options correct this error. When there is a physical connection issue on the CAN network, reconnecting the device and performing a firmware restart will correct the error.
…