-
Notifications
You must be signed in to change notification settings - Fork 29
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
Estimated print time off by a lot/seemingly random amounts #61
Comments
This issue has something to do with Klipper's Skew Correction feature. Commenting out my [skew_correction] section gives much more accurate estimates - off by a couple minutes instead of 10+ hours. Here is the estimate terminal output with skew_correction disabled:
|
Something about the post-process...um, process via PrusaSlicer is borked. The following gcodes were the same plate in PrusaSlicer exported twice. The 3.5 hour one was exported without doing anything special. The 1.5 hour one came about from the following procedure:
|
I have the same issue. I do not use skew correction, but I do use Prusa Slicer v2.7.4, on Fedora 39. The attached G-code is predicted in Prusa Slicer with a duration of 3:42. The actual print time was 3:03. |
Here is more evidence for this bug. I sliced a gcode, exported to my desktop without any post-processing, then ran klipper_estimator's estimate command via terminal two times in a row without changing anything. This is what my terminal output was:
Without changing anything, my estimated time changed by 10 hours. |
I updated to v3.7.2 from v3.4.0 to deal with the minimum_cruise_ratio change. I saw the same as @stevereno30: different estimates for the same input. I had similar results with v3.7.1, but v3.7.0 seems to be giving me consistent results (well, five times in a row for the same input). |
Hi @stevereno30, @fjpanag, and @b-fitzpatrick Sorry, I've been swamped lately and have not had a chance to look at this until now. I've just released version 3.7.3 which should fix this and #62. If you could test it out and report back, that would be a big help. Thanks in advance. Again sorry for the delay! Best regards, |
@dalegaard, I'm getting consistent and seemingly-reasonable results with v3.7.3. Thank you! |
No need to apologize. I can't be impatient when this is free software! My last print estimate, post-processed with 3.7.3, was off by <3 seconds compared to actual print time. Data point of one, but that seems about as perfect as it can be! |
For the past month, my klipper estimator has gone from being spot on to being terrible at estimating print times. In the following screenshot, the highlighted print job is when the issue started, but I have no idea what I changed between these two prints because there was a month between the two prints.
The top print in that screenshot is this gcode (zipped to keep below 25mb):
Bolt.zip
Running klipper-estimator with that same gcode gives this output:
If needed, this is my printer config:
printer.txt
The text was updated successfully, but these errors were encountered: