search

Frix-x / klippain-shaketune

Klipper streamlined input shaper workflow and calibration tools
GNU General Public License v3.0
696 stars 87 forks source link

Timer too close when running any Shake and tune test #122

Closed flavi0gritti closed 5 months ago

flavi0gritti commented 5 months ago

K-Shake&Tune module branch

Version

v4.0.0-1-g8b0862a9

Describe the bug and expected behavior

After updating to Shake and tune 4.0 this evening I can no longer run any of the test as I am constantly getting "timer too close" errors. I have been running the same tests this morning on the same exact machine, no hardware changes, on version 3.0 I wasn't getting any crashes at all. SCR-20240615-lpa

Additional information and klippy.log

klippy (1).log

jhorn70 commented 5 months ago

I am getting this result as well on every test I run with 4.0

godbnc commented 5 months ago

Ia global problem i think is can broken:))) cable or btt pi

Jbori347 commented 5 months ago

I've got the same problem. I'm able to view results of tests in the folders but have to restart klipper after every test

Frix-x commented 5 months ago

I'm aware of this issue. It's not solved at the moment but shouldn't be very problematic as the graphs are done in background and should be generated correctly. So in the meantime, if the issue happens during the second axis (Y) measurement during the AXES_SHAPER_CALIBRATION macro, then just do only X, restart klipper and do Y to get both of the graphs generated.

I'm working on solving this. But the common point for people having this issue is running either a low powered pi clone like a BTT CB1 or a lot of things like CANbus, high precision stepper control, etc...

Frix-x commented 5 months ago

I'll close this issue in favor of #120 that is the same