In my build Im having increasing invalid bytes on the Can bus communication with EBB36 V1.2. They increase about 50 to 100 bytes every 5 minutes even when the printer is ideling. When I crank the printing faster it gets even worst to the point Im getting the print stopped due to the Can Bus Timing problem.
My Pi is set to run 1M Can bus speed with TransmitQueueLength=1024
I'm using BTT U2C V2.1 , EBB36 firmware is flashed to 1M speed and BTTOctopus firmware also set to 1M speed.
As the Can Bus Cable to the head I'm using quality Igus Chainflex cable that is screwed to the U2C in one end and soldered straight to the EBB36 in the other end just to mske sure there is no way in hell there are bad crimps.
The printer sometimes can print for hours but eventually always crashes.
I believe that the timing problem is related to the invalid byte count increasing but I'm not 100% sure
I'm out of ideas,
I have also set new Klipper Host On Pi from the scratch and reflashes multiple times all the firmware everywhere.
My Pi is set to run 1M Can bus speed with TransmitQueueLength=1024
I'm using BTT U2C V2.1 , EBB36 firmware is flashed to 1M speed and BTTOctopus firmware also set to 1M speed.
As the Can Bus Cable to the head I'm using quality Igus Chainflex cable that is screwed to the U2C in one end and soldered straight to the EBB36 in the other end just to mske sure there is no way in hell there are bad crimps.
The printer sometimes can print for hours but eventually always crashes.
I believe that the timing problem is related to the invalid byte count increasing but I'm not 100% sure
I'm out of ideas,
I have also set new Klipper Host On Pi from the scratch and reflashes multiple times all the firmware everywhere.
Last edited:
