What type of wire are you using for CAN?
Can you show an example of what your are talking about?
The Mellow-Fly SB2040 came complete with a cable. That's what I'm using. I'm guessing the data wires are about 24 awg. I twisted the data wires, but maybe not as well as I should have.
My CAN adapter is a Mellow-Fly UTOC-3. Some communication readings below:
pi@fluiddpi:~ $ ip -details -s link show can0
3: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1024
link/can promiscuity 0 minmtu 0 maxmtu 0
can state ERROR-ACTIVE restart-ms 0
bitrate 1000000 sample-point 0.750
tq 62 prop-seg 5 phase-seg1 6 phase-seg2 4 sjw 1
gs_usb: tseg1 1..16 tseg2 1..8 sjw 1..4 brp 1..1024 brp-inc 1
re-started bus-errors arbit-lost error-warn error-pass bus-off
0 0 0 3 26 0 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
RX: bytes packets errors dropped overrun mcast
2166927 322369 0 0 0 0
TX: bytes packets errors dropped carrier collsns
3049571 406515 0 0 0 0
The trend shown above looks much better than it did a few days ago. I'm now thinking the erratic readings that I was seeing before today were related to nozzle clogging. I made some changes to address the clogging issue and that seemed to improve hotend stability. What I see today is very comparable to what I saw when the hotend was being controlled by the BTT Octopus.