Basic Information: Printer Model: Sapphire Plus (modified) MCU / Printerboard: MKS Eagle (STM32F407VGT6) via UART3 klippy.log klippy.log (1.7 MB) “Timer too close” error happens randomly at the begining of the print. When print started following happes: Printer homes X and Y with endstops P…

I confirm solution. I print for 2 weeks every day 24/7, with “performance” CPU governour this error never happened again.

Hello @PKav ! You may have a look here: [image] Timer too close Knowledge Base Timer too close Background A “Timer too close” error occurs when the MCU is asked to schedule an action at a time that is already in the past. This typically results from delayed c…

Hello! I checked everything there. It’s definitely not a hardware issue, because this error occurs only when print starts, never in the middle of the print. And these erratic extruder motor movements before print stops seems to be software issue too.

[image] Rescheduled timer in the past Knowledge Base Background Whereas Time too close rather indicates an overloaded / jammed host, this error points to an overloaded MCU Reasons Too high step rate Potential solutions Check for approaching the limit: Ch…

I already tried 1/16 microstepping and nothing changed. Same error, same weird extruder behavior. It happens only at the begining of the print while printing skirt at 40 mm/s. It never happens later, even when printer does G0 at 180 mm/s According to the performance chart in fluidd, MCU load never…

[image] I’m not sure what is causing this but you seem to exceed your MCU bandwidth by a significant factor. For some details on such graphs see Advanced Trouble-Shooting / Graphing Klipper

According to this graph UART between MCU and Host is used up by 1000%, but how is it possible? It’s not USB, it’s UART at default 250000 baudrate? How can it go above 100%? And how can I do further diagnostics? Should I dump all data between MCU and Host?

To quote from the link posted above: Bandwidth denotes the saturation of the communication line between Host and MCU. Scaling is based on a 250000 baud serial line. This means 100% here, when using a much faster USB connection, is not necessarily an indication for problems (why the hell do we pu…

[image] Sineos: With a factor of 10, we could slowly come into the region of a problem (at least this is the first time I see such high values). I guess, this is valid for USB, because USB-emulated COM-ports do not have baudrate. But I’m using UART and default baudrate. Three 150mm long wires…

[image] PKav: I guess, this is valid for USB, because USB-emulated COM-ports do not have baudrate. But I’m using UART and default baudrate. Three 150mm long wires: RX, TX and GND. So it shouldn’t go above 100%. If you use a direct serial connection and not USB then the value is definitively a…

I increaced baudrate to 1000000, but issue happened again. Then I tried lowering microstepping rate to 4 for extruder motor. Issue happened again, but no error occurred, printer just keeps overextruding and weirdly moving extruder producing high noise. So it seems like “timer too close” error is j…

Random erratic extruder movements at the beginning of the print

General Discussion

EddyMI3D March 9, 2023, 4:04am 2

Hello @PKav !

You may have a look here:

Topic		Replies	Views
SV07plus, KlipperScreen & MCU 'mcu' shutdown: Rescheduled timer in the past General Discussion	23	1722	January 1, 2024
Timer too close, multiple fans General Discussion	22	659	October 10, 2024
"Timer too close", always at the same point in gcode General Discussion	27	959	May 29, 2024
MCU ‘sb2040’ shutdown: Timer too close General Discussion	47	1175	June 25, 2024
Failed print due to following error message: Transition to shutdown state: Previous MCU 'mcu' shutdown: Timer too close General Discussion	15	1877	July 2, 2023

Random erratic extruder movements at the beginning of the print

Related topics