# Shutdown: Timer too close when running TEST\_RESONANCES/SHAPER\_CALIBRATE **URL:** \ **Category:** General Discussion\ **Created:** [June 8, 2022, 8:15am UTC](https://klipper.discourse.group/t/shutdown-timer-too-close-when-running-test-resonances-shaper-calibrate/3099 "2022-06-08T08:15:29Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Strolch](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Strolch](https://klipper.discourse.group/u/Strolch)\ **Post date:** [June 8, 2022, 8:15am UTC](https://klipper.discourse.group/t/shutdown-timer-too-close-when-running-test-resonances-shaper-calibrate/3099/1 "2022-06-08T08:15:30Z")
I get the infamous error “Timer too close” when running TEST\_RESONANCES or SHAPER\_CALIBRATE. Environment: - Delta Kinematic - Stepper settings: ```auto [stepper_?] step_pulse_duration: 0.000000190 rotation_distance: 32 microsteps: 16 full_steps_per_rotation: 400 homing_speed: 120 ``` - Klipper host: ```auto Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz 64bit x86_64 with 8 cores ``` The error occures at approx. 70Hz. Here’s the sar output when the error occures ```auto 17:10:37 CPU %user %nice %system %iowait %steal %idle 17:10:38 all 0,87 0,00 0,50 0,00 0,00 98,63 17:10:39 all 0,88 0,00 0,38 0,00 0,00 98,74 17:10:40 all 0,75 0,00 0,63 0,00 0,00 98,62 17:10:41 all 1,00 0,00 0,38 0,00 0,00 98,62 17:10:42 all 0,88 0,00 0,63 0,00 0,00 98,50 ``` I only got a working shaper by decreasing the µStep to 8… ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [June 8, 2022, 8:47am UTC](https://klipper.discourse.group/t/shutdown-timer-too-close-when-running-test-resonances-shaper-calibrate/3099/2 "2022-06-08T08:47:48Z")
Due to the special Delta kinematic the MCU needs to create a lot more steps than for a Cartesian one. Looks like your board cannot create enough steps without lagging behind. Post a klippy.log showing the issue. ---
**Author:** ![Strolch](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Strolch](https://klipper.discourse.group/u/Strolch)\ **Post date:** [June 8, 2022, 10:13am UTC](https://klipper.discourse.group/t/shutdown-timer-too-close-when-running-test-resonances-shaper-calibrate/3099/3 "2022-06-08T10:13:29Z")
> [@Sineos](#): > > Looks like your board cannot create enough steps without lagging behind. Last year (july) I successfully run those tests with 1.8° Stepper and 32µSteps with the same hardware (Printer & MCU). I also tried with and without STEP\_ON\_BOTH\_EDGES. With “off” the shutdown should occure much earlier because of doubling the MCU load. But - interestingly enough - the error was in the same frequency range. [klippy.zip](https://klipper.discourse.group/uploads/short-url/qqTd6jR2nn3MVqSRXbjuvcx4SBZ.zip) (27.9 KB) ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [June 8, 2022, 4:23pm UTC](https://klipper.discourse.group/t/shutdown-timer-too-close-when-running-test-resonances-shaper-calibrate/3099/4 "2022-06-08T16:23:01Z")
Can you post a full unmodified log? > [@Strolch](#): > > Last year (july) I successfully run those tests with 1.8° Stepper and 32µSteps with the same hardware (Printer & MCU). Just spitballing, but I think the acceleration changed from 7k to 10k during the test but I’m not sure if that would explain what you are seeing. ---
**Author:** ![Strolch](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Strolch](https://klipper.discourse.group/u/Strolch)\ **Post date:** [June 8, 2022, 6:43pm UTC](https://klipper.discourse.group/t/shutdown-timer-too-close-when-running-test-resonances-shaper-calibrate/3099/5 "2022-06-08T18:43:43Z")
No, because I get also failures when testing Y axes - and here it fails already at ~70Hz. Attached yesterdays and todays log. Today I had to go down to 4uszep to run a successfull calibrate. [klipper\_all.zip](https://klipper.discourse.group/uploads/short-url/4PGNgHh8Pe8BkpczAIXwTTSzvuY.zip) (3.4 MB) ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [June 8, 2022, 7:02pm UTC](https://klipper.discourse.group/t/shutdown-timer-too-close-when-running-test-resonances-shaper-calibrate/3099/6 "2022-06-08T19:02:44Z")
> [@Strolch](#): > > Last year (july) I successfully run those tests with 1.8° Stepper and 32µSteps with the same hardware (Printer & MCU). Now you apparently upgraded to 0.9 steppers. I’m by no means a Delta expert, but to my knowledge it needs all 3 axes to either move in X or Y direction. With doubling the steps on one axes, this means 6-folding it, when all 3 axes are used, right? ---
**Author:** ![Strolch](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Strolch](https://klipper.discourse.group/u/Strolch)\ **Post date:** [June 8, 2022, 8:07pm UTC](https://klipper.discourse.group/t/shutdown-timer-too-close-when-running-test-resonances-shaper-calibrate/3099/7 "2022-06-08T20:07:49Z")
Yes, but I also reduced the uSteps to the half - compared to last year. So 0.9 \* 16uSteps compared to 1.8\*32 uSteps. That’s no difference in steps/rotation. Addendum: last year I used a 2-core, 1.6GHz host. Now I used a 8-core with 3.5GHz each. And - according to the doc - Timer too close means the _host_ can’t handle the load… ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [June 8, 2022, 8:25pm UTC](https://klipper.discourse.group/t/shutdown-timer-too-close-when-running-test-resonances-shaper-calibrate/3099/8 "2022-06-08T20:25:26Z")
My understanding is that you still have a factor of 3: 3 steppers x 2 (.9 stepper) / 0.5 (uSteps) = 3 > [@Strolch](#): > > Addendum: last year I used a 2-core, 1.6GHz host. Now I used a 8-core with 3.5GHz each. > And - according to the doc - Timer too close means the _host_ can’t handle the load… Virtualized? ---
**Author:** ![Strolch](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Strolch](https://klipper.discourse.group/u/Strolch)\ **Post date:** [June 8, 2022, 9:05pm UTC](https://klipper.discourse.group/t/shutdown-timer-too-close-when-running-test-resonances-shaper-calibrate/3099/9 "2022-06-08T21:05:00Z")
No - plain hardware. And no - steps/rotation is the same on each axis. So the sum is the same… ---
**Author:** ![Strolch](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Strolch](https://klipper.discourse.group/u/Strolch)\ **Post date:** [June 22, 2022, 9:16am UTC](https://klipper.discourse.group/t/shutdown-timer-too-close-when-running-test-resonances-shaper-calibrate/3099/10 "2022-06-22T09:16:12Z")
So, finally it showed that the mcu (MKS Robin Mini) was simply too weak. Switched over to a Supernova board - now it runs fine with 128µSteps… ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [March 8, 2026, 1:29pm UTC](https://klipper.discourse.group/t/shutdown-timer-too-close-when-running-test-resonances-shaper-calibrate/3099/11 "2026-03-08T13:29:00Z")