-
-
Notifications
You must be signed in to change notification settings - Fork 5.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
[Klipper] [Documentation Request] Acceleration Calibration #3592
Comments
Hi @Brokengeiger, It did not look like there was a Klipper log file attached to this ticket. The log file has been engineered to answer common questions the Klipper developers have about the software and its environment (software version, hardware type, configuration, event timing, and hundreds of other questions). Unfortunately, too many people have opened tickets without providing the log. That consumes developer time; time that would be better spent enhancing the software. If this ticket references an event that has occurred while running the software then the Klipper log must be attached to this ticket. Otherwise, this ticket will be automatically closed in a few days. For information on obtaining the Klipper log file see: https://github.com/KevinOConnor/klipper/blob/master/docs/Contact.md The log can still be attached to this ticket - just add a comment and attach the log to that comment. Best regards, PS: I'm just an automated script, not a human being. |
It seems like you might be confusing velocity and acceleration. I typically print at 60-80mm/s velocity with 200mm/s non-print moves, and my acceleration is 4000mm/s^2. All I did to tune acceleration was turn it up until I started missing steps at 5000, then I dropped it to 4000 to be safe. None of the tuning for speed or acceleration is specific to Klipper unless you're using input shaping (which is well documented), and it's mostly subjective with regard to acceptable print quality. |
Max printable speed is often limited by how much plastic your hot-end can melt. Then you either configure it in your slicer, e.g. slic3r/prusaslicer/superslicer has it as a filament property (This is correct as some plastics need more energy to melt), or you basically manage your maximum feedrate yourself. If there is a lot of headroom left, I would recommend to tune input shaping, as it will get rid of a few artifacts, and allow you to get better prints at higher velocities (even with a wobbly printer). |
This article you just provided me, looks like this is nearly exactly what I might need. There is a few topics in there about jerk too, but was hoping for associations to how this all works with pressure advance to help tie it all together. But for now I think this page will do. |
Yes, it was a very good resource for me when I was on Marlin. for Klipper you'd probably want to:
The resonance compensation is something unique to Klipper and it's truly amazing what it can do. Unfortunately for me, my Printer's frame is just not made of high-enough quality parts, but I can now get very good prints at 80mm/s. The limiting factor for me is the melt flow rate of about 8.5mm²/s. So I can only do 60mm/s at 0.28mm layer height or start suffering under extrusion. |
Great list! Thank you kindly. I know I've done only some of these, but I'll parse over them all again. I've love to move safely from 30 to 80! |
Maybe to add an experience I have made when moving from Marlin to Klipper: |
Yeah it was night and day for me (marlin to klipper) - that's where I was thinking Klipper might need it's own specific set of instruction. But tonight when I get to that list above - I might know better. |
@Sineos you could probably compare the print times between Marlin and Klipper in those scenarios and judge from there. |
Last night I only got one test out of the way. I didn't have square_corner_velocity set in my config so it was taking defaults. I still have a few tweaks to do as the very next print, slightly more complex, no brim was a total mess at 60, prolly would have been fine at 60 with a brim though.
|
@dmbutyugin I did. Klipper is always faster using the same setting for accel, speed etc. @Brokengeiger
With the issues you are describing, I would first and foremost check the mechanical aspects of the printer:
Of course you can tune down accel and speed (btw. accel is more important in cutting down print times than speed) but it will only mask the symptoms but not cure the root cause. Also as @grigi mentioned, the resonance compensation is amazing. Again, in my humble opinion, this is top end tuning and makes no sense if the foundation is lacking. |
It appears the Klipper log file was not provided. |
No, I don't think this ticket should be closed. It's a standing request (and discussion) for what would be required for a comprehensive calibration manual for Klipper. |
It's fine (and appreciated) if you wish to add documentation to Klipper. A PR is probably the best way to discuss that (for example, see #3158), but a github issue ticket is also fine as long as someone is actively working on it. This particular ticket made reference to an event with the software ("I'm stuck printing at 30mm/s") but did not include the log. From my perspective, this ticket is invalid. If you would like to contribute I suggest opening a separate ticket/PR. Thanks, |
As a new user of Klipper I found many of the documentations and external documentations fairly well documented. I managed to my old RigidBot 1 upgrade (now essentially a reliabuild 3) onto klipper in 1 night with another day of calibration. However one aspect seems amiss - I'm stuck printing at 30mm/s. While I've run into some decent documentations out there for various systems, mostly marlin. It seems this topic has a vast enough difference on Klipper to warrant some critical choice words for acceleration and speed - especially with pressure advance properly configured and still feels like my prints are high quality at 30, A-OK at 40 but full on failure at 60.
Would love to be cool like my friends.
Klipper seems to have a more down to earth explanation and approach that appeals to my frame of thought that may help as a walkthrough of step by step.
Forgive me if this is intermixed with another topic that I missed - perhaps it can stand alone for itself?
The text was updated successfully, but these errors were encountered: