Invalid bytes On the Can Bus, What is the count on your invalid bytes in the Klippy Log?

[RevWizard]

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.

 

[PV_Mike]

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.

I am having similar issues, different Klipper shutdowns since conversion to can (Rpi3+, BTT-U2Cv2.1, Rp2040/2209 toolhead), after conversion things went fine for seveveral prints (5h+ a print).
I print mostly ABS. With PETG i get additional shutdowns related to extruder timeouts.
According to Klippers‘ trouble shooting this is related to an issue with linux kernel lower than v6.6 (mine is below)
The PETG issue is appsrently solved by adding ground to the pancake and the axles of the extruder gears. They report / I understood that „ems“-sparks accumulating in the filament are causing the can-bus issues.
However, I have since the conversion huge problems w/ different klipper-shutdowns, coming arbitrarly… once during QGL, others after 2h in mid print

 

[RevWizard]

After trying everything I have installed a 32 bit system on my Pi 3 and using Kiauhu I have installed Klipper, Moonraker , Mainsail, Klipper Screen. After installing everything on 32 bit system after hours of printing I don’t even get one retransmit and printer prints like a champ!
previously o have installed countless new 64 bit systems and with that had major Can bus retransmit error and printer shut downs.
I’m not sure what’s up but my Pi did not line 64 bit system
That’s all. Sounds crazy but mu stuff works spotless now