Fix to the absurdly low max_z_accel #136
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I have been helping a few people with their printers and keep finding issues relating to this config. The max_z_accel set here is absurdly low, and is so slow that it causes blobs for whenever a layer change is requested by gcode. I have updated it with a more appropriate acceleration, that should be suitable for a leadscrew based z axis. Although it's good practise for people to completely customise their own configurations, not everyone is as experienced as others, and small little settings like these can cause extra unneccesary confusion and troubleshooting.
Author
|
Comment: Supposedly Klipper's default is 100, however 400 should be fine. Still improved over the initial setting regardless. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have been helping a few people with their printers and keep finding issues relating to this config. The max_z_accel set here is absurdly low, and is so slow that it causes blobs for whenever a layer change is requested by gcode. I have updated it with a more appropriate acceleration, that should be suitable for a leadscrew based z axis. Although it's good practise for people to completely customise their own configurations, not everyone is as experienced as others, and small little settings like these can cause extra unneccesary confusion and troubleshooting.