-
Notifications
You must be signed in to change notification settings - Fork 167
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
Practical tips about accelerations #11
Comments
Unfortunately it's not as simple as rules of thumb, it just varies a ton depending on components, build quality, design, etc. I'll mull over how to potentially word it a bit better. |
Ok, I thought that components and mechanics would affect the recommendation by input shaper, but the reduction for outer perimeters and the increase for infill and so on could be set based on recommendations. Then it's more involved than I thought, and I wonder how to find out how much I can improve where quality doesn't matter or reduce where quality matters. |
perhaps posting the pngs for your input shaper x and y would allow for comparisons to what others look like? also, THANK YOU for all the work you have done on the tuning guide and this profile |
In your profiles, is it possible that you could start using the percentages in the acceleration fields? And then we just input our shaper result as the default/standard? |
@LAP87 In my experience, across similar printers, the input shaper result is more of a ceiling than something that linearly scales all your accels. At least with how I personally handle accels (keep them low where you can see it, go nuts where you can't). I think scaling it with the max doesn't really align with that |
You write
but it's not so clear how much to reduce/increase over the IS suggestions.
You could add a line about your printer: "IS suggests 5000 k for my printer, so I picked xx% for external perimeters, yyy% for sparse infill and zzz% for travel (assuming the motors have enough current to allow it)".
I didn't check the ratios, I just threw there some placeholders.
The text was updated successfully, but these errors were encountered: