MCU 'mcu' shutdown: Timer too close when homing

Basic Information:

Printer Model: Custom
MCU / Printerboard: Manta M8P
Host / SBC CB1
klippy.log
klippy.log (6.1 MB)

Describe your issue:

Hi. My printer just gets this error when performing g28 command and i dont understand why.

I have edited some .py files in order to fix a problem i have with horizon. Basically the idea is to set a dwell (G4) previous to homing z, and also, before performing the second home.

In order to do that, i have modified safe_z_home, adding a g4 previous to home z, and in homing.py, i have also added a g4 preivious to the second home, but i guess this is no the problem (i hope)

I atach them:
homing.zip (4.9 KB)

Latency/bandwidth issue.

Also, there are system load:

also, there are mysterious temperature_logger.py

BTW, this is not a good idea to modify files and add random code commands.

I will try to make the printer fail in that way and run the graphstats command in order to generate those graphs, maybe we can see something inusual.

Temperature_logger.py is not the problem as i have experienced this issue even not having It loaded in klippy extras, also, I wasn’t executing it in that moment.

In a first moment, i was very sure that the problem was a very big sample count value i had set in order to make the machine count a lot of samples before setting the endstop as triggered, but i guess this was making the mcu stay in a waiting mode, attending to this event, so other commands were being queued in the past. But after reverting these changes, i still have this problem, so i Guess i have some other process running in the machine causing this problem.