Timer Too Close error after M600 pause in recent Klipper builds

General Discussion
15

If you can reliably reproduce an issue, it should be possible to track it down. It’s a little time consuming, but generally possible.

The steps are:

  1. Make sure you’re running the unmodified code. (Placing code into the klippy/extras/ directory is a code modification.)
  2. Reproduce the issue on the latest upstream code.
  3. Find a recent version of the upstream code that does not show the issue.
  4. Use git bisect to track down which commit first introduced the regression - Klipper Versioning, Downgrading, and Bisecting .

Once the individual commit that caused the change in behavior has been identified then it’s often possible to figure out why there is a change in behavior.

-Kevin