MCU "shutdown: Timer too close"

[lunar tapir]

Hello, I have a problem with MCU "shutdown: Timer too close"

Once the Normal MCU and once the Can MCU

I've already tried a Pi because it runs normally on a FUJITSU Thin Client FUTRO S740 with Ubuntu 22.04.3 LTS

Can Rate is 1000000

Completely uninstalled Crowsnest for testing on Ubuntu and closed the camera without success

I didn't have a cam connected to the Pi, just USB from the Octopus and the u2c

The whole thing happens when printing (color change with TradRack) sometimes after 20 minutes and sometimes only after 50 minutes

An Octopus F407 is installed
U2C -> EBB36

All Klipper Version: v0.12.0-40-g77619e91

Do you have any other ideas where I could look?

I had a print run yesterday where there were 10 color changes after about 3 hours... it ran through 6 hours without any problems

[jagged sand]

do you print every time the same gcode? can you please upload this gcode? i just see a lot of "SET_VELOCITY_LIMIT" before the "timer too close" error. this can also be the issue, if you set different velocity/acc values without any move between it

[lunar tapir]

I always just moved the wipetower...

But today I made a print without color change in 3 hours without any problems

Tried again today and here's a video about it shortly before it was canceled

[jagged sand]

is this the gcode which has issues?

[jagged sand]

to be honest. the values in this list alone are not really "useful". you can only calculate something with it...

[jagged sand]

ok. i uploaded your log here: https://sineos.github.io/ and it looks like bandwith issues. can you doubecheck your can speed?

[jagged sand]

first interesting thing is the different slicer

[magic shale]

sorry wrong chat

[lunar tapir]

yes

[lunar tapir]

its 1000000 by both