search

bigtreetech / EBB

495 stars 106 forks source link

EBBCan error #124

Open wb4608328 opened 6 months ago

wb4608328 commented 6 months ago

MCU 'EBBCan' shutdown: Missed scheduling of next digital out event This is generally indicative of an intermittent communication failure between micro-controller and host.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

How to solve this

Pirat-1989 commented 5 months ago

I faced the same problem on the first layer of a complex part. I changed the firmware to a bitrate of 250000 and 500000, 1000000. And also removed the EBB from the printer's head to eliminate overheating. I use the U2C v2.1 and EBB 36 v1.2 kit. And also used ready-made firmware from the board repository.

orge70 commented 4 months ago

I have the same problem, but no solution

Townie-au commented 4 months ago

Anyone had any success with this issue. Also experience same issue.

orge70 commented 4 months ago

I changed my pi to rpi4, i read somewhere roi3 should be 32 bit or changed to rpi4, now i have no problem

Townie-au commented 4 months ago

I changed my pi to rpi4, i read somewhere roi3 should be 32 bit or changed to rpi4, now i have no problem

Do you mean you changed from a cb1 to a rpi4? What is roi3?

Townie-au commented 4 months ago

I tried changing the rt sample rate as specified in marks wiki but still no joy. klippy.log (16).txt

laborchet commented 3 months ago

Do you mean you changed from a cb1 to a rpi4? What is roi3?

I think they meant to type "rpi3"

i read the same forum thread he did, several people running rpi3 switched to the 32bit OS and solved their issue, or run a rpi4 and 64bit OS.

I am having this same issue, running a rpi3 with BTT kraken and EBB36, no u2c since the kraken has built in canbus, but im having this issue and lots of missed bytes in klippy log. going to try to switch to 32bit OS.