I'm using Klipper with an older 8-Bit MKS Gen L board. All of the prints I've sliced have printed fine so far.
But when trying to run the G-Code provided by the web tool I've been sporadically running into this error.
It's not consistent and triggers at different points in the file.
From my reading it's generally from when the step rate being streamed to the board from the PI is higher than the MCU can handle at that given time.
Since most of my prints seem to run fine I'm wondering if it has to do with the fact that the G-Code is moving the Z-Axis and extruder at the same time?
I've had 1 successful test in about 10 tries. Thought I'd mention it to see if there's any option you could think of to include that would possibly limit things to no trigger this issue on my older board.
MCU 'mcu' shutdown: Rescheduled timer in the past
This generally occurs when the micro-controller has been
requested to step at a rate higher than it is capable of
obtaining.
I'm using Klipper with an older 8-Bit MKS Gen L board. All of the prints I've sliced have printed fine so far.
But when trying to run the G-Code provided by the web tool I've been sporadically running into this error.
It's not consistent and triggers at different points in the file.
From my reading it's generally from when the step rate being streamed to the board from the PI is higher than the MCU can handle at that given time.
Since most of my prints seem to run fine I'm wondering if it has to do with the fact that the G-Code is moving the Z-Axis and extruder at the same time?
I've had 1 successful test in about 10 tries. Thought I'd mention it to see if there's any option you could think of to include that would possibly limit things to no trigger this issue on my older board.