MCU `EBBCan' shutdown: Missed scheduling cd next digit out event

[Alofly]

Hi, I'm having a lot of trouble with my Voron 2.5 and the ERCF V2. I'm troubleshooting, but I don't know how to handle this error.

MCU `EBBCan' shutdown: Missed scheduling cd next digit
out event
This is generally indicative of an it oermittent
communication failure between nicro-controller and f
Once the underiying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the fimwan
reload the


Klipper


config, and restart the host sofcware.
Printer is shutdown


The printer is unable to complete a print. This error occurs after more than 12 hours of printing and stops randomly. I can't associate it with any process.



Any idea what might be going wrong?

Printer : bigtreetech/Manta-M8P and CB2
BTT EBB 36
Cartographer 3D
MMU bigtreetech V1.0


Thank you for your help

 

[shiftingtech]

Importing your V2.5 from the future is probably the issue. Should have stuck to printers that naturally exist in this place and time.

 

[Alofly]

Yes, I realized my mistake. But I was hoping to find some help rather than a sarcastic comment.

I've had to check the servo arm twice and the Filametrix blade once. If you're familiar with the ERCF, you'll know I've used kilograms of filament in many tests. I've encountered all sorts of problems. I've used four different extruders, three different encoders, three EBBs, two MMUs, changed the CB1 to a CB2 and hundreds of hours.

The time travel you're suggesting seems straightforward to me, actually.

 

[shiftingtech]

but seriously, "missed scheduling" can fall into some of the same troubleshooting paths as some other common canbus related errors. You should have a look at

Timer Too Close

A guide for setting up CANBus hardware on 3D printers

canbus.esoterical.online

and *possibly* even

Timeout During Homing/Probing

A guide for setting up CANBus hardware on 3D printers

canbus.esoterical.online

 

[Alofly]

Thank you very much for your response, I am trying some solutions from the links you mentioned. They seem more oriented towards the problems I have with the Trident. Since this one has the BTT PI V1.2 installed.

 

[Alofly]

Hello again. I found a connector between the EBB and the Cartographer that might be causing problems. Everything has been working like clockwork. But after several hours of printing without any incidents, I am getting this error. This is really frustrating.

Can not update MCU 'mcu' config as it is shutdown Once the underlying issue is corrected, use the "FIRMWARE_RESTART" command to reset the firmware, reload the config, and restart the host software. Error configuring printer​

 

[Alofly]

More tests. On this occasion, I have detected that the Blobifier servo has malfunctioned again, blocking the Host when activated. I have replaced the servo and installed a new 5-volt power supply for the CB2.

Result:
MCU `mcu 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 Klipper config, and restart the host software.
Printer is shutdown


I forgot to mention that by applying some ideas from the previous links, I have assigned the fourth core to Kipper and the first three to the rest of the processes. This has not caused any change in either of the two printers, neither the Trident nor the 2.4, which continue to give 'too many retries' during the bed leveling.
I'm running out of ideas. I'm thinking about replacing the MCU with a Manta M8P but a V2 this time...