V0.10.0-122-gc179db3d - Timer too close

General Discussion
1

MCU ‘mcu’ shutdown: Timer too close

working Git version: ‘v0.10.0-107-g913d0992’
failing Git version: ‘v0.10.0-122-gc179db3d’

FLSUN QQ-S pro (delta kinematic)
Klipper host: 64bit x86_64 with 2 cores, AMD E-350 Processor, 2.8 GB
MCU mcu: MKS Robin Mini (FLSUN QQ-S Pro)
MCU Bluepill: Bluepill (PT100 Sensor)
Stepper driver: TMC2209, serial connection

Limits (timer too close) for simple moves:
v0.10.0-107: Klipper bails out at “G28; G0 Z10 F55000”
v0.10.0-122: Klipper bails out at “G28; G0 Z10 F120000”

Nevertheless, v0.10.0-122 fails doing a simple print (max. 80mm/s)
The identical gcode worked fine with v0.10.0-107.

Only workaround I found so far was to change microsteps from32 to 16 for all three axes.

klippy.zip (42.5 KB)

IMG_7394
IMG_73941920×2560 193 KB

IMG_7395
IMG_73951920×2560 219 KB

Last two prints show the markers where the failure occured.

1 Like
2

Did you ever find another solution to your problem?

I am having the exact same problem. It usually only happens halfway through my print though. The only thing that has worked for me is changing from 32 steps to 16 steps as well. Unfortunately, at 16 steps printing becomes very loud. I’m really hope there is some kind of fix for this.

3

No, not really. But I used hilbert curve for infill and layer fill. And I simply assume that the cumulative steps load because of PA and movement was too much for the Robin mini mb.