-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update SKR klipper configs to match newest Klipper recommendations. #281
Conversation
…et run_current = hold_current. Updated link to thermistor types.
@@ -162,7 +162,7 @@ homing_positive_dir: true | |||
## Make sure to update below for your relevant driver (2208 or 2209) | |||
[tmc2209 stepper_y] | |||
uart_pin: P1.9 | |||
interpolate: True | |||
interpolate: false | |||
run_current: 0.8 | |||
hold_current: 0.7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missed change on hold_current. Should be 0.8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the catch. Fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why should I turn off interpolate? I can't see the benefits of turning off interpolate. Enabling interpolation can often be quieter and achieve more accurate step movement.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jack9603301 Please take a look at this pull request. It goes deeply in to details. Klipper3d/klipper#4977
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doesn't that recommend 64 microsteps, or even 128 due to noise? 32 seem low.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't done any testing of microstep values greater than 64, and I haven't tested 64 microsteps on a Pi zero to verify it doesn't overload the system. That's why I chose 32 bit values to just play it safe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have done so far ~40 hours of printing since the change. 32 was on the bit louder side and those noises were really odd. So I went from 32 to 64 microsteps and the latter is stable and quiet(close to what it was with interpolate:true if not even better). Zero handled interpolation just fine, so it might be no issue. Though if someone could verify the load would be great.
remove hold_current values, as hold_current defaults to run_current.
@@ -316,7 +317,7 @@ pid_kd = 131.721 | |||
uart_pin: P1.9 | |||
interpolate: false | |||
run_current: 0.5 | |||
hold_current: 0.4 | |||
hold_current: 0.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think Klipper now recommends that you don't even define hold current
Duplicate PR. Closing. |
Relevant Klipper pull request here: Klipper3d/klipper#4977